The OBSIG process
From declaration to verification.
Understand how OBSIG records what a token creator declares, how a launch is prepared, and how its history can be independently inspected.
01 — Declare
Say what the coin is, before it exists
Five steps, one signature, and nothing on chain.
- Connect a Solana wallet.
- Enter the token details: name, ticker, supply and dev buy.
- Say what the token is for, in your own words.
- Sign the declaration message with that wallet.
- OBSIG records the declaration and seals its cryptographic digest.
Signing a declaration does not launch a token and does not spend SOL.
- Name
- Lantern Protocol
- Ticker
- $LTRN
- Supply
- 1,000,000,000
- Dev buy
- 0 SOL
- What it is for
- a treasury the holders vote on
- Declared by
- 4wTV1YmiEkRvAtNtsSGPtUrqRYQMe5SKy2uB4Jjaxnjf
bba74b319c51e0f0005cf0c16e8e8ccd89bd45d7ab235109ca7791c4058b5623
Hash the fields above yourself and you get this value. Nothing was signed, nothing was created on chain, and no SOL moved.
02 — Launch
Built from the declaration, signed by you
The launch flow runs on this token's own page. Every step below is implemented; none of it is a plan.
- 01MetadataThe picture and the links are stored and hashed. The document is frozen from this point.
- 02PrepareThe transaction is built from the sealed declaration and simulated against mainnet.
- 03ReviewAll sixteen accounts, the program, the recorded creator and the measured cost are shown.
- 04SignYour wallet signs. The browser re-checks the bytes against the policy before it asks.
- 05Broadcast (off)Switched off on this deployment. The transaction is judged, and the server refuses to send it.
- 06StatusTwo independent endpoints are asked about the signature until they agree or disagree.
03 — Verify
Two endpoints have to agree
A launch is not sealed because this server believes it happened. It is sealed because two independent endpoints described the same transaction.
Declaration digest
The sha256 of what you signed. It is fixed when you declare and every later entry commits to it.
Transaction signature
The handle a cluster knows your launch by. A caller may supply one; it is a claim until it is checked, never a fact.
Independent verification
Both endpoints must return the same transaction byte for byte, finalized, with no error and the same slot. One endpoint is not a second opinion.
The sealed record
Only then does a launch entry join the chain, carrying the signature, the mint and the slot it was read at.
04 — Explore
Read anyone's record, including ours
Nothing here needs a wallet. The record is public because that is the product.
- Search by name, ticker, chain id, wallet or mint.
- Filter by what the record says: launched, read, declared or unreadable.
- Open a token page to see its declaration beside what the chain said since.
- Inspect the full chain of seals, each committing to the one before it.
- Copy any digest or signature in full, or take the raw JSON.
- Name and tickerout of the signed declaration
- Chain idthe address of this record
- Declared bythe wallet that signed it
- Sealshow many entries the chain carries
- Slotwhen the chain was last read back
- Statuslaunched, read, declared or unreadable
Questions
The five that matter
Each answer describes what the code does, not what a launchpad usually says.
Does declaring a token cost SOL?
No. Declaring asks your wallet to sign a message, not a transaction. Nothing is created on chain, no account is opened and no fee is paid. The only thing that happens is that OBSIG writes your declaration into its record and seals it.
Does declaring automatically launch a token?
No. They are two separate acts with two separate signatures. A declaration is a statement about a coin that does not exist yet. Launching happens later, from that token's own page, and it is the only step that can touch the chain.
What does verified mean?
That two independent RPC endpoints were asked about the signature and agreed on everything: the transaction is finalized on both, it recorded no error, the slots match, and the whole transaction is byte for byte identical between them and identical to what was prepared. Only then is a launch sealed into the record. Anything less is reported as pending or rejected, never as verified.
Does OBSIG guarantee a token's safety or performance?
No, and it never will. OBSIG does not promise a coin will do well. It promises the record cannot be changed. A sealed declaration tells you what somebody committed to before the coin existed; what they do afterwards is on the chain, and this site publishes that too, including when the two disagree.
Can I inspect the proof myself?
Yes, and that is the point. /api/chain serves every field that goes into every digest. Each digest is a sha256 over the canonical JSON of its own entry, and each entry carries the digest of the one before it, so you can recompute the whole chain and disagree with our verdict.
Ready to launch with proof?
The declaration is sealed before the coin exists. The reading is sealed after it does. Both stay published, even when they disagree.