L2BEAT Bridges is a work in progress. You might find incomplete research or inconsistent naming. Join our Discord to suggest improvements!
Avalanche Bridge
About
Avalanche Bridge is an externally validated bridge. It uses a set of Wardens using secure SGX Enclave to sign transfers. On Ethereum side it uses periodically rotated EOA address for an Escrow. In the announcement, 3 out of 4 Warden signatures are... required, however the exact number is impossible to verify for an external observer.
About
Avalanche Bridge is an externally validated bridge. It uses a set of Wardens using secure SGX Enclave to sign transfers. On Ethereum side it uses periodically rotated EOA address for an Escrow. In the announcement, 3 out of 4 Warden signatures are... required, however the exact number is impossible to verify for an external observer.
Funds can be stolen if
Funds can be lost if
Funds can be frozen if
Users can be censored if
Transfers are externally verified
Outgoing transfers on Ethereum side are being watched by external entity which informs Avalanche side of the bridge about incoming transfer. The mechanism in other direction works very similar, users can burn tokens signaling external entity intention to transfer, which later informs Ethereum Bridge Wardens about incoming transfer.
Funds can be stolen if wardens decide to maliciously takeover them or there is an external exploit which will result in signing malicious transaction.
Users can be censored if wardens decide to censor certain transactions.
Funds can be lost if wardens loose the private key.
Funds can be frozen if wardens decide to stop processing transfers.
Destination tokens are wrapped
Tokens transferred end up as wrapped ERC20 proxies. The contract is named BridgeToken.
The system uses the following set of permissioned addresses:
Off-chain Multisig 6/8 using Intel SGX, which controls all the funds deposited to the bridge. There is no possibility to verify whether Intel SGX technology is being used.
