Odd… I have 3 channels to some of the bigger nodes. Olympus (Zeus), Megalith and 1ML.
Guess it doesn’t work 🤣 nostr:note10zl6swfmju0mxrx5afkdxgydpct9gwyx39rafwzezpr2txkkuezsmjn2u0
Very strange, it’s set up like it was last time I used BTCPayServer and I have inbound capacity. Oh well, one for another day.
In theory… I can now receive zaps to my BTCPay Server… in theory… 🤔
Happy new year everyone! 🥳
I’m opening some channels on BTCPay Server and want to create some inbound capacity. What’s the most cost effective way to convert lightning to on-chain BTC to create some? Would rather not buy an inbound channel. #asknostr #bitcoin #lightning
Nearly there 🥳 
Sleepy little man #petstr #dogstr 
It’ll be the processing/validation, the server is running on a 10gbit symmetrical connection so 700gb won’t be an issue 😁
69% 🥱 nostr:note1lh5fu3n8hzsnr293fsrm0cdl2asnlv6jrp45paujm2a7u5mqs35qkmn69d
?kjy_fallback_url=
Is it real this time? I’m sure I saw this earlier this year and turned out to be wrong.
Making progress, on 56% now 🤣 nostr:note1glr8t5jxnhpg9qtguvku9unwq7t7tukps602rqfnvk0hsmkzm78q78nu5f
Yeah, the second part of the blockchain takes the longest to sync 😅⏳
Used to take my nostr:npub1aghreq2dpz3h3799hrawev5gf5zc2kt4ch9ykhp9utt0jd3gdu2qtlmhct 1 day to fully sync, now the last 50% took like 4 days.
And people ask why inscriptions and big heavy shit is bad for the blockchain😭
#noderunners #bitcoin
Yeah, I used to use BTCPay Server before but moved to Alby Hub since I was mainly using lightning. Wanting to do more integration with some of my projects with both on-chain and lightning without hitting any API limits.
This is going to take a while… 
Moved to WoS while I close channels on #albyhub and establish on BTCPay Server. More flexible for the integration I want to do on Zap ⚡️ Vegas.
I like #albyhub but on chain is buried in the UI and not accessible via the #albygo app. Thinking I may move back to BTCPayServer in the new year.