# Permanent Data Preservation

SRC-101 standard makes operation code and info into Json strings, compresses them into multisig scripts and stores them in **scriptSig** of bitcoin transaction, like what SRC-20 is doing. All these data can't be cropped by miner nodes. It greatly ensures that all data are immutable and can be saved permanently. It also ensures that all types of bitcoin addresses can be supported.&#x20;

<figure><img src="/files/m8oOzjbIxmVCvaQwBW3k" alt=""><figcaption><p>SRC-20 and SRC-101 VS BRC-20</p></figcaption></figure>

SRC-101 doesn't store data in **OP\_ RETURN** which is entirely mutable. We don't want to create a provably-prunable output, everything should be keep in safety.

<figure><img src="/files/WFJpvbL4q8Gwiylp1X2r" alt=""><figcaption><p>SRC-20 and SRC-101 VS RUNES</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://bitname.gitbook.io/bitname/src-101/permanent-data-preservation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
