| title | parent | grand_parent | nav_exclude | has_children | has_toc | layout | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Ordisrespector |
+ Bitcoin |
Bonus Section |
true |
false |
false |
|
Ordinals is a project created to number sats. It also has a feature called inscriptions, which is the problematic part and what is mainly being touched on in this guide. An inscription is data stored onchain associated with a sat.
{% hint style="warning" %} Difficulty: Medium {% endhint %}
Why are they an attack on Bitcoin?
First of all, we probably should look at what Bitcoin is:
A Peer-to-Peer Electronic Cash System (Bitcoin Whitepaper)
There is no mention of data storage on the chain and only financial transactions. Ordinals abuse the Bitcoin timechain which was meant to process financial transactions to store data, and this has some issues, such as:
- Pushing out financial transactions, such as ones that need immediate confirmation such as force closes with pending HTLCs or a sweep-all TX.
- Driving up fee rates for the sole reason of inscribing a JPEG.
- It makes it way more expensive to maintain their node in the long term.
- It makes them liable for any illegal content in their jurisdiction that they store on their disk and broadcast freely.
...while paying 4x less for the same bytes.
Ordisrespector is a spam patch filter that works by detecting the pattern of Ordinals transactions that are entering the mempool of the node and rejecting them. The original patch was created by Luke Dashjr, you can see it here. Archive
{% embed url="https://gist.github.com/luke-jr/4c022839584020444915c84bdd825831" %}
{% hint style="info" %}
You enter commands and the PC answers by printing the results below your command. The system response is marked with the ">" character
{% endhint %}
- With
adminuser, update and upgrade your OS
sudo apt update && sudo apt full-upgrade- Install the next dependencies packages
{% code overflow="wrap" %}
sudo apt install autoconf automake build-essential libboost-filesystem-dev libboost-system-dev libboost-thread-dev libevent-dev libsqlite3-dev libtool pkg-config libzmq3-dev --no-install-recommends{% endcode %}
- Change to the temporary directory which is cleared on reboot
cd /tmp- Set the next environment variable
VERSION=28.0- Get the latest source code, the list of cryptographic checksums, and the signatures attesting to the validity of the checksums
wget https://bitcoincore.org/bin/bitcoin-core-$VERSION/bitcoin-$VERSION.tar.gzwget https://bitcoincore.org/bin/bitcoin-core-$VERSION/SHA256SUMSwget https://bitcoincore.org/bin/bitcoin-core-$VERSION/SHA256SUMS.asc{% hint style="info" %} If you already had Bitcoin Core installed and the OTS client with the IBD completed, you could do the timestamp check verification {% endhint %}
- Download the timestamp file
wget https://bitcoincore.org/bin/bitcoin-core-$VERSION/SHA256SUMS.ots- Execute the OTS verification command
{% hint style="warning" %} Skip this step if you stay building a new node {% endhint %}
ots --no-cache verify SHA256SUMS.ots -f SHA256SUMSThe following output is just an example of one of the versions:
Got 1 attestation(s) from https://btc.calendar.catallaxy.com
Got 1 attestation(s) from https://finney.calendar.eternitywall.com
Got 1 attestation(s) from https://bob.btc.calendar.opentimestamps.org
Got 1 attestation(s) from https://alice.btc.calendar.opentimestamps.org
Success! Bitcoin block 766964 attests existence as of 2022-12-11 UTC
{% hint style="info" %} Now, check that the timestamp date is close to the release date of the version you're installing
If you obtain this output:
Calendar https://btc.calendar.catallaxy.com: Pending confirmation in Bitcoin blockchain
Calendar https://finney.calendar.eternitywall.com: Pending confirmation in Bitcoin blockchain
Calendar https://bob.btc.calendar.opentimestamps.org: Pending confirmation in Bitcoin blockchain
Calendar https://alice.btc.calendar.opentimestamps.org: Pending confirmation in Bitcoin blockchain
-> This means that the timestamp is pending confirmation on the Bitcoin blockchain. You can skip this step or wait a few hours/days to perform this verification. It is safe to skip this verification step if you followed the previous ones and continue to the next ones {% endhint %}
- Check that the reference checksum in the file
SHA256SUMSmatches the checksum calculated by you (ignore the "lines are improperly formatted" warning)
sha256sum --ignore-missing --check SHA256SUMSExample of expected output:
bitcoin-26.0.tar.gz: OK
Bitcoin releases are signed by several individuals, each using its key. To verify the validity of these signatures, you must first import the corresponding public keys into your GPG key database.
- The next command downloads and automatically imports all signatures from the Bitcoin Core release attestations (Guix) repository
{% code overflow="wrap" %}
curl -s "https://api.github.com/repositories/355107265/contents/builder-keys" | grep download_url | grep -oE "https://[a-zA-Z0-9./-]+" | while read url; do curl -s "$url" | gpg --import; done{% endcode %}
Example of expected output:
[...]
gpg: key 17565732E08E5E41: 29 signatures not checked due to missing keys
gpg: /home/admin/.gnupg/trustdb.gpg: trustdb created
gpg: key 17565732E08E5E41: public key "Andrew Chow <[email protected]>" imported
gpg: Total number processed: 1
gpg: imported: 1
gpg: no ultimately trusted keys found
[...]
- Verify that the checksums file is cryptographically signed by the release signing keys. The following command prints signature checks for each of the public keys that signed the checksums
gpg --verify SHA256SUMS.asc- Check that at least a few signatures show the following text
Expected output:
gpg: Good signature from ...
Primary key fingerprint: ...
[...]
- If you're satisfied with the checksum, signature, and timestamp checks, extract the Bitcoin Core source code, install them, and check the version
tar -xzvf bitcoin-$VERSION.tar.gzExample of expected output:
bitcoin-28.0/
bitcoin-28.0/.cirrus.yml
bitcoin-28.0/.editorconfig
bitcoin-28.0/.gitattributes
bitcoin-28.0/.github/
bitcoin-28.0/.github/ISSUE_TEMPLATE/
bitcoin-28.0/.github/ISSUE_TEMPLATE/bug.yml
bitcoin-28.0/.github/ISSUE_TEMPLATE/config.yml
bitcoin-28.0/.github/ISSUE_TEMPLATE/feature_request.yml
bitcoin-28.0/.github/ISSUE_TEMPLATE/good_first_issue.yml
bitcoin-28.0/.github/ISSUE_TEMPLATE/gui_issue.yml
bitcoin-28.0/.github/PULL_REQUEST_TEMPLATE.md
bitcoin-28.0/.github/workflows/
[..]
- Build BerkeleyDB 4.8 to allow for legacy wallets, necessary to use JoinMarket, Electrum Personal Server, and possibly other tools
{% code overflow="wrap" %}
wget -O bdb.sh https://raw.githubusercontent.com/bitcoin/bitcoin/aef8b4f43b0c4300aa6cf2c5cf5c19f55e73499c/contrib/install_db4.sh{% endcode %}
- Assign execute permissions
chmod +x bdb.sh- Execute the
bdb.shscript
./bdb.sh bitcoin-$VERSIONExpected output:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 21.7M 100 21.7M 0 0 12.2M 0 0:00:01 0:00:01 --:--:-- 12.2M
db-4.8.30.NC.tar.gz: OK
db-4.8.30.NC/
db-4.8.30.NC/btree/
db-4.8.30.NC/btree/bt_compress.c
db-4.8.30.NC/btree/bt_compact.c
db-4.8.30.NC/btree/bt_compare.c
db-4.8.30.NC/btree/btree_autop.c
db-4.8.30.NC/btree/bt_conv.c
db-4.8.30.NC/btree/bt_curadj.c
db-4.8.30.NC/btree/bt_cursor.c
db-4.8.30.NC/btree/bt_delete.c
db-4.8.30.NC/btree/bt_method.c
db-4.8.30.NC/btree/bt_open.c
db-4.8.30.NC/btree/bt_put.c
db-4.8.30.NC/btree/bt_rec.c
db-4.8.30.NC/btree/bt_reclaim.c
db-4.8.30.NC/btree/bt_recno.c
db-4.8.30.NC/btree/bt_rsearch.c
db-4.8.30.NC/btree/bt_search.c
db-4.8.30.NC/btree/bt_split.c
db-4.8.30.NC/btree/bt_stat.c
[...]
- Enter to the Bitcoin Core source code folder
cd bitcoin-$VERSION- Execute the
autogen.shscript
./autogen.shExpected output:
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build-aux/m4'.
libtoolize: copying file 'build-aux/m4/libtool.m4'
libtoolize: copying file 'build-aux/m4/ltoptions.m4'
libtoolize: copying file 'build-aux/m4/ltsugar.m4'
libtoolize: copying file 'build-aux/m4/ltversion.m4'
libtoolize: copying file 'build-aux/m4/lt~obsolete.m4'
configure.ac:39: installing 'build-aux/ar-lib'
configure.ac:37: installing 'build-aux/compile'
configure.ac:24: installing 'build-aux/config.guess'
configure.ac:24: installing 'build-aux/config.sub'
configure.ac:27: installing 'build-aux/install-sh'
configure.ac:27: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
[...]
- The next command will configure the Berkeley DB path, set the next environment variable
export BDB_PREFIX="/tmp/bitcoin-$VERSION/db4"- Pre-configure the installation, we will discard some features and include others. Enter the complete next command in the terminal and press enter
./configure \
BDB_LIBS="-L${BDB_PREFIX}/lib -ldb_cxx-4.8" BDB_CFLAGS="-I${BDB_PREFIX}/include" \
--disable-bench \
--disable-maintainer-mode \
--disable-tests \
--with-gui=no{% hint style="info" %} Skip this step if you want only to build Bitcoin Core from the source code but not apply the Ordisrespector patch {% endhint %}
- Download the Ordisrespector patch
{% code overflow="wrap" %}
wget https://raw.githubusercontent.com/minibolt-guide/minibolt/main/resources/ordisrespector.patch{% endcode %}
- (Optional) Inspect
ordisrespector.patchfile to make sure it does not do bad things. If you see all OK, exit with Ctrl-X and continue with the next command
nano ordisrespector.patch- Apply the patch
git apply ordisrespector.patch- Enter the command to compile
make -j$(nproc){% hint style="info" %} This process can take quite a long time, 10-15 minutes or more, depending on the performance of your device. Please be patient until the prompt shows again {% endhint %}
- Enter the next command to install the new binaries precompiled for yourself on the OS
sudo make install- Check the correct installation requesting the output of the version
bitcoin-cli --versionThe following output is just an example of one of the versions:
Bitcoin Core version v24.1.0
Copyright (C) 2009-2022 The Bitcoin Core developers
[...]
{% hint style="info" %} Now you can continue with the installation progress of the Bitcoin Client following the Create the bitcoin user section or if you already had it installed, only continue with the next steps {% endhint %}
- Return to the
tmpfolder
cd ..- (Optional) Clean the installation files to be ready for the next update
{% code overflow="wrap" %}
sudo rm -r bitcoin-$VERSION bdb.sh bitcoin-$VERSION.tar.gz db-4.8.30.NC.tar.gz SHA256SUMS SHA256SUMS.asc SHA256SUMS.ots{% endcode %}
- (Optional) Delete no needed binaries before installed by
make installcommand
{% code overflow="wrap" %}
sudo rm /usr/local/bin/bitcoin-tx /usr/local/bin/bitcoin-wallet /usr/local/bin/bitcoin-util{% endcode %}
- If you have an existing Bitcoin Core installation without Ordisrespector applied, restart it using systemd and start a new instance with the Ordisrespector patch applied
sudo systemctl restart bitcoind- Monitor by the systemd journal and check the logging output. You can exit monitoring at any time with Ctrl+C and continue
journalctl -fu bitcoind{% hint style="info" %} After starting Bitcoin Core, wait a few minutes for Bitcoin Core to load the mempool, the indicator for this is the log: "Imported mempool transactions from disk: ...". A rather high indicator of "failed" imported transactions may have appeared, which is a good sign, it's the filter is taking effect and rejecting the Ordinals transactions after to apply the patch {% endhint %}
- Go to the public mempool.space clearnet or Tor link official web page
- Click on the first mempool candidate block in the green/yellow color blocks
- Put the pointer above the cube's dynamic graphic at the bottom right, and find transactions with for example 0.00010000 BTC, 0.00005000 BTC, 0.00000546 BTC, 0.00000330 BTC, 0.000005386 BTC... output amount, or similar recurrency amount and click on the cube of the transaction to do a second verification
- Look for "Taproot", "Segwit", "RBF" and "CPFP" tags (this last doesn't always appear)
- Click on the "copy to the clipboard" icon to copy the transaction ID
(<txid>), and paste this on your own Bitcoin Explorer (BTC RPC Explorer / Mempool), in a BTC RPC Explorer running on a MiniBolt environment, go to https://minibolt.local:4000 - Search the
"<txid>"on the browser of your own Bitcoin Explorer
Mempool space expected output:
BTC RPC Explorer expected output:
Or if you prefer, check directly through the Bitcoin Core CLI command, doing
bitcoin-cli getmempoolentry <txid>Expected output:
error code: -5
error message:
Transaction not in mempool
{% hint style="info" %} The before information indicates that the filter is working properly {% endhint %}
Add the Bitcoin Barcelona node as a peer in your node, or Ordisrespector runners community peers that shared their public addresses, in this way, it is easier to invade the network with Ordisrespector node runners.
- Edit and add to the
bitcoin.conffile, the next line/s at the end of the file
sudo nano /data/bitcoin/bitcoin.confIf you have enabled the Tor network
addnode=.....2pk5umz5vieqwcp3ead.onion:8333
If you have enabled the I2P network, add this line as well
addnode=.....3q5hw6625xyqekprljz6uasa.b32.i2p:0
By applying Ordisrespector to our node, we can have a different version of the mempool compared to the rest of the network and with it the estimation of the fees. It is possible to point the fee estimator to another node without Ordisrespector applied
- With user admin, stop LND if you have installed
sudo systemctl stop lnd- Edit
lnd.conf
sudo nano /data/lnd/lnd.conf- Add the next lines at the end of the file
[fee]
# Use external fee estimator
fee.url=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json
- Start LND again
sudo systemctl start lndOnce you get to the Configuration section of the Bitcoin Client: Bitcoin Core
- With user
bitcoin, create thebitcoin.conffile
nano /home/bitcoin/.bitcoin/bitcoin.conf- Include with the rest, the next lines at the end of the file. Save and exit
# Reject data in transactions
datacarriersize=0
permitbaremultisig=0
{% hint style="info" %}
Continue with the guide on Set permissions:... step
{% endhint %}
{% hint style="warning" %} Attention: with the previous configuration, Whirlpool will not work and either is recommended for mining use {% endhint %}
The latest release can be found on the GitHub page of the Bitcoin Core project. Always read the RELEASE NOTES first! When upgrading, there might be breaking changes or changes in the data structure that need special attention
Go to the Installation section, and replace the environment variable "VERSION=x.xx" value for the latest version if it has not already been changed in this guide. Continue until complete the entire Installation section
{% hint style="info" %}
Remember to restart the Bitcoin Core to apply the new version with sudo systemctl restart bitcoind
{% endhint %}
To uninstall Bitcoin Core with the Ordisrespector patch applied, follow the entire Bitcoin Core uninstall section
Same as the Bitcoin Core section