Transfer (Updating)

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: send event

Type of event: eg. deploy, mint, send, cancel.

n

yes

Nonce: keep track of each partial transaction

amt

yes, when sender is not receiver

Send Amount: always set amount If sender is not the receiver; default to the remaining balance when sending back to sender.

msg

no

Message: custom text, message, manifesto in any size

Example: Send 1000 orc (Deploy ID Inscription #2504160) in two partial transactions. Each transaction must have unique nonce.

  • Step 1: send 1000 (nonce 5) to the receiver address by inscribing send event to receiver

{ 
  "p": "orc-20",
  "tick": "orc",
  "id": "2504160",
  "op": "send",
  "n": "5",
  "amt": "1000"
}
  • Step 2: send the remaining balance back to the sender by inscribing send event to sender

{ 
  "p": "orc-20",
  "tick": "orc",
  "id": "2504160",
  "op": "send",
  "n": "6"
}

Last updated