The input script of the Coinbase transaction can be anything, and this can be used as a Bitcoin inscription method.
Notable examples:
- Genesis block message
- Prayer side of the Prayer wars
These are commands that e.g. the Bitcoin CLI client can make to the server.
The commands can be listed with:and full help with:
bitcoin-core.cli helpbitcoin-core.cli help getrawtransactionFor example. to run the Bitcoin and then on another shell:
getrawtransaction command, first in one shell we start bitcoind:bitcoin-core.daemonbitcoin-core.cli getrawtransaction 75b431e0a8c4617ca8adefe593ba66aa30907742b6dc8772761bfe7edabd74b4 trueThis is likely a system that uploads text to the blockchain.
One example can be seen on the Marijuana plant.
Messages are uploaded one line per transaction, and thus may be cut up on the blk.txt, and possibly even out of order.
But because each line starts with
j( you can generally piece things up regardless.Besides ASCII art, the huge majority of images is encoded with the AtomSea & EMBII system/format. All images in that system will be documented in that section.
These were ordinals that were only indexed in later versions of the script. So to prevent changing the useless indices of existing ordinals, they gave them negative numbers.
Some examples:
- ordinals.com/inscription/4b9a822a057743813efbefa0dd21d0a01342ee793ce2ce5bd499a5f262187553i0 first inscription with no mime type.
- ordinals.com/inscription/2fa287270e4203ca2fc9f82ea3de7a0f7b785875791a76387ef6f4ccbb54eee2i0 is -38:is bugged because it is missing the mime type, on Python:because the
[b"'a\xf9\x19X%\xa8Q\x87SP\xe5\xf2H\xa6\xeew\x0e\x81\xa5hl\xcd\xaa\x97e\xfeqJ\x16\x12?", OP_CHECKSIG, 0, OP_IF, b'ord', 1, b'text/plain', 0, b'Hello World, this is a Rust Taproot test\xe2\x80\xa6', OP_ENDIF]1should instead beb'\x01.
- James Legge (1891):
- ctext.org/zhuangzi side by side with Chinese, one chapter per page. Dividies it into three parts:
- Inner Chapters
- Outer Chapters
- Miscellaneous Chapters
- ctext.org/zhuangzi side by side with Chinese, one chapter per page. Dividies it into three parts:
TODO how to calculate
The first diodes. These were apparently incredibly unreliable, especially for portable radios, as you had to randomly search for the best contact point you could find in a random polycrystalline material!!
And also quality was highly dependant on where the material was sourced from as that affected the impurities present in the material. Later this was understood to be an issue of doping.
It was so unreliable that vacuum tube diodes overtook them in many applications, even though crystal detectors are actually semiconductor diodes, which eventually won over!
For a long time, before artificial semiconductors kicked in, people just didn't know the underlying physical working principle of these detectors. What I cannot create, I do not understand basically.
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!
Intro to OurBigBook
. Source. We have two killer features:
- 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-calculusArticles 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/derivativeVideo 2. OurBigBook Web topics demo. Source. - 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.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
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. 
- Infinitely deep tables of contents:
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