Contract Addresses

Contracts:

GitHub repository: https://github.com/Andalusia-Labs/karak-restaking

Ethereum Mainnet

NameAddressNotes

Vault (Impl)

0x46c64C1630f320b890d765E7C6F901574924b0C7

ERC4626 Vault

Vault Supervisor (Proxy)

0x54e44DbB92dBA848ACe27F44c0CB4268981eF1CC

Solady ERC1967 Proxy

Vault Supervisor (Impl)

0xF3fAFB319DE5E4b8ed067011a45D1c3cd471A636

Delegation Supervisor (Proxy)

0xAfa904152E04aBFf56701223118Be2832A4449E0

Solady ERC1967 Proxy

Delegation Supervisor (Impl)

0xDD5e5Ec73707D74210f380f5b9BB85868639b79e

Arbitrum Mainnet

NameAddressNotes

Vault (Impl)

0x326f52A56aC65610AAB45D94CC1706ced5cfBc25

ERC4626 Vault

Vault Supervisor (Proxy)

0x399f22ae52a18382a67542b3De9BeD52b7B9A4ad

Solady ERC1967 Proxy

Vault Supervisor (Impl)

0xd9cdec310b83ef713a9f64d984b4c1c9fea9e484

Delegation Supervisor (Proxy)

0x48769803c0449532Bd23DB3A413152632753c8f0

Solady ERC1967 Proxy

Delegation Supervisor (Impl)

0x54130dd18425C0e2F2e103B6CfA68Ed478879Ec9

Karak K2

NameAddressNotes

Vault (Impl)

0x18afCE071bbb52656bBb8F0090Aa53097E142ba5

ERC4626 Vault

Vault Supervisor (Proxy)

0xB308474350D75447cA8731B7Ce87c9ee9DA03B1C

Solady ERC1967 Proxy

Vault Supervisor (Impl)

0x0bd13f1760b5d33946527d430a34f2062ac5edc5

Delegation Supervisor (Proxy)

0xd3c4342f2b542f8c1Fc046F4E89195DeafA4a47E

Solady ERC1967 Proxy

Delegation Supervisor (Impl)

0xf6fd6195e7021a468c71d18524cf57d139427852

Mantle

NameAddressNotes

Vault (Impl)

0xa1e25Bad2a89814A61fd7a3e744b1fEd408e2b5f

ERC4626 Vault

Vault Supervisor (Proxy)

0x4a2b015CcB8658998692Db9eD4522B8e846962eD

Solady ERC1967 Proxy

Vault Supervisor (Impl)

0x5cdaa3d6e6d2bc90277a2819a92102afd8352630

Delegation Supervisor (Proxy)

0x025EA109029cE1da34f41D4C480C0bcf72248A16

Solady ERC1967 Proxy

Delegation Supervisor (Impl)

0xc5d81ca04acdb10e02e8fefa10e70cb634b042ea

Why are some contracts unverified on Etherscan?

The Solady ERC1967 minimal proxy contract is a small contract, 127 bytes, written in pure assembly making it impossible to verify on Etherscan since there is no code to verify. More details the verification issue can be found here.

Why are the vaults not pointing to the implementation on Etherscan?

The vaults are Beacon Proxies that point to a Beacon contract, the vault supervisor in this case, to get it's implementation address. You can verify the that a vault is pointing to the vault supervisor by using

cast storage [vaultAddr] 0xa3f0ad74e5423aebfd80d3ef4346578335a9a72aeaee59ff6cb3582b35133d50 --rpc-url [rpcURL]

Last updated