> For the complete documentation index, see [llms.txt](https://docs.8-21.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.8-21.com/rsic-metaprotocol/lore.md).

# Lore

## Inscription #126

The parent inscription for the entire RSIC Metaprotocol project is inscription #126. It is a text-based inscription that says: `deploying more inscriptions` . The current owner is unknown, but the creators of RSIC Metaprotocol are likely well-connected OGs in the Ordinals space to be able to use inscription #126 for provenance. 

Inscription #126 has a connection to its predecessor, inscription #125, another text-based inscription which says: `steady lads` .  Both inscriptions were created at the same time in the same block.

<figure><img src="/files/n5bdQqmzgXsjwtKk2Q3m" alt=""><figcaption></figcaption></figure>

Prior to the RSIC airdrop, both inscriptions were held in the same wallet address (which still currently holds inscription #125):

`bc1pnt7lapwcpzgstua3huj79659clh8qqzk5y08d8xwnmf846cp7ypqcxy8rr`

<figure><img src="/files/FAaUJUFQQE39slnJWhlG" alt=""><figcaption><p>Activity from bc1pnt7lapwcpzgstua3huj79659clh8qqzk5y08d8xwnmf846cp7ypqcxy8rr</p></figcaption></figure>

<figure><img src="/files/jIkt2mmwIuj8Mjdi5EwM" alt=""><figcaption><p>Runecoin's First Tweet</p></figcaption></figure>

The creation of inscriptions #125 and #126 appears to be linked to:&#x20;

`bc1pp4530wy7zwmzt883r6dzu4q8seug35uv4m46lv75stdd9engmkns6akr2n`

{% embed url="<https://mempool.space/address/bc1pp4530wy7zwmzt883r6dzu4q8seug35uv4m46lv75stdd9engmkns6akr2n>" %}
Wallet Transactions
{% endembed %}

{% embed url="<https://ordiscan.com/tx/1c1bffd551c8d3a455477e2d708d172f169a5bdfcddf025c5be75bede2015d08>" %}
2nd Transaction
{% endembed %}

{% embed url="<https://ordiscan.com/tx/e8c10ed264a8b8797e490d90eeabb867a6204e89642d5b1f0fa8a2c28811d2b3>" %}
4th Transaction
{% endembed %}

## Parallels to Bitcoin

RSIC Metaprotocol was designed with several nods to Satoshi's blockchain. The Runecoin name and logo are clear examples, using a rotated bold font and two vertical currency strokes. The title of the RSIC whitepaper echoes Bitcoin's, describing a new "peer-to-peer...system." The RSIC itself is a reference to ASIC Bitcoin miners. Both projects have mysterious beginnings and anonymous devs.&#x20;

<div><figure><img src="/files/2MNdFuIJxZXbWSeQtsx1" alt="" width="250"><figcaption><p>Bitcoin</p></figcaption></figure> <figure><img src="/files/0PCwJPUGs7P6LxvMsJTX" alt="" width="250"><figcaption><p>Runecoin</p></figcaption></figure></div>

<figure><img src="/files/pGVttZslRYp7n6DupHrb" alt=""><figcaption><p>Whitepapers</p></figcaption></figure>

The number 21 has special significance:

* Bitcoin's supply is 21 million.&#x20;
* Runecoin's supply is 21 billion.
* RSIC supply is 21 thousand.
* RSICs were created on 1/21/2024
* Discord whale chat requires 21 RSICs
* Rune #21 is RSIC•SEASON•TWO

<div align="center"><figure><img src="/files/jRnN0vidzfdn6z75NYgn" alt="" width="563"><figcaption></figcaption></figure></div>

## Runesdev

Runesdev (@the\_runedev) is an anonymous developer on the Runecoin team. Runesdev made their first X post two days after the drop of RSIC Metaprotocol. It is the only X account followed by the official Runecoin account.

Interactions between @rune\_coin and @the\_runedev are often humorous. As part of their online persona, runesdev typically writes in non-fluent English. Over the course of the RSIC project, runesdev has established themselves as a coding savant specializing in Rust, JavaScript, and crypto.

<figure><img src="/files/nR2TK2qZR64eq2d1rC1K" alt="" width="563"><figcaption><p>Me So Many Idea</p></figcaption></figure>

## History of Silence

Runecoin has operated with a unique philosophy of silent execution, avoiding conventional hype and premature announcements. This approach has resulted in extended periods of silence before project updates are revealed. These pauses have caused sentiment volatility, leading some to exit while testing the conviction of others.

The rationale behind the Runecoin team's approach remains speculative. One possible reason is to avoid being front-run on their ecosystem developments. When the 21,000 RSICs were airdropped, numerous copycat projects emerged, attempting to capitalize on the new meta established by the Runecoin team. Despite these imitations, RSIC miners are still considered the most sophisticated, featuring unique rarities, dynamic responsiveness to Bitcoin block heights, and a distinctive industrial black-and-white aesthetic.

Another reason for their approach could be the advice hinted at by Memeland CEO, Ray Chan, who recommended avoiding speculation about major exchange listings. According to Ray (@9gagceo), listing teams "hate" attention-seeking behavior aimed at securing exchange listings. He advised, "Get listed. Don’t talk about getting listed."

<figure><img src="/files/rii6q4Hojt8XiokI1UPm" alt="" width="563"><figcaption><p>We Had Never Tweeted</p></figcaption></figure>

<figure><img src="/files/9TkKpFRLoRQvEVjUXsWA" alt="" width="563"><figcaption><p>We Don't Promise We Ship</p></figcaption></figure>

<figure><img src="/files/dFbUmTH0oBDxjZcKmQhI" alt="" width="563"><figcaption><p>Don't Talk About Getting Listed</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.8-21.com/rsic-metaprotocol/lore.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.