BANGKA
Also recorded, and not part of the finding above: this picture is on 4 other launches, all of them this same creator's, and this creator has 4 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, 12.6% of the launches whose picture we hold carry one only their own creator reused. 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, BANGKA, mint 8i8cHhmGRZ5nbcRuMkyPEUdNMY1P8MuhGpuhYUtepump, observed at creation 2026-09-04 15:38 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/8i8cHhmGRZ5nbcRuMkyPEUdNMY1P8MuhGpuhYUtepump
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-09-04 15:38 UTC |
| Creator | 7UimBpmRiuxCvSox3CJWx5pa8BkvTrQLGobEpsDAPuQw |
| Creator took | 0.3% 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: 6 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 0 min after launch |
| Curve on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | yes |
| Recorded from | yqzmXume6G8nBqaYjavi7o… slot 444,281,233
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
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-09-04 15:38:34 UTC Slot 444,281,233, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-09-04 15:38:53 UTC +18s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 6 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 seen | 2026-09-04 15:39:05 UTC +31s
1.262e-7 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
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 5 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 12.6% of the launches whose picture we hold carry one only their own creator reused. See them → |
| This ticker | On 43 launches from 30 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 3 other launches, all of them this same creator's. Across the archive, 10.8% of the launches whose document we hold carry one only their own creator reused. See them → |
| This creator | 4 earlier launches, none of which reached a graduation threshold while we watched. Across the archive, 70.3% of launches come from a creator with more than one launch on record. See the creator's launches → |
Pool
| Liquidity | 0.1 SOL |
| Read from chain | 2026-10-27 03:59 UTC, just now |
What this launch claimed to be
| Name | BANGKA |
| Description | BANGKA TOKEN (BANGKA) Bangka Token is a digital asset inspired by the rich heritage, culture, natural resources, and local economy of Bangka. Built on blockchain technology, aims to create a digital ecosystem connecting communities, tourism, local businesses, and Bangka-inspired digital assets. BANGKA — Connecting Bangka’s Heritage, Community & Economy Through Blockchain. |
| Metadata held | sha256 56976ad30b9323a239e058ce8e6007e71c803c87d2fc074798c616b3b55ee88c 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-22 15:20 UTC. |
| Picture held | sha256 f118f5f472e533e71ab01daede42099f08faa962bbfe7fd9d8b60198dcddd6c2 · 248,908 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-12 05:48 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.