Dikaion · the fee account on solana · devnet live

The split is the proof.

τὸ δίκαιον — the share due to each. Dikaion ($DK) turns every pool fee into a public account: tolls accrue, anyone settles the claim, and five lanes take exactly 40 / 40 / 10 / 5 / 5. No keys, no votes, no discretion — the chart above is the receipt, drawn from vault history as it happens.

Open the Terminal Read the Program

I 40 burn

II 40 estate

III 10 ops

IV 5 depth

V 5 chaos

The board · read off the chain

Six figures, zero opinions

every number below is fetched live from the vault, the pool and the mint — refreshed every 15 seconds, no backend in between

$DK / USDC · the print $ — awaiting first print constant-product quote off live reserves

fees claimed · all time ··· everything the account has collected, USDC

accruing · pending ··· held between settlements — nothing leaks

$DK burned ··· share i only ever tightens the float

live supply · $DK ··· 1,000,000,000 at deployment

next settlement window ···

any wallet settles it · caller keeps 0.25% + dust

§01 · The split

Five shares, drawn once

the measure below is the whole treasury policy — constants compiled into the program, not settings any key can resize

INV-1 ··· claimed = keeper + pending + paid — asserted by the program after every settlement, checked live on this page

§02 · Settlement

How the account executes

one claim · five shares · failure-isolated by construction · nobody schedules settlement — anyone can run it

STEP 01 — THE ACCRUAL

A swap pays its toll

Every $DK swap on the main pool pays a 4.2% toll; a quarter of it — 1.05% — accrues to the protocol inside the pool, owed to the vault. Between settlements the toll only accumulates. Nothing leaks, nothing is scheduled.

toll 4.2% 1.05% to the vault accrues per swap

STEP 02 — THE CLAIM

Anyone settles

harvestClaim() is permissionless — any wallet, from anywhere, no allowlist. The caller pockets 0.25% of the claim plus rounding dust as the settler reward. A cooldown rate-limits the desk: 60 seconds on devnet.

permissionless settler 0.25% cooldown 60 s

STEP 03 — THE SPLIT

The shares execute

40 / 40 / 10 / 5 / 5 — hardcoded constants, not settings. Minimum claim, per-share minimums and integer dust guards keep the arithmetic honest to the last base unit.

40 / 40 / 10 / 5 / 5 bytecode constants dust-guarded

STEP 04 — THE ISOLATION

Every share runs alone

Guards validate before a lamport moves; each share runs as its own instruction. A stale feed or thin pool soft-skips — that amount stays pending, the settlement never halts, and the ledger records every skip.

soft-skip RouteFailed · ledgered retries next window

§03 · The ledger

Fees, as recorded

cumulative fees claimed, read from vault history on Solana devnet · no backend · no api keys · the steps are settlements that actually happened

Cumulative fees claimed · devnet Split 40/40/10/5/5 · Settler 0.25%

reading vault history · the ledger grows with the first settlements

Window start — first visible claim Now · slot —

fees settled · usdc ··· all time — everything the account has paid out

$DK burned ··· through share I only

settler cut 0.25% plus rounding dust, to whoever settles

pool toll 4.2% a quarter of it accrues to the vault

§04 · The estate

Nine holdings, held by bytecode

40% of every settlement lands here · equal weight · live feeds on devnet · nobody can raid the rows

9 assets equal weight 50 / 50 swap-lp ±3% twap gate

ticker	feed price	status	pool

see positions and routing at the terminal →

§05 · Guardrails

Walls, not promises

six gates every share passes · 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 shares skip any asset whose oracle is older than 15 minutes, paused, or negative. Skips are ledger entries, not errors.

G-03

Pool impact cap

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

G-04

Soft-skip isolation

Guards validate first, then each share runs as its own instruction. A failing lane emits RouteFailed and holds its funds pending — never takes the settlement down.

G-05

Timelocked custody

Fee-recipient and dev-treasury changes need a request/confirm delay — 60 seconds in this devnet edition. The world reads the intention first.

G-06

Self-auditing ledger

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

§06 · Queries

The fine print

eight answers · zero marketing

Q1What exactly is Dikaion?

A fee account that runs itself, on-chain. $DK trades on its own pool; the pool tolls are periodically claimed by the vault program and settled along five fixed shares — buy&burn, the stock estate, operations, depth, chaos. No human in the loop, no off-chain infrastructure: the whole account book is one on-chain program.

Q2Why "Dikaion"?

From the Greek τὸ δίκαιον — "the share rightly due to each." Older than the courtroom sense: dikē originally meant the boundary line drawn with a staff. That is the whole protocol in one word — lines drawn once, every party paid exactly what the lines assign, and the account itself as the proof that it happened.

Q3Who can settle the account?

Anyone, from any wallet. The caller receives 0.25% of the claim plus rounding dust as the settler reward. Settlements are rate-limited by a cooldown — 60 seconds on Solana devnet, five minutes planned for mainnet.

Q4What happens if a share fails mid-settlement?

Nothing catastrophic — by construction. On Solana a transaction cannot half-revert, so every guard is checked up front and each share runs as its own permissionless instruction. If a guard trips (stale feed, drift gate, thin pool), the lane soft-skips — a RouteFailed entry lands on the ledger, the amount stays pending for that lane, and every other share completes normally. The failed amount retries next window.

Q5Are the stock positions real?

On devnet 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 program consumes real equities price feeds and real position tokens.

Q6Why does 5% go to "chaos"?

An account that only makes optimal moves is an account that can be modeled, front-run and farmed. The chaos share buys a volatile side asset and burns it — deliberately inefficient value that keeps the whole engine from collapsing into a deterministic payoff matrix.

Q7Can the shares or destinations be changed later?

Not by any key we hold. The shares live in the program as constants. The authority role can rotate operational parameters (cooldowns, caps, asset list) — all timelock-protected and visible on-chain — but redrawing the split would require deploying an entirely new account book nobody is obliged to follow.

Q8When mainnet?

After the external audit completes and timelocks are extended to production values. Watch @dikaionspace — the ratification announcement is the only signal worth trusting.

§07 · Ratification

The account is open. Read it yourself.

Every settlement, every share, every skip lands on-chain where anyone can read it. Open the terminal and run the settlement yourself — follow the account for the mainnet signal, read the program for everything else.

Open the Terminal @dikaionspace Read the Program

announcement channelx.com/dikaionspace
home of the accountdikaion.space
the split · fixed40 / 40 / 10 / 5 / 5
settler reward0.25% + dust
cooldown · devnet60 seconds
keys heldnone that matter