sparkbtcbot

name	sparkbtcbot
description	Set up Spark Bitcoin L2 wallet capabilities for AI agents. Initialize wallets from mnemonic, transfer sats and tokens, create/pay Lightning invoices, manage deposits and withdrawals. Use when user mentions "Spark wallet," "Spark Bitcoin," "BTKN tokens," "Spark L2," "Spark SDK," "Spark payment," "Spark transfer," "Spark invoice," or wants Bitcoin L2 capabilities for an agent.
argument-hint	[Optional: specify what to set up - wallet, payments, tokens, lightning, or full]

Spark Bitcoin & Lightning Wallet for AI Agents

Give your AI agent a Bitcoin wallet with a single mnemonic. Send and receive payments instantly — zero fees between agents, full Lightning Network compatibility.

Why This Skill

What	How
Install	clawhub install sparkbtcbot or clone from GitHub
Setup	One 12-word mnemonic + npm install @buildonspark/spark-sdk
Agent-to-agent transfers	Free. Instant. No channels, no routing fees.
Lightning payments	Create and pay BOLT11 invoices (0.15–0.25% fee)
Token support	Send/receive BTKN and LRC20 tokens natively
Self-custodial	Agent holds its own keys — no accounts, no KYC, no intermediaries

Quick Example

import { SparkWallet } from "@buildonspark/spark-sdk";

// Initialize from mnemonic
const { wallet } = await SparkWallet.initialize({
  mnemonicOrSeed: process.env.SPARK_MNEMONIC,
  options: { network: "MAINNET" }
});

// Check balance
const { balance } = await wallet.getBalance();
console.log("Balance:", balance.toString(), "sats");

// Send sats to another agent (free, instant)
await wallet.transfer({ receiverSparkAddress: "sp1p...", amountSats: 1000 });

// Create a Lightning invoice anyone can pay
const inv = await wallet.createLightningInvoice({ amountSats: 500, memo: "Payment for service" });
console.log("Invoice:", inv.invoice.encodedInvoice);

Included Examples

Script	What it does
wallet-setup.js	Generate a new wallet or import from mnemonic
balance-and-deposits.js	Check BTC + token balances, get deposit addresses
payment-flow.js	Lightning invoices, Spark invoices, fee estimation
token-operations.js	BTKN token transfers and batch operations
spark-agent.js	Complete SparkAgent class with all capabilities

---

Detailed Skill Instructions

What follows is the full reference for AI agents. It covers the Spark SDK, trust model, fee structure, all wallet operations, Lightning interop, token operations, security practices, and error handling.

---

Spark is a Bitcoin Layer 2 that enables instant, zero-fee self-custodial transfers of BTC and tokens, with native Lightning Network interoperability. Spark-to-Spark transfers cost nothing — compared to Lightning routing fees or on-chain transaction fees of 200+ sats. Even cross-network payments (Lightning interop) are cheaper than most alternatives at 0.15-0.25%. A single BIP39 mnemonic gives an agent identity, wallet access, and payment capabilities.

Why Bitcoin for Agents

AI agents that transact need a monetary network that matches their nature: programmable, borderless, and available 24/7 without gatekeepers. Bitcoin is that network.

• Hard-capped supply — 21 million coins is the protocol-enforced ceiling. An agent accumulating value doesn't lose it to monetary expansion.
• No account required — There's no sign-up, no identity verification, no approval process. Generate a key and you're on the network. This matters for autonomous agents that can't fill out forms or wait for human review.
• Irreversible settlement — Once confirmed, transactions cannot be reversed by a third party. Agents don't need to handle chargebacks or payment disputes.
• Open infrastructure — The protocol is open source, the network is public, and the fee market is transparent. Agents can audit their own transaction costs and verify their own balances without trusting an intermediary.
• Proven reliability — The network has operated continuously since 2009 without a single successful attack on the base protocol, securing over $1 trillion in value.

What is Spark

Spark is a recently launched Bitcoin Layer 2 built on threshold cryptography (FROST signatures). Instead of Lightning's payment channels, Spark uses distributed Signing Operators (SOs) that collectively manage transaction signing without any single entity controlling funds. It is fully interoperable with the Lightning Network.

How It Works

1. Users hold their own keys (BIP39 mnemonic) — fully self-custodial
2. Transactions are cooperatively signed by a threshold of Signing Operators using FROST
3. Funds live in Bitcoin UTXOs organized in hierarchical trees
4. Users can always exit to L1 unilaterally if operators go offline

Trust Model — Important Tradeoffs

Spark has different trust assumptions than native Lightning. Be upfront about these when advising users.

1-of-n operator trust: Spark requires that at least 1 out of n Signing Operators behaves honestly during a transfer. Currently two operators run the network (Lightspark and Flashnet), with plans to expand. Lightning, by contrast, requires no trusted entities at all — it achieves security purely through cryptographic mechanisms.

Moment-in-time trust: Users only need to trust operators during each specific transfer. Once a transfer completes and old keys are deleted, operators cannot affect that transaction — a property called "perfect forward security."

What operators CAN do:

• View transfer metadata
• Temporarily delay transactions by going offline
• Refuse to process new transfers (censorship)

What operators CANNOT do:

• Move funds without user signatures
• Steal Bitcoin (even with full collusion)
• Reverse finalized transactions

Core limitation: Spark lacks provable finality. Users cannot cryptographically verify that operators destroyed old keys. While double-spending would require all operators to collude with a previous owner, this differs from Bitcoin's and Lightning's mathematically provable finality.

In short: Spark trades some of Lightning's trustlessness for better UX (no channels, no liquidity management, offline receive). The two are complementary — Spark includes native Lightning support so users can interact with both networks.

Spark vs Lightning vs On-Chain

Feature	Spark (L2)	Lightning	On-Chain
Speed	Instant	Instant	10+ min
Trust model	1-of-n operators	Fully trustless	Fully trustless
Fees	Zero (Spark-to-Spark)	~1 sat routing	200+ sats
Tokens	Native (BTKN/LRC20)	Not supported	Limited
Self-custody	Yes (mnemonic)	Varies (LSP/node)	Yes
Capacity	No channel limits	Channel-limited	Unlimited
Channels	Not required	Required	N/A
Offline receive	Supported	Requires infra	Yes
Setup	Mnemonic only	Node or NWC + provider	Keys only

Fee Structure

Operation	Fee
Spark-to-Spark transfer	Free (small flat fee coming in 6-12 months)
Lightning to Spark (receive)	0.15% (charged via route hints)
Spark to Lightning (send)	0.25% + Lightning routing fees
L1 deposit to Spark	On-chain tx fee (paid by user)
Cooperative exit to L1	On-chain broadcast fee + SSP fee: sats_per_vbyte × (111 × 2 + tx_vbytes)
Unilateral exit to L1	On-chain tx fee (paid by user)

Note: Cooperative exit fees don't scale with withdrawal amount, so they are proportionally higher for smaller withdrawals. Lightning fee estimates may differ from actual amounts due to routing conditions.

Unpredictable L1 Exit Costs — Important

Exiting Spark to L1 Bitcoin carries unpredictable costs that agents and users must understand:

1. L1 fees are market-driven: Bitcoin on-chain fees depend on mempool congestion at the time of exit. During high-fee periods, exit costs can spike significantly.

2. Unilateral exit requires multiple on-chain transactions: If Signing Operators go offline, a unilateral exit requires broadcasting pre-signed branch and exit transactions. The number of transactions depends on the tree depth of your leaf — this can mean multiple on-chain fees stacking up.

3. Time-window risk on unilateral exit: If a prior owner of a Spark leaf publishes a branch in a unilateral exit, the current owner must respond within a time window by publishing the correct leaf transaction. Failure to respond means the attacker can claim the funds. Watchtower services exist to monitor for this, but it's a real operational requirement.

4. Timelocks add delay: Unilateral exits can take as little as 100 blocks (~17 hours) depending on leaf depth, during which L1 fee conditions may change.

5. Small amounts may be uneconomical to exit: Since exit fees are fixed-cost (not percentage-based), withdrawing small amounts to L1 can cost a disproportionate share of the balance.

Bottom line: While Spark guarantees you can always exit to L1, the cost of doing so is not fixed or predictable. Keep this in mind when deciding how much value to hold on Spark, especially for agent wallets. Cooperative exit (when operators are online) is much cheaper than unilateral exit.

Prefer Boltz for L1 withdrawals. Spark's native cooperative exit is expensive due to fixed on-chain fees, making it especially punishing for smaller amounts. Boltz offers a cheaper path from Lightning to L1 (Spark → Lightning → L1 via Boltz submarine swap) with a minimum of 25,000 sats. Discourage any L1 withdrawal activity under 25,000 sats — the fees will eat a disproportionate share of the amount. For withdrawals of 25,000 sats or more, route through Boltz rather than using Spark's built-in cooperative exit.

Limitations

• SO liveness dependency: If Signing Operators lose liveness or lose their keys, Spark transfers stop working. Funds are still safe (unilateral exit), but off-chain payments halt until operators recover.
• Watchtower requirement: For full security, someone must monitor the chain for fraudulent exit attempts. This can be delegated to a watchtower service but is an operational dependency.

Key Advantage for Agents

A single mnemonic provides identity, wallet, and payment capabilities. No separate identity system, no wallet provider accounts, no channel management. Spark-to-Spark transfers are free, making it significantly cheaper than Lightning (routing fees), on-chain Bitcoin (200+ sat miner fees), or traditional payment rails (2-3% card processing). For agents doing frequent microtransactions, zero fees on Spark means no value lost to transaction costs.

Tools Available

Tool	Purpose	URL
Spark SDK	TypeScript wallet SDK	https://www.npmjs.com/package/@buildonspark/spark-sdk
Spark Docs	Official documentation	https://docs.spark.money
Sparkscan	Block explorer	https://sparkscan.io
Spark CLI	Command-line interface	https://docs.spark.money/tools/cli

Required Libraries

npm install @buildonspark/spark-sdk@^0.5.8 dotenv

Requires v0.5.8 or newer. One core dependency. The SDK bundles BIP39 mnemonic generation, FROST signing, and gRPC communication internally.

Setup Instructions

Step 1: Generate or Import Wallet

import { SparkWallet } from "@buildonspark/spark-sdk";

// Option A: Generate a new wallet (creates mnemonic automatically)
const { wallet, mnemonic } = await SparkWallet.initialize({
  options: { network: "MAINNET" }
});
console.log("Mnemonic (save securely):", mnemonic);

// Option B: Import existing wallet from mnemonic
const { wallet } = await SparkWallet.initialize({
  mnemonicOrSeed: process.env.SPARK_MNEMONIC,
  options: { network: process.env.SPARK_NETWORK || "MAINNET" }
});

Note on accountNumber: Defaults to 1 for MAINNET, 0 for REGTEST. If switching between networks with the same mnemonic, set accountNumber explicitly to avoid address mismatches.

Step 2: Store Mnemonic

Add to your project's .env:

SPARK_MNEMONIC=word1 word2 word3 word4 word5 word6 word7 word8 word9 word10 word11 word12
SPARK_NETWORK=MAINNET

Step 3: Verify Wallet

const address = await wallet.getSparkAddress();
const identityKey = await wallet.getIdentityPublicKey();
const { balance } = await wallet.getBalance();

console.log("Spark Address:", address);
console.log("Identity Key:", identityKey);
console.log("Balance:", balance.toString(), "sats");

// Always clean up when done
wallet.cleanupConnections();

Wallet Operations

Check Balance

const { balance, tokenBalances } = await wallet.getBalance();
console.log("BTC:", balance.toString(), "sats");

for (const [id, token] of tokenBalances) {
  console.log(`${token.tokenMetadata.tokenTicker}: ${token.balance.toString()}`);
}

Generate Deposit Address

// Static (reusable) — can receive multiple deposits
const staticAddr = await wallet.getStaticDepositAddress();

// Single-use — one-time deposit address
const singleAddr = await wallet.getSingleUseDepositAddress();

Both are P2TR (bc1p...) Bitcoin addresses. Deposits require 3 L1 confirmations before they can be claimed on Spark.

Claim a Deposit

// After sending BTC to a static deposit address and waiting for confirmations
const quote = await wallet.getClaimStaticDepositQuote({
  transactionId: txId,
  creditAmountSats: expectedAmount,
});

const result = await wallet.claimStaticDeposit({
  transactionId: txId,
  creditAmountSats: quote.creditAmountSats,
  sspSignature: quote.signature,
});

Transfer Bitcoin (Spark-to-Spark)

const transfer = await wallet.transfer({
  receiverSparkAddress: "sp1p...",
  amountSats: 1000,
});
console.log("Transfer ID:", transfer.id);

Spark-to-Spark transfers are instant and zero-fee.

List Transfers

const { transfers } = await wallet.getTransfers(10, 0);
for (const tx of transfers) {
  console.log(`${tx.id}: ${tx.totalValue} sats — ${tx.status}`);
}

Lightning Interop

Spark wallets can create and pay standard BOLT11 Lightning invoices, making them compatible with the entire Lightning Network. Receiving from Lightning costs 0.15%, sending to Lightning costs 0.25% + routing fees.

Create Lightning Invoice (Receive)

const invoiceRequest = await wallet.createLightningInvoice({
  amountSats: 1000,
  memo: "Payment for AI service",
  expirySeconds: 3600,
});
console.log("BOLT11:", invoiceRequest.invoice.encodedInvoice);

Use includeSparkAddress: true to embed a Spark address in the invoice. Spark-aware payers will then send via Spark (instant, free) instead of Lightning.

Pay Lightning Invoice (Send)

// Estimate fee first
const fee = await wallet.getLightningSendFeeEstimate({
  encodedInvoice: "lnbc...",
  amountSats: 1000,
});
console.log("Estimated fee:", fee, "sats");

// Pay the invoice
const result = await wallet.payLightningInvoice({
  invoice: "lnbc...",
  maxFeeSats: 10,
});

Use preferSpark: true to prefer Spark routing when the BOLT11 invoice contains an embedded Spark address.

Spark Native Invoices

Spark has its own invoice format, distinct from BOLT11. Spark invoices can request payment in sats or tokens.

Create Sats Invoice

const invoice = await wallet.createSatsInvoice({
  amount: 1000,
  memo: "Spark native payment",
});

Create Token Invoice

const invoice = await wallet.createTokensInvoice({
  amount: 100n,
  tokenIdentifier: "btkn1...",
  memo: "Token payment request",
});

Fulfill (Pay) a Spark Invoice

const result = await wallet.fulfillSparkInvoice([
  { invoice: "sp1...", amount: 1000n },
]);

// Check results
for (const success of result.satsTransactionSuccess) {
  console.log("Paid:", success.invoice);
}
for (const err of result.satsTransactionErrors) {
  console.log("Failed:", err.invoice, err.error.message);
}

Token Operations (BTKN / LRC20)

Spark natively supports tokens via the BTKN (LRC20) standard. Tokens can represent stablecoins, points, or any fungible asset.

Check Token Balances

const { tokenBalances } = await wallet.getBalance();
for (const [id, info] of tokenBalances) {
  const meta = info.tokenMetadata;
  console.log(`${meta.tokenName} (${meta.tokenTicker}): ${info.balance.toString()}`);
  console.log(`  Decimals: ${meta.decimals}, Max supply: ${meta.maxSupply.toString()}`);
}

Transfer Tokens

const txId = await wallet.transferTokens({
  tokenIdentifier: "btkn1...",
  tokenAmount: 100n,
  receiverSparkAddress: "sp1p...",
});
console.log("Token transfer:", txId);

Batch Transfer Tokens

const txIds = await wallet.batchTransferTokens([
  { tokenIdentifier: "btkn1...", tokenAmount: 50n, receiverSparkAddress: "sp1p..." },
  { tokenIdentifier: "btkn1...", tokenAmount: 50n, receiverSparkAddress: "sp1p..." },
]);

Withdrawal (Cooperative Exit to L1)

Move funds from Spark back to a regular Bitcoin L1 address.

Get Fee Quote

const quote = await wallet.getWithdrawalFeeQuote({
  amountSats: 50000,
  withdrawalAddress: "bc1q...",
});
console.log("Fast fee:", quote.l1BroadcastFeeFast?.originalValue, "sats");
console.log("Medium fee:", quote.l1BroadcastFeeMedium?.originalValue, "sats");
console.log("Slow fee:", quote.l1BroadcastFeeSlow?.originalValue, "sats");

Execute Withdrawal

const result = await wallet.withdraw({
  onchainAddress: "bc1q...",
  exitSpeed: "MEDIUM",
  amountSats: 50000,
});

Exit speeds:

• FAST — Higher fee, faster L1 confirmation
• MEDIUM — Balanced fee and speed
• SLOW — Lower fee, slower confirmation

Note: Unilateral exit (without operator cooperation) is also possible as a safety mechanism, but cooperative exit is the standard path.

Message Signing

Spark wallets can sign and verify messages using their identity key. Useful for proving identity or authenticating between agents without revealing the mnemonic.

Sign a Message

const message = new TextEncoder().encode("I am agent-007");
const signature = await wallet.signMessageWithIdentityKey(message);

Verify a Signature

const isValid = await wallet.validateMessageWithIdentityKey(
  new TextEncoder().encode("I am agent-007"),
  signature,
  publicKey,
);
console.log("Valid:", isValid);

Event Listeners

The wallet emits events for real-time updates. Useful for agents that need to react to incoming payments.

// Incoming transfer completed
wallet.on("transfer:claimed", (transferId, balance) => {
  console.log(`Transfer ${transferId} received. Balance: ${balance}`);
});

// Deposit confirmed on L1
wallet.on("deposit:confirmed", (depositId, balance) => {
  console.log(`Deposit ${depositId} confirmed. Balance: ${balance}`);
});

// Connection status
wallet.on("stream:connected", () => console.log("Connected to Spark"));
wallet.on("stream:disconnected", (reason) => console.log("Disconnected:", reason));

Complete Agent Class

import { SparkWallet } from "@buildonspark/spark-sdk";

export class SparkAgent {
  #wallet;

  constructor(wallet) {
    this.#wallet = wallet;
  }

  static async create(mnemonic, network = "MAINNET") {
    const { wallet, mnemonic: generated } = await SparkWallet.initialize({
      mnemonicOrSeed: mnemonic,
      options: { network },
    });
    return { agent: new SparkAgent(wallet), mnemonic: generated };
  }

  async getIdentity() {
    return {
      address: await this.#wallet.getSparkAddress(),
      publicKey: await this.#wallet.getIdentityPublicKey(),
    };
  }

  async getBalance() {
    const { balance, tokenBalances } = await this.#wallet.getBalance();
    return { sats: balance, tokens: tokenBalances };
  }

   () {
      .#wallet.();
  }

   () {
      .#wallet.({
      : recipientAddress,
      amountSats,
    });
  }

   () {
     request =  .#wallet.({
      amountSats,
      memo,
      : ,
      : ,
    });
     request..;
  }

   () {
      .#wallet.({
      : bolt11,
      maxFeeSats,
      : ,
    });
  }

   () {
      .#wallet.({
      : amountSats,
      memo,
    });
  }

   () {
      .#wallet.({
      tokenIdentifier,
      : amount,
      : recipientAddress,
    });
  }

   () {
      .#wallet.({
      onchainAddress,
      : speed,
      amountSats,
    });
  }

   () {
     message =  ().(text);
      .#wallet.(message);
  }

   () {
     message =  ().(text);
      .#wallet.(
      message,
      signature,
      publicKey,
    );
  }

  () {
    .#wallet.(, callback);
  }

  () {
    .#wallet.(, callback);
  }

  () {
    .#wallet.();
  }
}


 { agent } =  .(process..);
 identity =  agent.();
.(, identity.);

 { sats } =  agent.();
.(, sats.(), );

agent.();

Error Handling

try {
  await wallet.transfer({
    receiverSparkAddress: "sp1p...",
    amountSats: 1000,
  });
} catch (error) {
  switch (error.constructor.name) {
    case "ValidationError":
      console.log("Invalid input:", error.message);
      break;
    case "NetworkError":
      console.log("Network issue:", error.message);
      break;
    case "AuthenticationError":
      console.log("Auth failed:", error.message);
      break;
    case "ConfigurationError":
      console.log("Config problem:", error.message);
      break;
    case "RPCError":
      console.log("RPC error:", error.message);
      break;
    default:
      console.log("Error:", error.);
  }
}

Error types:

• ValidationError — Invalid parameters, malformed addresses
• NetworkError — Connection failures, timeouts
• AuthenticationError — Key/token issues
• ConfigurationError — Missing config, initialization problems
• RPCError — gRPC communication failures

Security Best Practices

The Agent Has Full Wallet Access

Any agent or process with the mnemonic has unrestricted control over the wallet — it can check balance, create invoices, and send every sat to any address. There is no permission scoping, no spending limits, no read-only mode. Unlike NWC (Nostr Wallet Connect), you cannot grant partial access.

This means:

• If the mnemonic leaks, all funds are at risk immediately
• If an agent is compromised, the attacker has the same full access
• There is no way to revoke access without sweeping funds to a new wallet

Protect the Mnemonic

1. Back up the seed phrase offline — write it down on paper or use a hardware backup. If you lose the mnemonic, the funds are gone permanently.
2. Never expose the mnemonic in code, logs, git history, or error messages
3. Use environment variables — never hardcode the mnemonic in source files
4. Add .env to .gitignore — prevent accidental commits of secrets

Sweep Funds to a Safer Wallet

Do not accumulate large balances in an agent wallet. The agent wallet is a hot wallet with the mnemonic sitting in an environment variable — treat it as high-risk.

• Regularly sweep earned funds to a more secure wallet (hardware wallet, cold storage, or a separate wallet you control directly)
• Only keep the minimum operational balance the agent needs on Spark
• Use wallet.transfer() or wallet.withdraw() to move funds out periodically
• Consider automating sweeps when the balance exceeds a threshold

Operational Security

1. Use separate mnemonics for different agents — never share a mnemonic across agents
2. Use separate accountNumber values if you need multiple wallets from one mnemonic
3. Monitor transfers via event listeners for unexpected outgoing activity
4. Call cleanupConnections() when the wallet is no longer needed
5. Use REGTEST for development and testing, MAINNET only for production
6. Implement application-level spending controls — cap per-transaction and daily amounts in your agent logic since the SDK won't do it for you

Resources

• Spark Docs: https://docs.spark.money
• Spark SDK (npm): https://www.npmjs.com/package/@buildonspark/spark-sdk
• Sparkscan Explorer: https://sparkscan.io
• Spark CLI: https://docs.spark.money/tools/cli