# Runestones on Signet

## Updating Bitcoin Core and Ord Client to Signet

First step:  Update your Bitcoin Core Config File.

In Bitcoin Core, click Settings -> Options -> Open Configuration File

Update the Config file to the code below. 

```
txindex=1
assumevalid=00000000000000000000bb92b1406fa2902380b878329c8c161a9ff1d0bf2e69
server=1
signet=1
```

Save and exit out and reopen Bitcoin Core.

Bitcoin Core will now sync with the Signet Network.

***

**Once Bitcoin Core is done syncing:**

Go to your Command Prompt. Be sure your command path is pointing to ord.exe. 

 Type `./ord --signet --index-runes index update`

{% hint style="warning" %}
*Add --cookie-file \<path> if required.  This will be required if you are saving your Bitcoin data to an external drive.  See* [*How to Find .cookie file*](/bitcoin-core-ord-client-setup-on-windows/how-to-find-.cookie-file.md)*.*

*Add `--data-dir <path>` if you want the ord data directory index to be saved to an external folder and not locally on your C drive.*\
\
*Example:*`./ord --cookie-file <path> --data-dir <path> --signet --index-runes index update`
{% endhint %}

Now you will need to run the server. Leave this window open:

`./ord --signet server`

{% hint style="warning" %}
*Add --cookie-file \<path> if required.  This will be required if you are saving your Bitcoin data to an external drive.  See* [*How to Find .cookie file*](/bitcoin-core-ord-client-setup-on-windows/how-to-find-.cookie-file.md)*.*

*Add `--data-dir <path>` if you want the ord data directory index to be saved to an external folder and not locally on your C drive.*\
\
*Example:*`./ord --cookie-file <path> --data-dir <path> --signet --index-runes server`
{% endhint %}

<figure><img src="/files/1e28YjViwIelKUC2JvMf" alt=""><figcaption></figcaption></figure>

Open a new Developer PowerShell for VS window.

cd to the folder your ord.exe is located in.

Run:

`./ord --signet wallet create`

{% hint style="warning" %}
*Add --cookie-file \<path> if required.  This will be required if you are saving your Bitcoin data to an external drive.  See* [*How to Find .cookie file*](/bitcoin-core-ord-client-setup-on-windows/how-to-find-.cookie-file.md)*.*

*Add `--data-dir <path>` if you want the ord data directory index to be saved to an external folder and not locally on your C drive.*\
\
*Example:*`./ord --cookie-file <path> --data-dir <path> --signet wallet create`
{% endhint %}

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

Make note of your mnemoic seed phrase. **DO NOT SHARE THIS WITH ANYONE.**

Now run:

`./ord --signet wallet receive`

{% hint style="warning" %}
*Add --cookie-file \<path> if required.  This will be required if you are saving your Bitcoin data to an external drive.  See* [*How to Find .cookie file*](/bitcoin-core-ord-client-setup-on-windows/how-to-find-.cookie-file.md)*.*

*Add `--data-dir <path>` if you want the ord data directory index to be saved to an external folder and not locally on your C drive.*

*Example:*`./ord --cookie-file <path> --data-dir <path> --signet wallet receive`
{% endhint %}

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

This will create a wallet address.

***

## Getting Signet Faucet BTC

Now, you will need to get some signet faucet funds. Here are a list of Bitcoin faucets for signet:

You can join the Babylon Discord and receive signet tokens in their #faucet-signet-btc channel:  <https://discord.gg/babylonglobal>

Other faucets:

{% embed url="<https://signetfaucet.com/>" fullWidth="false" %}

{% embed url="<https://signet.bublina.eu.org/>" %}

Copy the wallet address you created in the command line. Paste it into one of the faucets to receive BTC (signet).

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

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

Now you will need to wait for the transaction to be confirmed before it becomes available. You can run either `./ord --signet wallet transactions` and look to see if there are any confirmations on the transaction OR `./ord --signet wallet balance`

{% hint style="warning" %}
*Add --cookie-file \<path> if needed.*

*Add `--data-dir <path>` if you want the ord data directory index to be saved to an external folder and not locally on your C drive.*

*Example:*`./ord --cookie-file <path> --data-dir <path> --signet wallet balance`
{% endhint %}

<figure><img src="/files/GayVEfydMYA8BACoizGy" alt=""><figcaption><p>This shows that I am still waiting for confirmation on the faucet transaction.</p></figcaption></figure>

Once it confirms, you should see a "cardinal" balance.

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

***

## Etching Rune

Now you will prepare your batch.yaml file. Below is an example of a batch.yaml file you could use to etch your rune:

```yaml
# inscription modes:
# - `same-sat`: inscribe on the same sat
# - `satpoints`: inscribe on the first sat of specified satpoint's output
# - `separate-outputs`: inscribe on separate postage-sized outputs
# - `shared-output`: inscribe on a single output separated by postage
mode: separate-outputs
etching:
  # rune name
  rune: THE•BEST•RUNE #update name
  # allow subdividing super-unit into `10^divisibility` sub-units
  divisibility: 2
  # premine
  premine: 69.00
  # total supply, must be equal to `premine + (terms.cap * terms.amount)`
  supply: 6279.00
  # currency symbol
  symbol: ᚹ #update run symbol
  # mint terms (optional)
  terms:
    # amount per mint
    amount: 69.00
    # maximum number of mints
    cap: 90
    # mint start and end absolute block height (optional)
    height:
      start: 840000
      end: 850000
    # mint start and end block height relative to etching height (optional)
    offset:
      start: 1000
      end: 9000
  # future runes protocol changes may be opt-in. this may be for a variety of
  # reasons, including that they make light client validation harder, or simply
  # because they are too degenerate.
  #
  # setting `turbo` to `true` opts in to these future protocol changes,
  # whatever they may be.
  turbo: true

# inscriptions to inscribe
inscriptions:
  # path to inscription content
- file: <file path to file>
      #OR
- delegate: <inscription ID>
```

Here is the command for etching a rune:&#x20;

`./ord --signet wallet batch --batch <path-to-yaml> --fee-rate 1`

{% hint style="warning" %}
*Add --cookie-file \<path> if required.  This will be required if you are saving your Bitcoin data to an external drive.  See* [*How to Find .cookie file*](/bitcoin-core-ord-client-setup-on-windows/how-to-find-.cookie-file.md)*.*

*Add `--data-dir <path>` if you want the ord data directory index to be saved to an external folder and not locally on your C drive.*

*Example:*`./ord --cookie-file <path> --data-dir <path> --signet wallet receive`
{% endhint %}

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

Leave it open as it matures.  Usually 6 blocks will have to be confirmed after submitting for the rune to mature. You can check the tx status here:  <https://mempool.space/signet>

Once it is done maturing, you will get a confirmation on your command prompt:<br>

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

Once the transaction clears, you should be able to find the Rune on: <http://64.20.33.102:55018/runes>

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

<figure><img src="/files/EtaKdY3r9aUGrDaD3Efy" alt=""><figcaption><p><a href="http://64.20.33.102:55018/rune/ALEXA">http://64.20.33.102:55018/rune/ALEXA</a></p></figcaption></figure>

## Minting Runes on Signet

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

`./ord --signet wallet mint --fee-rate <fee-rate> --rune <RUNENAME>`

{% hint style="warning" %}
*Add --cookie-file \<path> if required.  This will be required if you are saving your Bitcoin data to an external drive.  See* [*How to Find .cookie file*](/bitcoin-core-ord-client-setup-on-windows/how-to-find-.cookie-file.md)*.*

*Add `--data-dir <path>` if you want the ord data directory index to be saved to an external folder and not locally on your C drive.*

*Example:*`./ord --cookie-file <path> --data-dir <path> --signet wallet mint --fee-rate <fee-rate> --rune <RUNENAME>`
{% endhint %}

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

## Sending Minted Runes to a Destination Wallet

If you want to send some of your Runes to another wallet, use the below command:

`./ord --signet wallet send --fee-rate <fee-rate> <destination-address> <Qty>:<RUNENAME>`

{% hint style="warning" %}
*Add --cookie-file \<path> if required.  This will be required if you are saving your Bitcoin data to an external drive.  See* [*How to Find .cookie file*](/bitcoin-core-ord-client-setup-on-windows/how-to-find-.cookie-file.md)*.*

*Add `--data-dir <path>` if you want the ord data directory index to be saved to an external folder and not locally on your C drive.*

*Example:*`./ord --cookie-file <path> --data-dir <path> --signet wallet send --fee-rate <fee-rate> <destination-address> <Qty>:<RUNENAME>`
{% endhint %}

*Be sure to update the values with < > with your parameters (see example below)*

Example:

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

{% hint style="warning" %}
*Add --cookie-file \<path> if required.  This will be required if you are saving your Bitcoin data to an external drive.  See* [*How to Find .cookie file*](/bitcoin-core-ord-client-setup-on-windows/how-to-find-.cookie-file.md)*.*
{% endhint %}


---

# 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://guide.ordinalshelp.com/bitcoin-core-ord-client-setup-on-windows/runestones-on-signet.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.