Oddbean new post about login | logout the new electrs build is ready, the docs said the build would take ~20 minutes, I didn't measure it but left it running in the background and it took longer than an hour. bitcoind is still syncing in the background, blocks are at june 2024 now, will probably be finished by tomorrow. After that I will start electrs with a fresh sync too. https://media.utxo.nl/wp-content/uploads/nostr/0/c/0cd714489d13eafeb5f0dcc5fb8a581599d619a68d693cd4f6d54effc7fa491f.webp
I took the latest lightning lnd from https://github.com/lightningnetwork/lnd/releases/tag/v0.18.3-beta At first thought I copied wrong version because the file dates are jan 1st 2020, but after checking —version it says 0.18.3-beta. Probably the machine used to build it has the wrong date or maybe needed for deterministic builds, I never looked in to how thats done. https://media.utxo.nl/wp-content/uploads/nostr/7/0/70a64819b224ed31893cf0f9e43299058596605d0c4bd3a20be07e5b6cd6fff9.webp
bitcoind has finished its sync, now I can start electrs. I wasn't sure how slow the sync would be so I tried it first from scratch but it was going very slow, would probably take days, so instead I copied over the data from my old disk, which was around 50 GB. With bitcoind running, electrs running, I can start the mempool backend and my now local block explorer is working: https://media.utxo.nl/wp-content/uploads/nostr/d/8/d8c3aee4a8967d6602e352d1522084b6e2b77d3f440b766413d27f564b87b235.webp
now I should also be able to start lightning lnd but I was getting errors: [ERR] LTND: unable to create partial chain control: unable to determine if bitcoind is pruned: unable to detect bitcoind version I vaguely remember @Derek Ross posted about a special config flag and after some digging around that was it: nostr:note18lz63u08tdtxslhznayxw6sq6f7t0mu4vtt6fd6lvfxek0h29d9qtgf8hm lnd can’t connect to bitcoin core v28 without it, after adding the flag the problem went away and my lightning channels are back online.
Now time to get the BitAxe lottery miner connected, I can't connect it directly to my bitcoin node, it needs something that does stratum protocol in between. A few options I found: public-pool, ckpool, stratum SRI. public-pool seems easy to use but needs nodejs stratum SRI looks way too complex for solo lottery mining, I don't understand anything on the docs so I'm trying out ckpool, it has instructions specifically for solo mining which I'm following: https://bitbucket.org/ckolivas/ckpool-solo/src/solobtc/README I'm doing it the same as with electrs, building it in the virtual machine so I can keep the NUC clean. Following the steps, I kept getting stuck on the ./configure command. For some reason this line in configure breaks it: PKG_PROG_PKG_CONFIG(). I'm not sure what it does but the only way I could continue was by removing it. This resulted in 4 files, I think only 1 is needed for solo mining but I copied all 4 to the NUC just to be sure. I pointed ckpool to bitcoind, and the bitaxe miner to ckpool and all looks good: https://media.utxo.nl/wp-content/uploads/nostr/5/5/55373953ccc9bf24d9fe793df10f98d4b63e74d8cf616fb54a099cf4e8fc8c90.webp https://media.utxo.nl/wp-content/uploads/nostr/0/3/03232d050fc23fc37b6b7bae401e142030780d1d53328ae20f5045a230df6b39.webp https://media.utxo.nl/wp-content/uploads/nostr/3/1/316a5bc64f12ee0414c1e456c66c96f06bc491ba19bc0080ec1ba9a351987e16.webp
Nostur is really great, but seriously? Automatically putting a poop emoji next to tags like #xmr or #monero by default? I thought I wouldn’t find this kind of thing in clients built for Nostr. What a shame! https://image.nostr.build/0e2fcc35f997b63af848ee9324a3e541b6811379eed4a9e8e3b5c76ed6d1f5ef.jpg
