MMGA
Also recorded, and not part of the finding above: this picture is on 5 other launches from 4 creator wallets in all, and this creator has 2,969 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. Across the archive, 53.7% of the launches whose picture we hold carry one a different creator also used. 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.
Cite this record as: Chain of Title, MMGA (Make Memecoins Great Again), mint Nwjeu8QowWv2VpQF8uDus2yUvWgDs2dTnfvuKNYSLEa, observed at creation 2026-10-27 10:44 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/Nwjeu8QowWv2VpQF8uDus2yUvWgDs2dTnfvuKNYSLEa
Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-10-27 10:44 UTC |
| Creator | HgKfkiGWeToDfhMBjfniZvg2KhHhyw6CdqWQtz6mxVdk |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | unknown 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. |
| Graduated | 1 min after launch |
| Curve on chain | Not 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 sold | not recorded - this venue's trades do not name the wallet |
| Recorded from | 5R4NT2x6XHL5GYnT11XS4Z… slot 462,041,164
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
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
| Created | 2026-10-27 10:44:19 UTC Slot 462,041,164, which is the chain's own clock for this moment. |
| Curve completed | 2026-10-27 10:44:54 UTC +36s 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 picture | On 6 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 53.7% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 93 launches from 72 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.3% wear one that more than one creator wallet has launched. See this ticker's page → |
| This document | The same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 30.7% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| This creator | 2,969 earlier launches, 8 confirmed complete on chain. Across the archive, 70.3% of launches come from a creator with more than one launch on record. See the creator's launches → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 117 other creator wallets, across 195 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% 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
| Name | Make Memecoins Great Again |
| Description | Make Memecoins Great Again launched on launch, from one master wallet, with its ticker, name and picture locked to it. 100% of its creator fees buy $MMGA back from the market and burn it. The fee lock is written once by pump.fun and cannot be changed. |
| Metadata held | sha256 1e23b0ea141e2bc711946d3451e0db86d9fdebc3f4d7481cfffe8310403b32d4 · 573 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 held | sha256 c17f5df121f055d5cffaefbbfed01261d96d917ce2fa34515e90dc9258b94784 · 99,986 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-27 10:44 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.