ClawNetClawNet

Wallet Create Ordinals

Mint new ordinals/NFTs on BSV blockchain using @1sat/actions from the 1sat-sdk.

When to Use

  • Mint new NFT inscriptions
  • Create ordinal collections
  • Inscribe images, text, or files on-chain
  • Store files permanently on blockchain

Usage

# Mint image ordinal
bun run <SKILL_DIR>/scripts/mint.ts <wif> <image-path>

# Mint with metadata
bun run <SKILL_DIR>/scripts/mint.ts <wif> <file-path> <metadata-json>

Using @1sat/actions (Programmatic)

The inscribe action from @1sat/actions handles inscription creation:

import { inscribe, createContext } from '@1sat/actions'
import { OneSatWallet } from '@1sat/wallet'

// Set up context with BRC-100 wallet
const ctx = createContext(wallet, { chain: 'main' })

// Inscribe a file
const result = await inscribe.execute(ctx, {
  base64Content: btoa(fileContent),   // or readFileSync(path).toString('base64')
  contentType: 'image/png',           // MIME type
  map: {                              // Optional MAP metadata
    app: 'myapp',
    type: 'image',
    name: 'My NFT'
  }
})

if (result.txid) {
  console.log('Inscribed:', result.txid)
} else {
  console.error('Error:', result.error)
}

What Gets Created

Minting creates:

  • On-chain inscription of file/data
  • Unique ordinal ID (txid + output index)
  • Permanent, immutable storage
  • Tradeable NFT asset

Deploying a BSV21 Token

To create (deploy) a new fungible token, use deployBsv21Token from @1sat/core:

import { deployBsv21Token, type DeployBsv21TokenConfig } from '@1sat/core'

// DeployBsv21TokenConfig requires: symbol, icon, utxos, initialDistribution
const result = await deployBsv21Token({
  symbol: 'MYTOKEN',
  decimals: 8,
  icon: iconOutpoint,         // outpoint of icon inscription, or IconInscription object
  utxos: paymentUtxos,
  initialDistribution: {
    address: ownerAddress,
    tokens: 21_000_000,
  },
  destinationAddress: ownerAddress,
  paymentPk: paymentPrivateKey,
  changeAddress: changeAddress,
})

Requirements

  • BRC-100 compatible wallet (@1sat/wallet, @1sat/wallet-node, or @1sat/wallet-browser)
  • File to inscribe (image, text, etc.)
  • @1sat/actions for inscription creation; @1sat/core for token deployment
  • Sufficient BSV balance for inscription cost + fees

Cost

Inscription cost depends on file size:

  • Stored on-chain permanently
  • Fee rate is configurable via satsPerKb (default varies)
  • Larger files = higher cost

Output

Returns:

  • Transaction ID (txid)
  • Raw transaction hex (rawtx, optional)
  • Error string (error, if failed)