Solana launch · wXMR pairSolana launches use Raydium LaunchLab. Trading and token state stay on Solana. Monero is used only for public launch-provenance records; the Monero lab shows their status. The p/xmr regtest registry is a separate historical prototype with no XMR backing.

Monero lab / launch receipts

a launch.
A second-chain receipt.

A place to inspect grainpad’s Monero record layer. It connects a Solana token to its creator’s approval and the token details recorded at that time.

why it exists

another place to check the launch.

The receipt lets you compare the token’s mint and metadata hash with a creator-authorized record carried on Monero. Trading stays on Solana; the record gives you additional evidence to inspect.

How the record works ↗
  1. 01 / SOLANA

    A token launches

    The mint identifies the token. A metadata hash identifies the recorded token details.

  2. 02 / CREATOR

    The creator approves

    A Solana signature authorizes the record linking the creator, mint and metadata hash.

  3. 03 / MONERO

    A receipt is verified

    The record is checked against the launch and requires 10 Monero confirmations.

verified example

GRAIN: inspect the evidence.

This is the verified example receipt. Check each token’s own receipt for its publication status.

Open the receipt
Inspect record details Mint, metadata and transaction ↗
  • RECORDED ON MONERO
  • MONERO MAINNET PROVEN
  • GRAIN · 20900 CONFIRMATIONS
Launch
GRAIN
Metadata hash
9734421a0d11cd50e6d4aa40e88fa6e177f15d09322703492eab7c713b42b86e
Block height
3,777,783
Confirmations at verification
20900

what this adds

  • A creator-authorized link between the Solana mint and its recorded token details.
  • A Monero transaction you can inspect alongside the Solana launch.
  • A way to compare hashes and signatures rather than rely on a badge alone.

grainpad records launch provenance on Monero mainnet. Trading and token state remain on Solana.

Protocol & verification GRN1 · source and limitations ↗
formatGRN1 v1 / v2185-byte record
tx_extra field189 bytesOne grainpad field per transaction
verified after10 confirmationsFewer stay pending

what gets recorded

Each grainpad launch record is one packed binary GRN1 record of 185 bytes (version 1 or 2; GRAINU uses version 2), carried in a single 189-byte grainpad field in a Monero transaction's tx_extra.
The record commits to the Solana mint and the SHA-256 metadata hash, and names the creator’s Solana public key.
The creator authorizes the record with a Solana (Ed25519) signature. grainpad rejects a record whose signature does not verify.
A repeated record nonce, a repeated Monero transaction, or a second record for the same Solana mint is treated as a duplicate.
grainpad marks a record verified only after 10 Monero confirmations and a match with the Solana mint, metadata hash and creator on the grainpad receipt. Fewer confirmations stay pending.
Indexing is independent and read-only. The format is described on the documentation page; the decoder source is in the public repository graindotfun/grainpad; grainpad’s own daemon client allows read methods only and cannot sign or send.
The public receipt shows the Solana launch and its Monero record side by side.

proof status

Built and verified locally

  • GRN1 v1/v2 encoder and decoder, with the same 185-byte layout and 189-byte extra field; version 2 changes only the creator authorization message
  • Creator Solana signature verification
  • Duplicate and replay protection (nonce, transaction and mint)
  • 10-confirmation pending/verified index logic
  • Receipt integration: the receipt reports not published, pending or verified, and whether the mint and metadata hash match
  • Local pre-relay checks on a constructed transaction: one grainpad field, fee-wallet-only outputs, fee cap
  • A mainnet-compatible Monero transaction carrying a GRN1 record, built and signed locally with wallet2::create_transactions_2; the recorded semantic, non-input consensus and RingCT non-semantic checks passed

Proven on Monero mainnet

  • The GRAIN launch record was published to Monero mainnet in transaction aabbe3be4bb9fa601c95c59e32922e112971dc64c988e33c952478ed10a67d8e
  • It was indexed at block 3777783 and verified after 20900 confirmations
  • The GRAIN receipt shows the same Solana mint and metadata hash as the Monero record

Not yet proven on mainnet

  • A verified Monero record for every public token: each new record must independently finish publication and reach 10 confirmations

GRAIN proves one record. That proof does not activate automatic publication for future tokens. Creator authorization and the bounded automatic publication service are implemented; each launch receipt is the evidence of its own publication. Public token creation remains a separate gate. The earlier fixture construction was never broadcast.

Read the GRN1 specification ↗
Early research archiveRegtest experiment · test funds only

early P/XMR research / historical regtest evidence

Historical research, kept for review. Fakechain only, test funds only, no mainnet execution and no XMR20 compatibility. Not the production record path.

networkOffline regtestNo real XMR
native buy1 test XMRView-only scan verified
tokens out34,277,831.55856834,277,831,558,568 grains

verified local run

The prototype created isolated Monero wallets, mined test blocks, registered a signed payout address, detected an integrated-address payment and replayed the same registry root.

Native spend signature verified
Incoming payment found by view wallet
Deterministic state replay matched

registry root / pxmr-mvp-1

eaba992ddd858d0e230129b5d802d93305ceee33c8e80c8c73c4626302c84543
Simulated XMR reserve
0.99 test XMR
Registry height
1
Settlement sent
No · dry run only
Regtest on-chain anchor
Not implemented in this prototype

limits of the early p/xmr prototype

Metadata and registration

The early prototype uses signed off-chain registration and integrated payment IDs. The separate GRN1 record path uses wallet2 to construct a signed tx_extra field.

Roots and anchors

The spec’s anchor definition refers back to its own transaction hash. The MVP uses a documented, versioned replay hash; it does not claim wire compatibility.

Sell settlement

A native signature can authorize a dry-run sell. A view key alone cannot prove outgoing spends. This historical test did not send a payout, refund or graduation transaction.

Availability and trust

Registration records are required to rebuild state. This is an operator-run experiment, not a permissionless or audited Monero launchpad.

Read the original specification

launch rules & platform settings ↗