# Bremo documentation This folder exists for one reason: so you never have to trust a web page. Every claim Bremo makes about itself is something you can confirm on your own machine, against the open source in this repository and against Ethereum mainnet. If a check does not match what is written, that is a bug or a lie, and you should say so publicly. ## One trap to know before you start Every check in these guides runs against your own machine, but the endpoint you point it at matters. Free public Ethereum RPC endpoints sometimes serve a degraded state in which `eth_getCode` of a live contract returns empty (`0x`) even while ordinary reads on the same endpoint still answer. In that state a "contract not found" or "no code" reply proves nothing, because it is indistinguishable from a genuinely non-existent contract. So if any check tells you a Bremo contract or the Uniswap factory has no code, do not conclude it is fake or missing: switch to a canonical block explorer or your own archive endpoint and run the check again. We have observed this degraded behaviour on free endpoints repeatedly, so treat it as expected, not exceptional. The detailed guides below repeat this warning at the exact steps where it bites. Start with whichever question you actually have. ## I want to confirm the supply is real and fixed Read [VERIFY.md](VERIFY.md). It walks you through proving, on your own machine and without permission from anyone, that the total supply of BREMO is 21,000,000, fixed forever, with no function anywhere that can create more. It checks the genesis allocation, the contract bytecode, and the live on-chain total supply. ## I am about to trade and want to avoid an imposter pool Read [VERIFY-POOL.md](VERIFY-POOL.md) before you send any transaction. Trading is irreversible. This guide shows you how to check whether a BREMO market exists at all, across Uniswap V3, Uniswap V2 and Sushiswap V2, and how to independently derive the one canonical BREMO pool address so a look-alike pool cannot take your money. CORRECTED 2026-08-05. A BREMO pool now exists. The Uniswap v3 BREMO/WETH pool at 0x44c9D9761f8039cD0e17F040bF06b546b6f3933D was created and funded on 2026-07-31 by the wallet that deployed the token. Checked 2026-08-05 from a public Ethereum node this project does not operate, it held 99,999.999999999985 BREMO against 0.000296248332821778 WETH, so it holds almost no ether and anyone trading against it can lose money. The 0.05 and 1 percent v3 tiers, Uniswap V2 and Sushiswap V2 still return the zero address. The project publishes no price, promises no return and does not encourage anyone to buy. The live answer is https://bremo.tech/market.json. What this section said on 2026-07-26, kept rather than deleted because it is the record of a claim that went stale: There was no BREMO pool at any of those three venues. That was verified against Ethereum mainnet on 2026-07-26 at block 25616178, across Uniswap V3 at all three fee tiers, Uniswap V2 and Sushiswap V2, each behind a passing positive control. When a pool does exist, its address will be published on the site and it will match what you derive from the guide. ## How fresh is that, and what if this file is old The date and block above are a floor, not a promise. They record when the check was last run, not that nothing has changed since. Read them the way you would read a timestamp on a bank balance. This matters in both directions, and the second one is the one people get wrong. If this file is old and still says no market exists, do not use that line to dismiss a real market. A pool can be created by anyone at any time without the project's involvement or consent. An out of date sentence in a document is not evidence about the current state of the chain, and treating it as such is exactly the mistake these guides exist to prevent. If this file is old and a page somewhere claims a market exists, do not use that claim either. The chain settles it, and nothing else does. So do not resolve the question from this file at all. Resolve it from Ethereum. [VERIFY-POOL.md](VERIFY-POOL.md) Method 1 answers it in about a minute with no tools installed: open the Uniswap V3 factory on Etherscan, call `getPool` with the BREMO and WETH addresses and each fee tier, and read the answer yourself. A zero address means no pool on that tier. A real address means a pool exists, and you should then confirm it has actual liquidity and that it matches what https://bremo.tech/trade publishes before you go anywhere near it. Method 3 in the same guide extends the check to Uniswap V2 and Sushiswap V2, because checking Uniswap V3 alone is not the same as checking whether a market exists. Run the control check first in every case. A check that cannot prove it is pointed at the right factory cannot tell you anything about BREMO, and a zero answer from a misconfigured check looks identical to a genuine absence of a pool. ## I want to check the transparency page's numbers against the chain Read [VERIFY-TRANSPARENCY.md](VERIFY-TRANSPARENCY.md). The transparency page publishes how the fixed 21,000,000 supply is split today: how much the treasury still holds, how much has been distributed, and how many addresses hold BREMO. This guide shows you how to reproduce each of those numbers from Ethereum mainnet yourself, so the dashboard is a claim you check rather than one you trust. Method 4 in that guide answers the harder question, whether the published holder list is missing anybody, by testing whether the listed addresses plus the treasury account for the entire 21,000,000. It needs only ordinary `balanceOf` calls, so unlike the holder-count log scan it runs on a free endpoint. ## I want to run my own node and stop taking anyone's word Read [RUN-A-NODE.md](RUN-A-NODE.md). Bremo is only as trustworthy as it is inspectable. This guide is reproducible from the open genesis file in this repository. It has three levels, from verifying the rules on your own machine today to joining the live network. It also explains why the treasury balance you read on the sovereign chain is not the number the transparency page publishes: those are two separate ledgers, and expecting them to match is the easiest way to mistake honest drift for a lie. ## I want to understand how decentralization actually progresses Read [VALIDATOR-2.md](VALIDATOR-2.md). Bremo runs on one validator today, the founder's. That is centralized and it is stated everywhere. This is the tested runbook for adding the second and third independent validators. Nothing in it has been executed against the live network yet, because voting in a signer is an owner action. ## Honest status - BREMO is not an investment. The site says so, these docs say so. Nothing here is a price, a valuation, a target, or a promise of gain. - There is one validator. Decentralization is on the roadmap and disclosed until it is real. - There was no market as of 2026-07-26, block 25616178, verified across three venues. That is a dated observation rather than a standing fact, and the section above tells you how to settle the question yourself against the chain at the moment you actually care about the answer. Every claim on this page is stated so that you can go and falsify it. Where a claim has a date attached, the date is part of the claim, and a claim whose date has gone stale should be rechecked rather than repeated. The right posture toward all of this is the one the token is built for: do not trust, verify.