0xjogir

bitcoin

Mac Mini (Late 2012) BTC Node - Chapter 2

[Chapter 3: Personal Electrum Server – Fulcrum](https://stacker.news/items/198598) is out!

Mac Mini (Late 2012) BTC Node - Chapter 1

# Chapter 3: Personal Electrum Server – Fulcrum

### Prerequisite

[Chapter 1: Hardware selection, upgrade, and Ubuntu Server installation](https://stacker.news/items/186239)

[Chapter 2: Installing, Configuring & Updating Bitcoin Core](https://stacker.news/items/192486)

### 1. Download the file

***Go into your “home” directory and create the following folders***
>mkdir fulcrum
>mkdir fulcrum_db

***Go to the Fulcrum Github release page https://github.com/cculianu/Fulcrum/releases and download the latest release***
>cd downloads
>wget https://github.com/cculianu/Fulcrum/releases/download/v1.9.1/Fulcrum-1.9.1-x86_64-linux-ub16.tar.gz
>wget https://github.com/cculianu/Fulcrum/releases/download/v1.9.1/Fulcrum-1.9.1-x86_64-linux-ub16.tar.gz.asc
>sha256sum --ignore-missing --check SHA256SUMS

***Extract the file***
>tar xvf Fulcrum-1.9.1-x86_64-linux-ub16.tar.gz

***Move the files to fulcrum folder***
>mv Fulcrum-1.9.1-x86_64-linux-ub16/* /home/<user>/fulcrum
>cd ..
>cd fulcrum

### 2. Creating the Key and Cert

***Creating the keys***
>openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout key.pem -out cert.pem
Generating a RSA private key

Press <enter> for all the defaults parameters. The files keys.perm and cert.perm should have been created in your fulcrum folder.

### 3. Configuration file

***rename the config file***
>mv fulcrum-example-config.conf fulcrum.conf

***Modify the config file***
>nano fulcrum.conf

Change the following in the config file:
- Change path of the datadir: home/<username>/fulcrum_db
- rpcuser: use the same one as the bitcoin.conf file
- rpcpassword: use the one used for the rpcauthy while setting up the bitcoin.conf file
- remove the # for the SSL= 0.0.0.0:50002
- remove the # for the certificate and put correct path home/<username>/fulcrum/cert.pem
- remove the # for the key and put correct path home/<username>/fulcrum/key.pem
- remove the # for peering and change for peering=false
- remove the # for fast-sync and change for what you are confortable fast-sync = 4000 (4g of ram)

CTRL-X, Y, ENTER

### 4.Creating the service file

***Creating service file***
>sudo nano /etc/systemd/system/fulcrum.service

Paste de following in the file and replace <user> by your server username.

[Unit] 
Description=Fulcrum After=network.target 
[Service] 
ExecStart=/home/<user>/fulcrum/Fulcrum /home/<user>/fulcrum/fulcrum.conf User=<user>
LimitNOFILE=8192 
TimeoutStopSec=30min 
[Install] 
WantedBy=multi-user.target

CTRL+X, Y, Enter

***Start this service
>sudo systemctl enable fulcrum.service
>sudo systemctl start fulcrum.service
>sudo systemctl status fulcrum.service

***To see the log***
>journalctl -fu fulcrum.service

The next chapter will be to sync your node to your own wallet!

Mac Mini (Late 2012) BTC Node - Chapter 3

I am really curious to have your feedback afterwards!

Hey mate, thanks for the feedback.

I am honestly debating if I will go ahead and install LND on my node yet. I will need to install Electrum Server before and see if I have enough space on the SSD. If i decide to go that route, it will be Chapter 4. I would definately install it using official release binaries.

I am glad that my little write up were useful. I want to make sure that my months of research can be sum up in a short concise matter and help other plebs.

Next Chapter is out!

[Chapter 2: Installing, Configuring & Updating Bitcoin Core](https://stacker.news/items/192486)

# Chapter 2: Installing, Configuring & Updating Bitcoin Core

#### Prerequisite

[Chapter 1: Hardware selection, upgrade, and Ubuntu Server installation](https://stacker.news/items/186239)

### 1- Installing Bitcoin Core

This section will be done remotely from another computer by connecting to your Node using SSH. Please follow previous Chapter to make sure your hardware is adequate, and that you have followed Ubuntu Server installation.

***First of all, we will validate that the installation was done properly and that the Ubuntu installation was NOT setup as a virtual machine (step 13 of section 3 of the previous chapter).***

>df -h

***Looking for updates***

>sudo apt update

***Updating***

>sudo apt upgrade

***Let's start by creating a “downloads” folder***

>mkdir downloads

***Go in the downloads folder***

>cd downloads

It is now important to understand what you are about to do. There are different ways to install Bitcoin Core. My preferred way is to download the release from Bitcoin Core [here](https://bitcoincore.org/en/download/)
 and do the GPG Key verification with the key list [here](https://github.com/bitcoin/bitcoin/blob/master/contrib/verify-commits/trusted-keys) on Github.

***Download the files from the Bitcoin Core website***

> wget https://bitcoincore.org/bin/bitcoin-core-24.0.1/bitcoin-24.0.1-x86_64-linux-gnu.tar.gz

>wget https://bitcoincore.org/bin/bitcoin-core-24.0.1/SHA256SUMS

>wget https://bitcoincore.org/bin/bitcoin-core-24.0.1/SHA256SUMS.asc

***Validate that the release file is listed in the checksums file***

>sha256sum --ignore-missing --check SHA256SUMS

***Use GPG to load keys locally from individuals found on the Github site***
Ignore any warning and failures, but you must be sure that the lists “OK” after the name of the release file downloaded
 
***Use GPG to load keys locally from individuals found on the Github site***

>gpg --keyserver hkps://keys.openpgp.org --recv-keys E777299FC265DD04793070EB944D35F9AC3DB76A

>gpg --keyserver hkps://keys.openpgp.org --recv-keys D1DBF2C4B96F2DEBF4C16654410108112E7EA81F

***Validate that the checksum file is verified***

>gpg --verify SHA256SUMS.asc

You should receive a “Good signature” beside the name associated to the key

***Extract the tar file. It will create a folder called bitcoin-24.0.1 so it is important that you call it in the next command line.***

>tar xzf bitcoin-24.0.1-x86_64-linux-gnu.tar.gz 

***Install the content in the following directory. It is IMPORTANT that you write the correct folder name based on your release number. If you have installed the release 25.0, the folder name has to be bitcoin-25.0***

>sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-24.0.1/bin/*

***Cross your fingers and launch Bitcoin Core***

>bitcoind -daemon

***Get blockchain info to see which block your node is at***

>bitcoin-cli getblockchaininfo

***Validate to how many peers your node is connected to***

>bitcoin-cli getconnectioncount

***If you want to follow the log of your node synchronization, you should open a secondary Terminal window and write the following command***

>tail -f .bitcoin/debug.log




### 2. Configuring Bitcoin Core (bitcoin.conf)

While the blockchain is synchronizing, you can start the configuration. In order to be fully synchronized, it will take approximately 18 hours. I found a great tutorial on youtube [here](https://www.youtube.com/watch?v=fx_mLXISrfM)

***Open a new therminal window and go to the /.bitcoin folder***

>cd /.bitcoin  

***We need to create a new configuration file***

>nano bitcoin.conf

***Paste de following text in the bitcoin.conf file***

>server=1
>txindex=1
>daemon=1
>rpcport=8332
>rpcbind=0.0.0.0
>rpcallowip=127.0.0.1
>rpcallowip=10.0.0.0/8
>rpcallowip=172.0.0.0/8
>rpcallowip=192.0.0.0/8
>zmqpubrawblock=tcp://0.0.0.0:28332
>zmqpubrawtx=tcp://0.0.0.0:28333
>zmqpubhashblock=tcp://0.0.0.0:28334
>whitelist=127.0.0.1
>rpcauth=<username>:[output of rpcauth.py]





***Keep this terminal window open and go back to the main window***

We will create a username and password for the RPC Authentification of the bitcoin.conf file we have created in the other terminal window and modify it

***In the original terminal window, be sure you are in your “downloads” folder***

>cd downloads

***In order to add a <username> and <password> to access to your node, go to Github.com/bitcoin/bitcoin and search for rpcauth.py. Go to the raw file and copy the link***

>wget https://github.com/bitcoin/bitcoin/blob/master/share/rpcauth/rpcauth.py

***Make the file executable***
>chmod +x rpcauth.py

***Execute the file with a <username> & <password> at the end of the command line***
>./rpcauth.py <username> <password>

***Copy the string and paste it in the configuration file of the auxiliary termina window***

Modify the <username> and <password> in the bitcon.conf file

>rpcauth=<username>:[output of rpcauth.py]


CTRL+X and save Yes 

***Restart bitcoind***
>Bitcoin-cli stop
>Bitcoind


###3.Creating the service file for automatic boot on start-up (bitcoind.service)

***Go back to Github.com/bitcoin/bitcoin and search for .service file. https://raw.githubusercontent.com/bitcoin/bitcoin/663f6cd9ddadeec30b27ec12f0f5ed49f3146cc9/contrib/init/bitcoind.service***

***Important note: The new service file does not work properly. The link above is for the service file from 2021***

***Download the .service file in your systemd folder***
>cd /etc/systemd/system
>sudo wget https://raw.githubusercontent.com/bitcoin/bitcoin/663f6cd9ddadeec30b27ec12f0f5ed49f3146cc9/contrib/init/bitcoind.service
>sudo nano bitcoind.service

***Change the file***

In the [service] section, make the following changes:

• Make sure that the “ExecStart” has the right path for the folder “bitcoind” on the same line as “daemonwait” (you can verify the path in another terminal with the command “whereis bitcoind”)
• you need to remove the “wait” in -daemonwait to have only -daemon
• Make sure that the bitcoin.conf file has the right path. 
• Change also the path for the datadir.
• Put a # in front of ExecStartPre=
• Change “user” and “group” for the actual user of the server instead of Bitcoin and Bitcoin
• Put a # in front of ProtectHome

>Press CTRL + X to save it, Y, enter

***Shutdown Bitcoin***
>bitcoin-cli stop

***Activate the new service file***
>sudo systemctl enable bitcoind
>sudo systemctl start bitcoind

***Validate the status***
>sudo systemctl status bitcoind

### 4. Enable TOR

***Go back to home directory***
>sudo apt install tor

***Validate that TOR has been activated***
>sudo systemctl status tor

***Edit TOR rc file***
>sudo nano /etc/tor/torrc

***Go all the way to bottom and enter 3 lines***
>ControlPort 9051
>CookieAuthentication 1
>CookieAuthFileGroupReadable 1

CTRL-X, Save

***Restart Tor***
>sudo systemctl restart tor

>sudo usermod -a -G debian-tor <username>

***Modify bitcoin.conf to add TOR lines***
>nano .bitcoin/bitcoin.conf
 
Add the following lines at the end of the file:

>proxy=127.0.0.1:9050 
>listen=1 b
>bind=127.0.0.1
>onlynet=onion
>addnode=ty5nq4ua4v47jmebyib7wtk6b25exd735twap6g3rckbfhvlzvrkdhid.onion:8333

CTRL+X, Y

***Reboot your node***
>sudo reboot

##How to upgrade bitcoin-core

***Go go downloads folder***
>cd downloads

***Remove the previous sha256sums and sha256sums.asc files***
>rm sha256sums
>rm sha256sums.asc

***Go to bitcoincore.org to download the latest release with its signature files***
>wget https://bitcoincore.org/bin/bitcoin-core-25.0/bitcoin-25.0-x86_64-linux-gnu.tar.gz
>wget https://bitcoincore.org/bin/bitcoin-core-25.0/SHA256SUMS
>wget https://bitcoincore.org/bin/bitcoin-core-25.0/SHA256SUMS.asc

***Validate that the release file is listed in the checksums file***

>sha256sum --ignore-missing --check SHA256SUMS

***Verify that the checksum file is verified***

>gpg --verify SHA256SUMS.asc

You should receive a “Good signature” beside the name associated to the key

***Extract the tar file. It will create a folder called bitcoin-25.0 in order to reflect the upgrade to the latest release***

>tar xzf bitcoin-25.0-x86_64-linux-gnu.tar.gz 

***Stop your node***
>bitcoin-cli stop

***Install the content in the following directory. It is IMPORTANT that you write the correct folder name based on your release number.***

>sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-25.0/bin/*

***Restart bitcoind***
>sudo systemctl start bitcoind

***Validate the version***
>bitcoin-cli –version

Et voila!

Stay tuned, I will be explaining how to install your Personal Electrum Server on your node in the next chapter!


>Maybe someone else can weigh in

I have found a website comparing both. I believe that CLN is lighter on the Node. However the only drawback I see is that it doesn't support Taproot.

https://voltage.cloud/blog/bitcoin-lightning-network/what-are-the-differences-between-lnd-and-cln/

The one I used is the newest server edition one from the website

Ubuntu Server 22.04 LTS

https://ubuntu.com/download/server

Thank you, I honestly wasn't expecting that many good feedback. I am glad people can find it useful/entertaining! 

Amazing! Let me know how it goes.

Also, I am debating between going with LND or C-LN. 

Any thoughts?

Thank you,

Im finishing it up pretty soon. I can only work on it a bit of time everyday. Keeping you posted! Next step if Bitcoin Core.

It is running really well, took less than 18 hours to fully sync and I do not even hear it. I guess the performance will be tested once I get a couple LN channels up but until now I am extremely satisfied.

I cannot put enough emphasis on getting a good quality SSD. I initially had a cheap 2TB (you can see it on the pictures) but it died on me (big mistake).

Thank you!

It doesn't seem like it but its a lot of research. I am now working on my next Chapter, which is installing Bitcoin Core.

# Chapter 1: Hardware selection, upgrade, and Ubuntu Server installation

### 1. Hardware selection

It is important to select adequately the hardware that will be used to build your Node. The Node will be running 24h /7 days and will countain your lightning channels. It is important to use high quality hardware and spend the extra dollars for it.

At the time of building my Node, there was a shortage of Raspberry Pi and I was looking for an optimal alternative. I have decided to go ahead and purchase a used Mac Mini (late 2012). 

It is recommended NOT to purchase a Mac Mini newer than 2012 (i.e 2014 and up) because Apple started to solder the RAM to the Logic Board after 2012. The Mac Mini Late 2012 is the last model that is fully customizable with SSD and RAM upgrades.

Here is the list of hardware that will be used in this build:

  • 2 x 8G DDR3L Sodim 1600Mhz 1.35V
  • 1 x Mac Mini (Late 2012) 2.5Ghz
  • 1 x Samsung Evo 870 1Tb SSD *

 * Note: As discussed earlier, it is important to select hardware of quality. I had initially purchased a low cost 2Tb SSD but it failed while trying to download the Bitcoin blockchain.


### 2. Hardware upgrade

To facilitate the upgrade of the hardware, you will need the proper tools to remove some T6 & T8 screws. 

Here are the steps to dismount the few components of the Mac Mini to upgrade the hardware: 

 1- Unplug the Mac Mini
 2- Turn it upside down with the black cover facing up.
 3- Put your thumbs in the 2 grooves of the cover and turn the piece counterclockwise.
![](https://nostr.build/i/ed7eb6c4132966df674a8d42fffa540d8ca6e6ff995a42494be50a9020859b45.jpg)
 4- Remove the cover.
 5- Remove 3 x T6 screws holding the fan.
![](https://nostr.build/i/0102a0456ef063770b1628bba695f85befc3299e09682701236ad79b6b9c700f.jpg)
 6- Lift the fan and disconnect the connector by pulling gently straight up the wires.
 7- Remove 1x T6 screw at the bottom of the shroud (black plastic piece on the left of the fan)
![](https://nostr.build/i/7a541ef3a9488560b546d01a3efe4234b2bedde9c301ad00461f776a8246ae26.jpg)
 8- Remove the shroud by holding the top right part with your fingers and turning it clockwise.
![](https://nostr.build/i/d371f164efe399d71776e681895ed5fb13135225ecad224a67b1d919bf8fc2a9.jpg)
 9- Remove 4 x T8 screws of the grill WIFI cover.
![](https://nostr.build/i/1b0bb5dea1b947d36e9529e5f4be666a535c67c200c8d1df0c3a95b49586aa2b.jpg)
 10-  The top of the grill is mounted under the Mac Mini case. Lift gently the bottom of the grill and pull towards yourself to remove the grill.
 11- Move the grill aside, you do not have to disconnect the WIFI sensor, just be careful.
 
 
 
#### 2.1 Upgrading the RAM

The RAM is visible and accessible from the moment you remove the cover. Simply release each RAM by releasing the clips on the side. Once disengaged, the RAM will spring in a 45-degree angle. Remove it and put back the upgraded RAM at a 45 degree angle and push it down for it to clip.

#### 2.2 Upgrading the SSD

It is important to note that the Mac Mini has 2 SSD bay. They are referred to as the “upper bay” and “lower bay”. Since we have flipped the Mac Mini upside down to remove the bottom cover, the “upper bay” is located under the “lower bay”.

The “upper bay” is mounted with an expansion kit that holds the SSD in position whereas the “lower bay” SSD is simply resting on top of the “upper bay” SSD.

One important aspect is that the connecting cables for the “lower bay” and “upper bay” SSD are not the same. The “upper bay” SSD connects on the logic board on the right and the “lower bay” SSD cable connects on the left. Removing the “upper bay” SSD requires removing the logic board therefore requires more work. It is recommended to install the new SSD in the “lower” bay. Here are the 2 scenarios:

1- Your Mac Mini has already a Hard Drive installed in the “lower” bay. In that case insert a credit card under the HD and gently pry it upwards. You will be able to slide it out of the bay. The reason to pry it gently is because since there is no “upper” bay drive, The HD is being held in the air by 2 screws on the side that are aligned in 2 holes in the Mac Mini case. Once the HD is removed, transfer the connecting cable and the 2 screws to the new SSD. To put back the new SSD, it is easier to rotate the Mac Mini 90 degree and have the mounting holes at the bottom and use the gravity to get the 2 mounting screws in the holes. After, connect the connector to the logic board.

2- Your Mac Mini has already a Hard Drive installed in the “upper bay”? Leave it there, you do not need mounting screws, but you need a new connecting cable. You will have to buy a “lower bay connector”. Once installed on the SSD, slide the SSD on top of the original one. The connector will plug on the logic board on the left of the “upper bay” SSD connector.

![](https://nostr.build/i/768efa64eaa8985496a4c711de5838afeef1a512c072cecce74f4851ecca30b7.jpg)


A good preparation would be to go in “Disk Utility” menu on MacOS and search for “upper” or “lower” position before starting to disassemble.

Reassemble everything and you are done.


### 3. Installing Ubuntu Server

The next step is to install Ubuntu Server on the device. You will need to have created a bootable USB stick in order to proceed with the following instructions:

1- Connect your device up with a keyboard/mouse, ethernet cable, screen and with the boot USB inserted into the device but still powered off.
2- With the USB inserted, turn on your device. If it brings you to a Ubuntu screen then great move on to step 4, if not carry out the next step.
3- If the device does not boot to a Ubuntu screen with the USB plugged in, we need to tell it to boot from a USB rather than the internal hard drive. Shut the device. Turn it back on and hold “ALT” key once the computer is starting to boot. The “ALT” key is replacing the “OPTION” key on a Mac. Please select UEFI in the menu in order to reboot with the Boot stick.
4- You will arrive on the Ubuntu Server.
5- Next choose your desired language.
6- Select to update to new installer if any updates available.
7- Allow it to detect or select your regional keyboard layout.
8- Choose the basic installation, do not select any additional options.
9- At the next stage it will like you to connect to the internet, the WiFi will not work at this stage so you will need to plug in via ethernet if not already done.
10- Once connected to the internet an IP address is shown on the screen, write it down and press Done
11- Unless you’re using a proxy on the next screen (Configure Proxy) press Done
12- Leave the default Mirror address by pressing Done. 
13- At the next screen Guided Storage Configuration you can select the disk setup, Uncheck “Set up this disk as a LVM” since you want to use the whole disk as your node and press Done.
14- The next screen will confirm the file system summary click Done.
15- Ensure you have opted for the correct disk and confirm action at the pop-up screen.
16- At the profile screen, you can provide your name, the servers name and provide the username.
17- It will ask you if you want to enable Ubuntu Pro, select skip for now.
18- At the SSH Setup screen, select to install OpenSSH server and select Done.
19- We did not opt to install any additional features at the next screen (Featured Server Snaps) click Done.
20- Once the install completes, the screen will show you (Install Complete!).
21- Select Reboot now.
22- Remove the USB drive when it tells you and press Enter.

This should now complete the Ubuntu installation stage, next we need to SSH to the server.

### 4. Connecting to the Ubuntu Server using SSH

Now that your Ubuntu Server is online, the rest of the operation will be done via another computer with SSH connection using Terminal. 

***To connect to your server, you will need to use the following command with the name of the server from step 16 and the IP address noted down in the step 10 from the previous section***

>ssh <server name>@<IP address>

***You will be prompt to enter the password from step 16***

><enter password>


Congratulation, you are now connected and ready to start installing your node applications!

The next Chapter will cover the installation of Bitcoin Core and the initial Blockchain synchronization.

nostr

So I have heard several times that Nostr is for Bitcoiners and that it's scalability is limited to them.

I beg to differ. I believe that people on Nostr embrace a protocol that provides a social media experience that is not ruled by algprithmed based on follower base that some influencer on Crypto Twitter exploits.

Everybody on Crypto Twitter has been notified of the existence of Nostr, it is covered by Paul Barron Network on several occasions, a lot of Crypto influencers (on twitter) know about it be remains only on Twitter. Why is that? Quite and simple because they profit on their Twitter followers. I havent seen a single "Twitter alts influencer" that have decided to jump on Nostr in the name of decentralisation.

I do not think that Nostr is for Bitcoiners, I just think that Nostr can only be fully appreciated by people who do not use their followers as exit liquidity and therefore weeds out most of CT.

What you guys think?