Running both instances of Bitcoin (SHA and Blake) on a single Start 9 server

I’d like to support the new Blake fork by mining using my existing Start 9. However, I still need to transact on the SHA chain so I’d like to run both versions on a single Start 9. Is it possible to run both instances safely?

1 Like

Yes, I’ll be releasing a video tomorrow on how to set this up. The currently supported configuration is Knots pre-RDTS as the main full node (with the normal versions of Datum Gateway, Mempool, and Electrs, plus official Sparrow). Then my Knots blake2b “Companion” (runs as a pruned node out of the box) with my custom “pruned companion” stack (Datum Gateway Blake2b Companion, Mempool Pruned, and Electrs Pruned). The final piece is a Blake2b compatible build of Sparrow (which I also have available on my Github until there is an official one)

I’ll eventually also be supporting the opposite configuration: main node as a Knots BLAKE2b full node with blake2b-compatible Datum Gateway, Mempool and Electrs and a Blake2b compatible build of Sparrow. Then my Knots pre-RDTS “Companion” along with my pruned companion stack (Datum Gateway Companion, Mempool Pruned, and Electrs Pruned) and official Sparrow.

5 Likes

Hi Paul,
Looking forward to this video tutorial. Yesterday all day fighting to set up the blake pow mining fig., but without succes. Conflicts in Datum/Stratum. Connor’s lab also gives good info. It is all still above my head but I can not leave this creasy rabbithol. See You later on YT meanwhile I continue figthing this amazing monster.

2 Likes

I have the latest Knots (RC4) and Datum RC4 installed. Also I will try to test my Obelisk SC1 Gen2 today on the Knots and Datum You have build. Can this setup co-exist?

2 Likes

So are we!!! Let’s keep it together, both running before we lose our hard earned BTC coins!

WOW! That’s a great job, Paul! I wait without holding my breath but we do need you to salvage the wrecking ship! LOL Thanks! A million sats wouldn’t be enough to pay you.

Yes, my forks are designed to run as a “companion” node stack alongside your main node stack. My goal is to allow folks to run a second (pruned) companion node on the same server. This will enable folks who want to follow and transact on both chains but can’t afford a second server or an expensive NVMe upgrade. It also could be used as a fallback option if there are issues with Retropex’s forks.

1 Like

Great! Can’t wait! Take your time, Paul! Slow & Steady wins the race, as they say in the UK, or in Scotland! The rat race can wait, so can we! Surely and securely. NVMEs are gold dust! I just found a 1 TB Samsung SSD 5 at the second hand-shop CEX here for 90 euros, with 5 year guarantee!!! Snaped it! Here are some guys on YT ranting on about Blake2b (mining) and otherwise: https://youtu.be/6Vms_s05-3Q?si=o8aWZ6Ojad5SXE78 More sensible guy---->>>> https://youtu.be/QKYdAzF4eyM?si=CSeC3WHxjdOLvFEI Anyway, “We Get By Cose We Try” (old song by Leo Pennant (c) 1973 “I Get By Cose I Try”. No spam!!! Haha!

Pardon,Sir.

I wonder if the video tutorial has already come out. Dont wanna missed out the video. Thanks a lot.

1 Like

Yes, keep at it, Paul. We need a full tutorial on these. Your Blake2b Sparrow clone isn’t connecting to my Start9 Electrs, not even to your Pruned Electrs anymore.

Hi, Paul. No sleep till Hammersmith (Motorhead); Your Blake2b Sparrow clone isn’t connecting to my Start9 Electrs, not even to your Pruned Electrs anymore.

Paul hasn’t published a video since 10 days ago “Testing BLAKE2B ASIC …”. Lots of us need that video to get our Start9s working again, apparently. All I can do right now is hammer out metal backup seeds.

1 Like

Sorry, lots of moving parts right now, so finding it hard to fit in a recording session. Things upstream are changing so fast that it is hard to keep up and release updates to my downstream apps.

5 Likes

Take your time Paul keep healthy first programming second

1 Like

Yes,Sir. Stay Healthy & Happy.

1 Like

Update on expected timeline for the companion stack video:

This one will cover installing the services on one of my test servers, plus actually using the companion stack to send/receive transactions. For that I will have two other test servers set up and fully synced. One will have pre-RDTS as the main full chain and BLAKE2b as the pruned companion node. The other will have BLAKE2b as the main full node and SHA256 as the pruned companion node. And my Umbrel server (I only have one) will be in the former configuration.

I’ve got the Umbrel and the two Start9’s working through the IBD (then electrs pruned will need to index after that). They should all finish up over the weekend here, and I’ll record the video after that.

2 Likes

Is the Knots (SHA256) Companion a pruned node by default? I downloaded it and didn’t see anything in the settings about pruned or full node.

1 Like

Good catch. I think when I ported in the extra bells and whistles from upstream, this reverted from pruned by default to based on the size of the disk (pruned if the disk is too small, pruned, otherwise full). I’ll fix this and push an update shortly so it defaults to pruned unless the user decides they want to run two full nodes.

1 Like

If you’ve already installed it, you will need to go to Actions and Config → Other Settings → Pruning and set it to 5000 MiB:

Otherwise it will likely try to run as a full node, and will fill up your disk if you don’t have enough space to run two full nodes.

1 Like