-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Conversation
Yes, looks like some bad merge brought it back. |
Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. |
not stale. |
Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. |
not stale |
Opened w3f/PPPs#5 I've added a |
Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. |
Switched to "In Progress", as I will also integrate proposed changes from w3f/PPPs#5 (prefix range query, restart and possibly ordering of keys). |
Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. |
Will open a new one with things for w3f/PPPs#5 |
This PR adds light client call as describe in #10623 .
I only diverge from proposed spec at w3f/polkadot-spec#590 by renaming
required bytes hash = 1;
in child trie description torequired bytes name = 1;
: so it is the same as the formerstorage_key
but without prefixing.Using child trie root hash sounds like a good idea but is not consistent with specifying a block number in the request.
When writing it I also did wonder if we should allow doing the query on multiple child trie (would be a bit of change in the format but pretty ok).
I also did remove the storage cache from the source (should have been removed already I think).