A maximally simple, maximally auditable fixed supply asset. No monetary policy, no privileged keys, no governance over supply.
Abstract. Bremo is a peer to peer electronic currency with a supply fixed at 21,000,000 units. It runs as the native asset of its own EVM compatible blockchain and as an equivalent ERC-20 on public EVM networks.
The full supply, 21,000,000 BREMO with 18 decimal places, is allocated in the genesis block. The consensus layer pays no block subsidy. Transaction fees are transfers of existing coins from senders to validators, so the total never changes. On the ERC-20 side, the entire supply is minted in the constructor and the contract exposes no mint path, no owner, and no upgrade mechanism. Supply invariance is therefore enforced by code on both networks, not by promise.
The chain launches with Clique proof of authority: a known signer set seals blocks in rotation at a 5 second target interval. PoA was chosen deliberately for the genesis phase because it is simple, cheap to run, and has no token emission. Signers are added or removed by majority vote of the existing set, which is the built in path from one validator to many. The end state is a signer set of independent parties with no majority operator.
Honest limitation: until multiple independent parties hold signer keys, the chain is centralized and its operator can reorder or censor transactions. This is disclosed rather than hidden, and resolving it is the first roadmap milestone.
The chain is fully EVM compatible (geth 1.13.15, forks through Gray Glacier, paris EVM target). Standard Ethereum wallets, libraries, and contracts work unchanged. This keeps Bremo inside the largest existing tooling ecosystem instead of inventing its own.
BREMO exists natively on the Bremo chain, where it pays gas and settles peer to peer, and as an ERC-20 on public EVM networks, where it can reach existing liquidity and custody tooling. The design intent is that combined circulating supply across both never exceeds 21,000,000: coins on one side must be locked in a bridge vault for coins to circulate on the other.
Status as of 2026-07-17: that intent is not yet enforced on chain, and we state so rather than let the design stand in for the deployment. Chain 48555 allocated 21,000,000 native units at genesis, and a separate 21,000,000 ERC-20 units were minted on Ethereum mainnet. The bridge vaults are deployed but hold no meaningful balance, so nothing currently locks one side against the other and the two supplies are independent. The ERC-20 on Ethereum is the representation being distributed; it is individually fixed at 21,000,000 with no mint function. Reconciling the two representations into a single verifiable 21,000,000, by funding the vaults, retiring one side, or formally designating one canonical, is an open and unfinished item. Verify both halves yourself: totalSupply() on 0x93CfAE1cfa7AAA1f7D4b8Af85697a600a8dAdC2C on Ethereum, and the balance of NativeVault 0x365feb27d1142412D621e6bC7c73470BdCBd8327 on chain 48555.
The v1 bridge is a pair of vault contracts, one holding native BREMO, one holding the ERC-20. Users lock on one side; an operator releases the equivalent on the other. Each release is bound to the hash of the originating lock transaction, on chain, so no lock can be paid out twice, and only the operator address can call release. The residual trust is availability and honesty of the operator while a transfer is in flight. The upgrade path is operator, then multisig federation, then light client or validity proof verification, and the bridge should hold only trivial value until at least the federation stage.
At genesis the full supply sits in a treasury address, which is publicly visible in the genesis file. There is no token sale. A distribution plan has not been announced; whatever it is, it will be published before it begins, and the treasury's movements are permanently auditable on chain.
It does not claim to be decentralized today; it has a documented path there. It does not claim the bridge is trustless; v1 is operator run. It does not promise returns, yield, or appreciation; it is software, not an investment product.