RUNELAB / DOCUMENTATION

How RuneLab Works

Follow the implemented path from form input to a verified token record.

Launch flow#

Create form
  -> metadata upload API -> Filebase / IPFS metadata
  -> launch transaction preparation
  -> wallet signs and sends on Solana
  -> confirmation check
  -> server-side verification
  -> persisted RuneLab token record

The browser builds the requested launch data, uploads metadata when needed, and asks the connected wallet to sign the serialized transaction. The wallet sends the signed transaction to Solana. The application waits for confirmation before submitting the launch record for verification and persistence.

Metadata upload#

Token artwork is uploaded first, then the metadata JSON references the resulting image. The metadata endpoint returns the immutable content reference used by the launch transaction. Optional website, Twitter, and Telegram fields are included only when valid HTTP or HTTPS URLs are supplied.

Verification and saving#

The server fetches the confirmed transaction and checks the submitted launch against it before creating the application record. A successful wallet signature alone does not create a RuneLab listing.

Token discovery#

After verification succeeds, the application saves the token record. RuneLab uses those saved records for its token directory and token detail pages, so a sent transaction is not treated as discoverable by the application until that record has been accepted.