> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allium.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Ordinals Inscriptions

The `bitcoin.nfts.ordinals_inscriptions` table contains inscription data aggregated from various ordinals explorer/data sources.

### BRC-20 Collections

The BRC-20 is a standard for creating fungible tokens that are stored on Bitcoin.

It uses Ordinals and Inscriptions to implement contract-like operations such as deploy tokens, mint new tokens, transfer tokens - all facilitated by encoding JSON data as Ordinal inscriptions.

Currently, BRC-20 inscriptions are traced by the `is_brc20/is_token` column, with their metadata columns prefixed with `token_`.

### Token-like protocols

With brc-20 as the leading protocol for fungible tokens, an `is_token` column has been added to allow easy filtering of token-like protocols. Even though we consider only `brc-20` and `orc-20` to be token-like now, we are open to addition of new ones.

## Table Columns

<table><thead><tr><th width="259.3333333333333">Column Name</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td>index</td><td>Index of the inscription.</td><td>4,051,600</td></tr><tr><td>inscription\_id</td><td>Inscription ID assigned. [https://ordinals.com/](https://ordinals.com/)</td><td>a997f335430dc852e42dddeca28ddb4b915cc09d07ed16794bee6d25aeee9db1i0</td></tr><tr><td>inscription\_name</td><td>Inscription name, if available</td><td>BTC Moonbirds 4984</td></tr><tr><td>status</td><td>Status of the inscription. Often inclue the rarity of the inscription (Common, Uncommon, Rare, Legendary, Founders Edition, Lengendary), if applicable.</td><td>Uncommon</td></tr><tr><td>rank</td><td>Rank of the inscription based on rarity, if applicable.</td><td /></tr><tr><td>attributes</td><td>Attiributes of the inscription.</td><td /></tr><tr><td>genesis\_height</td><td>Block height at the genesis of inscription.</td><td>788540</td></tr><tr><td>genesis\_timestamp</td><td>Timestamp of the inscription</td><td>2023-05-06 17:10:56</td></tr><tr><td>content\_type</td><td>Type of content inscribed. Includes text, audio, image, video, application & etc. Note that there is no standard format enforced for the type of content inscribed.</td><td>image/webp</td></tr><tr><td>content\_tag</td><td>Content tag, which is a reclassification of the raw <code>content\_type</code> field to make it easy to analyze.</td><td>image<br />video<br />application<br />audio<br />text<br />model<br />others</td></tr><tr><td>content\_length</td><td>Content length of the inscription in bytes</td><td>420</td></tr><tr><td>parsed\_inscription</td><td>The parsed output of the txwitness data. it would include fields such as <code>content\_type</code>, <code>content\_length</code> & <code>content</code></td><td><code>`{ "content": "7b2270223a226272632d3230222c226f70223a226d696e74222c227469636b223a2272737363222c22616d74223a2231303030227d", "content_length": 106, "content_type": "text/plain;charset=utf-8", "pretty_content": "{"p":"brc-20","op":"mint","tick":"rssc","amt":"1000"}" }`</code></td></tr><tr><td>parsed\_content</td><td>(For textual inscriptions)<br />The parsed content of the inscription, could be a utf-8 string or a json object</td><td><p><code>hello world</code> </p><p /><p><code>`{"p":"brc-20","op":"transfer","tick":"pepe","amt":"500"}`</code></p></td></tr><tr><td>content\_protocol</td><td>(For json inscriptions with a <code>p</code> key)<br />The protocol of the inscription, derived with <code>json\_content\['p']</code></td><td>brc-20</td></tr><tr><td>is\_unstable</td><td>Indicates if the inscription is considered unstable.<br />The definition might change overtime as the ordinals ecosystem evolves<br /><br />Currently, an inscription is considered unstable is input index > 0</td><td>true/false</td></tr><tr><td>genesis\_fee</td><td>The tx paid during the inscription of the ordinal, in satoshis</td><td>19384</td></tr><tr><td>satoshi\_timestamp</td><td>Timestamp where the satoshi was minted in the coinbase block</td><td>2023-05-10 14:25:01</td></tr><tr><td>collection\_name</td><td>Collection name of the inscription, if applicable.</td><td>ordfish</td></tr><tr><td>collection\_slug</td><td><p>Collection slug of the inscription, if applicable. </p><p><br />The collection slug is a human-readable, unique identifier.</p></td><td>ordfish</td></tr><tr><td>collection\_supply</td><td>Collection supply, if applicable.</td><td>100</td></tr><tr><td>collection\_icon</td><td>Collection icon, if applicable.</td><td>5b182278c42d5a74ab4dd9f43826a0a2fce0158000001ed3bdf44873f1378d93i0</td></tr><tr><td>collection\_description</td><td>Description of the collection, if applicable.</td><td>Ordinary literary fish. Look up an ordfish by entering its satoshi code into ordinals.com or aesthetic.computer</td></tr><tr><td>collection\_twitter\_link</td><td>Collection Twitter link, if applicable.</td><td><a href="https://twitter.com/digitpain">[https://twitter.com/digitpain](https://twitter.com/digitpain)</a></td></tr><tr><td>collection\_discord\_link</td><td>Collection Discord link, if applicable.</td><td><a href="https://discord.gg/aesthetic-computer">[https://discord.gg/aesthetic-computer](https://discord.gg/aesthetic-computer)</a></td></tr><tr><td>collection\_website\_link</td><td>Collection Website link, if applicable.</td><td><a href="https://aesthetic.computer">[https://aesthetic.computer](https://aesthetic.computer)</a></td></tr><tr><td>is\_brc20</td><td>Derived with <code>content\_protocol = 'brc-20'</code>. To be deprecated for <code>is\_token</code> + <code>content\_protocol</code></td><td>FALSE</td></tr><tr><td>is\_token</td><td><p>Used to identify token-like standards.</p><p /><p>Derived with <code>content\_protocol = 'brc-20' or 'orc-20' or 'orc20'</code></p></td><td>TRUE</td></tr><tr><td>token\_op</td><td>Operation: Type of event (mint, transfer, reg, deploy).</td><td>mint</td></tr><tr><td>token\_tick</td><td>The tick of the token-like inscription. <br /><br />Derived with <code>content\_parsed\['tick']</code></td><td>ordi</td></tr><tr><td>token\_amt</td><td>The amout specified in the token-like inscription. <br /><br />Derived with <code>content\_parsed\['amt']</code></td><td>1000</td></tr><tr><td>domain\_protocol</td><td>Domain name protocol used to parse the content</td><td>sns<br />bitmap</td></tr><tr><td>domain\_name</td><td>the domain name (portion before the <code>.</code> )</td><td>abc</td></tr><tr><td>domain\_namespace</td><td>the domain namespace (portion after the <code>.</code> )</td><td>sats</td></tr><tr><td>domain\_valid</td><td>true/false - domains are invalid if they are not the first or are unstable inscriptions</td><td>true/false</td></tr><tr><td>domain\_meta</td><td>the metadata of the domain op, such as <code>about</code>, <code>rev</code>, <code>avatar</code> fields.</td><td>`{"avatar":"cfab194b924f7785c6e453728e1c264b89b74843633278cda3ad3f57576c1e93i0","op":"reg"}`</td></tr><tr><td>is\_domain</td><td><p>true/false - whether the domain name/namespace fit the requirements of sns/bitmap protocols. </p><p><br />Malformed/illegal formats of inscriptions are removed here. There may be some edge cases because sns allows text inscriptions which have lots of noise.</p></td><td>true/false</td></tr><tr><td>output\_address</td><td>The receiver address of the ordinal in the inscription tx</td><td>bc1pq5e2zyzc486jwzlnfxtxvg6qutgffeulp3meuyrfc24v3sdyta5s2juu6r</td></tr><tr><td>output\_utxo\_id</td><td>The output utxo id of the ordinal in the inscription tx</td><td>7dfc561a916935c6e27510e8a463b74bfa948ff1467f404b61892817d27804ca:0</td></tr><tr><td>spent\_transaction\_hash</td><td>The transaction\_hash of the spent input utxo in the inscription tx</td><td>80de7ec2cbcf7fa9b14a9833107efe5a453be772abb5e3e697668da9b755f6b1</td></tr><tr><td>spent\_output\_index</td><td>The output index of the spent input utxo in the inscription tx</td><td>8</td></tr><tr><td>input\_addresses</td><td>The owner(s) of the spent input utxo in the inscription tx </td><td>bc1p9qtz90zjg85s458uw453ycnlt32xq5tg5fau5cp7gn6nv0me6xsq70y8xr</td></tr><tr><td>input\_address0</td><td><code>input\_addresses\[0]</code></td><td>bc1p9qtz90zjg85s458uw453ycnlt32xq5tg5fau5cp7gn6nv0me6xsq70y8xr</td></tr><tr><td>spent\_utxo\_id</td><td>The utxo id of the spent input utxo in the inscription tx</td><td>80de7ec2cbcf7fa9b14a9833107efe5a453be772abb5e3e697668da9b755f6b1:8</td></tr><tr><td>value</td><td>The value of the spent input utxo</td><td>853</td></tr><tr><td>transaction\_hash</td><td>The transaction\_hash of the inscription tx</td><td>7dfc561a916935c6e27510e8a463b74bfa948ff1467f404b61892817d27804ca</td></tr><tr><td>block\_hash</td><td>The block\_hash of the inscription tx</td><td>00000000000000000003992047db606364ba3d7fda5d343fc9a3155961a4f976</td></tr><tr><td>block\_number</td><td>The block\_number of the inscription tx</td><td>785817</td></tr><tr><td>block\_timestamp</td><td>The block\_timestamp of the inscription tx</td><td>2023-04-17 14:57:25.000</td></tr><tr><td>unique\_id</td><td>Unique ID of the inscription.</td><td>a997f335430dc852e42dddeca28ddb4b915cc09d07ed16794bee6d25aeee9db1i0</td></tr></tbody></table>
