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
Return a proof that a transaction or message has been included in a block via rpc.
Problem Definition
Currently, when asked to prove that a transaction has been included in a block, tendermint loads the block of a given height, and provide a simple proof. In order to provide the same functionality, celestia will have to selectively load the transaction data (#221) and extract a proof from IPFS.
Proposal
After saving and loading data via IPFS #374, finalizing node types, and being able to selectively load block data #221, we will be able to start implementing this proposal.
Implementation
It will likely take 2-4 PRs to close this issue. One to handle extracting proofs from IPFS, one to search for and find tx and msgs, and at least one more to handle changing the actual rpc code.
The text was updated successfully, but these errors were encountered:
Note: this might impact the e2e tests in case they check for Tx with proofs. So in case we merge #218 and only store data in ipfs, we might have to disable proof checking until we fixed this issue at hand.
We still have to return a proof that a PayForMessage is included in the block, but I don't think this issue is relevant any longer since it is focused on using IPFS to store block data.
Summary
Return a proof that a transaction or message has been included in a block via rpc.
Problem Definition
Currently, when asked to prove that a transaction has been included in a block, tendermint loads the block of a given height, and provide a simple proof. In order to provide the same functionality, celestia will have to selectively load the transaction data (#221) and extract a proof from IPFS.
Proposal
After saving and loading data via IPFS #374, finalizing node types, and being able to selectively load block data #221, we will be able to start implementing this proposal.
Implementation
It will likely take 2-4 PRs to close this issue. One to handle extracting proofs from IPFS, one to search for and find tx and msgs, and at least one more to handle changing the actual rpc code.
The text was updated successfully, but these errors were encountered: