Pons-native OHM, Miner, Flywheel, and managed-wallet infrastructure for Robinhood Chain
MURI turns human-readable X commands into bounded onchain actions. This repository publishes the Solidity trust boundary: protocol factories, managed wallets, launch controllers, fee routing, custody modules, tests, compiler artifacts, deployment scripts, and canonical Robinhood Chain receipts.
The contracts make the wallet authoritative. X identifies the user, the root owner authorizes one deterministic managed wallet, and the agent can call only the named actions and limits encoded onchain.
| Asset | Address |
|---|---|
| MURI token | 0xd823603b620c10c3a7cdf86e8ab44fa611e85001 |
| Pons V3 pool | 0x00784EAE93Fe8142E84302319a5b72bFDC0736a2 |
These are the only MURI token and pool bindings used by Flywheel V2.
- OHM-style protocols launch fixed-supply Pons tokens with funded staking rewards, inventory-backed bonds, treasury routing, TWAP-bounded buybacks, and management of the original Pons-locked liquidity position.
- Miner protocols launch fixed-supply Pons tokens around 25-tile mining rounds, shared Quiver randomness, separate prize and reward liabilities, staking, prepaid automation, reserves, and treasury buybacks.
- Flywheel V2 gives both protocol families one shared fee and rewards layer. Creator-side Pons WETH fees route 70% to project rewards, 20% to MURI buybacks, and 10% to operations and security. Bought MURI routes 50% to burn, 30% to performance rewards, and 20% to protocol reserves.
- Managed Wallet V3 preserves one deterministic address per X identity while adding typed Flywheel launches, explicit action limits, owner-controlled recovery, and an ownership-transfer lifecycle that keeps the wallet address and funds unchanged.
| System | Status | Canonical deployment |
|---|---|---|
OHM-style pons-ohm-syncus@1.0.0 |
Deployed | MuriProjectFactory |
Miner pons-miner@1.0.0 |
Deployed and activated | MuriMinerProjectFactory |
| Managed Wallet V1 | Historical release | MuriManagedWalletFactory |
| Managed Wallet V2 | Deployed execution boundary | MuriManagedWalletFactoryV2 |
| Flywheel V2 canonical adoption | Finalized | canonical adoption receipt |
| Flywheel V2 shared deployment | Finalized | Stage 2 receipt |
| Flywheel V2 activation | Activated | Stage 3 receipt |
| Managed Wallet V3 | Deployed and active | MuriManagedWalletFactoryV3 |
| Contract | Address |
|---|---|
| Governance | 0x9A98C2b75f89b29818Deb7a8F6E3BF6D8F5Cb728 |
| Registry | 0x4033Bb9d49b95647596cbCf7fA95CE9B6654e22b |
| Launch gateway | 0x833823913D94bc8C3000Ea33f5B4F4FEC0c2B33F |
| Shared project factory | 0x22e69850f8dfa9F0d7f164bf7F17a05948c2606F |
| OHM module factory | 0x5dCD53D07300118dEe761521f95173D2D250AD43 |
| Miner module factory | 0xd19459c79cD9e6f1b149826D6055f1Ff2C0B721D |
| Managed Wallet V3 factory | 0x043F0cF4786cF0fD7b101723df203893aAf8390e |
| Epoch controller | 0x508d9EdE2f2283ac006B95FFA7742C7461fd0e17 |
| MURI buyback executor | 0x5Cac91C62d076B1073589B00879135e2eFd9F211 |
flowchart LR
X[X identity] --> APP[MURI application]
OWNER[Root owner] -->|EIP-712 authorization| V3[Managed Wallet V3]
APP --> V3
AGENT[Bounded agent signer] --> V3
V3 -->|typed OHM or Miner launch| GW[Flywheel Launch Gateway]
GW --> PF[Flywheel Project Factory]
PF --> OHMF[OHM Module Factory]
PF --> MINERF[Miner Module Factory]
PF --> PONS[Pons launch contracts]
PF --> REG[Canonical Flywheel Registry]
PONS --> ROUTER[Per-project Fee Router]
ROUTER -->|70%| REWARDS[Project reward vault]
ROUTER -->|20%| BUYBACK[MURI buyback executor]
ROUTER -->|10%| OPS[Operations and security]
BUYBACK -->|50%| BURN[MURI burn]
BUYBACK -->|30%| PERF[Performance rewards]
BUYBACK -->|20%| RESERVE[Protocol reserve]
REWARDS --> EPOCH[Challengeable reward epochs]
The launch gateway is the only Flywheel launch authority exposed to Managed Wallet V3. It validates wallet provenance and typed requests before the shared factory prepares the module graph, performs the Pons launch, verifies the canonical result, and completes registry enrollment in the same transaction.
See docs/ARCHITECTURE.md for the complete lifecycle and
trust boundaries.
Counts are physical Solidity lines, including comments and blank lines. Run
npm run loc to reproduce the totals.
| Area | Files | Lines |
|---|---|---|
| Core OHM/Pons | 11 | 2,630 |
| Managed wallets | 7 | 2,195 |
| Miner | 10 | 2,869 |
| Flywheel V2 | 21 | 6,707 |
| Shared deployment, types, and tokens | 5 | 487 |
| External interfaces | 4 | 179 |
| Internal libraries | 7 | 218 |
| Production source tree | 65 | 15,285 |
| Tests and mocks | 22 | 8,001 |
| Foundry deployment scripts | 8 | 1,474 |
| All Solidity | 95 | 24,760 |
Every production source file is indexed in
docs/MODULE_REFERENCE.md.
- Canonical Pons, WETH, V3, locker, position-manager, router, and Quiver dependencies are pinned by address and release-time code hash.
- Factories validate manifests, configuration hashes, implementations, values, validity windows, replay protection, and deterministic predictions.
- Project modules are initialized atomically and implementation instances are locked.
- Managed wallets expose semantic actions instead of a generic call surface.
- Every managed action has an explicit nonce, target binding, value limit, and rolling spend boundary.
- Prize, reward, staking, reserve, bond, and treasury liabilities remain in purpose-specific custody contracts.
- Flywheel epochs use strict precommit, challenge, funding, claim, and expiry transitions.
- Buyback and liquidity paths enforce oracle, liquidity, deviation, slippage, deadline, and spend-cap policies.
- Governance changes pass through the canonical Flywheel governance boundary.
- User withdrawal, redemption, and earned-claim paths remain separate from launch and deposit controls.
Requirements:
- Solidity
0.8.24 - Foundry
1.7.1 - EVM target
cancun - optimizer enabled with
500runs - Node.js
22+
forge build
forge build --sizes --skip script
forge test -vvv
npm ci
npm run check:nodeFork tests are opt-in:
export RH_ARCHIVE_RPC_URL="https://your-archive-rpc.example"
forge test --match-path "test/*Fork*.t.sol" -vvvThe independent solc-js compiler writes source-only ABI and bytecode artifacts
to artifacts/. The published artifacts are produced with the
same compiler, optimizer, and EVM settings described above.
Curated Robinhood Chain receipts live in
deployments/4663:
receipt-mainnet.jsonrecords the OHM-style release.miner-release-mainnet.jsonrecords the Miner and Managed Wallet V2 release.flywheel-v2-canonical-adoption-mainnet.jsonrecords the canonical MURI token, pool, governance, and observation-ring adoption.flywheel-v2-stage2-mainnet.jsonrecords the 23-transaction shared Flywheel and Managed Wallet V3 deployment.flywheel-v2-activation-mainnet.jsonrecords the governance bootstrap and activation transaction at block18478360.flywheel-v2-runtime-inventory.jsonmaps every implementation, global clone, factory, adapter, and V3 wallet component to its finalized address and runtime code hash.
The activation receipt confirms the successful 600-second oracle-readiness
snapshot, approved runtime pins, active launch gateway, active buyback executor,
and cleared bootstrap authority. See
docs/RELEASE_CHECKLIST.md for the publication
procedure.
muri-contracts/
|-- .github/workflows/ CI for Foundry and solc-js
|-- artifacts/ published source-only ABI and bytecode artifacts
|-- deployments/4663/ curated Robinhood Chain receipts
|-- docs/ architecture and complete module reference
|-- script/ Foundry deployment scripts
|-- scripts/ compiler, receipt, and manifest tooling
|-- src/
| |-- interfaces/ external integration surfaces
| |-- lib/ internal libraries and guards
| |-- tokens/ staking receipt tokens
| `-- *.sol protocol contracts
|-- test/ unit, fuzz, fork, and invariant tests
|-- foundry.toml
|-- LICENSE
|-- NOTICE
`-- SECURITY.md
The combined repository is distributed under GPL-2.0-or-later because it contains GPL-derived Uniswap V3 material. MURI-authored files carrying an MIT SPDX identifier remain available under MIT when used independently, subject to the GPL obligations of the combined work.
Third-party attribution, license provenance, and compiler-metadata notes are
maintained in NOTICE.