B20 launch packet
Every launch keeps symbol, metadata, tax settings, creator wallet signature, and BSC context in one manifest.
keccak256 | salt | manifest | BSC
BSC first B20-concept launch substrate
B20 genesis, compressed for BSC.
B20X wraps ticker genesis, tax entropy, metadata commitments, and creator wallet signatures into one BSC-only launch registry.
One path from creation to display.
B20X gives a BSC meme launch a visible route: create the token locally, sign from the creator wallet, then let the launch registry index the CA.
Genesis stack
B20 launch packet
Local SDK command
Creator wallet sync
Visible BSC collection
A launch packet the index can read.
The B20 language is packaging: ticker, image, metadata, tax settings, SkillRoyalty capability, and signer intent travel together instead of living as scattered launch notes.
Local signature
The creator signs the launch packet locally; private keys never touch the registry server.
Salted manifest hash
Launch inputs are hashed so drafts, token addresses, and collection records can be matched.
Verified launch index
Only CA records that pass wallet signature and BSC validation appear in the collection.
The product flow is short.
Create
Use the B20X create page to shape name, ticker, image, socials, and tax settings.
Run local SDK
The actual transaction stays local. The private key never goes to the website.
Broadcast on BSC
The launch is BSC-only, with BNB liquidity context and a creator wallet behind it.
Sync wallet
Sign a lightweight B20X sync message so the registry can discover matching CAs.
Pin snapshot
Known CAs can be pinned as a fallback so the collection remains visible during API hiccups.
Display
The Launches page shows the token, source, scanner state, signer, CA, volume, and market cap.
The loop closes on one chain.
B20X deliberately refuses the multi-chain story. The logic only becomes legible when every launch shares the same execution ground: BSC chain id, BNB liquidity context, one digest grammar, and one collection memory.
Chain id 56 is the first gate. Anything outside BSC is treated as non-B20X noise.
Name, ticker, image, socials, tax, and creator intent are compacted into a canonical packet.
Salt, metadata digest, and manifest digest turn the launch into a repeatable proof surface.
The creator wallet signs the packet locally; the server only receives the signature and public data.
The registry checks CA, chain id, signature recovery, manifest hash, and scanner state.
Only verified creator-wallet records become ranked, searchable, and visible on B20X.
The cryptography is there to organize the launch.
The manifest, hash, signature, tax vector, and attestation wording are not decoration. They give the launchpad a shared grammar for deciding which CAs belong in the B20X collection.
Chain gate
BSC only
Primitive
B20 concept
Digest
Keccak manifest
Attestation
Local signature
Registry
Server verified
Tax
Custom bps vector
B20X role
Genesis + index
What B20X is and is not.
B20X is a BSC launchpad and collection surface around the B20 concept. It is not an official chain standard and it never asks the website to hold a deployer private key. The server stores public launch records, signatures, scanner summaries, and pinned CA snapshots.