# WSATs (Wrapped Satoshis)

{% hint style="warning" %}
**WARNING:** Read every word if you decide to test. These will be worthless. Use at your own risk.
{% endhint %}

## Overview

WSAT is a simple metaprotocol built on top of bitcoin, utilizing ordinals & inscriptions, allowing for ordinal enjoyors to pseudo-inscribe any already ***existing inscription*** onto any ***sat number*** mined in a block less than, or equal to, current block-height.&#x20;

These "wrapped sats" are represented by an inscribed JSON file.

## Purpose

Make all mined sats available to all inscribors, including lost sats in the earliest mined bitcoin, owned by Satoshi Nakamoto.&#x20;

## The JSON

```
{
  "wsat": "1",
  "id": "70a29978d1182b4aea8315b204491227fe7289ac5a4d499f18a5fde31f16f0a7i0",
  "address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"
}
```

[*Inscription link*](https://ordinals.com/inscription/44306309a57b01f039b26db3110f78a1120dd9cb25e08e261f81892ef7e8fd2fi0)

## Syntax

<table><thead><tr><th width="132">Key</th><th width="105">Required</th><th>Description</th></tr></thead><tbody><tr><td>"wsat"</td><td>yes</td><td><em><strong>sat number</strong></em> to be wrapped</td></tr><tr><td>"id"</td><td>yes</td><td>Inscription ID of the <em><strong>existing inscription</strong></em></td></tr><tr><td>"address"</td><td>yes</td><td>The address both the <em><strong>sat number</strong></em>, and the <em><strong>existing inscription</strong></em> must be located for a 100% valid WSAT</td></tr></tbody></table>

## Validity

WSATs shall be in a state of 100% valid, 50% valid, or invalid.&#x20;

**First is first; however, 100% valid beats 50% valid beats invalid.**

Validity is fluid - as the state of the chain updates, so does the state of each WSAT's validity. WSATs can become valid, or invalid, at any moment.&#x20;

<table><thead><tr><th width="176">Validity</th><th width="800">Condition</th><th></th></tr></thead><tbody><tr><td>100%</td><td><p><em><mark style="color:green;"><strong>Both</strong></mark></em> <em><strong>sat number</strong></em> is located in "address",<br></p><p><em><strong>AND</strong></em><br><br><em><strong>existing inscription</strong></em> is located in "address"</p></td><td></td></tr><tr><td>50%</td><td><em><mark style="color:yellow;"><strong>Either</strong></mark></em> <em><strong>sat number</strong></em> is located in "address",<br><br><em><strong>OR</strong></em><br><br><em><strong>existing inscription</strong></em> is located in "address"</td><td></td></tr><tr><td>0%</td><td><em><mark style="color:red;"><strong>Neither</strong></mark></em> <em><strong>sat number</strong></em> is located in "address",<br><br><em><strong>OR</strong></em><br><br><em><strong>existing inscription</strong></em> is located in "address"</td><td></td></tr></tbody></table>

## Summary

The WSAT (the JSON we create) can be moved, sent, traded, etc. The WSAT is created to represent the "unobtainable" ***sat number,*** while also representing the ***existing inscription*** that has now been assigned (or pseudo-inscribed) to ***sat number***. Just like individual sats represent inscriptions, so now do WSATs - subject to the WSATs validity.

Ultimately, those that own the real sats have the real control. Exercise with extreme caution, and remember this is made up nonsense.

## Credit

[*original WSAT proposal by XCPinata.*](https://test-309.gitbook.io/wsat-an-experimental-theory/)


---

# 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://lyndoco.gitbook.io/wsat/wsats-wrapped-satoshis.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.
