Mints

The bitcoin.nfts.mints table contains 3 type of mints.

standard mints - the inscription transactions, considered to be the first 'mint' of an ordinal. More info on an inscription.
trustless mints - in which a buyer sends a payment which gets split into multiple utxos which are then used in subsequent reveal transactions to receive the inscription.
- the first transaction is not related to a reveal transaction and does not appear in this table
- the subsequent reveal transactions will appear in this table, 1 row per inscription. Note that these inscriptions which originate from a trustless mint will be tagged trustless_mint instead of standard_mint
launchpad mints - in which a buyer buys from a launchpad and receives the inscription. In this scenario, the inscription may have been pre-minted before selling
- upon pre-minting and before the sale, the inscription appears as a standard mint
- after it is sold on the launchpad, the inscription will be considered a launchpad mint and no longer a standard mint
- launchpad mints can be identified by a non-null platform value

These are the type of trustless mints and launchpad mints current indexed by Allium.

Platform

Protocol

Description

Magic Eden

Premint sales

Magic Eden's launchpad which allows for creators to easily launch new collections. Inscriptions are preminted and sold on the launchpad

Magic Eden

Trustless mint

Magic Eden's inscription service

Column Names

Column Name

Description

Example

platform

The platform used to faciliate the mint. NULL for standard mints

magiceden

protocol

The protocol of the platform.

premint_sale

trade_type

Type of trade. SINGLE_TRADE for single token mint or BUNDLE_TRADE when more than 1 token is minted in a transaction.

SINGLE_TRADE

order_match_type

Type of order.

MINT

buyer_address

Pubkey of the buyer, defined as the party sending the funds

3NQFMfMLXQDjesdbH3UndorSSpRxePLjHr

seller_address

Pubkey of the seller, defined as the party sending the NFT

bc1pv224sdmtw7a6l9n6t2psshn8k5uu65t0yyf5u44xry85fxhelppsxxq84u

_nft_recipient

Pubkey of the party receiving the NFT. May be different from buyer_address

bc1phyjlwz5cjwntte4d5txqze79kv4mk4ww3thapr0hpmvawqyq9wzqglf5yy

_sales_proceeds_recipient

Pubkey of the party receiving the funds. May be different from seller_address

3Gg5VKGRzZ7Xx5afc39pqRexZ17zjkQN8Z

currency_address

Address of the currency used in the mint.

NULL

currency_symbol

Symbol of the currency used in the mint.

BTC

raw_gas_fee

Gas fee of the trade in satoshis. For multi-transaction batch mints, this would be the sum of the following components: 1. gas fee any common transactions divided by size of batch mints 2. gas fee of the individual reveal txn

50088

gas_fee

Gas fee of the trade normalized

0.00050088

usd_gas_fee

USD value of the gas fee

13.471162591

raw_price

Price of the NFT in number of satoshis. (includes fees)

450000

price

Price of the NFT normalized by dividing raw_price by the number of decimals. (includes fees)

0.0045

usd_price

USD price paid for the NFTs in this mint. The USD value of the mint is calculated by multiplying the hourly exchange rate of the currency (e.g. BTC) with the price oracle data source from exchanges.

122.65245

buyer_fees

Fees paid by the NFT buyer.

It might be "unimplemented" if we haven't parse the fees for that protocol yet. Otherwise, it will be a json with 9 columns.

"creator" fees are the ones paid to the nft creator (royalties); "platform" fees are paid to the marketplace; "total" fees are the sum of both fees

Use this syntax to access a specific fee:buyer_fees['usd_total']::double. And don't worry about the unimplemented ones, they will become null

{ "creator": 0.625, "platform": null, "raw_creator": "625000000000000000", "raw_platform": null, "raw_total": "625000000000000000", "total": 0.625, "usd_creator": 0.40125, "usd_platform": null, "usd_total": 0.40125 }

seller_fees

Fees paid by the NFT seller. Similar in structure to buyer_fees

agg_fees

Sum of the fees paid by the NFT buyer and the seller. Similar in structure to buyer_fees

total_mint_quantity

Total number of mints at the transaction level for a batch mint. total_mint_quantity = sum(item_quantity at the same txn_id)

item_quantity

Number of mints at the row level, associated with the movement of a single utxo. In some cases, 2 inscriptions can be in the same utxo, resulting in a bundle trade.

inscription_id

inscription id, composed of the genesis transaction hash with a i0 suffix to represent the first inscription in the tx

1f4301eb3189723067f94a6d336f363419095719c85fed44f482df4c4b668452i0

inscription_name

The inscription name, if available.

bitCroSkull #160

inscription_number

The inscription number, sometimes known as index, if available

810280

collection_name

The collection name, if available.

bitCroSkull

collection_slug

The collection slug, if available. The collection slug is a human-readable, unique identifier.

bitcroskull

content_type

Content type of the inscription

image/png

content_tag

Content tag, which is a reclassification of the raw content_type field to make it easy to analyze.

image video application audio text model others

content_length

Number of bytes of the inscription content

4410

content_protocol

(For json inscriptions with a p key) The protocol of the inscription, derived with json_content['p']

brc-20

content_parsed

(For textual inscriptions) The parsed content of the inscription, could be a utf-8 string or a json object

hello world

{"p":"brc-20","op":"transfer","tick":"pepe","amt":"500"}

is_brc20

Derived with content_protocol = 'brc-20'. To be deprecated for is_token + content_protocol

true

is_token

Used to identify token-like standards.

Derived with content_protocol = 'brc-20' or 'orc-20' or 'orc20'

true

token_tick

The tick of the token-like inscription. Derived with content_parsed['tick']

ordi

token_amt

The amout specified in the token-like inscription. Derived with content_parsed['amt']

100

sats_per_token_tick

Satoshis per token-like amount. Only valid for launchpad mints. Derived with satoshi of the launch / token_amt

1000000

usd_per_token_tick

USD per token-like amount. Only valid for launchpad mints. Derived with USD of the launch / token_amt

1.50

domain_protocol

Domain name protocol used to parse the content

sns bitmap

domain_name

the domain name (portion before the . )

abc

domain_namespace

the domain namespace (portion after the . )

sats

domain_valid

true/false - domains are invalid if they are not the first or are unstable inscriptions

true/false

domain_meta

the metadata of the domain op, such as about, rev, avatar fields.

{"avatar":"cfab194b924f7785c6e453728e1c264b89b74843633278cda3ad3f57576c1e93i0","op":"reg"}

is_domain

true/false - whether the domain name/namespace fit the requirements of sns/bitmap protocols.

Malformed/illegal formats of inscriptions are removed here. There may be some edge cases because sns allows text inscriptions which have lots of noise.

true/false

genesis_fee

Genesis fee of the inscription when it was inscribed. If there are multiple inscriptions created in the tx, this number is divided by the total number of inscriptions created in the transaction.

3455

satoshi_timestamp

The timestamp of the satoshi when it was mined.

40628.07531

transaction_hash

Transaction hash of where this mint occurred.

b3fc902f3e4c5971e07d34342b20ce50a041dcfa74375d754421c5cbe8f68da3

transaction_index

Index of the transaction within the block

block_timestamp

Block timestamp of the mint.

45064.58436

block_number

Block number of the mint.

790330

block_hash

Block hash of the mint.

0000000000000000000554007bb5de9e5a64921be93a15950f73cf7696bccd11

unique_id

Unique ID of this mint.

1f4301eb3189723067f94a6d336f363419095719c85fed44f482df4c4b668452i0

Last updated 11 months ago