Events
Events represent specific actions that happen within the Runes protocol. They are emitted every time a new block is processed by the indexer.
An example "Event" object looks as follows:
Attribute descriptions
id
Unique identifier for an event (in sequential order from when they were processed by the indexer)
type
Represents the type of action the event represents. The nana indexer exposes three different type of events, which are the following
mint
Is emitted any time a new rune is minted
etch
An "etching" in runes is a term that describes a token generation event. When a new rune is "etched", it means that a new rune was created. This event is emitted any time a new rune is created.
transfer
Is emitted any time a rune is transferred during edicts. An "edict" represents a transfer instruction within the runes protocol.
block
The block in which the event ocurred
transaction_hash
The transaction hash in which the event ocurred
rune_protocol_id
A unique identifier representing the rune. Runes are identified by the block and tx index of an "etch" transaction with the format block:tx
rune_name
A readable representation of a rune name with spacers included (the "•")
rune_raw_name
The raw representation of the rune (without spacers included). These are unique to every rune.
amount
The raw amount of the rune transferred with decimals excluded. To get the amount with decimals you can do amount / 10^decimals
decimals
The amount of decimals specified by the Rune during its "etch".
from_address & to_address
For "from_address" represents the source of the runes event. For "to_address" represents the desitnation of the runes from the event. Can be any of the following:
address
The source of a rune transfer/event is a valid address
GENESIS
The source of a rune amount transferred in the event is from aan etch or an edict. This of this as "Coinbase" from bitcoin - it basically means that the runes transferred during the event had no previous owner
UNALLOCATED
Rune transfers/ etchings and mints are processed with "Runestones", which are protocol messages that specify the behavior in which runes are manipulated within the protocol. When there is an "etch" or a "mint", rather than transferring to a bitcoin address or UTXO they transfer to the unallocated rune payload, which is processed by edicts (the last instruction of a runestone).
TLDR: Unallocated means the runes came from a mint or an etch, and the source is unknown because the Runes were created in the transaction.
GET /runes/events/block/:height
Description
This endpoint retrieves all Mint, Etch, and Transfer events from a specific block. It returns an array of events.
URL
/runes/events/block/:height
Method
GET
URL Parameters
height(integer) - The block height from which to retrieve events.
Success Response
Code: 200 OK
Content:
GET /runes/events/tx/:hash
Description
This endpoint retrieves all Mint, Etch, and Transfer events from a specific transaction. It returns an array of events.
URL
/runes/events/tx/:hash
Method
GET
URL Parameters
hash(string) - The transaction hash of the transaction you want to fetch events from.
Success Response
Code: 200 OK
Content:
GET /runes/events/address/:address
Description
This endpoint retrieves all Mint, Etch, and Transfer events from or to an address. It returns an array of events.
URL
/runes/events/tx/:hash
Method
GET
URL Parameters
address(string) - A valid bitcoin address (RPC does not support getting from UNALLOCATED or GENESIS)
Success Response
Code: 200 OK
Content:
Last updated