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
I am working on updating verkle-tree-visualizer for blockscout explorer (https://github.com/blockscout/blockscout-verkle-tree), which is heavily based on the current repository. The problem I've met now is verification fails when trying to verify data from Condrieu testnet. It seems it worked at the end of August, but it does not work now.
In the search for a solution, I've tried to run the binary on the data obtained from Condrieu testnet on the current project. For that, I've downloaded block number 367492 and explicitly provided storage root of the previous block (367491) which is 15452534ee17148b5a69afb11dafa1c540b6efa18ed0545656df2e9def5a1ce7. Unfortunately, it panicked with the following message:
f905fdf905f8a004e3252a0f4f6bba4bfc3613f48e81e0e843336468ceb3cab5c52cd9b9d6e751a01dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d4934794f97e180c050e5ab072211ad2c213eb5aee4df134a071515ed239e2cc61b87f36b85171e0feb2b0c60c64aeb12e6e864340d3fe088fa056e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421a056e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421b901000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000083066af283059b848401c9c3808084639b9cc699d883010a15846765746888676f312e31382e36856c696e7578a043a71673dd255ec9504411c29c89ca9093f2110d31fad187777d95e0ff397cb48846f07a050ef572e907b902cd00000000010000001a0400000046fc4065b024c027d541c02c382fdbbdd024cdb84ab88408f0a9ccb950a6a2ea0238746d580a1022ca9acf8295f5933bdabeef9450dc3f06c1fb0a6f66b97b4a6f26bd340f37b09d9dd28c91c3876fa3aa25186497c85c229031455857f98abc32b9ac7c4012154f7a4bd7c810fa3c67e6be141d3330124a6dd5dbb8810f6d3c64eff9a00ca7e682353e1ba8ab024a93bf62cce77a732c6dca45155e412937572894d9b83118ee648909ac83d7318ded5b8ccebffa770a8cb1d895bf8010dc7022bb27e49872fac517bd1b18d665c452fc51995862cf7d9fd0abbaeceacc6ead6354da48440def2a88e02847ee47502fca12db208b9eade5229a00e944943d5a6a7dfc0d9d5b5f0621a0efecf91d3418bb2574284b8205fc6456eca4150953b4286869d4498af7a8e89790e68818385c0d7dbcd0f5d0590b95af12aeb0ac46174c476c70f551512fc31501c9f34c49001e4a787528b7f105c95eb6e7f34b6af36219095b433e90a68579cca76927d7c64f96acb2650990cef6b2d88f1b581a825431701827683ed859fe6238d00a40b7c9c85eafe4a37ec599dee3b8a3d3f4d55ac2aaf0862a450282ff69838583128596e7d3f9079a88c2570bb822032bbffb1bc5c399cec47bc30e498c9b5d9ac38ec70f7d7c713ae98c979147fe866d925c1b02b3fe6a6a48bcb1170a29e95ad7283b693d7e859b3f95ae42bdee8af4451a258c16755e6e07bc1b519fae8fa7f346502b0511ead7f08bf9874244d240c5b73b6d393be93216faf90757236e66825be92adf8393055c10a3e444b4b13da1213882d687b0b2369e79806c58dc48d9f9f94b31f9a8b1b4e557b1f6257338a9721deda3a1d7c4ff03cfd4fb2ca1dc9aeb18839e8624af02217844956f509c81a530dacce2b44d7d537f21b5cba5d7185e5e4d82e6eb00802f9699127b5bd728f9055d7dedc64e8f2e3812331d21f1a46c17839c94c74ff19db0e5b0256a25d401f90110f842a08dc286880de0cc507d96583b7c4c2b2b25239e58f8e67509b32edb5bbf293c00a00000000000000000000000000000000000000000000000000000000000000000f842a08dc286880de0cc507d96583b7c4c2b2b25239e58f8e67509b32edb5bbf293c01a06131c481ffc5e6015c7104000000000000000000000000000000000000000000f842a08dc286880de0cc507d96583b7c4c2b2b25239e58f8e67509b32edb5bbf293c02a00200000000000000000000000000000000000000000000000000000000000000f842a08dc286880de0cc507d96583b7c4c2b2b25239e58f8e67509b32edb5bbf293c03a0c5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470c0c0
de-serialized block:
- parent hash: 04e3252a0f4f6bba4bfc3613f48e81e0e843336468ceb3cab5c52cd9b9d6e751
- storage root: 71515ed239e2cc61b87f36b85171e0feb2b0c60c64aeb12e6e864340d3fe088f
- block number: 059b84
- key, value list:
8dc286880de0cc507d96583b7c4c2b2b25239e58f8e67509b32edb5bbf293c00 => 0000000000000000000000000000000000000000000000000000000000000000
8dc286880de0cc507d96583b7c4c2b2b25239e58f8e67509b32edb5bbf293c01 => 6131c481ffc5e6015c7104000000000000000000000000000000000000000000
8dc286880de0cc507d96583b7c4c2b2b25239e58f8e67509b32edb5bbf293c02 => 0200000000000000000000000000000000000000000000000000000000000000
8dc286880de0cc507d96583b7c4c2b2b25239e58f8e67509b32edb5bbf293c03 => c5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470
Verkle proof:
* verification hints: 3 Present
* commitments: 46fc4065b024c027d541c02c382fdbbdd024cdb84ab88408f0a9ccb950a6a2ea 0238746d580a1022ca9acf8295f5933bdabeef9450dc3f06c1fb0a6f66b97b4a 6f26bd340f37b09d9dd28c91c3876fa3aa25186497c85c229031455857f98abc 32b9ac7c4012154f7a4bd7c810fa3c67e6be141d3330124a6dd5dbb8810f6d3c
thread 'main' panicked at 'the proof didn't check', src/block_verifier.rs:53:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
What may the problem be related to? Am I doing something wrong?
The command used to start the binary:
cargo run -- --filename=block_367492.rlp --parent-root=15452534ee17148b5a69afb11dafa1c540b6efa18ed0545656df2e9def5a1ce7
The text was updated successfully, but these errors were encountered:
rimrakhimov
changed the title
Cannot verify data from Condrieu testnet
Cannot verify data from Condrieu testnet
Dec 15, 2022
I am working on updating
verkle-tree-visualizer
for blockscout explorer (https://github.com/blockscout/blockscout-verkle-tree), which is heavily based on the current repository. The problem I've met now is verification fails when trying to verify data fromCondrieu
testnet. It seems it worked at the end of August, but it does not work now.In the search for a solution, I've tried to run the binary on the data obtained from
Condrieu
testnet on the current project. For that, I've downloaded block number 367492 and explicitly provided storage root of the previous block (367491) which is15452534ee17148b5a69afb11dafa1c540b6efa18ed0545656df2e9def5a1ce7
. Unfortunately, it panicked with the following message:What may the problem be related to? Am I doing something wrong?
The command used to start the binary:
The text was updated successfully, but these errors were encountered: