[Guide] FULL NODE OpenSUSE 15.3: bitcoind + electrs + c-lightning + RTL

[BlackHatCoiner]

Make sure to update your package manager and other packages.

I've updated both, and even restarted, but the version remains the same. My system doesn't know any newer versions:

protobuf-compiler is already the newest version (3.6.1.3-2+rpi1)

Code:

root$ sudo apt install plocate

Did you perhaps mean sudo apt install locate? There's no package by the name "plocate". Also, I don't get anything in return when I run the locate command. Maybe it only works on OpenSUSE? Absolutely nothing:

Code:

root@raspibolt:/home/bitcoin# locate libprotobuf
root@raspibolt:/home/bitcoin# 

(I've installed the locate package)

[vv181]

I've updated both, and even restarted, but the version remains the same. My system doesn't know any newer versions:

I would try to install it with Python dependencies installed.

Code:

make clean
pip install --user poetry
python -m poetry install
./configure
python -m poetry run make -j4

Then install if it works.

Code:

sudo make install

It looks like building CLN didn't require a system protobuf lib since I did not install it but was able to build it, either with @n0nce guide or the above one. The way of installing using Poetry above install the protobuf depedency which required to build cln-grpc.

Adjust the python command accordingly if your default python version is not the same.

[BlackHatCoiner]

Unfortunately, I'm still with protoc 3.6 as the newest version, and can't build c-lightning v0.11.2.

Code:

python -m poetry run make -j4

This particular command returned me the same ugly error above.

The worst part is that I've run lots of commands that I don't know what they do. But, that's just personal, I'll have to study more.

[n0nce]

Make sure to update your package manager and other packages.

I've updated both, and even restarted, but the version remains the same. My system doesn't know any newer versions:

protobuf-compiler is already the newest version (3.6.1.3-2+rpi1)

Then it probably depends on the Linux version you're running.
What I tried and sent you before, was on Ubuntu 20.04 LTS, as I figured Raspibolt is Debian or Ubuntu based.

Can you try these commands to figure out what you're running?

Code:

lsb_release -a
cat /etc/os-release
hostnamectl

Code:

root$ sudo apt install plocate

Did you perhaps mean sudo apt install locate? There's no package by the name "plocate". Also, I don't get anything in return when I run the locate command. Maybe it only works on OpenSUSE? Absolutely nothing:

Code:

root@raspibolt:/home/bitcoin# locate libprotobuf
root@raspibolt:/home/bitcoin# 

(I've installed the locate package)

Then, a whole bunch of stuff is actually completely missing. You need the protobuf compiler and libraries.

[BlackHatCoiner]

Code:

lsb_release -a
cat /etc/os-release
hostnamectl

Code:

bitcoin@raspibolt:~ $ lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

bitcoin@raspibolt:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

bitcoin@raspibolt:~ $ hostnamectl
   Static hostname: raspibolt
         Icon name: computer
        Machine ID: <hidden>
           Boot ID: <hidden>
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 5.10.103-v7l+
      Architecture: arm

[n0nce]

~

Alright, I spun up a new Debian 10 Droplet.

(1) Updated package manager and packages

Code:

sudo apt update && sudo apt upgrade

(2) Install latest protobuf for Debian 10

Code:

sudo apt install protobuf-compiler

(3) Check protoc version

Code:

root@helloworld:~# protoc --version
libprotoc 3.6.1

==> Indeed, seems like Debian 10 Buster does not have latest protobuf in its package manager by default! So it's not your fault, BlackHatCoiner!

Now, last Raspibolt release is quite a while ago, so upgrading it is probably not an option. Let's solve this otherwise.
[1] Add the buster-backports sources to our package manager.

Code:

echo "deb http://deb.debian.org/debian buster-backports main" >> /etc/apt/sources.list.d/sources.list

[2] Update package manager

Code:

sudo apt update

[3] Install protobuf again

Code:

sudo apt install -t buster-backports protobuf-compiler

[4] Maybe, for good measure also install these (they should come with protobuf-compiler, though).

Code:

sudo apt install -t buster-backports libprotoc-dev libprotoc23

I just tried compiling Core Lightning, and am happy to report that it works fine!

Code:

./configure
make -j $(nproc)

If you have any more questions about any of the commands, don't hesitate to ask here or through DM!
I say this specifically because of:

The worst part is that I've run lots of commands that I don't know what they do. But, that's just personal, I'll have to study more.

[BlackHatCoiner]

It still stops here during make:

Code:

error: failed to run custom build command for `cln-grpc v0.0.1 (/home/bitcoin/lightning/cln-grpc)`

Caused by:
  process didn't exit successfully: `/home/bitcoin/lightning/target/debug/build/cln-grpc-beb9091097bb64ac/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "protoc failed: node.proto: This file contains proto3 optional fields, but --experimental_allow_proto3_optional was not set.\n" }', cln-grpc/build.rs:2:53
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
make: *** [plugins/Makefile:191: target/debug/examples/cln-plugin-startup] Error 101

Thanks for your time, though.

[n0nce]

It still stops here during make:

Code:

~

Thanks for your time, though.

Did the install work?

Code:

protoc --version

And I'd probably do a make clean or just re-clone the repo at this point; you've tried a lot of stuff.

No worries! This is an OpenSUSE full node guide, but if it contains a few tips for Debian users, why the hell not..

[vv181]

I just tried compiling Core Lightning, and am happy to report that it works fine!

Do you try it out on a 32-bit system environment?

[BlackHatCoiner]

Did the install work?

Code:

protoc --version

Yes.

Code:

libprotoc 3.12.3

And I'd probably do a make clean or just re-clone the repo at this point; you've tried a lot of stuff

I did both make with clean and re-cloned the repository. It still stops in sudo make install as it fails to parse the manifest at `/home/bitcoin/lightning/cln-rpc/Cargo.toml`.

[BlackHatCoiner]

I have a question. How does lightning daemon works normally when I've renamed the lightning directory? (lightning is the v0.11.2 directory, lightning2 is the old v0.10.2 directory which is running at the moment)

What binary does it run when I execute lightningd?

[Rath_]

What binary does it run when I execute lightningd?

Probably the one you compiled more recently. You probably used "sudo make install" after the compilation which should have replaced old binaries.

[psycodad]

I have a question. How does lightning daemon works normally when I've renamed the lightning directory? (lightning is the v0.11.2 directory, lightning2 is the old v0.10.2 directory which is running at the moment)

What binary does it run when I execute lightningd?

Maybe try

Code:

whereis lightningd

in a shell (assuming it is in your $PATH when you execute it like that).

[n0nce]

I have a question. How does lightning daemon works normally when I've renamed the lightning directory? (lightning is the v0.11.2 directory, lightning2 is the old v0.10.2 directory which is running at the moment)

What binary does it run when I execute lightningd?

For location either of these:

Code:

whereis lightningd
which lightningd

For version:

Code:

lightningd --version

What binary does it run when I execute lightningd?

Probably the one you compiled more recently. You probably used "sudo make install" after the compilation which should have replaced old binaries.

Correct; sudo make install actually just copies the binary you just compiled into a default location on your PATH, such as /usr/local/bin/.
If there's another binary there with the same name, it is indeed replaced.

You could work around that by either renaming the old binary before sudo make install, such that it's not overwritten.
Or you could also start lightningd directly from the build directory.

Code:

bitcoin@localhost:~/lightning> ./lightningd/lightningd --version
v0.11.2

[ibruteforce94]

Do you also maybe have a guide for updating core lightning node without losing funds/channels?

[n0nce]

Do you also maybe have a guide for updating core lightning node without losing funds/channels?

I had at least considered making one, but I believe I've never gotten around to doing it.
Usually, I put links to my guides on my webpage so they can be found easily.

But in essence, you can just install the new version (just like in the guide, but checking out latest version number) 'on top' of the old installation and it will just replace the binary; not touching your seed, channels and other existing data.

[ibruteforce94]

Awesome, I postponed updating to v22 to not screw something up, it works just installing over old files as you said. Thanks!

[unicornmangle]

n0nce thanks for taking the time to make the guides they are very useful as im learning the rest of how bitcoin operates. I think i like baremetal as opposed to arm is there a benefit? What about Mac Mini the latest versions with 16g of ram? i prefer mac os i know its a walled garden but most things are just done right in the os.

I'm hopeful i will get to do my first lightning transaction sometime tonight! everything is done except RTL doing it on futurebit for now but will probably migrate it to a thread ripper that i have sitting for the past 2 years or is that overkill?

[Carlton Banks]

Part 3 (optional): Hardening
This is a version 3 hidden service, so it cannot be found in any way unlike servers in the clearnet or Tor v2.

not sure if this is altogether true.

The tor project people advise to defend against side-channel attacks that can (supposedly) discover the IP of hidden services, they have an add-on (vanguards) to mitigate the issue.

not sure if more recent versions of tor daemon manage the side-channel attacks better, although a "lite" version of the add-on has been part of the main tor daemon, since last year I think. The recommendation at that time was that any serious hidden service should continue to use the full vanguards add-on.

[n0nce]

n0nce thanks for taking the time to make the guides they are very useful as im learning the rest of how bitcoin operates. I think i like baremetal as opposed to arm is there a benefit? What about Mac Mini the latest versions with 16g of ram? i prefer mac os i know its a walled garden but most things are just done right in the os.

You're confusing some terms here. Bare-metal refers to installing software directly on the base OS without any virtualization layer like a VirtualBox VM or Docker.
ARM is a processor architecture; used for instance in Raspberry Pi SoCs, but also in Apple mobile chips and lately the M1 and M2 families of laptop and desktop chips.

You absolutely don't need a Mac Mini with 16GB to run a full node. Something cheap with 8GB totally suffices. For a server application like a Bitcoin full node with Electrum and Lightning on it, I do recommend sticking to Linux. If you want to use that Mac Mini for personal stuff, too, you may want to look into running the Bitcoin stuff in a VirtualBox VM with OpenSUSE.

I'm hopeful i will get to do my first lightning transaction sometime tonight! everything is done except RTL doing it on futurebit for now but will probably migrate it to a thread ripper that i have sitting for the past 2 years or is that overkill?

You installed Bitcoin Core and Core Lightning on your Futurebit Apollo? How is it going?

If you have the Apollo, a Mac Mini and a Threadripper-based PC, I'd absolutely recommend leaving the node on the Apollo (Orange Pi 4), as long as you installed custom OS like described in my guide.

It pulls the least amount of power and runs Linux by default. So it's kind of an easy choice.