0% found this document useful (0 votes)
38 views7 pages

Runes Guide

This document provides instructions for setting up Bitcoin Core and Ord to run a Bitcoin node and wallet. It details downloading and installing Bitcoin Core, configuring the blockchain storage location, and running bitcoind.exe. It then covers downloading Ord, replacing or using the index file, and running ord.exe with the server command. Mainnet wallet creation and receiving addresses are also configured.

Uploaded by

trxnnx
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
38 views7 pages

Runes Guide

This document provides instructions for setting up Bitcoin Core and Ord to run a Bitcoin node and wallet. It details downloading and installing Bitcoin Core, configuring the blockchain storage location, and running bitcoind.exe. It then covers downloading Ord, replacing or using the index file, and running ord.exe with the server command. Mainnet wallet creation and receiving addresses are also configured.

Uploaded by

trxnnx
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Bitcoin Core Setup (Node)

It is recommended to use an SSD for this next step. HHDs are too slow. 1tb is the minimum
size needed but, 2tb would be better to future proof your setup. If you need a
recommendation many suitable drives have been linked in #nft-crypto-chat.

1. Download the latest version of Bitcoin Core (26.1) -


https://bitcoincore.org/en/download/ and extract the zip file to you desired folder. I
would recommend you put it in the root folder of your SSD. (D:/, E:/, etc.)
2. Run bitcoin-qt.exe. When prompted to choose the directory you would like the
blockchain downloaded to choose the bitcoin core folder (The folder that contains your
"bin" folder. In the example below you would put E:\bitcoin-26.0-win64\bitcoin-26). Be
sure that “Limit block chain storage is unchecked.
3. When you click 'OK' bitcoin-qt will start the process of syncing with the blockchain. This
can take up to a couple of days depending on your system. When complete you will no
longer see a progress bar, and a check mark icon will be visible in the lower right hand
corner of bitcoin-qt.

4. You can now close bitcoin-qt (this may take some time, let it shut down gracefully).

5. Once bitcoin-qt has shut down create a shortcut of bitcoind.exe, you can place this
anywhere you would like, leave it where it is or move it elsewhere such as your
desktop. Right-click the shortcut and click 'Properties'. Add “-datadir=E:\bitcoin-26.0-
win64\bitcoin-26.0 -txindex=1” to the Target field replacing the path above with the
folder you chose in step 2.
6. Open the shortcut you created and keep it running while you setup Ord (bitcoind must
always be running in conjunction with Ord for Ord to work!).

Ord (0.17.1) Setup and Rune Indexing

1. Download the latest Ord release from: https://github.com/ordinals/ord/releases (0.18.1


at time of writing) and unzip it into your bitcoin folder (IF you used the zip file to install
ord it will be the folder that contains your bin folder).

2. Download the file of your choice from: https://ordstuff.info/indexes/0.18/ (Currently only


the version without sats is uploaded, if you would like to include sats then either index
yourself or wait for the upload which should be live later tonight (4/11/24)).
(This step can be done without downloading the file above if you wish, however it is
not recommended as it will be much slower. What you are downloading here is an
almost fully indexed version of index.redb. You can choose to index on your own by
skipping steps 2-4. Then prior to step 6 running one of the following commands
depending on whether or not you want to index sats along with runes or just runes.

“ord --cookie-file "YOUR COOKIE PATH" --index-runes --index-sats index update”

“ord --cookie-file "YOUR COOKIE PATH" --index-runes index update”)

3. Extract the file and either replace your old index.redb or use the --index flag to point to
the new file. Your index file should be found in:

C:\Users\YOURUSERNAME\AppData\Roaming\ord

4. You should already have an instance of bitcoind.exe running from step #6 of setting up
your node. If you do not, run an instance with the shortcut you created. Bitcoind.exe
must always be running prior to executing any commands in Ord.

5. Navigate to the folder containing ord.exe and open a command prompt by typing cmd
in the address bar and then hitting enter.

6. In the window that opens type the following command, replacing the cookie path with
your cookie path.

ord --cookie-file "YOUR COOKIE PATH" server

The result should look something like shown below. Ord is finishing the index you
downloaded in step 2 of Ord setup.
7. Once the index is complete it should look like this:

Congratulations! You have installed and indexed Ord for use with runes. Keep both
bitcoind.exe and your ord.exe server running for the next steps.

Mainnet Wallet Operation

1. Open up another instance of ord.exe (same process as step #5 from “Ord (0.17.1)
Setup and Rune Indexing”.
2. Run this command:

ord --cookie-file "YOUR COOKIE PATH HERE" wallet create

The resulting output should be your seed-phrase. Copy it down. Don't be that guy.

3. Generate an address using this command:

ord --cookie-file "YOUR COOKIE PATH HERE" wallet receive

The output should be a receiving address like this:


4. You should be done setting up Ord. As a final test run this command:

ord --cookie-file "YOUR COOKIE PATH HERE" wallet balance

The result should look like this:

Setting up a Regtest Environment

I'm tired.. probably tomorrow...

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy