Governance
Who controls the diamond, read from the chain.
How it works
A guardian key can freeze the diamond but cannot move funds. Upgrades go through whoever owns it — which is checked below rather than taken from the documentation.
Checking who owns this diamond…
Protocol fee share
…
veFeeShareBps — the cut of swap fees routed to lockers
Total locked weight
…
veTotalWeight — your share is your weight over this
Fee reserve
…
veFeeReserve — accrued and unclaimed
Your weight
—
connect a wallet to read it
Upgrade admin
…
upgradeAdmin()
Diamond owner
…
There is no proposal or vote method on this diamond — the loupe exposes none. Voting weight entitles you to fee share; protocol changes are made by the diamond's owner through diamondCut. This page shows that structure rather than simulating a governance process that is not deployed.
Privileged calls
Listed for transparency. Your wallet is not the owner, so these will revert — the simulation below says so before you sign.
Fill in the argument to build a transaction.
Pool policy
Each pool can carry an off-chain policy, identified by a hash and an epoch. Updates are signed by the policy signer and can be submitted by anyone. The signature is what authorises them, not the sender.
Open a pool
Owner-only. Two-token pools pick a curve; N-pools take a token list and always use the StableSwap invariant.
Fill in the pool parameters to build a transaction.