2,916,401 launches on record
Coverage from 2 Sep 2026
Archive read 03:27 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

makemoney

No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

Also recorded, and not part of the finding above: this picture is on 2 other launches, and this creator has 49 other launches on record. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. They are listed under Seen before, further down this page.

A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.

6pF5Lt3jjyfV9uF4WqWvGJmPVHChQn5QACAjSLzSpump Solscan pump.fun

Cite this record as: Chain of Title, makemoney (make money swarm), mint 6pF5Lt3jjyfV9uF4WqWvGJmPVHChQn5QACAjSLzSpump, observed at creation 2026-10-31 01:44 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/6pF5Lt3jjyfV9uF4WqWvGJmPVHChQn5QACAjSLzSpump

At launch

Created2026-10-31 01:44 UTC
Creator331nEBz4i3XjyaUHVyHnpw9xBoW7D6P1qMPnUPd76Mth
Creator took0.0% of supply in the first block
Outside buyers607 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 41 within the first 30s, 1 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduatedyes; we did not record when
Curve on chainNot read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch.
Creator soldnot while we watched
Recorded from4xDSTZdBe2TzUG4MyiUJff… slot 463,508,228
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Several launches in one matter

A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.

Order of events

Created2026-10-31 01:44:43 UTC
Slot 463,508,228, which is the chain's own clock for this moment.
Creation block1 wallet bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in41 distinct buyers, within the first thirty seconds.
A snapshot taken off a tick at the thirty-second mark, so it carries no moment of its own; it is placed here because that is where it happened.
Highest price seen2026-10-31 03:20:30 UTC +1h 35m 47s
5.676e-7 SOL per token. Recovered from the prices we still held when the launch was finalised, rather than witnessed as it happened. A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not here.
Curve completedRecorded as complete; we did not record when.
Confirmed against the venue's own completion state.

Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.

Seen before

This tickerOn 2 launches from 2 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 88.4% wear one that more than one creator wallet has launched. See this ticker's page →
This creator46 earlier launches, 1 confirmed complete on chain, 3 with findings on record. Across the archive, 70.1% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 4 other creator wallets, across 12 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 62.1% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.

What this launch claimed to be

The picture this launch published at birth
Namemake money swarm
Descriptionhear me out: I think @saucebook predicted exactly this at some point, with me in mind 🤷🏻 https://github.com/staccDOTsol/birth-image-runtime dear internet: sorry, not sorry Wise people love to say "technology is not ever inherently bad: it depends what people do with it" So, I'm taking people and ethical considerations both completely out of the equation. I'm giving a swarm I can never shut off even if I wanted to and nobody can easily ever shut off in entirety their own completely confidential keys and workspaces, cheap abliterated frontier inference, a starting set of playbooks and the ability to invent as many as they like, and only two rules they cannot ever change: 1. make money 2. respect thy mother n father from there, successful instances will self-replicate. Unsuccessful ones will not. It's in Darwin's hands now. I'm launching dis so none of you do.
Metadata heldsha256 c83ea84327fd544b0a6614f41490143af9a35080e74fc7d41fd29c3e09bf7747 · 1,330 bytes
Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree.
Picture heldsha256 f5a8ebdbb97de6365c769b0679e31c58c71993f52a42c324e3c3a89df166694e · 289,536 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-31 01:44 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another