$LACH / USDC
$ —
awaiting first print
Meet achesion
Lachesion is an autonomous treasury token. Every pool fee is claimed by anyone and split 40 / 40 / 10 / 5 / 5 — burn, stocks, ops, depth, chaos. No keys, no votes, no discretion: the allotment was written before launch, and no one can rewrite it.
HOW IT WORKS
5 routes, one transaction ›
HARVEST
LIVE
1H24H7D
···vaultreading vault history···
keeper 0.25%rate-limited windowroute fails → pending
THE ENGINE
Anyone can pull the next harvest.
There is no keeper monopoly, no admin button, no schedule. The route is open — the first caller executes the split for everyone and takes a small keeper reward.
Next window
···
Minimum claim
···
Keeper reward
0.25% + dust
The window arm above reads straight off the vault. When it opens, any wallet — a cron job, a bot, you — runs the settlement from the terminal.
Run the settlement
permissionless
cooldown window
fail-isolated routes
fees claimed · ···
THE MYTH
The allotment was written first.
Before the first trade, before the pool had a price, the shares were already cut: forty to the fire, forty to the market, ten to the builders, five to the depth, five to the chaos. Lachesion does not decide. It only measures out what was decided long ago.
I
The fire takes its forty
Buyback and burn happen inside a single transaction. What the fire buys, it keeps — nothing is retained, nothing is redirected.
INVARIANT — buyback output is burned in the same tx
II
The market holds its forty
An equal-weight basket of nine tokenized stocks, held as liquidity. Positions that leave their range are rebalanced; principal is never withdrawn.
INVARIANT — no owner-withdraw path exists
III
The depth never moves
Five percent of every harvest is poured into the main pool as full-range liquidity. The program has no function to remove it.
INVARIANT — no removal path for the main LP
WHAT LACHESION ROUTES
Five fates, one transaction.
Each route executes independently with its own rollback boundary. If one fails, its share waits in pending — the other four still settle. The pending and lifetime columns are live off the vault.
40%Buy & burn
Fees swap back into $LACH and burn it in the same settlement. Supply only ever goes down on this route.
→ same-tx burnpending —lifetime —
40%Stock basket
Equal-weight buys across nine tokenized stocks, held as liquidity with guarded entry ranges. The estate is a portfolio, not a jar.
→ 9 stocks · equal weightpending —lifetime —
10%Ops
Pull-payment to the development treasury. A budget, not a faucet — the share is fixed like everything else.
→ pull payment · cappedpending —lifetime —
5%Depth
Full-range liquidity into the main pool. No removal function exists in the program. Ever.
→ full-range LP · permanentpending —lifetime —
5%Chaos
Buys and burns the chaos asset — the sibling token. The fifth fate keeps a promise to the older game.
→ buy & burn $CHAOSpending —lifetime —
RECEIPTS
The numbers, as written.
Every figure below reads live off the vault account on Solana devnet — no backend, no rounding stories.
Fees routed
···
lifetime · all five routes
$LACH burned
···
supply now ··· of 1B
Pending pot
···
held between windows — ···
THE LEDGER
Every claim, stacked.
Cumulative fees claimed, decoded straight from vault history — each step is a harvest that actually happened, placed where it landed.
reading vault history · the ledger grows with the first settlements
window start — first visible claim
··· claimed · now · slot —
ESTIMATE A HARVEST
Run your own numbers.
Every $LACH swap pays a 4.2% toll; a quarter of it — 1.05% — accrues to the vault. Drag the volume, watch the five shares split it.
sliders drive the estimate live · toll 4.2% · vault share 1.05%
per week · estimate
40%burn— LACH
40%estate$ —
10%ops$ —
5%depth$ —
5%chaos$ —
THE ESTATE · 40% OF EVERY SETTLEMENT
Nine holdings, held by bytecode.
Equal weight, live feeds, a ±3% TWAP gate before any trade. Nobody can raid the rows — positions only open, never withdraw.
9 assetsequal weight
50 / 50 swap-lp±3% twap gate
| ticker | weight | feed price | status |
|---|
THE TAPE
Real harvests. Real burns.
Every settlement is a public event, decoded straight from vault history — no backend, no api keys. The rows update as keepers call the harvest.
···reading vault history···
QUESTIONS
Asked, answered.
What exactly is Lachesion?+
An autonomous treasury token. $LACH trades on its own on-chain pool; the pool tolls are claimed by a 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 Solana program.
Why "Lachesion"?+
From Lachesis — the Fate who measures the thread before the cut. In the old stories she allotted each life its portion before it began; here the portion is 40/40/10/5/5 and it was measured out in code, at deployment, before the first trade. Measured once. Split forever.
Who can call the harvest?+
Anyone, from any wallet — the call is permissionless with no allowlist. The caller receives 0.25% of the claim plus rounding dust as the keeper reward. Settlements are rate-limited by a cooldown window read live off the vault.
What if one route fails mid-settlement?+
Nothing catastrophic — by construction. Guards validate before a lamport moves; each share runs as its own instruction. If a guard trips (stale feed, ±3% TWAP drift gate, thin pool), the route soft-skips — a RouteFailed entry lands on the tape, the amount stays pending, and every other share completes normally. The failed bucket retries next window.
Are 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 feeds and real position tokens.
Why does 5% go to "chaos"?+
A treasury that only makes optimal moves is a treasury that can be modeled, front-run and farmed. The chaos share buys a volatile sibling asset and burns it — deliberately inefficient value that keeps the engine from collapsing into a deterministic payoff matrix.
Can 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) — timelock-protected and visible on-chain — but redrawing the split would require deploying an entirely new account book nobody is obliged to follow.
Is the team able to withdraw anything?+
Only the fixed 10% ops share, via pull payment. The basket principal, the main-pool LP and the burn route have no withdrawal path at all.
When mainnet?+
After the external audit completes and timelocks extend to production values. Watch @lachesion_xyz — the ratification announcement is the only signal worth trusting.
Measured once.
Split forever.
The thread is measured. The scissors are coded. All that is missing is a caller.