-
Notifications
You must be signed in to change notification settings - Fork 680
BlockchainDouble seems to be using the wrong Trie import #664
Comments
I think this is due to the fact that we pre-seed accounts with ether on start up, and Secure trie makes things incompatible. Though I'm not entirely positive, and if that is true, I wonder if there is a simple way around it. Have you tried swapping the Trie out for the SecureTrie then running the ganache-core tests? I'm curious if the |
Adding this to the 3.0 milestone release. |
@kfichter I haven't yet researched the getProof myself, if you'd like to try adding eth_getProof in the |
fixed in ganache@3.0.0-internal.0 |
@davidmurdoch I'd definitely be happy to tackle |
@kfichter I still haven't implemented it in the and tests would go here: https://github.com/trufflesuite/ganache-core/tree/next/src/chains/ethereum/tests/api/eth (you'd name the file To set up the repo, check out the Let me know if you need any help! |
Related issue: #382 |
Noticed this while trying to implement
eth_getProof
on top of ganache. It seems likeBlockchainDouble
is importingTrie
as:https://github.com/trufflesuite/ganache-core/blob/1177fe8a2711066a1b082b15d22585158001e80d/lib/blockchain_double.js#L9
When I'd expect to see:
The base
Trie
class (instead of the "secure"Trie
) spits out invalid proofs because the keys aren't hashed before insertion.You can see this discrepancy within
ethereumjs-vm
, which indeed uses the "secure" version here. Although using the base class is technically fine, it does produce a non-standard (and incompatible) result foreth_getProof
.The text was updated successfully, but these errors were encountered: