Closed Inkvi closed 8 months ago
Thanks for bringing this to attention. There was some issue with the configuration of one of the test client
nodes which was causing the mismatch in computation. We have taken care of this and updated go-main
branch with the default block_number
for ARBITRUM
.
You can use the other API routes to get more information and then compute committee_root for blocks of supported chains.
GetBlockByBlockNumber: curl --location 'https://querylayer.lagrange.dev/blocks/block?chain_id=<CHAIN_ID>&block_number=<BLOCK_NUMBER>' \
--header 'x-api-key: <API_KEY>'
GetBlockByBlockHash: curl --location 'https://querylayer.lagrange.dev/blocks/block-hash?chain_id=<CHAIN_ID>&block_hash=<BLOCK_HASH>' \
--header 'x-api-key: <API_KEY>'
GetLastFinalizedBlock: curl --location 'https://querylayer.lagrange.dev/blocks/last-finalized-block?chain_id=<CHAIN_ID>' \
--header 'x-api-key: <API_KEY>'
Perfect, thanks for fixing.
In the program I use
and the logs produce
The api through returns a different result (28a4754819df7e2a456d8517ecd4a1c0bc1f1dffbe8e2458a6e8aa73e2e90b38) The query I used:
The result:
Are they actually matching and I am missing some kind of data conversion or there is a bug?