Skip to content

Commit

Permalink
GITBOOK-6: No subject
Browse files Browse the repository at this point in the history
  • Loading branch information
@twofaktor @gitbook-bot
twofaktor authored and gitbook-bot committed Sep 27, 2024
1 parent b9d0352 commit b8448e7
Show file tree
Hide file tree
Showing 15 changed files with 326 additions and 303 deletions.
8 changes: 6 additions & 2 deletions README.md
View file
Original file line number Diff line number Diff line change
@@ -1,11 +1,15 @@
---
description: >-
Build your own "DIY" Bitcoin & Lightning full node on a Raspberry Pi. No need
to trust anyone else.
Build your own "DIY" Bitcoin & Lightning full node, and other stuff on a
Raspberry Pi. No need to trust anyone else.
---

# RaMiX

{% hint style="danger" %}
**Attention: this guide is in the WIP (work in progress) state. Many steps may be incorrect. Act behind your responsibility**
{% endhint %}

Build your own "do-everything-yourself" Bitcoin full node, Lightning, and other stuff on a Raspberry Pi, making you sovereign.

No need to trust anyone else. Don't trust, verify!
Expand Down
64 changes: 31 additions & 33 deletions bitcoin/bitcoin/bitcoin-client.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -308,8 +308,8 @@ All commands entered are stored in the bash history. But we don't want the passw
**Example** of expected output:

```
> String to be appended to bitcoin.conf:
> rpcauth=minibolt:00d8682ce66c9ef3dd9d0c0a6516b10e$c31da4929b3d0e092ba1b2755834889f888445923ac8fd69d8eb73efe0699afa
String to be appended to bitcoin.conf:
rpcauth=minibolt:00d8682ce66c9ef3dd9d0c0a6516b10e$c31da4929b3d0e092ba1b2755834889f888445923ac8fd69d8eb73efe0699afa
```

* Copy the `rpcauth` line, we'll need to paste it into the Bitcoin config file
Expand Down Expand Up @@ -649,15 +649,15 @@ etehks3xyh55nyjldjdeckk3nwpanivqhrzhsoracwqjxtk8apgk.b32.i2p port 0
* Ensure bitcoind is listening on the default RPC & P2P ports

```bash
sudo ss -tulpn | grep LISTEN | grep bitcoind
sudo ss -tulpn | grep bitcoind
```

Expected output:

<pre><code>> tcp LISTEN 0 128 127.0.0.1:<a data-footnote-ref href="#user-content-fn-8">8332</a> 0.0.0.0:* users:(("bitcoind",pid=773834,fd=11))
> tcp LISTEN 0 4096 127.0.0.1:<a data-footnote-ref href="#user-content-fn-9">8333</a> 0.0.0.0:* users:(("bitcoind",pid=773834,fd=46))
> tcp LISTEN 0 4096 127.0.0.1:<a data-footnote-ref href="#user-content-fn-10">8334</a> 0.0.0.0:* users:(("bitcoind",pid=773834,fd=44))
> tcp LISTEN 0 128 [::1]:8332 [::]:* users:(("bitcoind",pid=773834,fd=10))
<pre><code>tcp LISTEN 0 128 127.0.0.1:<a data-footnote-ref href="#user-content-fn-8">8332</a> 0.0.0.0:* users:(("bitcoind",pid=773834,fd=11))
tcp LISTEN 0 4096 127.0.0.1:<a data-footnote-ref href="#user-content-fn-9">8333</a> 0.0.0.0:* users:(("bitcoind",pid=773834,fd=46))
tcp LISTEN 0 4096 127.0.0.1:<a data-footnote-ref href="#user-content-fn-10">8334</a> 0.0.0.0:* users:(("bitcoind",pid=773834,fd=44))
tcp LISTEN 0 128 [::1]:8332 [::]:* users:(("bitcoind",pid=773834,fd=10))
</code></pre>

* Please note:
Expand Down Expand Up @@ -968,7 +968,7 @@ sha256sum --ignore-missing --check SHA256SUMS
**Example** of expected output:

```
> bitcoin-25.1-aarch64-linux-gnu.tar.gz: OK
bitcoin-25.1-aarch64-linux-gnu.tar.gz: OK
```

* The next command downloads and automatically imports all signatures from the [Bitcoin Core release attestations (Guix)](https://github.com/bitcoin-core/guix.sigs) repository
Expand All @@ -982,12 +982,12 @@ curl -s "https://api.github.com/repositories/355107265/contents/builder-keys" |
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
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
[...]
```

Expand All @@ -1000,8 +1000,8 @@ gpg --verify SHA256SUMS.asc
* Check that at least a few signatures show the following text

```
> gpg: Good signature from ...
> Primary key fingerprint: ...
gpg: Good signature from ...
Primary key fingerprint: ...
```

* If you completed the IBD (Initial Block Download), now you can verify the timestamp with your node. If the prompt shows you `-bash: ots: command not found`, ensure that you are installing the OTS client correctly in the [proper section](bitcoin-client.md#opentimestamps-client)
Expand All @@ -1014,26 +1014,24 @@ ots --no-cache verify SHA256SUMS.ots -f SHA256SUMS
The 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
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
```
{% endhint %}

{% hint style="info" %}
Now, just check that the timestamp date is close to the [release](https://github.com/bitcoin/bitcoin/releases) date of the version you're installing
{% endhint %}
* Now, just check that the timestamp date is close to the [release](https://github.com/bitcoin/bitcoin/releases) date of the version you're installing

{% hint style="info" %}
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
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
Expand All @@ -1042,7 +1040,7 @@ If you obtain this output:
* If you're satisfied with the checksum, signature, and timestamp checks, extract the Bitcoin Core binaries

```sh
tar -xvf bitcoin-$VERSION-aarch64-linux-gnu.tar.gz
tar -xzvf bitcoin-$VERSION-aarch64-linux-gnu.tar.gz
```

* Install them
Expand All @@ -1062,9 +1060,9 @@ bitcoin-cli --version
The following output is just an **example** of one of the versions:

```
> Bitcoin Core RPC client version v26.0.0
> Copyright (C) 2009-2022 The Bitcoin Core developers
> [...]
Bitcoin Core RPC client version v26.0.0
Copyright (C) 2009-2022 The Bitcoin Core developers
[...]
```

* **(Optional)** Delete installation files of the `/tmp` folder to be ready for the next upgrade
Expand Down Expand Up @@ -1154,7 +1152,7 @@ sudo ufw status numbered
Expected output:

```
> [Y] 8333 ALLOW IN Anywhere # allow Bitcoin Core from anywhere
[Y] 8333 ALLOW IN Anywhere # allow Bitcoin Core from anywhere
```

{% hint style="info" %}
Expand Down
Loading

0 comments on commit b8448e7

Please sign in to comment.