The origin protocol.

The beginning

An origin is a coin's recorded beginning. The creator sets its name, ticker and image, connects a wallet, and signs those details together with the mint address. That signed snapshot becomes its birth record.

The record stays with the coin's metadata. Its fingerprint can be calculated again, and its signature can be read back to the same creator key. The question is precise: does this record still match the beginning that was signed?

A beginning you can carry.

A hosted check answers a question while its service is available. But a result badge carries neither the signed fields nor the public material needed to repeat the calculation. You cannot reconstruct a signature from a green light.

BORNFIELD closes that gap with portable origins. A birth record packages the launch fields, one-time signature, eight-node return path and creator root into a versioned JSON file. The holder keeps the inputs, rather than just a link to the result.

1. KEEP
   Take the record out of the interface.

   Choose Save birth record on a coin. The file contains public verification material; secret seeds and passphrases are excluded.

2. REPLAY
   Rebuild the result from its inputs.

   Open Readback, select Saved record and load the file. The fingerprint and return path are recomputed locally. A stored success flag is never an input.

3. COMPARE
   Bring your own point of reference.

   Enter a creator root obtained separately. A signature can be internally consistent and still belong to a different key; Readback reports that difference.

The improvement is independence from record-serving infrastructure for saved-record integrity checks. Portability and an explicit trust reference are added around hash-based signing; they do not increase the underlying signature scheme's cryptographic security level.

Set an origin

Create follows three stages. You compose the coin, set its origin, then approve its launch. The creator key is prepared inside that flow; returning creators unlock the same keyspace.

1. 01

   Compose

   Give the coin a name, ticker and image. These are the visible starting points of its birth record.

   DRAFT
2. 02

   Set origin

   Connect the creator wallet, build or unlock its keyspace and register the public root. The key stays in this browser session.

   SIGN
3. 03

   Launch

   Review the draft. At launch, the browser derives the mint and signs the fingerprint with an unused slot, then asks your wallet to approve the pump.fun transaction. The confirmed coin enters the Field.

   ENTER

The birth record

The signed part of a birth record is a launch manifest. BORNFIELD puts its fields in alphabetical order, writes each as a key=value line, and adds the record domain before calculating the fingerprint.

bornfield/launch/v1
creator=<creator wallet address>
image=<image URI>
leaf=<one-time key index>
mint=<token mint address>
name=<token name>
symbol=<token ticker>

Readback repeats these exact steps. A different mint, creator, name, ticker, image URI or slot index produces a different fingerprint. The v1 record signs these fields; the description and social links remain separate metadata.

The mint keypair comes from the creator key's seed and launch index under bornfield/mint/v1. Its public address joins the other signed fields, tying the record to that coin.

Creator keyspace

A creator key opens a keyspace: a Merkle tree containing 256 one-time signing slots. Each slot is a Winternitz key. A record uses one slot, while the shared public root lets every record point back to the same creator key.

Each slot signs one distinct message. The first slot records the creator key's registration. Launch preparation tracks subsequent slots so a used key does not sign a second record. In the signature payload, a slot is represented by the leaf index.

The browser derives the creator key from a deterministic wallet message signature, using BORNFIELD's own domain. An optional passphrase is mixed in with scrypt. Registration links the public root to the creator wallet with signatures from both keys.

Readback

Readback recalculates the birth record's fingerprint and follows its signature to the creator root. Every intermediate hash comes from that calculation. The final comparison gives the record its result.

1. READ 01
   Recover the fingerprint

   Put the recorded launch fields back in canonical order and calculate their SHA-256 digest.

2. READ 02
   Read the signing slot

   Use the fingerprint digits and checksum to complete the 67 WOTS hash chains from the signature.

3. READ 03
   Follow the path

   Compress the chain ends into a leaf, then combine it with the eight recorded sibling nodes.

4. READ 04
   Return to the root

   Compare the calculated root with the birth record's public root. The creator registration connects that root to the wallet.

import { launchDigest } from "@/lib/pq/messages";
import { verify } from "@/lib/pq/xmss";

const birthRecord = metadata.pqc;
const fingerprint = launchDigest({
  mint, creator,
  name: metadata.name,
  symbol: metadata.symbol,
  image: metadata.image,
  leaf: birthRecord.signature.leaf,
});

const result = verify(fingerprint, birthRecord.signature, {
  root: birthRecord.root,
  pubSeed: birthRecord.pubSeed,
  height: birthRecord.height,
});
const status = result.valid ? "Record intact" : "Record mismatch";
// result.computedRoot / result.path

Record interfaces

BORNFIELD assembles the birth record, checks its signature and places the confirmed coin in the Field. The wallet approves the launch, pump.fun creates the token, and Solana executes the transaction.

For code compatibility, the birth record is stored under metadata.pqc. Its public fields include root, pubSeed, height, messageHash and signature. The interface calls messageHash the fingerprint; the creator's secret key stays outside the published record.

The quantum-origin concept is expressed through hash-based signing at the coin's beginning. Readback checks that signed beginning. Token balances and transfers continue to follow Solana's authorization rules.