snowbridge
snowbridge copied to clipboard
Snowfork
A trustless bridge between Polkadot and Ethereum
For gas saving, we could use the sparse merkle tree multi-proof to validate the commitment signed by beefy authority set. More detail can see https://github.com/darwinia-network/darwinia-bridge-sol/pull/104
This change allows the inbound channel in the snowbridge parachain to forward dispatchable calls to third-party parachains. Changes: * The dispatch pallet is now responsible for either executing the message...
The goal is to allow the bridge module to interact with ETH and ERC20 applications living on separate parachains. Messaging will be implemented using XCMP. The interaction should be bidirectional:...
The bridge currently assumes that if a Proof of Work is correct, and is on the longest chain, then it contains a valid block. This should be a fairly safe...
The ERC721App currently ignores the tokenURI of the NFT. Supporting the tokenURI requires SCALE encoding of arbitrary length strings on Ethereum. Arbitrary length strings require a compact SCALE encoded length...
Quick test of a beefy client that does full signature verification instead of 2-step interactive random protocol, just for interest sake - likely won't merge Results: - Running flow with...
The current plan for the Basic Polkadot to Ethereum Message Channel is to use an ordered queue for replay protection. This is somewhat censorship resistant, but an attacker can still...