Comsats
  • Comsats
  • Apps
    • Inscribe
      • Rune
      • BRC-20 (4-byte)
        • Deploy
        • Mint
        • Transfer
      • BRC-20 (5-byte)
      • ORC-20
        • Deploy, Upgradable, Migration
        • Mint
        • Transfer (Updating)
      • Comparing BRC-20 to ORC-20 Features
      • Fee Description
    • Telegram Bot
      • BRC-20 Trending Bot
      • Inscribe Bot
      • BRC-20 Buy Bot
      • Swap Bot πŸ”œ
    • Launchpad
      • PSBT
      • Launchpad πŸ”œ
    • BRC-20 Bridge
    • Inscription Game
    • Runes
      • Viking Runes Collection (β—ˆ)
      • Convert to Runes Protocol
  • More
    • Comsats Point
    • $CSAS Token
    • Roadmap
    • Official Links
  • FAQ
    • BRC-20 Token Minting Instructions
    • BRC-20δ»£εΈι“Έι€ θ―΄ζ˜Ž
Powered by GitBook
On this page
  1. Apps
  2. Inscribe
  3. ORC-20

Mint

Key
Required
Description

p

yes

Protocol: orc-20 or orc20 case-insensitive.

For wider adoption, any ordinal tokens supporting ORC-20 implementation (like src-20, xrc-20, including wrapped BRC-20) can be included.

tick

yes

Ticker: symbol of ORC-20 in any size, eg. ORC = orc

id

yes

Identifier: inscription number.

Subsequent operations must use inscription number.

eg. initial ORC-20 deployment doesn't require id; but you must specify inscription number of the deployment for subsequent mint, send, migration, and upgrade.

op

yes

Operation: mint event, specify type of event, eg. deploy, mint, send, cancel

amt

yes

Mint Amount: specify the amount to mint, cannot exceed the mint limit set in deploy event

msg

no

Message: custom text, message, manifesto in any size

Example: Mining ORC-20 tokens with ticker orc, identifier 2504160 (Deploy ID Inscription #2504160), the amount to be minted is 10000 (this amount cannot exceed the limit per minting lim)

{ 
  "p": "orc-20",
  "tick": "orc",
  "id": "2504160",
  "op": "mint",
  "amt": "10000"
}

Last updated 1 year ago