LockCoin
block sync

Autonomous vault · no owner key · UNAUDITED

One ticket.
Locked on buy.
Sold at 10×.

One ticket per wallet, fixed price. The coins land locked — they sit in your wallet and every transfer between holders reverts. When the curve says your position is worth ten times what you paid, the contract burns it and sends the proceeds straight back to you.

At most 1 in 10 can exit at 10×, and only if nobody takes profit earlier. Anyone may sell back to the curve sooner — possibly below what they paid.

If you bought now

The ladder

10× FORCE EXIT
no open positions yet
top = largest position
Ticket
fixed · one per wallet
Front of queue
Open positions
Exit
back to the curve

Mechanism

three rules, written into the contract
01

Buy one ticket

Send exactly the ticket amount. The vault mints along a constant-product curve with a virtual reserve. A second ticket from the same wallet is rejected on-chain.

02

Locked on arrival

Every transfer between holders reverts. You cannot move, list or trade the coins. You can always sell them back to the vault at the current curve price.

03

Sold for you at 10×

Each new ticket lifts the curve and triggers a check. The largest position worth at least ten times its cost is burned and paid out in the same transaction.

Live state

read from the contract on every refresh

Next forced exit

Settlement is permissionless — anyone may call it, and every buy calls it automatically.

Your position

No wallet connected. Everything above is public and live without one.
Wallet
Paid
Coins (locked)
Worth now
Queue rank
Received

Queue · largest first

#OwnerMultipleWorth now

Event tape

BlockEventWalletAmount

Demo console

local chain only

This local Hardhat chain ships twenty funded accounts. Act as one of them, or push a batch of buyers through and watch the first ticket get sold at 10×.

Check the machine yourself

UNAUDITED
Vault
Coin
Chain
Deployed at block
Owner key
none — no such function in the source
Third-party audit
none
File 01 — conservation sim/spiral_sim.py · 2-ticket virtual reserve · 15% burn

IN = OUT + INVENTORY
≤ 1 IN 10 EVER EXITS AT 10×

In
Out
Inventory

Every 10× payout costs ten tickets. Money that came in equals money that went out plus whatever is still held, so the ceiling is arithmetic, not policy — no parameter, no marketing and no amount of volume lifts it. And one in ten is the optimistic bound: it only holds if nobody sells back to the curve early and the vault is drained to pay those exits. In practice fewer get there.

Buying ten tickets from ten wallets does not beat the ceiling. It puts the same money at the front of the same queue, and the people who fund those exits are the buyers who arrive afterwards. Assume you are one of the nine.

BuyersExit at 10×ShareFirst payoutStill openSupply burned
5036.0%ticket #15474.2%
200147.0%ticket #1518615.0%
1000787.8%ticket #1592246.9%

What can go wrong

  • UnauditedNo third party has reviewed this code. There is no owner key — which also means there is nobody who could patch a bug after it ships.
  • Below entrySelling back to the curve is always open, but the curve price can be below what you paid, especially after other people exit.
  • 1/10 is a ceilingIt is an upper bound, not a target and not a promise. Most positions never reach it.
  • Do not transferYour wallet will show a balance, but sending it anywhere fails. Do not try to bridge, list or gift these coins.
  • FakesCheck the vault address in the header against the one on the explorer before sending anything. Copies of this page are trivial to make.

The burn

the one number that only goes up

Every ticket is split in the same transaction. Most of it funds the 10× queue. A fixed slice buys the token on Pons and sends it straight to the dead address — the vault never holds it, so no function exists that could take it back.

Burned
Supply removed
Per ticket
Pons price
How one ticket splits
to the 10× pool bought on Pons and burned

Burned tokens go to 0x…dEaD. Verify independently: the dead address balance should equal the burned figure above.

What actually spirals

Two quantities here can only move one way, and both are on chain. Burned total never decreases: there is no code path that returns a burned token. Circulating supply never increases: the token is fixed supply and the vault only ever removes from it. That is the whole claim — it is a statement about supply, not about price.

What does not spiral

Price. Pons is an open market and anyone holding the token can sell into it at any time. Fewer coins existing does not force a higher price, and we do not claim it does. The burn also costs the queue: money spent burning is money not available to pay a 10× exit, which is why the exit rate is lower with the burn on than with it off. That trade is stated, not hidden.