EVMORE vs Wrapped Bitcoin: the structural argument against custodial scarcity

The dominant way Ethereum DeFi gets exposure to Bitcoin scarcity in 2026 is still WBTC — Wrapped Bitcoin. Roughly $X billion of TVL sits in WBTC across lending markets, AMMs, and yield products. It is the integration story most protocols default to.

It is also, on close inspection, a strange instrument. To use Bitcoin scarcity inside Ethereum, you must give up self-custody to a third party (BitGo and successors), trust a federation of merchants to mint and burn on your behalf, and accept that your “Bitcoin exposure” is a synthetic ERC-20 whose backing exists in a vault you cannot see.

EVMORE is the structural argument that you should not have to make any of those concessions to get a hard-capped, mined, ERC-20 scarcity asset on Ethereum.

What WBTC actually is

WBTC is an ERC-20 issued by a custodian (BitGo, then transitioning through various custody arrangements over the years). When a user wants to mint WBTC, an approved merchant deposits BTC with the custodian and the custodian mints the corresponding WBTC. When a user wants to burn WBTC, the reverse happens — merchant burns WBTC, custodian releases BTC.

The instrument has these characteristics:

• Backed 1:1 by BTC held in custody. Attested periodically.
• Mintable only by approved merchants. The merchant list is small.
• Burnable only by approved merchants. Same.
• Pausable. The contract has admin pause functions.
• Blocklist-capable. Specific addresses can be denied transfer.

Every one of those characteristics is the opposite of how the underlying Bitcoin works.

What goes wrong, structurally

The structural failure modes of a custodial wrap fall into four buckets:

1. Custodian risk. The vault can be hacked. The custodian can become insolvent. The custodian can become subject to regulatory action that freezes the vault. None of these are theoretical; the WBTC market has repriced multiple times around custodian uncertainty since 2024.

2. Merchant risk. The merchant set is a federation. If merchants exit or are sanctioned, the mint/burn capacity contracts. If the merchant set’s composition becomes geographically concentrated, the entire issuance pipeline inherits the regulatory risk of that geography.

3. Attestation risk. “The vault holds N BTC” is a claim. Most of the time it is a true claim. But you are trusting a periodic audit report, not a real-time on-chain proof, and the difference between those two things has historically been where bad things happen.

4. Pause / blocklist risk. The contract can pause. Your “self-custody Bitcoin exposure” can be paused. The contract can blocklist. Your specific address can be denied transfer. The fact that these powers have rarely been exercised does not mean they do not exist; they exist in the contract source code today.

What goes wrong, practically

The structural failure modes above manifest in measurable ways. Consider what has actually happened in the WBTC market:

• Depeg events. WBTC has traded below 1 BTC during custodian uncertainty episodes. The discount has historically been 0.5%-2%, but the existence of a discount at all is the market pricing the structural risk in real time.
• Custody transition shocks. When the underlying custodian arrangement changed in late 2024, WBTC repriced and several DeFi protocols emergency-deprecated WBTC as collateral. The asset’s “fungibility with Bitcoin” was, for that window, contested.
• Merchant outage. When a major merchant has been temporarily disabled, the burn path has slowed and arbitrage between WBTC and BTC has widened the spread.

None of these are signs that WBTC is run badly. They are signs that “custodial wrap of external L1” is a fragile category of asset.

What EVMORE removes

EVMORE removes the entire category of failure mode by removing the wrap. There is no underlying asset to be custodied. There is no merchant to mint. There is no attestation to be performed. The asset is born ERC-20, in the EVM, by submitting a valid KeccakCollision proof to a Vyper contract.

Here is the failure-mode map side-by-side:

Failure mode	WBTC	EVMORE
Custodian compromise	Total loss of backing	Not applicable — no custodian
Merchant outage	Mint/burn slows	Not applicable — no merchants
Attestation gap	Trust report	Verify supply by reading the contract
Contract pause	Yes (admin function)	No — not in the contract
Address blocklist	Yes (admin function)	No — not in the contract
Bridge exploit	Implicit in the wrap	No bridge in base layer
Depeg vs underlying	Real risk	No underlying to depeg from

Several of those rows are “not applicable” because EVMORE is not a wrap. That is the structural argument: the most reliable way to remove a failure mode is to remove the thing that causes it.

What WBTC has that EVMORE does not

Let me be fair. WBTC has properties EVMORE does not, and they matter for some users.

Price exposure to BTC. This is the headline reason people hold WBTC. They want one BTC of beta. EVMORE does not give you that; EVMORE has its own price discovery.

Liquidity. WBTC has years of accumulated liquidity in the major AMMs. EVMORE is new and will need to build its own liquidity profile.

Recognised collateral. Major lending protocols (Aave, Compound, Morpho) accept WBTC as a settled collateral type with calibrated risk parameters. EVMORE will need to be onboarded individually.

Brand familiarity. A user has heard of Bitcoin. They have not heard of EVMORE yet.

If your goal is BTC-price exposure inside Ethereum DeFi, WBTC remains the instrument of choice. If your goal is “an Ethereum-native scarce asset I can self-custody and use as collateral without a custodian sitting in the middle,” EVMORE is the instrument that matches.

The compositional argument

The most interesting consequence of EVMORE’s native-ERC-20 architecture is what becomes composable. Consider a lending market that wants to onboard digital scarcity as collateral:

With WBTC: the market accepts WBTC, but the position’s true risk includes the custodian. The market either ignores this (mispricing) or applies a custodian-risk haircut (penalising users). The risk parameters are imported from off-chain reality.

With EVMORE: the market accepts EVMORE, and the position’s risk is the asset’s risk — price volatility, smart-contract risk in EVMORE itself, and market liquidity. There is no off-chain reality to import. The risk model fits inside the EVM.

This compositional cleanliness compounds across the stack. Yield aggregators, structured products, options markets, perps — every layer above the base ERC-20 inherits a cleaner risk model when the asset itself does not carry a custodian.

The portability argument

A bearer asset is one whose ownership is transferred by transferring the key. Bitcoin is a bearer asset. Cash is a bearer asset. WBTC is not — the bearer holds a claim that is settled against custodian inventory, and the custodian can choose not to honour the claim (because of a freeze, a hack, an insolvency, a regulatory action).

EVMORE is a bearer asset by construction. There is no claim. There is no inventory. There is no custodian. The token contract is the source of truth.

Try the thing

The way to evaluate this argument is not to read more about it; it is to read the WBTC contract source and read the EVMORE contract source side by side. WBTC’s contract is roughly 300 lines of Solidity with admin pause, blocklist, mint-from-merchant, and burn-to-merchant functions. EVMORE’s EvmoreToken.vy is roughly 627 lines of Vyper with no admin pause, no blocklist, and no merchant-gated mint — only a verify-this-proof-then-mint path.

The asset that does not have a pause function cannot be paused.

That sentence is the structural argument.