Build on Solana

Everything Domino does for a Solana app: start from the template or your own app, sign members in with their wallets, reward balances, NFTs and program calls, and move from devnet to mainnet.

Domino runs quests, points and leaderboards for your Solana app. Members sign in with their wallet, Domino reads devnet or mainnet to check what they did, and your app shows the result. This page gathers every Solana guide in one place.

Start

Pick the path that matches where you are.

Sign members in with their wallet

A member's Solana wallet is how Domino knows them and what its quests read. Choose the sign-in that fits your app:

On Android phones and the Solana Seeker, members connect a wallet app through Mobile Wallet Adapter on an HTTPS page. Call registerMwa() at the top level of a client module that loads with the page, not in a React effect, and it shows in the wallet list; the template registers it already.

Members can also link more wallets after they sign in. A Squads vault or smart wallet can't sign a message, so it links with a transaction that carries Domino's code instead. A quest reads every Solana wallet the member linked.

What a quest can check on Solana

Each check reads Solana mainnet or devnet, and most guides start from a snippet.

Check token balances

Holding SOL, an SPL or a Token-2022 token. Snippet: token-holder.

Reward holding for days

Holding a token every day for a run of days. Snippet: token-hold-streak.

Check NFT holdings

Holding an NFT from a Metaplex Core or Token Metadata collection, compressed NFTs (cNFTs) included, or a Token-2022 token group. Snippet: nft-holder.

Reward Seeker owners

Holding a Seeker Genesis Token, the token every Solana Mobile Seeker comes with, or a token from any other Token-2022 token group. Snippet: seeker-holder.

Check Solana native stake

SOL the member's wallets delegate to your validator, from every stake account they control. Snippet: validator-stake.

Read Solana program accounts

The stake, lock or position your program keeps at an address derived from each wallet, decoded with its Anchor, Codama or Shank IDL. Snippet: solana-program-state.

Check DAO voting power on Realms

Governing tokens the member deposited in a DAO on Realms (SPL Governance), and optionally their vote on a proposal. Snippet: realms-voter.

Check Solana liquidity providers

LP tokens of a Raydium or Meteora Dynamic AMM pool in the member's wallets, with the pool types it can't read. Snippet: solana-lp.

Check on-chain actions on Solana

Calling your program, such as a swap, mint or deposit. Snippet: solana-action.

Check an instruction's arguments

The arguments your program was called with, decoded with its Anchor, Codama or Shank IDL. Snippet: solana-action.

Complete without a check

The same action, completed within about 10 minutes without the member asking. Snippet: solana-action-automatic.

Reward using your Solana program

A wallet.programActivity() tracker records each transaction a member's wallet makes that calls your program, for weekly leaderboards and day streaks without an indexer. Snippet: program-activity.

Complete a quest from a signed Solana transaction

Your app's server sends the signature of a transaction the member signed, and Domino finds the member by the wallet that signed it, with no sign-in to your app first. Experimental.

Check-in stations

The booths or doors of an event, each with an optional time window: the member's signed transaction counts only at a station that is open, and a quest can let each member complete it once per station. Experimental.

Quests as blinks

A member completes the quest from a Solana Action in an X post or a wallet: your server builds the transaction, Domino adds the quest's memo and shows the points. The template serves its memo quest as one.

In-person quests with Solana Pay

Members scan a printed QR code at a booth, door or stage with their mobile wallet, and complete the quest for that station. domino quests stations qr writes the codes.

In-person check-ins with a code

No wallet needed: members scan a printed QR code with their phone's camera, sign in to your app, and complete the quest for that station. Snippet: station-codes. Experimental.

Test with real Solana transactions

domino quests fixtures reads transactions you made on chain and answers a quest's test as ctx.wallet.transactions() would, with your program's instructions decoded.

Award on-chain badges on Solana

Your server mints a soulbound Token-2022 badge, or a compressed NFT for large drops, to the member's wallet when they complete a quest, with your own authority, and a later quest rewards holding it. Snippet: solana-badge.

Start from your program's Anchor IDL

A quest for one instruction of your Anchor program, with its arguments as settings, or for a field of the account it keeps per wallet, with a test, written by domino quests from-idl.

Answers from real Solana transactions

Test a quest against transactions you made on chain: domino quests fixtures turns their signatures into facts.wallet.transactions.

Install a snippet with pnpm dlx shadcn@4.21.0 add https://snippets.domino.run/r/<snippet>.json.

Points, leaderboards and referrals work the same as for any other app. A leaderboard's payout list names the wallets members proved by signing Domino's own message, for you to pay. When an approved settlement's pool is in SOL or an SPL token, pay it on Solana: Domino builds the transfers, and your wallet signs them in Console's Pay on Solana or from the CLI. Solana payouts are experimental.

When your server mints a badge or sends a payout for a completion, record a receipt with the transaction, and your team sees it on the completion in Console, linked to Solana Explorer. Receipts are experimental.

Move from devnet to mainnet

Build against devnet with free tokens, then switch each piece to mainnet before your members arrive.

Point your quests at mainnet

  • Balance and transaction reads. Change chain from devnet's "solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1" to "solana". ctx.wallet.transactions() reads mainnet when you leave chain out.
  • NFT collections. Change the collection's prefix from solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1/nft: to solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp/nft:, with your mainnet collection's address.
  • Token mints and programs. Set your mainnet mint and program in the quest's settings, in code or in Console.

A balance tracker, such as the token-hold-streak snippet's, keeps the chain and token it was published with: add a new tracker for mainnet, with its own key, and point the quest at it.

In the template, both sample quests read the devnet constant in domino/devnet.ts; set it to "solana". A linked Solana wallet reads on both clusters, so members don't link again.

When you set a program, Domino looks for it on mainnet first, then on devnet. A mainnet program that publishes no IDL there decodes its instructions with the IDL it publishes on devnet.

Promote to Live

Quests change in your project's Test environment. Publish them there, try them, then promote Test to Live, where a person on your team approves the change. See test and live.

Sign members in on Live

  • A Live app login key. Live keys need an HTTPS origin: create one for your deployed address, as in develop on localhost, and allow vouching on it as on your Test key. A promotion never copies keys.
  • Wallet sign-in on Live. If members sign in through Domino, check Solana under Settings → Sign-in in Live too. Each environment has its own setting.
  • Your app's environment. In the template, set DOMINO_APP_LOGIN_KEY to the Live key, DOMINO_APP_ORIGIN to the HTTPS address, and IRON_SESSION_SECRET, which production requires.

A project needs a plan when it goes live; see plans and pricing.

Where next

On this page