I’ve implemented a lightning node for the BLAKE2b chain, called “Lightning Fork”. Of course, bootstrapping this thing requires folks to lock up sats and create a network of channels, before it can be of any use. Anyone have some BLAKE2b sats that they aren’t afraid to risk to help me set up and beta test a shiny new lightning network?
5 Likes
What is the fastest way to get some if we haven’t mined any already?
I watched a YouTube interview yesterday hosted by Desert Dave where Chris Guida was proposing making mining rewards unable to be spent until Sept. 2027 because of a dispute with some mining pools. I am not sure if this applies to solo mining… But, it sounds like if you hit a block the rewards are delayed.
Is an exchange like Neoxa the solution?
1 Like
Yes, if they mess with the mining rewards, then the only way to get spendable sats will be either via the Neoxa exchange or by selling goods and services.
2 Likes
I’d defiantly be a tester for you.
What do you think would be a number of sats to start working with. 10 million?
Work out the particulars and let me know and of course look into where to buy a few sats if they lock up the blocks for 12 months.
I lost all my xbt in a boating accident but I think I can rustle up some change for a lightning node
2 Likes
I found your boating accident location. There was nothing there.
1 Like
at the bottom of the deep blue sea. Gone forever
1 Like
IMPORTANT: Make sure you have worked out how to use replay protection when transacting on the BLAKE2b chain before you start funding your Lighting Fork. The app does NOT have a mechanism to retrieve UTXOs on the SHA256 chain that get accidentially sent to the base layer wallet.
Setup is pretty straight forward. When installing on Umbrel, select your BLAKE2b node (whether that is Knots proper or my Knots (BLAKE2b) Companion app). Do not point it at a SHA256 node. Then just lauch it and go through the wizard to set up a new node. If you want to personalize your node with a custom name, you can find that in the advanced settings menu.
After insatlling on Start9, select your BLAKE2b node via Actions & Config > Configuration > Select Node. Do not point it at a SHA256 node. Then add a Tor address via Interfaces > Peer Interface > Add Onion Service. You can personalize your node with a custom name via Actions & Config > Configuration > General Settings.
Initially, the BLAKE2b lightning network is pretty boring. It consists of 3 of my test servers with a single, balanced channel between them in a line:
PaulsCode Start9 Full <8m–8m> PaulsCode Start9 Pruned <8m–8m> PaulsCode Umbrel Pruned
Here is the connection info for my nodes:
PaulsCode Start9 Full:
03986eb35a17c136c559d08d4c8e7b40f967870f1887811f9955619c381928c36d@emmcdshbfmzegyuzzxm2xjmyuscqglafbpgbpyetvzd5vluk4ggvilyd.onion:9737
PaulsCode Start9 Pruned:
039c6be4053a51c3ca1b10dbea660467989b0ab85889e7345fabb52c96688dd066@c5h2lxsvx6j42jtrnac36gle7wbwykqngwt2phbu2oxz3qubmol6m4qd.onion:9737
PaulsCode Umbrel Pruned:
03bc65e7dba6233f6214f4f47dac2691a6c30284b395c32208635ecf464bcf14a4@gj6ggvh45o3hhsfknkwibihxzw6zhp6ymzoouxo3ylor2b6v6x6boeyd.onion:9735
As you open channels with my nodes, let me know your connection info and I’ll open channels back (until I run out of the sats that I’ve reserved for lightning).
I think the maximum default channel size is 16 million, but it is actually better for decentralizing the network to have many small channels rather than fewer large channels. My proposal is that each person who wants to help bootstrap the network, post your node’s connection info, and agree (where it is affordable) to open equal chanels with eachother.
For example, user A opens a channel of 1,000,000 sats to user B, and user B opens a channel for 1,000,000 sats back to user A. If we get lots of connections like this, it will create a good network of routes, rather than one large centralized hub that everything is routing through.
Once we get a lot of nodes going, then things can be more randomized where we don’t necessarily have to have two channels between every node.
2 Likes
Setting up a channel now 
Cool. If you find that one of my nodes is down, just wait a bit and retry. I am running a lot of tests on my end as well, and some of them are with having one end of a channel unreachable to test failure scenarios.
1 Like
Are the sats I have from last weeks mining locked up?
If 100 blocks have passed since mining then they are spendable.
1 Like
I think you are asking if they are replay protected. I would say no. Technically they have diverged for now, but because of the “vibe coding troll” threat, the previous transactions could replay at any point (it just takes one troll anywhere in the world with access to a LLM to write a transaction repeater, and every transaction on the SHA256 chain that didn’t go through during the chain freeze leading up to the hard fork will be replayed on the BLAKE2b chain if it is still valid, thus opening up all subsequent transactions on the BLAKE2b chain to be replayed back to the SHA256 chain, and so-on).
You will want to ensure that your BLAKE2b coins are replay protected before you start sending them anywhere. For that, I recommend getting Sparrow BLAKE2b up and running, and use a version of SeedSigner that supports replay protection to send your BLAKE2b coins to yourself. Once you confirm that transaction did not replay on the main chain, you can be sure about your two stacks being perminantly separated and safe from replay moving forward.
1 Like
And that would be where? Do I have to build it?
1 Like
I have a version here for the SeedSigner Plus (big screen version) I think there is an unoficial firmware for ColdCard too, and there are probably other forks of SeedSignerOS besides mine for the smaller seedsigner standard model (I haven’t been plugged into the hardware signer discussion as much as others have been)
1 Like
Ok. Gotcha. Unfortunately right now I just don’t have an extra 150$ lying around. I’ll just watch your Lightning Fork from a-far. Thanks
1 Like
Actually, I just thought of a simple option that doesn’t require a seedsigner with the updated OS. All you need is Shrike or Sparrow BLAKE2b:
- Create a new hot wallet in Shrike/Sparrow BLAKE2b
- Send a small amount from your cold storage to the new hot wallet (something insignificant, not dust, but no need to risk much here).
- Send that amount from the hot wallet back to cold storage, with unified sighash selected (make sure it shows Replay protected).
- Now do a consolidation transaction in your cold storage, combining the replay protected UTXO with other UTXOs that you want to also be replay protected.
The output from #4 will be replay protected UTXOs in whatever size you need, that never left cold storage, and never required a hardware signer that supported unified sighash.
1 Like
Last night my Little HS Box joined the CONVOY pool… On my way to having sats for beta testing.
A week of solo mining at 500GH yielded no blocks. By the time I received the miner from eBay… I was already late for class.
1 Like