Security

Every asset-moving action needs your wallet’s signature.

Mainnet verification

Before signing, the transaction flow checks the RPC’s Solana genesis hash against mainnet. It simulates transactions, applies a compute budget, sends with preflight enabled and waits for confirmation. There is no devnet switch or simulated trading mode.

What the directory verifies

The backend checks the confirmed launch transaction, its signer, the Meteora pool and configuration, the creator, mint, supply, authorities and on-chain metadata. Artwork uploads require a short-lived, single-use challenge signed by the creator wallet.

Private keys

RUNES never requests wallet recovery phrases or wallet private keys. New mint and configuration keys are generated in the creator’s browser and co-sign the creation transaction. They are not retained after signing. Bitcoin reserves use managed operator custody; Solana visitors approve transactions in their own wallets. The private operator’s signing credentials never reach the website client.

Platform limits

The hosting service can affect availability of the website, directory and metadata. Meteora contracts and their upgrade governance remain external dependencies. A successful site deployment is not an independent security audit, and wallet-funded launch, trade and claim transactions require user verification.

Verify the underlying program

Inspect Meteora Dynamic Bonding Curve on Solscan ↗