snowbridge
snowbridge copied to clipboard
Snowfork
A trustless bridge between Polkadot and Ethereum
Currently our apps read channel addresses from memory every time a message or user instruction is acted upon. Since a `Channel` struct contains 2 addresses (both inbound and outbound), reading...
from https://github.com/Snowfork/polkadot-ethereum/pull/219#discussion_r566169369 For the IncentivizedChannel, replay protection is done with nonce-per-message. As we require and expect all commitments to be processed by the channel in order, we can just do...
I might just not seeing it but having a link to [Snowbridge Doc](https://snowbridge-docs.snowfork.com/) as part of the README should be useful.
- [x] Keep execution header state in storage in beacon client - [x] Reverse execution header syncing so that headers are synced sequentially instead of backwards - [x] Resume syncing...
The previous version was not very accurate, see discussion in SNO-150 Fixes: SNO-150
Added a vault to store ether on behalf of EthApp. * The vault is secured with `Ownable` openzeppelin contract. * Only one version of EthApp can hold ownership of the...
Resolves: SNO-591,SNO-613,SNO-714 Requires: https://github.com/Snowfork/polkadot-sdk/pull/114
Run the following command to generate an initialization preimage: ``` snowbridge-control initialize ```