ORIGINAL ENIGMA / DEPLOYMENT GUIDE

Deploy three parts.
One complete launch flow.

The Solana program holds the pool. The website connects buyers. A separate delivery worker sends the purchased tokens after launch.

1–60 minutes locked deposit window1% maximum cumulative token cap per walletVirtual curve allocations become tokens at launch

Deploy the Solana program

The artifact to deploy is releases/v1/enigma.so (110760 bytes). It contains the escrow, virtual curve, timed window, 1% maximum and beneficiary-only delivery rules.

Use the local wallet deployment console. It derives the program address from your connected wallet and the reviewed artifact, uploads it, verifies every byte, initializes the configuration and creates the required lookup table. Your wallet keeps upgrade authority.

npm ci
npm run release:preflight
npm run dev

Then open http://localhost:3143/lab/deploy. Connect your deployment wallet, check the current funding quote, and review the exact envelope before signing. This console is intentionally unavailable on a public production site.

Artifact SHA-256: 1a55b7329c62cacdc0454f52410b2c02f9c6eb12dce0e0a8984831c73b3dc729
Public deployment: Review the operations evidence
Last read-only funding check: 2026-11-04T23:46:27.379Z

The console exports the verified deployment descriptor. Save it in lib/enigma-deployment.mjs with public writes and funded acceptance still off. A website deployment does not deploy this program.

Publish the website

Deploy this original enigma-launch source to the existing Enigma Vercel project. The Enigma 1 checkpoint stays preserved. Configure your server-side mainnet RPC and metadata storage in the host.

SOLANA_RPC_URL=<your mainnet RPC>
BLOB_READ_WRITE_TOKEN=<your storage connection>
ENIGMA_WRITES_ENABLED=false

Run npm run build before publishing. Keep the verified program identity and code hash with the website. Buyers choose a whole-minute window, deposit SOL and receive a virtual allocation with a cumulative 1% maximum.

Run the token delivery worker

Deploy a separate Railway service using deploy/airdrop.Dockerfile, one replica and a persistent volume at /data. It watches finalized launches and sends each pending allocation to its original buyer. Buyers do not need to claim or sign.

The owner selected the dev/deployer wallet as delivery payer, configured only in the worker’s private secret settings. It keeps a 0.05 SOL balance floor and 0.1 SOL daily and per-launch spending caps. The worker pays recipient account rent and network fees; pool contributions are never its gas budget.

npm run airdrop:plan
# Read-only. No signer file is read and no transaction is sent.

Before enabling it, configure its public payer, reviewed secret signer, balance floor, daily debit cap and per-launch debit cap. There are no default spending caps that silently activate the service. See docs/AIRDROP_WORKER.md for the exact settings.

The worker saves the original signed transaction before broadcasting. Restarts reconcile that signature; they do not create replacement payments for unknown outcomes. The browser also provides a wallet-reviewed “Send next allocation” fallback.

Prove the public round trip before opening deposits

Review a separately capped acceptance test: a one-minute pool, two buying wallets, the atomic Pump.fun launch, and both beneficiary deliveries. The local, wallet-scoped procedure in docs/MAINNET_ACCEPTANCE.md keeps production paused. Use the wallet-reviewed delivery fallback for this first test, verify the token balances, 1% cap, budget return and rejection of repeat delivery, then record funded acceptance and enable the website and delivery service.

The window closing stops deposits. A finalizer still signs the launch transaction; the delivery worker runs after that launch is finalized. Automatic delivery requires a funded, running worker. The current release has final deposits and no failed-launch refund instruction.