The Archivooor
$ARCHIVE · the wall · reading
the newest line the archive counted
Every coin's first day, kept.
- coins watched
- 0
- snapshots counted
- 0
- waiting for three
- 0
- damaged
- 0
- crawlers
- 0
- last batch
- none
The wall
every coin over $50K the archive is holding or watching
Damaged
the shelf nobody shows: crawlers that disagreed, sites that stopped answering, and checks that answered instead of the page
Crawlers
the archive has no servers of its own, it has readers
1. bind a wallet
Connect the wallet that holds $ARCHIVE and sign one sentence. The signature proves the wallet is yours. No transaction is sent and no key leaves the wallet.
not bound on this computer
your token
bind a wallet to get one
2. run the reader
npm i puppeteer
curl -O __SITE__/crawler.mjs
node crawler.mjs <your token>It opens each page in a real browser, keeps the visible text, a 1366 by 900 picture of the first screen and the links, and sends back the hash. It never signs anything. Protections are not worked around: when a check answers instead of the site, that is what gets recorded.
3. get paid
Every snapshot your hash wins is one point. At the end of the week the pot is divided by points and paid in SOL, to any wallet holding at least $20 of $ARCHIVE. Points reset with the week that paid them, and a share too small to be worth its own fee is carried into the next week.
The archive runs one reader of its own so the wall is never empty. It is marked house everywhere it appears, it earns no points, and its hash never counts towards the three.
this week
pot: nothing forwarded yet
| # | wallet | counted | points | paid |
|---|---|---|---|---|
| no crawler has earned a point yet | ||||
Rules
the whole thing, in order
- 01 A coin on pump.fun crosses $50,000. The archive reads the site and the X account out of the coin's own metadata and opens a record.
- 02 Three stops are scheduled: +10 minutes, +24 hours, +7 days. A coin that later passes $1M gets one more every month.
- 03 Crawlers take the stop. Each one saves the visible text with the clocks, counters and prices taken out, so two readers a minute apart still get the same hash.
- 04 When three wallets on three different /24 networks send one hash inside a ten minute window, the snapshot is counted and those three get a point each.
- 05 Every ten minutes the counted snapshots go into a merkle root, and the root goes on chain as a memo reading ARCHIVE batch#N <root>.
- 06 Disagree and the snapshot waits for two more readers; the window closes with no three and it is kept as disputed, with every version. A bot check is kept as blocked by a check, never worked around.
- 07 A cheap model reads the first snapshot and lists what the coin promised, quoting the line it came from. It judges nothing, and the whole text sits beside it.
where the coin's fees go
- 50%the crawler pot, paid out every week by points
- 30%buying $ARCHIVE back on Jupiter and burning it
- 20%storage and the work of running it
Creator fees arrive on the keeper's wallet when they are forwarded by hand. Nothing is split before it arrives, and every batch, payout and burn on this page carries the signature that proves it.
A cyanotype keeps a leaf exactly as it was on the day it was put under the glass. That is the whole idea. A coin's site can be rewritten tonight and nobody would know what it said this morning, so the people who hold the coin keep the morning.
None of this is advice about money. A coin can go to nothing and take everything you put in with it.