Overview
BETH brings native ETH to Canton Network as a wrapped token. Credentialed participants deposit ETH through an Ethereum bridge and receive BETH on Canton. Redemption burns BETH on Canton before the bridge pays ETH to the specified Ethereum address.
BETH is designed to represent native ETH at a 1:1 ratio. It does not represent WETH or stETH. The current design does not stake deposited ETH.
BETH follows the same model as CBTC, the first non-native asset on Canton. The two assets use separate contracts, credentials, and governance.
How minting works
Section titled “How minting works”- A credentialed participant creates a BETH deposit account on Canton. The account supplies a stable identifier.
- The participant deposits native ETH into the Ethereum bridge contract, together with that identifier. A plain ETH transfer is not a valid deposit.
- Attestors observe the finalized Ethereum deposit. Canton governance confirms and executes the mint.
- The participant receives BETH on Canton and can use it in compatible wallets and applications.
How burning works
Section titled “How burning works”- A participant creates a withdrawal account with an Ethereum destination address.
- A withdrawal command burns BETH on Canton.
- Attestors authorize the Ethereum payout. The bridge pays native ETH to the destination address.
- After Ethereum finality, Canton records the completed redemption.
Key facts
Section titled “Key facts”| Item | Detail |
|---|---|
| Asset | Wrapped native ETH on Canton Network, designed as 1:1 |
| Networks | Ethereum Mainnet and Canton Network |
| Bridge fee | Free at launch. Ethereum gas costs are separate. |
| Transaction limits | 0.01 to 100 ETH per deposit or withdrawal |
| Precision | 10 decimal places |
| Access | Minting and redemption require onboarding and the BETH Minter credential |
Availability
Section titled “Availability”Access to minting, redemption, and third-party applications depends on onboarding and the relevant provider’s approval.
Ask the docs
Answers come only from this documentation and can be wrong. Check the linked pages.
Ask a question about BitSafe, CBTC or the developer guides. For example: