finality line edits

This commit is contained in:
Eric Wong 2022-09-22 14:41:06 -05:00
parent e50d4001eb
commit d979ed397b
4 changed files with 28 additions and 28 deletions

View File

@ -81,4 +81,3 @@
- [Github](./reference/github.md)
- [Deployed Contracts](./reference/contracts.md)
- [RPC Nodes](./reference/rpcnodes.md)
- [Blockchain Finality Recommendation](./reference/finality.md)

View File

@ -167,4 +167,30 @@ The [constants](https://github.com/wormhole-foundation/wormhole/blob/dev.v2/sdk/
| Solana | 1 | | NFTWqJR8YnRVqPDvTJrYuLrQDitTG5AScqbeghi4zSA |
| Ethereum | 2 | | 0x26b4afb60d6c903165150c6f0aa14f8016be4aec |
| Terra | 3 | | terra1plju286nnfj3z54wgcggd4enwaa9fgf5kgrgzl |
| Binance Smart Chain | 4 | | 0x26b4afb60d6c903165150c6f0aa14f8016be4aec |
| Binance Smart Chain | 4 | | 0x26b4afb60d6c903165150c6f0aa14f8016be4aec |
## 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.
| Chain Name | Wormhole Chain ID | Suggested Number of Block Confirmations |
| :------------------ | :---------------- | :---------------------------------------- |
| Solana | 1 | 32 |
| Ethereum | 2 | 1 |
| Terra Classic | 3 | Instant |
| Binance Smart Chain | 4 | 15 |
| Polygon | 5 | 512 |
| Avalanche (C-Chain) | 6 | 1 |
| Oasis (Emerald) | 7 | 1 |
| Aurora | 9 | 1 |
| Fantom | 10 | 1 |
| Karura | 11 | 1 |
| Acala | 12 | 1 |
| Klaytn | 13 | 1 |
| Celo | 14 | 1 |
| NEAR | 15 | |
| Terra | 18 | Instant |

View File

@ -1,25 +0,0 @@
# 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 |

View File

@ -35,7 +35,7 @@ To emit a VAA, always use `publishMessage` which takes in the following argument
- How Batch VAAs are generated based on a message's `nonce` is described below.
2. `Consistency` (uint8): the number of blocks that Guardians will wait before signing a message
- Each blockchain has different finality periods. In general, higher consistencies mean more security against blockchain reorgs.
- [Here](../../reference/finality.md) are the consistency levels by blockchain that are used by the xAsset layer to have a high level of guarantee against reorgs.
- [Here](../../reference/contracts.md) are the consistency levels by blockchain that are used by the xAsset layer to have a high level of guarantee against reorgs.
3. `Payload` (bytes[]): raw bytes to emit
- It is up to the emitting contract to properly define this arbitrary set of bytes.