Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transaction and event proofs against ethereum block headers #6

Open
HarryR opened this issue Jul 2, 2018 · 0 comments
Open

Transaction and event proofs against ethereum block headers #6

HarryR opened this issue Jul 2, 2018 · 0 comments
Labels
enhancement New feature or request speculative Speculation and long-term thought

Comments

@HarryR
Copy link
Owner

HarryR commented Jul 2, 2018

As per the work by Grid+ on bridging EVM blockchains I thought it would be nice to make it compatible with this, without being limited to deposit / withdraw.

I initially didn't take this approach because I wanted to avoid large proofs, so the approach taken was to make the proof size, and thus overhead, as small and as simple as possible. The 'trustless' nature of the Grid+ bridge doesn't rely on using Ethereum block headers specifically, it uses a staking mechanism.

The problem with the approach that uses Ethereum block headers is essentially that proofs a single event require the whole receipt, which includes all of the events, and the 256 byte log bloom, in addition to the MPT proof of the transaction within the block. The smaller and simpler approach taken thus far in this project extracts all of the transactions and logs into a predictable format, then constructs a normal merkle tree with them.

Related links:

TODO: add more details

@HarryR HarryR added enhancement New feature or request speculative Speculation and long-term thought labels Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request speculative Speculation and long-term thought
Projects
None yet
Development

No branches or pull requests

1 participant