Merkle Roots
Status: Under Development
The contents of this page are currently under development and may be updated frequently without prior notice. It is not recommended to use the information on this page for production purposes.
Background
This page lists the active MerkleRoots and Leafs: a cryptographically secured whitelist of actions available to the Strategist, such as mETH routing and rebalancing. The ManagerWithMerkleVerfication contract can supports multiple MerkleRoots, with each Strategist assigned to a specific MerkleRoot.
For more details on the mechanics, interpretation, and walkthroughs, please see Merkle Verification
Active List
The current MerkleRoot x Strategist assignments can be viewed using Sim Explorer (note: update to latest block).
Root_Standard (Active)
MerkleRoot: 0xceb11021b722169f1a4e5ec9aed95891466deb551b47629680750bc7564c4e64
Purpose: Regular rebalancing of mETH between the Vault, DelayWithdraw, PositionManager(s), and restaking protocols.
ActiveLeafs: 28
Strategists: 2 Veda - 0x3AD03F992FE3282830dd36016B409Cf9B055a3dD Mantle - 0xbDFae803A88BB4f71aA1B7ba00893B21A42862D0
Github: Public access TBDhttps://github.com/Se7en-Seas/cMETH-boring-vault/blob/feat/divide-and-simplify-trees/leafs/StrategistLeafs.json
File:
Root_Standard (Historical)
When new Roots are updated, we may preserve the old root for some time for the purposes of existing stakes and claiming from decommissioned position managers. Roots will be rotated between pairs of Strategist signers.
MerkleRoot: 0x9746e6e59bb9c9a05af48b466df5be3dbd2bd8db622ecb1e7d1c1451de273e2c
Purpose: Regular rebalancing of mETH between the Vault, DelayWithdraw, PositionManager(s), and restaking protocols.
ActiveLeafs: 60
Strategists: 2 Veda - 0x7cc4E9Cc7a7772FadDbDC488d63F10162730E10d Mantle - 0x3370bEAc97d1654e03674Aab1B89668237ba320E Github: https://github.com/Se7en-Seas/cMETH-boring-vault/blob/main/leafs/StrategistLeafs.json
File:
Root_Setup
MerkleRoot: 0x998cebb020d797c4fdb030bb0b292199b22f5ae9be65c568b93ce5658d7ee16c
Purpose: Infrequent or one-time actions, such as acceptOwnership.
ActiveLeafs: 8
Strategists: 2 Veda - 0x56B7A6726C7B3e6F6634963dBE104b143fE06e05 Mantle - 0xD3C0363B30b798256E77C70fDaF725008926e2Ec
Github: Public access TBDhttps://github.com/Se7en-Seas/cMETH-boring-vault/blob/feat/divide-and-simplify-trees/leafs/SetupLeafs.json
File:
Root_Rewards
Purpose: Routing reward assets between the BoringVault and RewardHandler systems.
TBD
Root_Security
Purpose: Arbitrary calls on PositionManagers that may be necessary due to new or unanticipated functions released by restaking protocols, such as new methods for claiming rewards or receiving AVS payments.
TBD
Last updated