Explainer
How a byline works
Every coin on BYLINE is signed by a real X account, proven without the X API. The dev's record follows the handle, whichever wallet they use.
Two tricks carry most memecoin rugs. The dev launches from a fresh wallet every time, so nothing they did before follows them. And the coin lists somebody else's X account as its socials, so buyers think they know who is behind it.
BYLINE answers both. A coin can only launch here once its dev has proved, from their own X account, that they are launching this exact coin from this exact wallet. The launch transaction names the handle on-chain, and every coin that handle ever signs lands on one page: its Beat.
Signing a coin, in four steps
1
Your wallet makes the coin's address
Your browser generates the new coin's mint keypair, as on any pump.fun launch. It never leaves your browser.
2
BYLINE writes your code
The code is the first 10 characters of sha256("byline:1:" + your wallet + the mint), in base58. It fits your wallet and this one coin, and nothing else.
3
You tweet it
From the X account you claim, you post the pre-written tweet with the code, then paste its link. Any public tweet works; replies too.
4
BYLINE reads it, then you sign
The server reads the tweet through X's public embed service and checks the author and the code. Only then does it build your launch, which carries a memo naming your handle and the tweet.
Why it holds up
- The wallet signed the handle. The memo byline:1:<handle>:<tweet id> is inside the launch transaction, signed by the creator's wallet.
- The handle posted a code only this wallet and coin fit. The code hashes the creator and the mint, so it is different for every launch.
- An impersonator can't fake it. They can write any handle into a memo, but they can't make that account post the code. Their coin shows as unconfirmed or a mismatch, never under the real handle.
- A real tweet can't be reused. Pointing a new coin at an old proof tweet fails, because the code in it was made for a different mint.
- BYLINE never takes the browser's word. The server re-reads the tweet before it builds a launch and refuses if the check fails. Afterwards the indexer recomputes each code from the creator and mint on-chain and re-reads the tweet itself.
What a byline doesn't prove
It proves control, not honesty. A byline shows that whoever launched the coin controlled that X account at launch. It says nothing about whether they will treat buyers well. A real person can still rug; the difference is that it stays on their record.
Accounts change hands. An X account can be sold, shared or hacked. A byline can't tell who was typing.
Tweets can be deleted. If a proof tweet disappears after BYLINE saw it verified, the coin keeps its byline, marked as since deleted. BYLINE remembers this in memory only, so after a restart such a coin shows as unconfirmed until it can be checked again. A renamed X account shows as a mismatch, since the tweet now belongs to a different handle.
It depends on X's embed service. Tweets are read from X's public oEmbed endpoint, which needs no key. If X changes or turns it off, the launch page says so and launching stops. BYLINE never launches an unverified coin.
The record covers BYLINE only. Coins a handle launched elsewhere, or from wallets it never signed with, don't appear on its Beat.
Reading the stamps
- Verified on X
- The tweet is up, posted by the named handle, and holds the code for this wallet and mint. Counted on the record.
- Tweet since deleted
- BYLINE saw it verified, then X stopped showing the tweet. Still counted.
- Unconfirmed
- The tweet is unavailable and BYLINE never saw it verified, or X's service didn't answer yet. The handle isn't printed as the byline, and it isn't counted.
- Mismatch
- The tweet is by someone else, or doesn't hold this coin's code. Left off the front page and not counted.
Alive or dead: a coin is dead when it is older than 7 days, under $5K market cap and under $100 traded in the last 24 hours. Unknown data never makes a coin dead. Market data comes from Jupiter, with pump.fun as the fallback.
On-chain, and non-custodial
- Coins are real pump.fun launches built by PumpPortal and signed in your own wallet. BYLINE has no program of its own, holds no keys and signs nothing.
- The launch memo is at most 44 bytes, and every launch also touches the registry address FqrRWNbAATtGPAJmqa6T81ZHGeJZ2R886H896izWdcdJ, an address nobody holds a key to. The front page is rebuilt from that address's transactions, not a database.
- Before your wallet sees it, the launch is checked against a list of allowed programs and simulated, and refused if it would cost more than your dev buy × 1.25 + 0.1 SOL.
- Tweet text is read as plain text on the server. BYLINE never shows X's embed code.