Launch coins with
a verifiable origin.

Create a coin. Bind its identity. Leave a record anyone can inspect. A launchpad concept for the tokenized NVIDIA ecosystem.

Launch a coin ↗How it works

proposed pair: NVDA
record digest: SHA-256
signature: Hash-based demo

runbit@origin: ~/verifywots-style · sha256 · w=16

runbit@origin:~$ verify --live

># signσ[i] = H^d[i](sk[i])

># verifypk[i] =? H^(15-d[i])(σ[i])

># compressℓ = H(pk[0] || … || pk[66])

># climbroot =? H(…H(ℓ || a[0])… || a[7])

… 62 more chains

msg--------------------------------

leaf--------------------------------

root 0/8--------------------------------

[ .. ] generating one-time keys

Local cryptographic demo

Coins

reference market

/

· Public data from pqc.market ↗. These coins were not launched on Runbit.

← All coins

NEW COIN / 01

A beginning worth
putting on record.

Define your coin and create a local draft of its public manifest.

CREATOR IDENTITY

Start with
your signature.

Create a browser-only signing identity and verify a signed message.

PUBLIC IDENTITYNot created

Identity begins with a key.

ECDSA P-256Local session

A key. A message.
A verifiable connection.

This working example generates a signing key in your browser. The private key remains in memory and disappears when you reload.

Message to sign

A local signing demonstration. It is not a wallet, an on-chain identity, or a post-quantum security claim.

PUBLIC VERIFICATION

Trust the record.
Check the math.

Change a field. Recompute the fingerprint. See whether the record still matches.

project.json

VERIFICATION TRACE

01 Parse project manifest
02 Normalize field ordering
03 Compute SHA-256 digest
04 Compare with reference

Reference digest

Computed digestRun verification to compute.

Ready to verify.

A matching hash confirms the record is unchanged. It does not confirm the creator’s claims, model execution, or investment quality.

RUNBIT / INTRODUCTION

An origin layer
for coin launches.

Discover the coin. Read its record. Follow its origin.

Project lifecycle

A coin starts with a creator and a manifest: its name, symbol, purpose and signature concept. The market now displays real token metadata from pqc.market. Logos and reported figures belong to those external tokens; the collection is a timestamped snapshot, not a live feed or a list of Runbit launches.

Declare→Record→Verify

NVIDIA & the market

The proposed NVIDIA connection is a liquidity pair with a tokenized NVDA asset. The asset, issuer and venue still need to be selected. It does not imply NVIDIA sponsorship, hardware execution or an active market.

Explore NVIDIA NIM documentation ↗

What a proof tells you

The animated terminal generates 67 fresh one-time hash chains, signs a random local message, checks the signature, and recomputes an eight-level Merkle authentication path. “Alter message” runs verification against changed data and produces a genuine rejection. Each cycle uses fresh keys. This educational WOTS-style demonstration is not an audited XMSS implementation, a deployed on-chain signature, or evidence of NVIDIA execution.

The Verify workspace computes a real SHA-256 hash locally. An identical hash means the record matches the reference. This is an integrity check; proving model execution or hardware provenance requires additional infrastructure.

The Identity workspace demonstrates ECDSA P-256 signing through the browser’s Web Crypto API. It does not provide post-quantum signatures or an on-chain account.

Implementation status

Search, filters & project detailsWorking locally

Draft creation & record hashingWorking locally

Browser signing demonstrationWorking locally

Wallet connectionSupported wallets

NVIDIA NIM inferencePlanned

Token launches & NVDA pairNot active

Launch coins witha verifiable origin.

Coins

A beginning worthputting on record.

Start withyour signature.

A key. A message.A verifiable connection.

Trust the record.Check the math.

An origin layerfor coin launches.