HostDeFi › Library › Is ETH safe on Base?

Is ETH safe on Base? The chain's own asset — no contract at all

ETH on Base is the page where the checklist runs out of things to check — the chain's native asset, no contract at all, grading A (100) on our September 27, 2026 read behind ~$326.6B of cap.

Snapshot 2026-09-27 · Base · ~$43.5M liquidity · holders unresolved · 597 days live · ~$326.6B cap · ~$42.3M daily volume

Ether on Base is listed at 0x0000000000000000000000000000000000000000 — the zero address, the placeholder native assets carry because there is no token contract to point at. The grade is A (100): with no deployer contract there is nothing to mint, nothing to freeze, nothing to rewrite. The single flag is the thin-pool warn — ~$43.5M of tracked depth against a ~$326.6B cap. Behind the letter: ~$42.3M of daily volume and 597 days of the listing.

This is the batch's quiet page — the asset the checklist was built to vet, and on which it finds the one configuration safer than any contract: no contract at all. What the page can honestly add is everything the A can't see — the bridge custody the asset's backing actually travels.

The zero address means no attack surface

On every other page in this series, the flag set describes powers a contract holds over holders. On this one there is no contract: ETH on Base is the chain's native gas asset — balances live at the protocol layer, moved by the chain's own accounting, not by code a deployer wrote. The checklist's verbs — mint, freeze, blacklist, owner-rewrite — have no function to attach to.

That absence is the strongest safety statement the format can make: a ledger entry that no contract governs is one that no contract can be used against. The A-100 here isn't an assessment that passed — it's an assessment with nothing to assess, which is the only way to be permanently safe from the failure modes this whole series exists to catalog.

~$326.6B of cap with a 0.01% pool

The warn flag is real even where there's no contract to flag: ~$43.5M of tracked DEX depth against a ~$326.6B cap is ~0.013% coverage — the thinnest ratio the ledger has ever printed, because the denominator is the entire asset, not a token's slice. The honest reading differs from every other thin-pool warn in the batch: ETH's market exists on every venue on earth — the on-chain pool is a rounding error on global depth, and the cap isn't an on-chain market at all.

The flag still earns its print for the reader who exits on-chain specifically: selling size through Base's pools means sizing against ~$43M, whatever the Coinbase order book says. On this asset that caution is nearly never binding — ~$42.3M of daily volume shows the venue is used — but the checklist's habit of printing the ratio is correct even at its most extreme denominator.

The custody story the grade can't see

The paragraph the A owes the reader: ETH on Base is native — but its backing path is bridged. Every unit of ether on Base corresponds to ether held in the bridge's custody on ethereum, delivered by the rollup's canonical bridge. The asset has no contract risk and carries full bridge risk — the trust moved from "does the token contract behave" to "does the chain's bridge custody hold," which is a different question the checklist doesn't grade.

That's the honest boundary of every native-asset A-100: the letter certifies there is no deployer who can hurt you; it is silent on the sequencer, the bridge, and the L1 settlement the chain's safety actually depends on. On Base, that machinery is among the most scrutinized in the sector — but "the checklist sees no contract" and "there is no trust surface" are not the same sentence.

597 days of the ledger's bloodstream

The age column — 597 days — marks how long the Base listing has been tracked, and the figures are what a native asset looks like: ~120.5M units of total supply (the asset's whole float, chain-agnostic), a cap that is the asset's cap rather than a deployment's, and a venue (~$43.5M) that exists to route ether on-chain rather than to carry the asset's market.

The holders field resolves null — expected on a native asset, where per-wallet balances are the chain's account set rather than a token's holder list. The page prints the gap rather than estimating: on the one row where "everyone who uses the chain holds it," a holder count was never going to be the interesting number.

What "safe" means when nothing can be flagged

The calibration paragraph: ETH's A-100 answers "is there a contract that can hurt me" — definitively no, because there is no contract. It does not answer "is ether safe" — a $326B asset whose risk lives in market structure, bridge custody, and the chain's own consensus. The page is the clearest case in the series for the split the checklist always intends: contract layer inert, everything above it a separate question.

The related-link discipline matters here more than anywhere: the reader who needs to know about ETH on Base beyond the letter should read the bridge custody page and the chain page — the risk moved layers, and the map shows where it went.

Where base-ETH sits in the safety map

Against the batch it is the structural zero: UNI/SHIB/BONK/RAY all earned A-100 on contracts that renounced their powers; base-ETH earned it by never having powers to renounce. The distinction is worth the letter's honesty — "renounced" means someone chose to give up control; "native" means control was never in the contract layer to begin with.

Within Base's own coverage it is the reference point: the native asset whose A the chain's other tokens are measured against, the asset every Base user's gas bill and pool denomination runs on.

The venue's real job on a native asset

The ~$43.5M pool figure makes more sense once its role is named: on a chain whose gas token is the listed asset, DEX liquidity isn't where the asset's market lives — it's where the chain's commerce happens. Every Base swap that prices in ETH, every pool denominated in it, runs through venues like this one; the depth exists to serve the chain's trading, not to carry ether's market cap. That reframing is why the 0.013% coverage ratio is a measurement curiosity rather than a hazard — on the one asset whose market truly is everywhere, the tracked pool is a tool, not a door.

597 days inside the map's ether census

This listing closes the batch's ether census: ethereum's canonical WETH (A-100, inert by definition), base's own wrapped copy (A-100), arbitrum's proxied leg (B-80), polygon's mintable receipt (B-75) — and now the native asset itself, the row that exists so a reader checking "ETH" on Base lands on a page that says plainly: there is no token contract here, and the thing to verify is the bridge, not a deployment.

Holding it, honestly

If you hold ETH on Base you hold the chain's bloodstream on the only configuration safer than a clean contract — no contract. ~$326.6B of cap, ~$43.5M of on-chain venue, ~$42.3M of daily flow, and a flag set with nothing to flag. The A-100 is complete on the layer it measures; the bridge-custody layer above it is where the asset's real trust story lives.

Frequently asked