The verified OPCODE contract was deployed through Ethereum’s canonical CREATE2 factory on 25 June 2026. Its constructor minted exactly 1,000,000,000 OPCODE with 18 decimals to 0xf551…c48f. The code has ERC-20 transfers and EIP-2612 permit, but no owner, proxy, later mint, contract burn, pause, blacklist or transfer tax. Total supply is immutable.
The app’s live fee endpoint lists a standard 25 basis-point fee. Holding 5,000 OPCODE lowers it to 15 bps, 20,000 to 10 bps and 75,000 to 5 bps, an 80% discount. These tiers are server-side product rules; the token contract neither enforces nor freezes them. The site says a share of protocol fees may fund market buybacks, while its footnote makes them discretionary and cancellable. It also says burn reduces supply, but this fixed-supply contract has no burn function. Sending bought tokens to an inaccessible address could reduce usable circulation, not totalSupply().
Distribution remains concentrated and unexplained by a public allocation schedule. On 5 September 2026, a 3-of-4 Safe held 800,776,004.1337 OPCODE and a 2-of-5 Safe held 99,800,000, together about 90.0576%. A Uniswap v4 PoolManager held about 9.8230%. The Safe signer addresses are visible on-chain, but Opcode has not published who they represent, what vesting duties apply or what treasury mandate each Safe has.
The trading contracts have a different control boundary from OPCODE itself. The live Gateway is a direct, non-proxy deployment and checks signed order fields, but its SolverList manager can add or remove eligible solvers and transfer management through a two-step handoff. At block 25,909,035, the OPCODE deployer was manager, no transfer was pending, and three solver addresses were enabled; the manager/deployer itself was one of them. This role cannot mint OPCODE or seize an unsigned wallet balance, but it decides which addresses may settle through this Gateway. The legal independence of the other solver operators is not publicly established.