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
Just as was done for block headers and block bodies, now receipts should be shared around and accessible via json-rpc API.
We don't currently have them in the data set. Items to be done here are:
Create a new block data dump in the format of rlp encoded [header, [txs, uncles], receipts]
Add receipts to the propagation (this is mostly prepared)
Get a json rpc eth call to test this: eth_getTransactionReceipt would be the typically used one for this, however this needs a mapping from tx hash to block has, which we don't have and which I assume the "Canonical Indices Network" is supposed to provide. Perhaps we can temporary create a debug json rpc call that requests it by block hash + tx number or similar.
Edit: New suggestion from @KonradStaniec is to use/implement getLogs but only with blockhash as filter (partial implementation).
The text was updated successfully, but these errors were encountered:
Just as was done for block headers and block bodies, now receipts should be shared around and accessible via json-rpc API.
We don't currently have them in the data set. Items to be done here are:
eth_getTransactionReceipt
would be the typically used one for this, however this needs a mapping from tx hash to block has, which we don't have and which I assume the "Canonical Indices Network" is supposed to provide. Perhaps we can temporary create a debug json rpc call that requests it by block hash + tx number or similar.Edit: New suggestion from @KonradStaniec is to use/implement
getLogs
but only withblockhash
as filter (partial implementation).The text was updated successfully, but these errors were encountered: