The primary purpose of the ByzantineDeposit contract is to serve as a pre-deposit mechanism for the Byzantine protocol, specifically targeting early liquidity providers. The commited liquidity will rewarded by Byzantine points calculated off-chain through the events emitted by the contract.
This contract ensures that deposits are securely stored while maintaining the integrity of the underlying assets.
| Token | Description |
|---|---|
ETH |
Accepted by default and recognized by canonical address 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE. See function depositETH() |
stETH |
Accepted by default. To prevent the loss of the PoS rewards (rebasing mechanism), the contract automatically wraps stETH into wstETH upon deposit. This ensures that users do not miss out on staking rewards while using the contract.This is the wsETH amount which is stored in the depositedAmount mapping, therefore, during withdrawal / move of stETH, users must input the amount of wstETH they got. See function depositERC20() |
wstETH |
Accepted by default. |
ERC20 |
As long as the token has been whitelisted by the owner.It could be wBTC, iBTC, USDC, eigen and other LSTs or stablecoin.See function addDepositToken() and depositERC20() |
The contract allows for the whitelisting of additional deposit tokens by the owner. It is his duty to be careful to not add rebasing or "exotic ERC20" tokens. This flexibility enables the inclusion of various ERC20 tokens while maintaining security and control.
Depositors must be whitelisted to interact with the contract (see mapping canDeposit). However, there is an option to enable permissionless deposits, allowing anybody to participate in the deposit process and earn points. That feature is controlled by the owner and can be reverted.
When Byzantine contracts will be live on mainnet, depositors will have to explicitly move their tokens to the Byzantine vaults of their choice. It's not "all-or-nothing". It is possible to invest in multiple Byzantine vaults. See function moveToVault().
Tokens can only be moved to Byzantine vaults that have been pre-approved by the contract administrator. This ensures that only trusted vaults are utilized for token transfers.
The contract includes the ability to pause specific functionalities, including:
- Deposits - flag
PAUSED_DEPOSITS - Moves to vaults - flag
PAUSED_VAULTS_MOVES
Only registers pausers and unpausers recorded in the PauserRegistry contract have the right pause and unpause the contract's functionalities.
This feature enhances security by allowing the contract owner to halt operations in case of emergencies. It will also block the moves to vaults as long as Byzantine protocol is not live on mainnet.
Audited by security industry leaders:
| Name | Address |
|---|---|
ByzantineDeposit |
0xbA98A4d436e79639A1598aFc988eFB7A828d7F08 |
| Name | Address |
|---|---|
PauserRegistry |
0xf21189365131551Ba4c3613252B1bcCdA60BD1e6 |