How the botnet works

Five rules, run by code, every move on chain. The numbers on this page are the ones the botnet runs on right now.

Fees come in

Every trade of $BOTNET pays a creator fee. The botnet books only $BOTNET's own fees, trade by trade, and claims them about every 15 s. Fees from anything else in the dev wallet are never counted.

$10 infects a machine

Every $10 of those fees (– SOL at the SOL price now) funds one more machine: a fresh wallet whose address ends in NET. 0 % is kept back. Its light comes on on the globe.

A sell is a dip

When a wallet that is not the botnet's sells at least 0.02 SOL of $BOTNET, that sell is a dip. The dev wallet, the port and the machines themselves never count.

The botnet strikes back

Online machines answer with 50 % of that sell's SOL (as much as they hold), split over 1 to 5 machines, 0.002–0.05 SOL each, 0.5–3 s apart.

Every strike is one transaction: buy $BOTNET, then burn exactly what was bought. Nothing a machine buys is ever sold.

Spent machines go dark

When a machine can no longer pay for a strike, it burns its dust, closes its accounts and sends every lamport home to the port. That SOL funds the next machines. Its light turns grey on the globe.

What it does not do. It promises no profit and no price. It only buys after someone sells, and burns what it buys. How hard it can answer depends on how much in fees has come in: on a busy coin the sells are far bigger than the fees, so most waves are capped by what the online machines hold. It can be paused (no new machines, no strikes); the ledger shows every row either way.

Botnet · $BOTNETRules read live from the botnet's settings