Bremo
Protocol

The Bremo Protocol.

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.

1. Supply

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.

2. Consensus

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.

3. Execution

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.

4. The two representations

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. 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.

5. Bridge

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.

6. Distribution

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.

7. What Bremo does not claim

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.

Back to bremo.tech