For a detailed analysis of one transaction see: Nelson-Mandela.jpg.
Best guess so far, all in ASCII hex of output scripts:
Ordinals are inscriptions created with the protocol described at: docs.ordinals.com/inscriptions.html The protocol was designed by developer Casey Rodarmor, and shares a few similarities with the AtomSea & EMBII protocol.
The protocol also includes a way to have ownership over inscriptions, effectively creating an NFT system on top of the bitcoin blockchain. AtomSea & EMBII also already had such a system however. In either case, Ciro Santilli couldn't give less of a fuck about who owns some random publicly viewable digital asset.
For whatever reason, orinals became extremelly popular compared to the AtomSea & EMBII format, leading to millions os inscriptions, and 10k+ images as of block 830k. They also started to take up a substatial portion of the available block space.
This in turn led to a lot of child porn rediscussion, and people linking back to this page to view earlier inscriptions: incoming links.
Unfortunately, unlike AtomSea & EMBII and even cryptograffiti.info uploads, most ordinals are designed to be just souless bulk collectibles, as with as much artistic merit as any random collectible card set or postage stamps you may find at a newpaper stall. To make things worse many of them are likely algorithmically generated. Eternal September had truly arrived to the Bitcoin blockchain. As a result, machine learning would be almost essential in order to find interesting uploads amidst such bulk.
The source code for the reference uploader and indexer is at: github.com/ordinals/ord
The reference viewer server for the runs at: ordinals.com.
The i0 at the end of the URL above means "inscription 0". This is because a single transaction can have multiple inscriptions.
Some of them have sold for high prices. Magic Eden is a popular interface for trading them:
The ordinals also started taking up large portions of the Bitcoin blockchain:
Apparently the "Taproot" Bitcoin update made it easier to upload image-sized data once again, which had become prohibitively expensive 2023 and much earlier:
Bitcoin addresses are by convention expressed in Base58, which is a human readable binary-to-text encoding invented by Bitcoin.
It is a bit like Base64, but obsessed with eliminating characters that look like one another in popular but stupid fonts like capital "I" and lower case ell "l". As such, any embedded text is rather obfuscated due to this limitations, and people often resort to leet-like replacements such as '1' to represent 'I'.
This seems to be one of the earliest strategies used to encode messages into the Bitcoin blockchain. The first known example appears in 2011. Then starting November 2011, a large number of messages were inscribed n short successsion, presumably by a single person or small group.
The interest in Base58 encoding might have initially arisen with people's desire to have "vanity addresses", that is Bitcoin addresses that have real words in them, much like vanity plates or vanity numbers. Such addresses with long words in them are hard to find while keeping the address spendable, because they have to correspond to a private key. An extreme notable example is:which contains the awkward 13 letter word:
embarrassable
in it. TODO: proof that it is pendable?
Perhaps inspired by this, some people also decided to use Base58 addresses as a way to create more general unspendable inscriptions, even even though the method is much more clumsy and complicated than P2FKHS. There is however a certain art to working under limitations.
Figure 1. . Although it is not solely focused on inscriptions and may also contain functional burn addresses, it is likely that the methods of Khatib/Legout capture the overall trend of base58 inscription counts.
These messages were originally found with: github.com/cirosantilli/bitcoin-inscription-indexer#payload-size-out-utxo-2vals which tracks the largest transactions with unspent outputs.
Bitcoin Burn Addresses: Unveiling the Permanent Losses and Their Underlying Causes later revealed many new ones.
Finding Base58 messages is intrinsically hard for a few reasons
The interesting following transactions contain base58 encoded messages on addresses, sorted chronologically, and heighlighted either due to their earliness or historical or artistic quality:
Related:
  • bb41a757f405890fb0f5856228e23b715702d714d59bf2b1feb70d8b2b4e3e08 999,657 bytes. Joins a bunch of tiny inputs into a single output
  • 623463a2a8a949e0590ffe6b2fd3e4e1028b2b99c747e82e899da4485eb0b6be and 5143cf232576ae53e8991ca389334563f14ea7a7c507a3e081fbef2538c84f6e both have 3,075 outputs of 1 satoshi each and a single input. We were not able to identify any meaningful data in it, file just says data, and there aren't long ASCII strings. However, the outputs were unspent as of 2021, which suggests that they might actually be data.
Analysis of some of them follows.
Test buy 2023-04-10 in the UK:
  • fee: 0.99 pounds, minimum buy: 1.99 pounds
  • bought 10 pounds, minus 0.99 fee, totalled: 0.00039162 BTC (£8.92) presumably after further fees/spread
  • bitcoin price on Google on that day: 22,777.54 GBP / BTC
  • bitcoin transaction fees were about 2.7 BTC on that day
Sending 5 pounds to wallet 12dg2FaiZLp3VzDtLvwPinaKz41TQcEGbs
  • network fee: 0.00001989 BTC
  • total bitcoin cost: -0.00023928 BTC
  • new balance: 15,234 satoshi (39,162 - 23,928).
  • total spent: £5.45
  • time est.: about 30 minutes
This worked and I received 21939 satoshis (23928 - 1989) on Electrum on one of the outputs of transaction 1177268091cbeaacbcaac5dc4f6d1774c4ec11b4bcffafa555cd2775eafb954c.
Sending 1 satoshi back! The lowest fee in Electron is 1120 Satoshis targeting 25 blocks (4 hours). Let's do it. Failed, server forbids dust, minimum is 1000 satoshi. OK, sending 1000 satoshi, at 1139 fee.
In this section we list charitable organizations that support education or research:
Crankstart Foundation by Ciro Santilli 40 Updated 2025-07-16
At crankstart.org/grants the organization's website describes mostly California activities, but they do at least also act in the University of Oxford, see: Section "University of Oxford study costs".
Presumably the name refers to crank starting an old car, as in helping out those in difficulty like poor students get started in life. But is also an obscure slang for a type of handjob according to Urban Dictionary.
LibreTexts by Ciro Santilli 40 Updated 2025-07-16
Follows the "certified teacher only" approach which is in Ciro Santilli's opinion a fatal flaw of most elearning systems out there, OurBigBook.com won't suffer from that!
But that is a very, very good project.
All notes appear to have been extracted from existing notes, as noted on the bottom of each page.
TODO how does it work exactly? Do they ask for permission from authors in every case, including when the content has open license? Or when it has open license, do they just do it? In some cases, the notes have no license, so they must have asked.
TODO what is the source code that authors write? LaTeX or something else? LaTeX feels extremely likely given that it is what most original materials were already written in.
They are attempting a "model up this entire university" thing: phys.libretexts.org/Courses which is good. E.g. they have a bunch of "quantum mechanics ones under: phys.libretexts.org/Bookshelves/Quantum_Mechanics
Appears to be UC Davies-based mostly.
They claim to use this closed source backend: www.nice.com/resources/cxone-expert-knowledge-management? Seriously? For a publicly funded project with low-tech requirements?? It is mind blowing.
Some issues:
OK let's database it:
Fundação Estudar by Ciro Santilli 40 Updated 2025-07-16
Video 1.
What I learned in Harvard part 1 by Jorge Paulo Lemann (2012)
Source. Portuguese talk about his experiences. A bit bably, but has a few good comments:
  • You don't learn the Harvard experience, you absorb it.
  • Being amongst excellent people makes you learn what excelent people are like, just like only by tasting many different types of wine can you know what good wine is like.
    This one does have bias danger though. But detecting greatness, is as type of bias arguably.
It is harder to measure the impact of nonprofits than of for-profits, since you can't just look at their bank balances.
This is one fundamental difficulty of nonprofit work, how to prove that you deserve the investments and not someone else.
Qiskit by Ciro Santilli 40 Updated 2025-07-16
Python library, claims multiple backends, including simulation and real IBM quantum computer.

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 2.
    You can publish local OurBigBook lightweight markup files to either https://OurBigBook.com or as a static website
    .
    Figure 3.
    Visual Studio Code extension installation
    .
    Figure 4.
    Visual Studio Code extension tree navigation
    .
    Figure 5.
    Web editor
    . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
    Video 4.
    OurBigBook Visual Studio Code extension editing and navigation demo
    . Source.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact