Pierre Krieger
Pierre Krieger
Yes, go for it! I don't think we need to maintain backwards compatibility in smoldot, you can just overwrite `/paritytech/grandpa` with the replacement name. You should be able to test...
cc https://github.com/paritytech/substrate/issues/10969 (I've coincidentally just noticed that when debugging some parachains stuff)
https://github.com/paritytech/substrate/pull/11938 also now changed other protocol names. (see also https://github.com/paritytech/polkadot/pull/5849, but it only changes protocols not implemented in smoldot at the moment)
https://github.com/paritytech/substrate/pull/12545
This is unfixable before Beefy is shipped.
Recent block numbers _are_ supported, but this is completely useless because there's no future-proof way to define "recent".
Ah right, we used to look in the cache of recent blocks, but I intentionally removed that hastily after realizing that the cache of recent blocks could contain non-canonical blocks...
Seems to have been fixed a while ago in https://github.com/paritytech/smoldot/pull/820, but needs a test.
Thanks to https://github.com/paritytech/smoldot/pull/1773 we can now be sure that adding the runtime to the database will not make it exceed the maximum allowed size for local storage.
> querying the hash of the runtime code from the network, instead of the value This is the major remaining item in this issue.