Skip to content

Cookie Chain quick start

Add Morsel to a Cookie Chain dApp. Install the SDK, set chain="cookie", connect, send COOK and read the balance, with React, without React, or with no SDK at all.

  • Cookie Chain

Cookie Chain is the SVM network Morsel grew up on. Its native coin is COOK. Morsel signs for Cookie Chain in the Chrome extension, in its in-app browser on iPhone and Android, and by QR from a desktop browser.

Cookie Chain
SDK keycookie
Chain idsolana:9wDaBRDgArEUpvhHxGguNkwozsZh4UpG
Older idsgorbagana:testnet-v3
Native coinCOOK, 9 decimals
Public RPChttps://rpc.cookiescan.io
ExplorerCookieScan
  • COOK pays every fee. The connected wallet needs a little COOK before it can send.
  • Two ids, one network. Send the CAIP-2 id. The older gorbagana:testnet-v3 still works, so dApps built before 0.4 keep working. Despite its name, it names Cookie Chain mainnet.
  • COOKIE_CHAIN is still exported. It keeps its 0.3 shape (name, chainId, symbol, rpcUrl, explorerUrl). Its chainId, cookie-mainnet, is a label, not a chain id: don't pass it to the wallet. Use svmChain('cookie').id.
  • Morsel is the wallet here. Other wallets rarely advertise Cookie Chain, so on most desktops the modal shows Morsel and the copy says Morsel supports Cookie Chain.

For every network side by side, see Networks and chain ids.

1. Install

Terminal
npm install @morsel-wallet/adapter @solana/web3.js

The hooks and the connect modal need React 18 or 19, with react-dom. The core works without React.

2. Set the network

App.tsx
import { WalletProvider, WalletModalProvider, WalletModal, ConnectButton } from '@morsel-wallet/adapter';
import { Balance } from './Balance';
import { SendCookie } from './SendCookie';

export default function App() {
  return (
    <WalletProvider chain="cookie" autoConnect>
      <WalletModalProvider>
        <ConnectButton />
        <Balance />
        <SendCookie to="RECIPIENT_ADDRESS" />
        <WalletModal />
      </WalletModalProvider>
    </WalletProvider>
  );
}

chain="cookie" is your app's network. WalletProvider creates the Morsel adapter, finds the other installed Wallet Standard wallets, and opens a read connection to the public Cookie Chain RPC. In production, pass your own endpoint with rpcUrl: a string is for cookie only; for several networks pass a record such as { cookie: 'https://…' } or a function of the chain.

3. Connect

<ConnectButton /> opens the modal. Morsel comes first, its row reading Works on Cookie Chain. Another installed wallet is listed only if it advertises solana:9wDaBRDgArEUpvhHxGguNkwozsZh4UpG. When none does, a note says Morsel supports Cookie Chain. and names the installed wallets that don't, yet. Once connected, the button becomes an account chip with the Cookie Chain mark.

  • Chrome with the Morsel extension: the user approves in the extension.
  • Desktop without it: the modal shows a QR code. The user scans it with the Morsel app and approves on their phone.
  • Phone browser: Continue in Morsel opens your page inside Morsel's browser, where it connects in one tap.

To open the modal from your own button:

TSX
import { useWalletModal } from '@morsel-wallet/adapter';

const { open } = useWalletModal();
<button onClick={() => open()}>Connect</button>;

4. Sign and send a transaction

SendCookie.tsx
import { PublicKey, SystemProgram, Transaction } from '@solana/web3.js';
import { useChain, useWallet } from '@morsel-wallet/adapter';

export function SendCookie({ to }: { to: string }) {
  const { publicKey, sendTransaction } = useWallet();
  const { chain, connection } = useChain();

  async function send() {
    if (!publicKey) return;
    const tx = new Transaction().add(
      SystemProgram.transfer({
        fromPubkey: publicKey,
        toPubkey: new PublicKey(to),
        lamports: 1_000_000, // 0.001 COOK: 9 decimals
      })
    );
    tx.feePayer = publicKey;
    tx.recentBlockhash = (await connection.getLatestBlockhash()).blockhash;

    const signature = await sendTransaction(tx, connection);
    console.log(chain.explorerTx(signature));
  }

  return <button onClick={send} disabled={!publicKey}>Send 0.001 COOK</button>;
}

sendTransaction asks Morsel to sign for Cookie Chain, naming Cookie Chain's chain id, then sends through connection. Morsel also checks the transaction itself: a blockhash exists only on the network that issued it, so Morsel asks the networks which one it belongs to and shows the user that network before they sign.

  • To have the wallet broadcast through its own node instead, call signAndSendTransaction(tx). It resolves with the signature. A wallet that can't send by itself signs, and the transaction goes out through useChain().connection.
  • To sign without sending, call signTransaction(tx).

5. Read the balance

Balance.tsx
import { useWallet, useWalletBalance } from '@morsel-wallet/adapter';

export function Balance() {
  const { connected } = useWallet();
  const { balance, symbol, loading } = useWalletBalance();
  if (!connected) return null;
  return <p>{loading ? 'Loading…' : `${balance} ${symbol}`}</p>;
}

With no connection passed, useWalletBalance() reads from useChain().connection, so this shows COOK on Cookie Chain, and symbol is 'COOK'. balance is in whole COOK; lamports is the raw amount. Call refetch() after a send.

Without React

The core works in any framework, or none.

cookie.ts
import { PublicKey, SystemProgram, Transaction } from '@solana/web3.js';
import { MorselWalletAdapter, connectionFor, svmChain } from '@morsel-wallet/adapter/core';

const chain = svmChain('cookie')!;
const connection = connectionFor(chain); // or connectionFor(chain, 'https://your-rpc.example')
const morsel = new MorselWalletAdapter({ chain });

await morsel.connect(); // call it from a click

const lamports = await connection.getBalance(morsel.publicKey!);
console.log(`${lamports / 10 ** chain.native.decimals} ${chain.native.symbol}`);

const tx = new Transaction().add(
  SystemProgram.transfer({
    fromPubkey: morsel.publicKey!,
    toPubkey: new PublicKey('RECIPIENT_ADDRESS'),
    lamports: 1_000_000, // 0.001 COOK: 9 decimals
  })
);
tx.feePayer = morsel.publicKey!;
tx.recentBlockhash = (await connection.getLatestBlockhash()).blockhash;

const signature = await morsel.sendTransaction(tx, connection);
console.log(chain.explorerTx(signature));

svmChain('cookie') also accepts the chain id or an older id, and answers null for one it doesn't know. connectionFor throws for an unknown network instead of falling back to Solana. Always pass chain: a MorselWalletAdapter built without one keeps 0.3's behaviour, where the wallet's own network applies.

Without the SDK

Talk to Morsel directly with the chain id. You still build the transaction with @solana/web3.js and a Cookie Chain Connection.

The injected provider

In Chrome with the Morsel extension, and inside Morsel's browser on iPhone and Android, Morsel injects window.morsel.

provider.js
import { Connection, PublicKey, SystemProgram, Transaction } from '@solana/web3.js';

const COOKIE = 'solana:9wDaBRDgArEUpvhHxGguNkwozsZh4UpG';
const connection = new Connection('https://rpc.cookiescan.io');
const provider = window.morsel;

await provider.connect();
const lamports = await connection.getBalance(provider.publicKey);

const tx = new Transaction().add(
  SystemProgram.transfer({
    fromPubkey: provider.publicKey,
    toPubkey: new PublicKey('RECIPIENT_ADDRESS'),
    lamports: 1_000_000, // 0.001 COOK: 9 decimals
  })
);
tx.feePayer = provider.publicKey;
tx.recentBlockhash = (await connection.getLatestBlockhash()).blockhash;

const { signature } = await provider.signAndSendTransaction(tx, { network: COOKIE });

Pass network every time. Without one, window.morsel uses its own network, which is Solana, not Cookie Chain. An id Morsel doesn't know is refused with 4901; it is never signed as Solana.

Wallet Standard

standard.ts
import { getWallets } from '@wallet-standard/app';
import { Connection, PublicKey, SystemProgram, Transaction } from '@solana/web3.js';
import bs58 from 'bs58';

const COOKIE = 'solana:9wDaBRDgArEUpvhHxGguNkwozsZh4UpG';
const connection = new Connection('https://rpc.cookiescan.io');
const morsel = getWallets().get().find((w) => w.name === 'Morsel');

const { accounts: [account] } = await morsel.features['standard:connect'].connect();
const owner = new PublicKey(account.address);

const tx = new Transaction().add(
  SystemProgram.transfer({
    fromPubkey: owner,
    toPubkey: new PublicKey('RECIPIENT_ADDRESS'),
    lamports: 1_000_000, // 0.001 COOK: 9 decimals
  })
);
tx.feePayer = owner;
tx.recentBlockhash = (await connection.getLatestBlockhash()).blockhash;

const [{ signature }] = await morsel.features['solana:signAndSendTransaction'].signAndSendTransaction({
  account,
  chain: COOKIE,
  transaction: tx.serialize({ requireAllSignatures: false, verifySignatures: false }),
});
console.log(bs58.encode(signature));

chain is required: Morsel refuses a send without one, or with an id it doesn't know. Wallet Standard returns the signature as bytes; bs58 turns it into the usual string. See Wallet Standard.

Next

  • Connect kit: every prop, hook and component, and upgrading from 0.3.
  • Provider API: the injected provider in full.
  • Deep links: send phone users straight into Morsel's browser.

Try one of these