# Manually unravelling inscriptions from a single UTXO with Sparrow wallet (experimental)

This tutorial only works:\
When the sat offsets are far enough apart so the padding between them can cover transaction fees. If they are all \~546 sats apart you may be able to split them from uninscribed BTC it is mixed with but you'll need another solution to separate them, [explained here](https://github.com/leather-wallet/extension/issues/3483#issuecomment-1569071815).

When fee rates on the bitcoin network are low enough for the padding to cover the fee and leave a modest 546 sats with the inscription (to stay above the dust limit). <br>

Diagram of a normal UTXO with a single inscription:

![](https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2FPUBppdU4Vh1Mv9Qvn1fJ%2Fimage.png?alt=media\&token=ec9d0a36-2212-4660-a97b-a82d01982ab1)\
\
Diagram of an UTXO with multiple inscriptions. This is non-standard.&#x20;

<figure><img src="https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2Fwwir3vL0UKNSjQA4r3HU%2Fimage.png?alt=media&#x26;token=aaa000a9-9a2f-483f-9175-87d8eb37e716" alt=""><figcaption><p>One UTXO with 5 inscribed sats, with enough uninscribed sats (padding) in-between to recover them manually</p></figcaption></figure>

### Step 1 confirm the issue.&#x20;

A transaction like this combined many inscriptions into a single bitcoin output (UTXO) these inscriptions now share one UTXO and the sat offsets are non-standard. A normal offset is 0, which means the first sat in the UTXO is inscribed. \
Example transaction: <https://mempool.space/tx/8162eb8dc7c7fe3677b47d1802c92db1a4d9c7e7e53f306fa03e830a65c018e9>

<figure><img src="https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2FURpRbnxICsbMoc2BNNFW%2Fimage.png?alt=media&#x26;token=92a17656-a319-4034-8f4c-d2c965df28d9" alt=""><figcaption><p>7 inputs (10000 sats each), a single output (42030 sats) and a mining fee (27970 sats). </p></figcaption></figure>

Checking the output on an API like this will show the inscriptions in the output as long as you have not send them elsewhere, change the transaction hash and output (:0 at the end) to view the situation for your transaction/output: \
<https://ordapi.xyz/output/8162eb8dc7c7fe3677b47d1802c92db1a4d9c7e7e53f306fa03e830a65c018e9:0>&#x20;

<figure><img src="https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2F3zZTsjlJcCR2fdn8Wnvx%2Fimage.png?alt=media&#x26;token=ef5a5480-710e-4b3e-b759-b103ead1a6ff" alt=""><figcaption><p>The first output is ":0" the second would be ":1", then ":2" etc. </p></figcaption></figure>

An output with inscriptions will look like this, the long inscription numbers are displayed:

<figure><img src="https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2FKBhY8UdmLJOqXHPz5nwm%2Fimage.png?alt=media&#x26;token=5f4a58c4-461d-4933-aa6e-4ba732e9ee4b" alt=""><figcaption><p>An output as displayed by the ordapi.xyz/output API, this one has 5 inscriptions. 1 would be normal and wanted.</p></figcaption></figure>

### Step 2: Note the inscription hashes in a spreadsheet

8ed73bedb37b6d2605d5c2706f43d56f0f34c8e66381ea4b5c2612f25f6fb4bci0\
8997bcb90cf6e5eb2bebadc12d5fb8bde5f155c62cff15a896aa58d67a6cd2c8i0\
13317bdd1f8d5d51b5449a309aee0af23539d5c5996ad717b78c6650b3e4b942i0\
69622c541fef9858ce7a8999d53fe9b917db9c839f0584b80413c502cf2d5d2di0\
7580e0c00a47d402824ebbde4a5cbfe8d7010347e2772ae48b654f3f88d03efei0

### Step 3: Check sat offsets per inscription to find where they are in the "pile"

Check all these inscriptions on an ordinal explorer that displays the sat offset. For example ordinals.hiro.so. Search for the inscription numbers found in step 2 on the ordinal explorer to find:

<figure><img src="https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2F6fWfch5GMYYU3Ssfah9t%2Fimage.png?alt=media&#x26;token=df84d721-f20f-43ce-ac25-57dec88e08c5" alt=""><figcaption></figcaption></figure>

Add a column in your spreadsheet and note these offsets next to the ordinal number. You can also add the short ordinal number for easier identification. Once you have all of them use the spreadsheet to order them from low to high offset.&#x20;

| Sat offset | Short inscription number | Long inscription number                                            |
| ---------- | ------------------------ | ------------------------------------------------------------------ |
| 0          | 9055598                  | 8ed73bedb37b6d2605d5c2706f43d56f0f34c8e66381ea4b5c2612f25f6fb4bci0 |
| 10000      | 9055600                  | 8997bcb90cf6e5eb2bebadc12d5fb8bde5f155c62cff15a896aa58d67a6cd2c8i0 |
| 20000      | 9055597                  | 13317bdd1f8d5d51b5449a309aee0af23539d5c5996ad717b78c6650b3e4b942i0 |
| 30000      | 9055599                  | 69622c541fef9858ce7a8999d53fe9b917db9c839f0584b80413c502cf2d5d2di0 |
| 40000      | 8898358                  | 7580e0c00a47d402824ebbde4a5cbfe8d7010347e2772ae48b654f3f88d03efei0 |

\
Ideally, we separate the inscriptions and get them on a 0 sat offset. But we can settle for separating them and having a non-zero offset in case we make a mistake but let us be careful to double-check the number of uninscribed sats between inscriptions after every separation. This will increase the success rate.&#x20;

### Step 4. Determine the first amount to send to separate the first inscription (from the top of the pile):

Total output: 42030 sats - sat offset: 40000 sats = difference 2030 sats

<figure><img src="https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2FiudfxEnXna6IbdejYGkT%2Fimage.png?alt=media&#x26;token=12ac6c4d-13ca-441c-9ece-083b49a89d75" alt=""><figcaption><p>Splitting the sats from the pile is a step by step process. The first one is inscription 8898358.</p></figcaption></figure>

It is important to set a fee that leaves enough sats with the inscription so it stays over the dust limit. For safety you should leave 546 sats with the inscription 2030-546= 1484 sats for the fee would be available.&#x20;

### Step 5. Import the Leather seed into Sparrow wallet

a. Install and open Sparrow wallet from <https://sparrowwallet.com>

b. Select "new wallet" from the "File menu.&#x20;

c. Name your wallet

d. Set the "script type" to "Taproot" at the top of the settings page.

e. Select New or imported Software wallet" from under "Keystores"

f. Select "Use 24 words" and enter your Secret Key from Leather. Note you must use the exact same seed phrase/Secret Key as the one you use in Leather, or these instructions won't work. Do not use a passphrase.

g. Select "Create Keystore" then "Import Keystore". <mark style="color:blue;">Note: m/86'/0'/0' assumes you want to access the Ordinal Inscription address on Account 1 in the Leather extension. If, for example, you want to access Account</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**269**</mark> <mark style="color:blue;"></mark><mark style="color:blue;">in Leather, change the derivation path to m/84'/0'/</mark><mark style="color:blue;">**268**</mark><mark style="color:blue;">'</mark>

h. Select "Apply" in the bottom right corner.

i. Select "No password" or set a password.

### Step 6. Find the right UTXO in Sparrow from the sidebar

![](https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2FHr8jURlZZwIhvaNwmhdz%2Fimage.png?alt=media\&token=bff0f3fe-6a12-4995-b343-f419329fdbef)<br>

### Step 7. Right click the UTXO (42030 sats in this first case) to send selected.&#x20;

<figure><img src="https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2FKaA4C21uduRKyL1qeUeQ%2Fimage.png?alt=media&#x26;token=e5fe48d8-69f1-4cd5-acc5-84844581e18c" alt=""><figcaption><p>Selecting the UTXO to send, in this case ...<a href="https://ordapi.xyz/output/8162eb8dc7c7fe3677b47d1802c92db1a4d9c7e7e53f306fa03e830a65c018e9:0">018e9:0</a> </p></figcaption></figure>

It is important not to add any other UTXO's or it will change everything and mix more BTC with the existing UTXO which is not wanted.&#x20;

### Step 8. Set a taproot address to receive the inscription

### Step 9. Set the amount and fee very precisely&#x20;

Set the Amount to send and fee very precisely so the fee and amount together equal the top of your pile exactly up to the first inscribed sat (in this first case total 2030 sats).&#x20;

<figure><img src="https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2FjhVhAp2Y230SP15Sv9FG%2Fimage.png?alt=media&#x26;token=630edadc-b3dd-4f07-869f-d1263be7a433" alt=""><figcaption><p>Set Amount and Fee</p></figcaption></figure>

### Step 10. Wait for confirmation on the Bitcoin blockchain

The fee rate can be to low to get processed right away. In this case 9.64 sats per vB is lower than the current average. Wait patiently!

### Step 11. Check both the outputs on the new transaction

1\. Check that the first output indeed transfers the first inscription from the pile.\
2\. The second output is everything left from the UTXO, in this first case 38516 sats

<figure><img src="https://2711255060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgNoCNE0bvsne0MKkDx44%2Fuploads%2F6q84RSHrWXNFwaIFf4bl%2Fimage.png?alt=media&#x26;token=8fe9f7a4-cbda-4570-af8e-6ee1f6b29859" alt=""><figcaption><p>Inputs and outputs as displayed on mempool.space when 1484 sats are spend as fee.</p></figcaption></figure>

<https://ordapi.xyz/output/\\><transaction hash>:0 to check output one. \
<https://ordapi.xyz/output/\\><transaction hash>:1 to check output two for inscriptions.\
(replace \<transaction hash> with the transaction id, for example as found on mempool.space)

### Step 12. Repeat from step 2 (skip step 5)

Repeat the steps, ideally from step 2 and 3 to make sure our offsets are still accurate and that the sat was successfully separated.&#x20;

Make sure the table you created in step 2 and 3 is still accurate by checking the inscriptions they contain and checking the offsets. \
\
Note that the second output above (40000 sats) is the next one selected in Sparrow Wallet, to separate the next inscription. Expected with 10000 sats to be send/spend as fee. <br>
