NULL
—Documentation

Step-by-step guides, integrations and operator setup.

Getting started

  1. Install a Solana wallet such as Phantom, Solflare or Backpack, and connect it with Connect Wallet.
  2. Open Vault and create your Vault key. Pick a strong passphrase, then click Download backup right away.
  3. Shield a small amount of SOL to try it out. Your protected balance shows up once the indexer has picked up the deposit.

Launch a token

  1. Enter a name, ticker (1–10 letters or digits), an image of up to 2 MB, and optionally a description and links.
  2. If you want to be the first buyer, set an initial buy. It is added to the create transaction with 1% slippage headroom.
  3. Review and sign. NULL pins the image and metadata to IPFS, builds the pump.fun create_v2 transaction, simulates it, and only then asks your wallet to sign.
  4. If Privacy Rings is ticked, a second transaction creates the mint's SPL interface. If it fails, the token is still live and you can retry from the token dashboard.

Market cap and volume on the dashboard come from DexScreener. A brand-new token shows "not indexed yet" rather than an estimate.

Vault

  • Shield moves SOL or any SPL / Token-2022 token from your connected wallet into the Vault. The first deposit of a mint also creates its ring interface, and your wallet pays the rent.
  • Private Send pays a registered wallet address, or a null: shielded address (which works without registration). The asset and amount are hidden; the sender and recipient are not.
  • Unshield withdraws to any public address. The destination, asset and amount are public.
  • Split / Merge reorganises your notes. A single proof can spend only a limited number of notes, so merge before sending a balance made of many small deposits. Merging requires the Vault to be registered.
  • Register Vault publishes the Vault's public viewing and nullifier keys. Others can then pay it by Solana address, and merging becomes possible. It is optional.

Stealth Trade

  1. Unlock the Vault, then click + New trading wallet. Download a new backup afterwards, because older backups won't contain this wallet.
  2. Fund it, either from the Vault (an unshield) or directly from your wallet (a public transfer).
  3. Search for a token or paste its mint, choose an amount and slippage, then swap. Quotes and routes come from Jupiter. The swap is checked to need only the trading wallet's signature, simulated, then signed in your browser.
  4. Withdraw by shielding back into the Vault, or by sending to an address.

Sealed P2P

  1. Create an offer: what you sell, what you want, an expiry and, optionally, a single allowed counterparty. You sign a free message to prove you own the wallet.
  2. Send the link through a private channel. The part after #k= is the decryption key, and browsers never send it to servers.
  3. The counterparty accepts by signing a message. Then the seller creates a durable nonce and pre-signs the two-leg transaction.
  4. The buyer clicks Verify, sign & submit. NULL rebuilds the expected transaction, compares it byte-for-byte, checks the seller's signature and that the nonce is still live, then hands it to the wallet.
  5. Afterwards, the seller reclaims the nonce rent. To call off a signed offer, the seller uses Revoke, which closes the nonce on-chain.

Integrations

  • Helius Privacy Rings via @heliuslabs/spr@0.9.0-alpha, running in the browser. RPC, indexer (/v1/spr) and the attested prover are reached through NULL's proxy, so the API key stays on the server.
  • pump.fun via @pump-fun/pump-sdk@4.3.1, using create_v2 (Token-2022) and creator fee collection.
  • Jupiter Swap API v1 (quote + swap) and token search.
  • DexScreener for public market data and charts.
  • Pinata to pin token images and metadata to IPFS.

Operators

The environment variables are listed in .env.example. The minimum for live use:

  • HELIUS_API_KEY for RPC and Privacy Rings. Without it, the Vault can still create keys but shows a development state for everything else.
  • PINATA_JWT for launches.
  • DATABASE_URL (Postgres) for launch records and sealed offers, which are stored as ciphertext.
  • NEXT_PUBLIC_OTC_SETTLEMENT_LIVE=true turns on on-chain P2P settlement. Enable it only after an end-to-end test with small amounts.