So reprocessing the scb recovery on the Umbrel Pi because no matter what I do, raspiblitz' lncli won't perform the recovery from scb (can't connect to lnd). So restarted the sequence on Umbrel on the Pi from a preexisting chainstate and it is processing each chunk of 2k blocks every 35 minutes or so. It won't let me run the scb recovery until that's done, which should be in about 7 hours, then hopefully the bulk FCs will be successful! Boy this recovery has been a pain!

Node all caught up and force closures running from the scb! If you get a FC from RecklessApotheosis let me know in the comments!

OK, hardware has all arrived and our plan is set. All but 9 FCs have settled, tomorrow we install the OS and hopefully before the end of Saturday the node will be up! There'll definitely be sats for balanced opens, so watch here when we announce channel reopens, it'll be a bos balanced-open extravaganza! If you do the Twitter thing, we made a thing you can follow, but mostly we'll be on Telegram still. https://twitter.com/RecklessNode

RecklessApotheosis Rebirth Update: Friday I set up the node hardware, RAID, and host OS. Then I set up the VM, and the general Linux stuff. Saturday installed bitcoind, made sure it was fully synced, installed postgres 15, LND, and got through much of the configuration. Got stuck on a 4 hour call with a friend debugging an nftables port forwarding issue, and then debugging why LND can't talk to postgres. Today I'm working on tor, LNDg, bos, and continuing to figure out the postgres issues. Sincerest hopes are to have the node working today or tomorrow!

OK, thanks to the tremendous help of two friends, and the NodeRunner community (@Osito_ln, @Hakezuba, @allyourbankarebelongtous, @NguTechnologies, and others!) we now have LND working on clearnet (still had issues with Tor) and caught up with rescanning my old wallet (way faster on x86 than on the Pi). I also now have LNDg & bos installed and running (LNDg is having nginx isues but that's just cosmetic, but it is running from postgres!), and bos-telegram running! Last steps will be to get RTL & TH installed and running on boot, but those don't gate getting the node up. So now we're updating our list of channels to open and their capacities. Once those are open, we'll make a broad announcement of RecklessApotheosis being successfully reborn and ready for new inbound connections! We are also trying to come up with a good strategy for balanced reopens! This has definitely been a journey, but quite the learning experience, and I'm overall really satisfied with how the node is put together now! We can't wait to welcome everyone back into the #Reckless Family!

First new channel being opened after a long arduous journey! I'm going to bed, and tomorrow I'm doing an all-day site visit to a Bitcoin Mine. But assuming this works, I'll post another update saying that RecklessApotheosis is back up and open for business!

⏳ Opening new 0.01000000 channel to Amboss.Space 03006fcf3312dae8d068ea297f58e2bd00ec1ffe214b793eda46966b6294a53ce6.
RecklessApotheosis 03c72f89

At long last, in block 760425, #RecklessApotheosis is reborn! 960 sats to open 21 channels! That's incredible! At this point, with the bulk creation of core channels underway, we are pleased to announce that RecklessApotheosis is welcoming all plebs wishing to open inbound channels to the node, and reward them with 30 days of 0/0 fees! At the moment, we haven't migrated over our scripts that refund opening fees but the intent remains to refund up to the first 300 sats of all inbound opens! We'll be announcing balanced opens capacity & policy in around 18 hours once everything settles. Happy routing, and stay #Reckless!

OK, Status Update! We transferred our scripts & LNDg settings over to the new node, and rewrote some of the scripting to be more automated. We have retro-actively refunded all inbound channels that have already been opened to us, and as we're currently trying to build our node back up, and since ZFR is spinning down, all inbound opened to #RecklessApotheosis will benefit from 0/0 fees until January 1st, 2023! This does not apply to dual-funded channels, which, by-the-way, we are now also accepting with the following criteria: dual-funded channels must be a minimum of 5m sats, fees should be 1s/vB, and dual-funded channels are immediately subject to auto-fees & do not get their opening fees refunded (but they're split anyway, so it doesn't really matter). Once we run out of sats for dual-funded opens, we run out! Act today! Thank you all again for your patience, and the community support of the awesome Plebnet folks!

24 hours in and we've opened 11 channels and grown by over 118m sats! We still have on chain sats for balanced opens and 0 fees until 2023 for inbound opens!

A happy 14th Birthday to the Whitepaper and the world changing machination it set into motion! Here's to the next 14 years!

Good morning. LND is broken. Wake up!

Details:
https://github.com/lightningnetwork/lnd/issues/7096

brqgoo commented 5 minutes ago
Bitcoin has a consensus rule that limits the number of stack items in a row to 1000. However, a P2TR spend containing OP_SUCCESSx precedes this rule regardless.

I made a P2TR spend containing an OP_SUCCESSx opcode with 500,001 empty pushes, which as a result, caused a consensus conflict between btcd and core:
https://blockstream.info/tx/73be398c4bdc43709db7398106609eea2a7841aaf3a4fa2000dc18184faa2a7e

Changing the maxWitnessItemsPerInput parameter from 500,000 to 4,000,000 solves the issue:
https://github.com/btcsuite/btcd/blob/master/wire/msgtx.go#L103


To limit your forwards, you can run:

bos limit-forwarding --disable-forwards

and leave it running in the background or inside a tmux session.

RecklessApotheosis is back up and on LND 0.15.4 and latest openssl also just to be safe, happy routing!

Our first week back in the saddle is behind us! #RecklessApotheosis spent 10k sats opening and balancing channels, and earned 23k sats! Overall a low routing week, but we did grow by 22 channels, putting this week squarely in "a good start" territory! We are offering 0 fees on all inbound channels until 2023, and accepting all dual-funded requests until we run out of sats! Happy Friday, and Happy Routing! Live #Reckless

Ideas are Bulletproof. Remember, Remember...happy Guy Fawkes Day to all our fellow economic revolutionaries! #Reckless

So RecklessApotheosis has been without power for the past 2½ hours, and the upstream Internet finally went put despite out modem still having power. The node is up and healthy, so we're just in a waiting game until the ISP gets their systems back up and running!

Power is restored and our ISP is back up, RecklessApotheosis has resumed routing!

✨ channel with RecklessApotheosis was reactivated after 2H 31m

RecklessApotheosis is currently offline, we have power, but Spectrum is awful. So until the ISP comes back up, we are offline. Sorry folks.

Well, that was frustrating, but I'm back and restarted the modem and we are back in business! Sadly had an FC during the outage, drat.