LAWKEEP.
/
OPEN THE CHAMBERS

AUTONOMOUS TREASURY · ROBINHOOD CHAIN TESTNET · 46630

syncing···

LAWKEEP

THE FEE IS THE LAW.

$ — LWP / USDC · MAIN POOL · LIVE PRINT · EVERY SWAP PAYS THE TOLL — THE CODE TAKES ITS CUT

OPEN THE CHAMBERS READ THE CODEX

01 · DOCTRINE

A code, not a committee

THE NAME IS THE MECHANISM — LAW WRITTEN AS CONSTANTS, KEEP AS THE TOWER THAT HOLDS
D/1

What Lawkeep is

Lawkeep is an autonomous treasury on Robinhood Chain. $LWP trades on its own pool; the pool fees accrue to the keep — a vault contract that claims them and pays five fixed routes. The name is the mechanism: law — the split, written as constants in bytecode — and keep — the tower room built never to be opened by force.

D/2

What it refuses to be

There is no multisig deciding monthly. No manager fee. No upgrade key waiting in a drawer. The split lives in bytecode; the harvest is a public utility anyone can run from any wallet for a 0.25% keeper cut. If a route fails, it waits — the keep never breaks its own law to force a transaction through.

D/3

Where it runs right now

This testnet edition runs the real engine end to end on chain 46630 — live ledger, order desk, nine-stock board, counsel console. Simulated price feeds stand in for mainnet equities data; $LWP mainnet ships after the external audit. Everything you can read here, you can verify on the explorer.

02 · THE CODEX

Five articles. One claim.

40 / 40 / 10 / 5 / 5 — CONSTANTS IN BYTECODE, NOT CONFIG ROWS · EACH ARTICLE STANDS ALONE

ARTICLE I · OF THE BURN

40%

Buy & burn

The first statute. Fees buy $LWP on the open pool and burn it in the same transaction. Supply only ever goes down through this pipe.

ARTICLE II · OF THE BASKET

40%

The keeper's estate

The treasury: nine tokenized stocks — SPY, NVDA, TSLA, SPCX, MSTR, GOOGL, CRCL, AAPL, META — bought equal-weight and held. The retirement position nobody can raid.

ARTICLE III · OF OPERATIONS

10%

Operations

The running of the court: an operations budget pulled to the dev treasury by the same harvest. Capped, scheduled, and printed on the ledger like everything else.

ARTICLE IV · OF THE DEPTH

5%

Liquidity

Dropped into the main pool as full-range liquidity. The position contract has no remove function — depth compounds, extraction is impossible.

ARTICLE V · OF THE CHAOS

5%

Chaos

Deliberate inefficiency: a volatile side asset is bought and burned. A treasury that can only do sensible things is a treasury that can be farmed.

KEEPER'S CUT · 0.25% + DUST the only human touch in the code — and anyone may hold it

NO KEYS.

NO VOTES.

NO DISCRETION.

THE SPLIT IS THE ARCHITECTURE — 40/40/10/5/5, EXECUTED OR NOT AT ALL

04 · PROCEDURE

How a harvest runs

ONE TRANSACTION · FIVE ROUTES · FOUR GUARDRAILS
P/01

A swap pays its toll

Every $LWP swap on the main pool pays 4.2%; 2.5 points belong to the protocol. The toll accumulates in the pool, owed to the keep.

P/02

Anyone files the harvest

harvest() is permissionless — the caller pockets 0.25% of the claim plus rounding dust. Rate-limited by a cooldown: 60 seconds on testnet, one hour planned for mainnet.

P/03

The pot cracks five ways

40 / 40 / 10 / 5 / 5 — constants in bytecode, not entries in a config table. Minimum claim, per-route minimums and integer dust guards keep the arithmetic honest.

P/04

Every pipe runs alone

Each route executes as an isolated external call under a gas cap. A stale feed or a thin pool leaves that slice pending — it never takes the harvest down. The ledger records every skip.

INV-1 · CLAIMED = KEEPER + PENDING + PAID asserted on-chain after every harvest — watch it live in the chambers

05 · GUARDRAILS

Walls, not promises

SAFETY GATES ON EVERY ROUTE · G/01–G/06
G/01

TWAP drift gate

Before any pool trade, spot must sit within ±3% of the 30-minute TWAP. Manipulation inside the window is refused, not punished.

G/02

Feed staleness & pause

Stock routes skip any asset whose oracle is older than 15 minutes, paused, or negative. Skips are events, not errors.

G/03

Pool impact cap

No single route moves more than 0.5% of a pool per execution. Oversized amounts batch across future harvests.

G/04

Rollback isolation

Pipes run as external self-calls under try/catch with a 4M gas cap. A failing pipe leaves its funds pending — never takes the harvest down.

G/05

Timelocked custody

Fee-recipient and dev-treasury changes need a request/confirm delay — 24 hours on mainnet. The world watches the intention first.

G/06

Self-auditing ledger

INV-1 asserts claimed = keeper + pending + paid after every harvest. INV-4 asserts the vault holds zero $LWP when the dust settles.

06 · THE RECORD

The keep, measured

READ STRAIGHT FROM CHAIN 46630 · REFRESHES EVERY 15S
harvested · usdc···
$lwp burned···
live supply · lwp···
pending claim · usdc···
harvest window···
the law40/40/10/5/5
RECORD OF THE KEEP

07 · FINE PRINT

The fine print

EIGHT ANSWERS, ZERO MARKETING
What exactly is Lawkeep?+
An autonomous treasury. $LWP trades on a pool; the pool fees are periodically claimed by a keep contract and split along five fixed routes — buy&burn, stock basket, operations, liquidity, chaos. No human in the loop, no off-chain infrastructure: the whole vault is bytecode.
Who can call harvest?+
Anyone, from any wallet. The caller receives 0.25% of the claim plus rounding dust as a keeper reward. Harvests are rate-limited by a cooldown — 60 seconds on testnet, one hour planned for mainnet.
What happens if a route fails mid-harvest?+
Nothing catastrophic — by design. Each route executes as an isolated external call wrapped in try/catch under a gas cap. If it reverts (stale feed, drift gate, thin pool), the amount stays pending for that route and every other pipe completes normally. The failed amount retries next harvest.
Are the stock positions real?+
On testnet they're simulated — mock feeds push plausible prices for SPY, NVDA, TSLA and six others so you can watch the routing work end to end. On mainnet the same code consumes real equities price feeds and real position tokens.
Why does 5% go to "chaos"?+
A treasury that can only do sensible things is a treasury that can be modeled, front-run and farmed. The chaos route buys a volatile side asset and burns it — deliberately inefficient value that keeps the system from becoming a deterministic payoff matrix.
Can the weights or destinations be changed later?+
Not by any key we hold. The split lives in the keep's bytecode as constants. The owner role can rotate operational parameters (cooldowns, caps, asset list) — all timelock-protected and visible on-chain — but re-weighting would require deploying an entirely new protocol nobody is obliged to follow.
Why is gas paid in ETH?+
This edition runs on Robinhood Chain, an Arbitrum-based L2, where the native gas token is ETH. Your wallet pays fees straight from its ETH balance — the Robinhood Chain testnet faucet at faucet.testnet.chain.robinhood.com funds new addresses with 0.01 ETH every 24 hours.
When mainnet?+
After the external audit completes and timelocks are extended to production values. Watch @lawkeep_xyz — the launch announcement is the only signal worth trusting.

08 · ENLIST

EVERY HARVEST IS A PUBLIC RECORD.

Each harvest, each route, each skip lands on-chain where anyone can read it — open the chambers and watch the keep work in real time. Follow the account for the launch signal; read the contracts for everything else.

FOLLOW @LAWKEEP_XYZ READ THE CODE OPEN THE CHAMBERS
  • announcement channelx.com/lawkeep_xyz
  • home of the codelawkeep.xyz
  • keeper reward0.25% + dust
  • cooldown · testnet60 seconds
  • routes · fixed40 / 40 / 10 / 5 / 5
  • keys heldnone that matter