ampdat control

Ethereum block 26,455,469 · 20 Nov 2026 09:39 UTC

From blockchains to who controls your vault.

A tutorial that follows one question up a ladder: when money sits in a smart contract, who can change the rules it sits under?

How to read this

Each section adds one layer, says why it matters for the question, and ends with the best primary reading we know. The ladder has four rungs:

  1. The machine. Ethereum, smart contracts and tokens: what a contract is, and how anyone can read its history.
  2. The money. Lending, vaults and stablecoins: where deposits go and what they are made of.
  3. Three systems. Morpho (the vaults), Safe (the multisigs that hold the vaults' keys) and the stablecoin issuers (the asset underneath).
  4. The control chain. How the three join into one answer to who controls a position, and how AI agents reach and pay for data like it.

Each section stands alone, so skip what you know. Words in bold are the ones later sections lean on; the ethereum.org glossary covers the rest.

1Blockchains and Ethereum

Ethereum is a shared computer whose whole state anyone can read and nobody can quietly edit.

That one property makes a title search possible: the records are public, ordered and replayable.

  • Accounts. There are two kinds. An externally owned account (EOA) is controlled by one private key. A contract account is controlled by its code. Both have a 20-byte address such as 0xBEEF…21de.
  • Transactions and blocks. A transaction is a signed instruction from an EOA. Validators order transactions into blocks, about one every 12 seconds, and each block changes the state.
  • Finality and reorgs. The newest blocks can still be replaced (a reorg). After about 13 minutes a block is finalised and will not change. A careful reader marks fresh facts as unconfirmed until then.
  • Reading the chain. Software talks to a node over JSON-RPC: eth_call reads current state and eth_getLogs fetches history. Reading needs no permission.
  • Layer 2s. Chains such as Base run on top of Ethereum for cheaper transactions. Small stablecoin payments often settle there.

Read next

2Smart contracts

A smart contract is a program stored at an address, and its stored values change only when that program runs.

So to know who can change a contract's terms, you read its code and ask which functions are restricted to whom.

  • Code and storage. Contracts are usually written in Solidity and compiled to bytecode for the Ethereum Virtual Machine (EVM). Each has its own storage: numbered slots holding balances, addresses, limits and flags.
  • Functions and getters. Anyone can call a public function. A read-only function (a getter) returns a stored value for free, such as owner() or timelock().
  • Access control. A restricted function checks the caller first: "only the owner", or "only an address holding the curator role". Those checks are the whole of on-chain governance.
  • Events and logs. When something important happens, a contract emits an event, stored as a log in the transaction's receipt. Logs are the contract's own change history.
  • Tokens. An ERC-20 token is a contract that keeps a table of balances and a few standard functions (transfer, approve, balanceOf). USDC is one; so is a vault share.
  • Proxies and upgrades. Many contracts are a thin proxy that forwards calls to an implementation contract. Whoever holds the proxy's admin key can swap the implementation, which changes every rule at once.
  • Verified source. Bytecode is hard to read. A contract is verified when its published source compiles to exactly the deployed bytecode, on Etherscan or Sourcify.
  • Timelocks. A timelock makes a change wait a set time between being proposed and taking effect. The wait is the depositor's notice period.

On Ampdat Control

See pending changes live. Timelocks make queued changes public before they bind. Every change queued on a Morpho vault right now, with the time each can take effect.

Read next

3DeFi building blocks

DeFi is financial services written as smart contracts. Two pieces matter here: lending markets and vaults.

A lending market pays interest on deposits. A vault is a fund that spreads deposits across markets for you.

  • Lending. Lenders supply a token to a pool. Borrowers post collateral worth more than they borrow and pay interest, which flows to lenders.
  • Oracles. A contract cannot see market prices, so an oracle contract reports them. A wrong oracle is a wrong valuation of every loan.
  • Loan-to-value and liquidation. Each market sets a maximum ratio of debt to collateral. A loan that crosses it can be liquidated: anyone repays the debt and takes the collateral at a discount.
  • Vaults and ERC-4626. A vault takes one asset, issues shares, and puts the asset to work. ERC-4626 standardises the money side: deposit, withdraw, total assets, shares to assets. ERC-7540 extends it to vaults where withdrawals are requested and settled later.
  • What the standards leave out. ERC-4626 says nothing about who chooses where deposits go, who sets fees, or how much notice a change gives. Those rules differ by protocol, so each protocol has to be read on its own terms.

The risks people usually discuss are market risk (bad collateral, a bad oracle) and code risk (a bug). This tutorial is about a third: control risk, what the people holding the keys are allowed to do.

Read next

4Stablecoins

A stablecoin is an ERC-20 token meant to be worth one dollar, and most large ones have an issuer whose keys can change your balance.

Most vault deposits are denominated in one, so the issuer sits above every vault that holds its coin.

There are two broad designs. A fiat-backed coin (USDC, USDT, PYUSD, USD1) is minted by a company against dollars and Treasuries held off chain. A crypto-collateralised coin (DAI, and its successor USDS) is minted by contracts against collateral locked on chain, under a governance system.

What the token contract lets its keyholders do is the on-chain part of the risk:

  • Mint and burn: create or destroy supply, usually through minters with allowances or limits.
  • Freeze or blacklist: stop one address from moving its coins. Some coins can also seize or destroy a frozen balance.
  • Pause: stop all transfers.
  • Upgrade: replace the implementation behind the proxy, which can add or remove any of the above.
  • Appoint: change who holds each of those powers.

Coins differ a lot on these. USDC and USDT can freeze addresses. DAI's token cannot be upgraded and has no freeze or pause. USDS has no freeze either, but its code can be upgraded by Sky's governance contracts. What is off chain (reserves, redemption rights, legal terms) cannot be read from a contract.

On Ampdat Control

Look up a stablecoin. Who can upgrade, mint, freeze and pause each of six major stablecoins, and who holds those keys. Start with USDC.

Read next

5Morpho

Morpho splits lending into a fixed base layer and managed vaults on top, so nearly all of its human discretion lives in the vaults.

The base layer: markets

One immutable contract holds every market. A market is defined by five fixed values: the loan token, the collateral token, the oracle, the interest rate model and the liquidation loan-to-value. Anyone can create a market, nobody can change one, and a problem in one market does not spread to another.

The managed layer: vaults

Few depositors want to pick markets themselves. A vault is an ERC-4626 contract that takes one asset and lends it across chosen markets. The firm that manages it is called the curator. There are two generations:

MetaMorpho (v1.0, v1.1)Morpho Vaults V2
Lends intoMorpho markets directlyAdapters, which can reach markets, older vaults and other protocols
RolesOwner, curator, allocators, guardianOwner, curator, allocators, sentinels
LimitsA supply cap per marketAbsolute and relative caps per exposure, plus optional gates on who may deposit or withdraw
NoticeOne vault-wide timelockA timelock per function; a function can be abdicated so it can never be called again
VetoThe guardian revokes a pending change; the curator can also revoke a pending cap or market removalThe curator or any sentinel revokes a pending change

The pattern is the same in both. A change that adds risk (raise a cap, add a market or adapter, shorten the timelock) is submitted, waits out the timelock, and is then accepted. A change that removes risk usually applies at once. While a change is pending, someone named can revoke it.

So three questions describe a vault's terms: who holds each role, how long the timelock is, and what is pending right now. The role holder is just an address. It may be one person's key, a multisig or a DAO, and the vault does not say which.

On Ampdat Control

Look up a vault. Every Morpho vault on Ethereum has a free page: who holds each role and what that holder is, the notice each change gives, and what is pending. Try Steakhouse High Yield Term USDC.

Read next

6Safe

A Safe is a smart contract wallet that acts only when enough of its owners sign, and it is where most vault roles are actually held.

Reading the vault tells you an address holds the owner role. Reading the Safe tells you how many people that is.

  • Owners and threshold. A Safe has a list of owner addresses and a threshold: a 2-of-3 Safe needs any two of three owners to sign. A 1-of-7 Safe looks like a committee, but any one signer can act alone.
  • Modules. A module is another contract the Safe has authorised to execute transactions without any owner signatures. Modules power automation and recovery, and they are also a way around the threshold.
  • Guards. A guard is a contract that checks every transaction before and after it runs and can block it. It restricts what the signers can do.
  • The rest of the configuration. Each Safe is a proxy pointing at a shared implementation (the singleton), with a fallback handler for calls it does not recognise and a nonce that counts executed transactions.
  • Changes are transactions. Adding an owner, lowering the threshold or enabling a module is itself a Safe transaction, and each emits an event. So a Safe has a change history like any other contract.

A census of the MetaMorpho vaults by Ampdat Control shows why this layer matters. At block 26,190,823, across the 452 vaults with a role held:

FindingCount
Roles held by a Safe538 of 922, across 116 Safes
Vaults owned by a single key, with no multisig181
Vaults owned by a Safe that one signer controls (threshold 1)35
Safes with a module that can act without the signers18
Safes with a guard2

Other kinds of holder exist too. Aragon DAOs hold 49 guardian roles. And 29 owner keys are EOAs with an EIP-7702 delegation: the key has pointed its account at contract code, and can re-point it at any time.

On Ampdat Control

Look up a Safe. The Safes that hold vault roles, each with its owners, its threshold and any module that can act without them. This 1-of-7 Safe owns the vault from the last section.

Read next

7The control chain

Control over a deposit is a chain of contracts, and each link answers the same three questions: who can act, how much notice they must give, and who can stop them.

What can change at each link Signers Keys held by people, or by further contracts. The vault itself never names them. Role holder: a Safe, a single key or a DAO A Safe acts when m of n owners sign. A module can act without them; a guard can block. Vault Owner, curator, allocators, guardian or sentinels. Risk-adding changes wait out a timelock. Stablecoin the vault holds The deposits themselves, as an ERC-20 balance. Its rules are set by the issuer, not the vault. Issuer keys Can freeze an address, pause transfers, mint, or upgrade the token contract. sign for holds a role on holds A signer is added, removed or swapped Threshold lowered, module enabled, guard removed Cap raised, market or adapter added, fee set, timelock shortened, role reassigned
  1. SignersKeys held by people, or by further contracts. Can change: a signer is added, removed or swapped.
  2. ↓ sign for
  3. Role holder: a Safe, a single key or a DAOA Safe acts when m of n owners sign. Can change: threshold lowered, module enabled, guard removed.
  4. ↓ holds a role on
  5. VaultOwner, curator, allocators, guardian or sentinels. Can change: cap raised, market or adapter added, fee set, timelock shortened.
  6. ↓ holds
  7. Stablecoin the vault holdsIts rules are set by the issuer, whose keys can freeze an address, pause transfers, mint, or upgrade the token.
Each arrow is a power held over the box below. The vault is where a depositor starts, but its terms are only as firm as every link above it and the issuer beside it.

Reading the chain for one vault goes like this:

  1. The vault names an address for each role and a timelock for each kind of change.
  2. The role holder is a key, a Safe, a DAO or some other contract. A Safe adds its own threshold, modules and guard.
  3. The signers are the Safe's owners. An owner can itself be another Safe, so the chain can go up more than one level.
  4. The asset the vault holds is a stablecoin whose issuer can freeze, pause or upgrade it, above and outside everything the vault controls.

Four consequences follow:

  • Documentation is not evidence. A vault's page may say "governed by a multisig with a 3-day timelock". Only the chain says whether that is still true this block.
  • The weakest link sets the terms. A 7-day timelock means little if a 1-of-n Safe can shorten it, or if a module can act without the signers.
  • Any link can change. A new signer, a lower threshold, a shorter delay, a new cap, a new implementation: each is one transaction, and each emits an event.
  • Pending changes are public before they bind. A queued change sits on chain with the time it can take effect. A depositor who looks has notice; one who does not has none.

Others publish related views. L2BEAT's Stages grades who can upgrade a rollup and with what delay, and DeFiScan reviews protocol-level centralisation. Both are assessments by reviewers. Reading the keys directly is a different exercise: it is computed from events with no opinion attached, and it works per contract and per block.

On Ampdat Control

Follow a chain yourself. Start at a vault, go up to the Safe that owns it and down to the stablecoin it holds. Each page links to the next.

8Agents that pay for data: x402 and MCP

More and more, the reader of on-chain data is an AI agent acting for a person, so a data service has to be something an agent can find, call and pay for without a sign-up form.

x402: payment inside HTTP

HTTP has always had a status code 402, "Payment Required", that nothing used. x402 gives it a meaning:

  1. The client asks for a paid resource.
  2. The server replies 402 with its terms: the price, the token (USDC), the chain (Base) and the address to pay.
  3. The client signs a USDC transfer authorisation for that amount and repeats the request with it attached.
  4. A facilitator verifies the signature and settles the transfer on chain. The server returns the answer.

There is no account, API key or invoice, and a call can cost one cent. The payer signs an authorisation instead of sending a transaction (EIP-3009), so it needs no gas. Coinbase runs the main facilitator and the Bazaar, a directory where agents discover x402 services. A companion pattern, sign-in with a wallet (CAIP-122), lets a service recognise a returning wallet, for example to give its first calls free.

MCP: tools an assistant can install

The Model Context Protocol is a standard way for an assistant such as Claude or ChatGPT to call outside tools. A service publishes an MCP server listing its tools, each with a name, a description and typed inputs. A person adds the server once; after that the assistant decides when to call it. A skill is a short instruction file that tells the assistant when and how to use those tools.

Together they give a data service three routes to its readers: a web page a person or a search engine can read, a tool an assistant has installed, and a paid call an agent makes on its own.

On Ampdat Control

Give your assistant the check. Add the MCP server /mcp to Claude or ChatGPT (how to connect) and ask who controls a vault before you deposit. What an agent can ask, as JSON.

A reading path

If you read only ten things, read these in order.

  1. Intro to Ethereum: the machine.
  2. Anatomy of smart contracts: storage, functions, events.
  3. Upgrading smart contracts: why an admin key can matter more than the code.
  4. ERC-4626 explained: what a vault promises, and what it leaves unsaid.
  5. Morpho on vaults and curators: who manages a vault.
  6. The MetaMorpho README: each role and what it may do, from the source.
  7. Safe's smart account overview and modules: what stands behind a role.
  8. The USDC contract source: what an issuer's keys can do.
  9. x402.org: how an agent pays for one answer.
  10. A live vault page: the chain read end to end.

Now look up what you hold. Ampdat Control is a free title search for every Morpho vault on Ethereum, the Safes that hold their roles and six stablecoins: who can change the terms, how much notice you get, and what is already queued.

How the service works, its API and its tools for assistants are in the docs.