snowbridge
snowbridge copied to clipboard
Snowfork
A trustless bridge between Polkadot and Ethereum
Resoloves: SNO-829, SNO-779, SNO-871
Resolves: SNO-586,SNO-866,SNO-696 Requires: https://github.com/Snowfork/polkadot-sdk/pull/116
Changes the validator set successions to still be strictly increasing, but not necessarily consecutive. This can greatly improve cost-efficiency of the bridge, but is also useful in recovery scenarios like...
Hi there, I've encountered some unmet peer dependency warnings while using the @snowfork/snowbridge-types library, specifically related to the @polkadot/keyring library. Here's the error I'm encountering: ``` WARN Issues with peer...
BEEFY justifications are encoded as [`VersionedFinalityProof`](https://github.com/lederstrumpf/substrate/blob/e4a39b2a0f1effe151e7390402085ebcbf60a632/primitives/consensus/beefy/src/commitment.rs#L238-L242)s. Snowbridge's commitment scanner currently parses these BEEFY justifications as [`OptionalSignedCommitment`](https://github.com/Snowfork/go-substrate-rpc-client/blob/main/types/beefy.go#L43-L46) [here](https://github.com/Snowfork/snowbridge/blob/b92b1db7d9622534780c711860c95d9b1242a588/relayer/relays/beefy/scanner.go#L134). This inadvertently works because the first byte of an encoded `VersionedFinalityProof` signals the...
More context in https://snowfork.slack.com/archives/G01BGMGLAC9/p1720027597396119 Requires: https://github.com/Snowfork/snowbridge-subsquid/pull/1
### Context Currently the beefy test fixture is some mock data and it's challenging to generate the data. Since beefy is already enabled on polkadot, seems make more sense to...
Snowbridge companion: https://github.com/Snowfork/polkadot-sdk/pull/144
More context in https://github.com/Snowfork/snowbridge/pull/1137 authored by @Lederstrumpf and @bhargavbh, many thanks. Revamp the relayer to skip mandatory commitment when beefy authorities not changed.