You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In madara, we only use tree identifiers for the contract storage. The other contract and class tries, as well as the ephemeral in-memory (hashmapdb) tries needed to compute transaction, receipt and event commitments in a block.
We do that because we have hit a case where when just giving the empty slice as identifier, the state root ends up mismatching during sync. We did not investigate what was going on, but some of the code of the crate probably works under the assumption of the identifier always being 16 bytes or at least non empty
I'd be cool if the bonsai-trie supported arbitrary trie identifiers
The text was updated successfully, but these errors were encountered:
In madara, we only use tree identifiers for the contract storage. The other contract and class tries, as well as the ephemeral in-memory (hashmapdb) tries needed to compute transaction, receipt and event commitments in a block.
Currently, we use a junk identifier for storing these trees inside a BonsaiStorage, like this https://github.com/madara-alliance/madara/blob/8ece8dd21c957e5cad13ce9ee891483b77322387/crates/client/block_import/src/pre_validate.rs#L308
We do that because we have hit a case where when just giving the empty slice as identifier, the state root ends up mismatching during sync. We did not investigate what was going on, but some of the code of the crate probably works under the assumption of the identifier always being 16 bytes or at least non empty
I'd be cool if the bonsai-trie supported arbitrary trie identifiers
The text was updated successfully, but these errors were encountered: