finality
This commit is contained in:
parent
ec8155f4fc
commit
f3c940fe6d
|
@ -81,3 +81,4 @@
|
||||||
- [Github](./reference/github.md)
|
- [Github](./reference/github.md)
|
||||||
- [Deployed Contracts](./reference/contracts.md)
|
- [Deployed Contracts](./reference/contracts.md)
|
||||||
- [RPC Nodes](./reference/rpcnodes.md)
|
- [RPC Nodes](./reference/rpcnodes.md)
|
||||||
|
- [Blockchain Finality Recommendation](./reference/finality.md)
|
||||||
|
|
|
@ -0,0 +1,25 @@
|
||||||
|
# Blockchain Finality Recommendations
|
||||||
|
|
||||||
|
The goal of Wormhole is to provide high confidence that only _finalized_ messages are observed and attested. Different chains use different consensus mechanisms and so there are different finality assumptions with each one.
|
||||||
|
|
||||||
|
Below is a table of suggested finality recommendations for each of the chains supported by the Wormhole ecosystem to have the highest confidence of finality.
|
||||||
|
|
||||||
|
However, these are just suggestions and developers are free to define their own finality windows for their applications. Ultimately, the tradeoff is between speed and security.
|
||||||
|
|
||||||
|
| Blockchain | Suggested Number of Block Confirmations |
|
||||||
|
| ----------- | ----------- |
|
||||||
|
| Ethereum | 1 |
|
||||||
|
| Binance Smart Chain | 15 |
|
||||||
|
| Polygon | 512 |
|
||||||
|
| Avalanche | 1 |
|
||||||
|
| Oasis | 1 |
|
||||||
|
| Aurora | 1 |
|
||||||
|
| Fantom | 1 |
|
||||||
|
| Karura | 1 |
|
||||||
|
| Acala | 1 |
|
||||||
|
| Klaytn | 1 |
|
||||||
|
| Celo | 1 |
|
||||||
|
| Solana | 32 |
|
||||||
|
| Terra Class | Instant |
|
||||||
|
| Terra 2 | Instant |
|
||||||
|
|
Loading…
Reference in New Issue