Skip to main content

System addresses

tip

Stable. These are fixed protocol constants. They do not change between releases.

TL;DR​

MetaFlux reserves a small set of well-known addresses with special protocol meaning — the null address, the senders the protocol itself writes as, the treasury, the buyback fund, and a reserved burn sink. Integrators and explorers will see these on-chain; this page says what each one is.

Every address on this page is keyless. Each is a hand-picked constant (mostly a repeated-nibble "vanity" pattern like 0x7777…7777), not derived from any public key. A normal MetaFlux address is the last 20 bytes of the keccak-256 hash of an account's public key — exactly the derivation every EVM chain uses. Because these constants were never produced that way, no private key maps to any of them: finding one would mean inverting keccak-256 onto a chosen 20-byte target, which is cryptographically infeasible. So none of these addresses can sign a transaction. Where value moves in or out of them, it is the protocol itself doing it under system authority — never a user with a key.

The addresses​

AddressNamePurposeOperated by
0x0000000000000000000000000000000000000000NullThe zero / null address — an unset or absent valueNobody (sentinel)
0x2222222222222222222222222222222222222222SystemGeneric protocol/system-authority sender for internal writesProtocol
0x3333333333333333333333333333333333333333Oracle feederThe system sender that publishes oracle price updatesProtocol
0x5555555555555555555555555555555555555555FaucetTestnet faucet that funds test accountsProtocol (test networks only)
0x7777777777777777777777777777777777777777TreasuryProtocol treasury — holds the treasury fee share and buyback MTF; the mint / burn point for supply changesProtocol
0x8888888888888888888888888888888888888888Assistance fundHolds collected fee USDC destined for buyback and executes the on-market MTF buyProtocol
0x000000000000000000000000000000000000deadBurnReserved, provably-unspendable sinkNobody — spends from it are always rejected
0x0000000000000000000000000000000000005b07Spot backstopCustody sink for collateral the protocol takes in on a liquidation: base bought off a starved book, and portfolio-margin collateral seized to cover a USDC deficitNobody — a keyless reserved address

All hex is shown in canonical lowercase, 0x-prefixed, 40 characters — the exact form an explorer displays.

What each one is​

Null — 0x0000…0000​

The all-zero address. It is a sentinel, not an account: it stands for "unset", "absent", or "no address here" in protocol data. Nothing is meant to hold a balance at the null address, and no one operates it. Keyless.

System — 0x2222…2222​

The generic protocol/system-authority sender. When the protocol needs to make an internal state write that is not attributable to any single user or more specific role, it writes as this address. It is keyless and operated only by the protocol — there is no user behind it.

Oracle feeder — 0x3333…3333​

The oracle price feeder. The protocol's oracle updates — the per-block reference prices described on the Oracle prices page — are published from this system sender. Keyless; operated by the protocol as part of consensus. You cannot submit oracle prices by "sending from" this address.

Faucet — 0x5555…5555​

The test-network faucet. On testnet it funds test accounts so integrators can exercise the API without real funds. It is keyless and protocol-operated. On mainnet the faucet does not dispense — there is no free mint of real assets.

This address is also the faucet's reserve: a claim TRANSFERS out of the balance held here, and creates nothing. The address is keyless, so the reserve accepts a pre-fund but no signer can spend it. An empty reserve refuses every claim — read its account_state to see whether the faucet can pay. See POST /faucet.

Treasury — 0x7777…7777​

The protocol treasury. It holds the treasury's share of collected fees and the MTF accumulated by the buyback. It is also the single point through which supply changes flow: when governance changes total supply, MTF is minted into or burned from the treasury balance. Keyless; operated by the protocol under governance. See Tokenomics for the economic model and Fees for where fees go.

Assistance fund — 0x8888…8888​

The buyback operational fund. Fee revenue destined for buyback is collected here as a real, explorer-visible USDC balance, and the protocol spends it on the open MTF/USDC market to execute the buyback. It is keyless — there is no key that can move its funds — but it is protocol-operated: the buy is a protocol action, not a user transaction. The bought-back MTF then flows to the treasury and the buyback split described in Tokenomics.

warning

This address ACCEPTS an ordinary transfer, and nothing comes back. It is guarded as a transfer source, not as a destination, so a spot transfer to it succeeds. There is no key to return it and the protocol's only spend path is buying MTF, so USDC sent here is a permanent donation to the buyback. Check the destination before you sign.

USDC sent here does count toward the buyback's next fire. No read reports that balance — see deleted reads. What it cannot do is keep an already-started drain running below the governed trigger — only the buyback's own schedule does that. See Fees.

Burn — 0x0000…dEaD​

The canonical EVM burn sink. It is keyless and, uniquely on this page, provably unspendable: the protocol rejects every attempted transfer whose source is the burn address, under any path. Nothing can ever move value out of it.

The address is reserved. Supply is reduced by decreasing the treasury balance through a governance vote, not by sending tokens here. No burn path routes through this address.

Spot backstop — 0x0000…5b07​

Custody sink for collateral the protocol takes in when it settles a liquidation. Two paths park tokens here, both as ordinary token balances:

  • The forced spot-margin liquidation waterfall. When the book is too thin to absorb a forced close, the insurance fund buys the base and parks it here.
  • A portfolio-margin collateral seizure. When a PM account ends a liquidation in a USDC deficit and holds eligible non-USDC collateral, the protocol takes that collateral at its haircut-valued mark and settles that much of the USDC debt. The seized units land here.

So a balance at this address is not one product's residue. Read it as "collateral the protocol now holds and has not yet disposed of".

It is NOT the treasury. The treasury also holds unissued MTF supply, and a supply-cut vote burns from that row — so collateral standing behind a settled debt must not sit there.

Keyless, and provably so: landing on this fixed image of eighteen zero bytes followed by 0x5b07 would take a 2^160 preimage search, so no signer can ever act as it.

warning

The portfolio-margin seizure path needs a governance vote that sets a collateral haircut. No such vote has ever been enacted on either running chain (measured 2026-09-03 over the full archive), so only the spot-margin waterfall credits this address.

Two categories​

Every address here is keyless, but they split into two kinds:

  • Protocol-operated (system authority). System, Oracle feeder, Faucet, Treasury, and Assistance fund. No key signs for them, but the protocol writes to or from them as part of its own operation (oracle publication, faucet credits on test networks, treasury supply changes, buyback execution). The legacy Spot fee sink was in this group and is now inert.
  • Never-spendable. The Burn address. No key and no protocol path can ever move value out of it.

The Null address is neither — it is a sentinel value, not an account anyone acts on.

FAQ​

Show FAQ

Q: Could someone find the private key to the treasury or the burn address? A: No. These are not derived from any public key; they are fixed constants. Recovering a key for one would require inverting keccak-256 onto a specific 20-byte target, which is infeasible. There is no key to find.

Q: Can I send tokens to the burn address to destroy them? A: The burn address is reserved but not wired into the active supply path today — supply reductions happen by governance reducing the treasury balance, not by sending here. Treat the burn address as reserved.

Q: The faucet gave me funds on testnet. Will it on mainnet? A: No. The faucet only credits on test networks. On mainnet there is no faucet dispense.

Q: I see a balance at the assistance fund on the explorer — whose is it? A: Mostly fee revenue the protocol has collected for buyback and will spend on the open market to buy MTF. No user controls it; the protocol operates it. The balance may also include USDC a user sent to the address by mistake — that transfer is accepted and is not reversible, so it becomes part of the buyback budget.

See also​