I'm having issues connecting my blue wallet to my lndhub. I've tried trouble shoots from online but none are working for me. My biggest issue is when I go to scan the qr code from lndhub, it says invalid lnd hub URL. I was able to connect it through my local IP address by typing in the http://1**.***.*.*:3008 format, but obviously that won't work unless I'm at home. Any help would be appreciated!

UPDATE: I forgot to add Blue to the orbot app...

New to the lightning concept, and I understand it as a solution around Bitcoin's high transaction fee and long confirmation time.

Got started with the Aqua wallet to set up my lightning wallet. So, I have a few questions.

• Is this specific wallet trustworthy?
• am I, in general, trusting anyone else to close the lightning channel when I need the funds on the Blockchain?

So how does the trust structure work here and who exactly am I trusting to keep my funds safe here? Want to understand these before I put in my fund.

I'm running a self-hosted Alby Hub instance. I woke up to an email that said a node had been closed and anything in it had been returned to my wallet. I had about 150,000 sats in the node, and about 30,000 were returned to my wallet. How can a node I paid to set up just randomly close, and why didn't I get all of my sats back? Any help is appreciated.

Seen a lot of people complaining about trouble with various node software lately, both custodial and non-custodial types that try to handle channel management "automatically." Some of them kinda work, but you lose control of the fees you pay and troubleshooting can be hell because you don't control your own channels.

Thing is, channel management just isn't as hard as the FUDers claim, especially if you're not running a routing node to make fee income. Yes, liquidity is a new concept, but once you grok it things are easy. Hell, I AM running a routing node and channel management is still just an annual weekend project, and frankly kind of a fun one.

These are the tools I most recommend to run a DIY LN node:

• Raspibolt - The original DIY tor-focused LN guide, now supporting all major architectures. Gets you what you need while leaving all extras optional, 100% under your control. This is how I run my node.
• Raspiblitz - Suped-up Raspibolt with more tools and QoL features built-in by default. Still DIY but maybe a little farther from the metal.

Raspibolt is even a good small project to *learn* the Linux CLI, if that's something you're interested in.

I hope my blog post at https://gadgeteer.co.za/how-to-test-if-a-self-hosted-alby-hub-wallet-is-connected-and-to-get-an-alert-if-not will help out other Alby Hub self-hosters who want to get alerts if their wallets are offline. This seems to be working fine for me now, and the same theory can be applied for a Python script or even a bash script.

Hi!

I have been trying to send from Phoenix wallet to Alby Hub via lightning in different moments. If I try to send 5,000 sats, it's ok. But if I try to send 250,000 sats or 10,000 sats, the transaction fails. In Alby Hub I have a 1,000,000 channel with space to receive, so this is not the issue.

I contacted with Phoenix wallet and Alby Hub supports, and they say the system is ok. Do you know if there is a limit amount to send via lightning? I ask this because I had the same problem trying to send from Coinos to Phoenix or to Alby.

Could you help me, please?

Thanks

https://preview.redd.it/cm79rl00l07e1.jpg?width=549&format=pjpg&auto=webp&s=6883b69077ab27ccb9fe3dc5dda3255949bbc2e2

I've been dipping my toes into the Lightning universe this past year, mainly to support a few podcasts I frequent. Alby was by gateway into this and I've just moved over to a self-hosted Alby Hub (via Docker) as per their instructions these past few months.

All appears to have gone through fine, but I noticed only 36k of my 63k sats migrated. I checked the transaction and noticed a send of 27k sats for "Lightning inbound channel, provided by Megalith LSP".

I'm assuming this was when I opened my first channel.

I don't remember seeing any warning about the charge before I connected, and I understand these services need some form of subsidy to stay afloat, but I think almost half of my "spending" pot was a little much.

Is this normal when connecting to a Lightning Service Provider?

https://preview.redd.it/hoyl31arnh2e1.png?width=660&format=png&auto=webp&s=2fadb5d96f360f292930783941ae9153288ce9e6

I want to send bitcoin on LN and recieve it on chain. boltz.exchange seems good but are they trustworthy and reliable for larger amounts? Alternatively, is there a wallet supporting both ln and on chain that can serve the same function?

Hi anyone I’m in the USA I have a Coinbase wallet what’s confusing me is that when I go to pay the Vendor I get 3 options the Amount I need to pay a Payment request field and a Peer field. I’ll be damed if I know I’m looking at. I looked at some videos but I’m still confused as fuck.

Hello,

I have been running my node since 2020, and it has suddenly stopped synching. I am using LunaNode's one-click deployment. It stopped working at block 865,866 on Oct 16th. At that time I notice there is a huge spike in CPU usage on my server. I upgraded from the m.2 to the m.4 plan for more CPU, but it is still not synching. Also, the CPU usage is around 80% again after the upgrade. Any idea what is going on? I am really lost.

My apologies of this is the wrong Group.

How do I retrieve the remaining on-chain 25000 sats from my LND?

https://preview.redd.it/91snf5gcwpqd1.png?width=772&format=png&auto=webp&s=9ec01e9cd7ea491bb1c10190f2e9d951418d4851

If I try to send it all to my BTC address it errors with ...

https://preview.redd.it/6tzg2eqnwpqd1.png?width=563&format=png&auto=webp&s=882716dd0719a8245c5c697309ea57396f12a046

September has consistently been a tough month for cryptocurrencies:

Bitcoin
2019: Dropped from $9,700 to $8,300, rebounded to $9,200 in October.
2020: Fell from $11,600 to $10,700, surged to $13,800 in October.
2021: Slid from $47,000 to $43,800, bounced to $61,000 in October.
2022: Stayed around $20,000, slightly up to $20,600 in October.
2023: Modest gains from $25,800 to $27,000 in October.

Ethereum
2019: Dropped from $170 to $160, modest recovery to $180 in October.
2020: Fell from $440 to $320, rebounded to $390 in October.
2021: Slid from $3,200 to $3,000.
2022: Dropped from $1,600 to $1,300.
2023: Held steady around $1,600.

But October often brings a rebound! Will September 2024 follow the same pattern?

Hi.

Could you please point me tutorials where I could learn how to develop smart contracts and DApps that run in the Lightning Network?

I've "googled" it but all I get are related to Ethereum and Solana...

Thanks.

Can someone comment or link me to some resource.. Penalty channel closing transaction published but transaction fees at that time (let's say) are ~2000 sats/byte or basically too high for tx to be mined in the required time? What is it 500 blocks? What happens?

⚡We've added a Lightning invoice decoder to Amboss Space!

Invoice decoders deliver insights about payment requests that can come in the form of an invoice, an LNURL, or a Lightning Address.

To demonstrate the insights you can derive, we've prepared a thread of wallet invoices! https://m.primal.net/IflK.png

Starting simple, here an invoice from BitcoinJungleCR, a custodial lightning wallet: https://amboss.space/lightning-decoder?request=lnbc26530n1pnxr0krpp5fzk3u3h46zwu2h9c020kkagaez33fhfgwtk4e0hkdvtg56pk6tvsdqqcqzpuxqyz5vqsp5gtp6m6xc8663lth4a07mrf434u0ryzusdzhafc44ukl6ahyw6w0q9qyyssq0dzfdugg4d9sykwmk3t4vcecwqwxtd5qr2zaj4dnldmm52rsvaq93ecddzdxlpzsqt06qexnruerznzh22u50v79ajtun8c75k9gkyqpxx7wna

Similar setups include: zbd, walletofsatoshi , and Strike

This is a BOLT11 invoice where it pays to a single node destination. Routing Node Operators will use the Payee Pubkey information to discover new nodes to connect to so that the network can have a variety of routes to pay BTC Jungle CR reliably.

https://amboss.space/node/03797da684da0b6de8a813f9d7ebb0412c5d7504619b3fa5255861b991a7f86960

Next up in complexity, a BOLT11 invoice from Breez, a self-custodial lightning wallet: https://amboss.space/lightning-decoder?request=lnbc140270n1pnxr0sppp5rzurtshg5e6dk9zgewt3p3jm8t33t9vspq55u6huu2yxvew6v76qdrgyp7q5nmjv9hxwefq2dhxz6m9yp7zqcnjv4jh5w309ac8ymmxd9kx2hmfd4skweflv9hxjmtpds74xmnpddjjvcm0d3hhy020wfskuem9cqzzsxqrrssrzjqvgptfurj3528snx6e3dtwepafxw5fpzdymw9pj20jj09sunnqmwpapyqqqqqqz3rsqqqqlgqqqqqqgq9qsp5ck43qflj7v764wzwmu68nw4u8a7nc2sxh3jg25u5x43epza4fzyq9qyyssq0t9pjqz9fkyk0cgfp7salwgs42urzvkdnk8cscucmxm3xeuuw8ypu6ypwdn5adcq73wuq8y820aevtgnledpfclytq7jnfxr6p8tjgspcpvw3x

If you check the Payee Pubkey of the Breez invoice, you'll reach a page that says "Unable to find this node". This isn't a error; this reveals that @Breez_Tech is using "private" node destinations.

To help the lightning payment reach the destination, it will require Route Hints! https://m.primal.net/IflV.png

In the Routing Info is a Pubkey, revealing a well-connected 28 BTC capacity node that will convey the payment to the "private" node destination. https://amboss.space/node/031015a7839468a3c266d662d5bb21ea4cea24226936e2864a7ca4f2c3939836e0?section=General Services with similar setups include: MuunWallet (uses a swap service), ElectrumWallet (yes they do lightning!)

"Private node" here only means unannounced to the network (like not listed in the phone book), not a guarantee of privacy.

There are many reasons to use private nodes in practice and most of them are operational: load balancing, payment reliability, failover protection, etc.

Even more complex, we have @CashApp invoices, which include 2 separate paths to reach a private node destination. https://amboss.space/lightning-decoder?request=lnbc1pnxrdk6dqdgdshx6pqg9c8qpp59d8cvaf5209myfkn9wk67ywa5exyt230gjpkjs7dh0yxzczaqk4ssp5e8e6wehwurw4zdfs6lkj5s9my702vpxjs26zfyv3vmrw00x64k0q9qrsgqcqpcxqy8ayqrzjqv06k0m23t593pngl0jt7n9wznp64fqngvctz7vts8nq4tukvtljqz3rvvqq88sqqsqqqqqqqqqqqqqq9grzjqtsjy9p55gdceevp36fvdmrkxqvzfhy8ak2tgc5zgtjtra9xlaz97pmylyqqt0gqquqqqqqqqqqqqqqq9gwmef3kht3jvnnft2yqagtdr6qsp0mw00mcs334wmjakjxf7m0suy3dm0cjcr9vd03c500225tf4suxu9ufrsqrl2p3k748ctvlygm3cpcr888n

Instead of only one potential path to pay, there are now two which can be attempted. This allows one of the public nodes to undergo maintenance while the other remains online to ensure higher payment reliability.

Makes sense when you have 50 million potential users!

Okay now it gets crazy complex: Fedi Bravo includes not only two separate routing paths, but there are multiple hops in the second path! https://amboss.space/lightning-decoder?request=lnbc14020n1pnxr074dqqpp5xzdnu633p42vkzff63smmvwnq6sceaulhv7dzsjznwagnapa56xqsp57g7ryur6wu5nm8jujm0cud8mtuhl7xapzrvlz0dqk5p9ct6ultgq9qrsgqcqpjnp4qv0q27a396eh8yxewxpmnydkwghn4rj4f79n3305e9hats65u4ctjxqyz5vqrzjqtcv0de3efq29pwhcy42r3w8cl92gkvd84knfyzvxu2v6r28s5nyqqqqqqqqqqqqpvqqqqqqqqqqqqqqrcr9yqdjfz0gc5xwxwxandhgy66k4hc873u5fgv2vx65ak0crct2pfyr7zrxmuuqq2ccqqyqqqqlgqqqqqqgq2qp0p3ahx89ypg596lqj4gw9clru4fze357k6dysfsm3fngdg7zjvsqqqqqqqqqqqq9sqqqqqqqqqqqqqq0qg3ttsncut24rz2a3ztnzh739rqad26d2gta7p4frktpynac6c3rpdz3kfexv44jqd3tqjkuwyqp97laun39nf2p0vp7hf5afdnaerxqpt97cd0

Look how long the invoice string is! That is a lot of data to pack into an invoice, which can also make the invoices more difficult to scan as QR codes or be unable to fit into a tweet.

Setups like this one are fascinating, but each decision is a tradeoff.

In the 2-hop path, the first stop is LQWDTech followed by "Henwen 🐷", which was also used in the 1-hop path.

This must make Henwen one of the "Gateways" into the ecash Federation. https://amboss.space/node/0364913d18a19c671bb36dd04d6ad5be0fe8f2894314c36a9db3f03c2d414907e1 https://amboss.space/node/02f0c7b731ca40a285d7c12aa1c5c7c7caa4598d3d6d34904c3714cd0d47852640

Mind blower time. Let's talk about Aqua invoices. https://amboss.space/lightning-decoder?request=lnbc10u1pnx8q58sp5cvup8kkedrjfam0yqvhtydml82fg9tmpep8nxcqhm0s8jvppac9spp52zywkv3exryqemtuphutpfrmh6qz09epvln74y0mjn3sg3fzyqrqdpz2djkuepqw3hjqnpdgf2yxgrpv3j8yetnwvxqyp2xqcqz95rzjqgjw2dner5zaawm3q3tj30wgu8k56gsg9seprne6hyr7kj4v3gmpxzzxeyqq28qqqqqqqqqqqqqqq9gq2y9qxpqysgqwks76mx5zmy2gyvzlrqdpwqdru3m0rnrdm7nek7xh9398upyhfxsy8txfhm07hmvzdw7sajstv2zt75hjdhhsktyfx6edz4jhtm5cdqpx69erp

Aqua invoices only include a single route hint, but the route hint is to a private node!

The payee pubkey is a public node, Boltz, which swaps between the lightning network and Liquid_BTC.

Boltz is using "magic routing hints" allowing Liquid to Liquid payments within an LN invoice. This invoice isn't actually used to send a lightning payment; it's using an invoice as a communication tool for a Liquid transaction. https://docs.boltz.exchange/v/api/magic-routing-hints

What else would you like to know about invoices? What other insights can you gain from this tool?

Greetings All!

I am currently readying an information-based blog site for which I want to provide the option to accept small Lightning donations something akin to the "Buy me a coffee" option you see on many sites.

I just need something ultra-simple where people can just zip me a few sats if they feel the site has been useful to them and I want to know the cheapest and, more importantly, easiest to implement solution that will actually work.

Firstly, pardon my ignorance if this is a stupid question as I am still quite new to Lightning, but if I just provide a link/QR code to the receive address displayed on my Phoenix wallet on the site, would that work, or would it send a message saying the invoice is already paid if more than one person used it?

I saw another poster talking about OpenNode, but as my site is not an E-commerce site I want to avoid having to set up WooCommerce or the like unless I need to.

Any advice would be greatly appreciated. Thanks

I need some help from some of you clever lads and lasses on here. Last Friday (5/31) I sent an on-chain payment to fund my Phoenix lightning wallet (I am a beginner with Lightning). I read before that there can be problems with the swap-in to Lightning if the amount is too small, so I sent 2 million sats (which is not an insignificant amount to me at least). As of now, the amount is still shown as incoming with a "sleep" mark. I know the swap-in can fail if the max fee is too low, so this is set to 20,000 sats which I would have thought would be sufficient.

In Phoenix, I see under "Mempool" message like "Fees are currently estimated at around 9,928 sat" but the swap-in never occurs.

The one response I have gotten from Phoenix email support so far was as follows:

Can you go to Settings > Wallet Info > Swap-in wallet ? If the deposit has confirmed, but is not swapped, you should have a "swap-in attempt" message with a failure regarding due to high fees. It will give you the exact fee that was expected by the network.Note that the message in your screenshot is an estimation and can be off.Also, make sure you're running Phoenix v2.2.4 (see Settings > About to know your version).<<

I checked this and there are no "swap-in attempt" messages. I also confirmed I am running v2.2.4.

Can anyone help me figure out what might be going on? Is it possible the estimated fees are off and are constantly above 20,000 sats? I thought if this was the case I would at least have swap-in messages.

I would be really grateful for your help as Phoenix support have stopped answering my emails.

I recently integrated opennode on my site to accept lightning payments. I didn't think anyone would actually use it, but I was wrong! Got $1.50 worth of sats already! I've been using Stripe for my other payments and it's crazy how much they take out of each transaction. Most of my sales are micro payments. I end up losing almost 15% with Stripe and with Opennode it's just a flat fee of 1%. Really hoping that I can get more lightning users!

If anyone is using AI regularly (GPT/Claude/Gemini/etc...) and doesn't want to have multiple monthly subscriptions, feel free to try my site. You just pay for the API usage which ends up being super cheap in comparison to a 20 dollar monthly fee. The site is novlisky.io

Thanks!

Any lightning enthusiast willing to open channels?

03a858314a8b0bda32475cb90c34056d3a4faeb00a88489f4fd7689cc39b208c84@fbzvyv5seznojibqxrepoynxchxf22v4edpi66vkkkoz6j5yts3h66yd.onion:9735

https://amboss.space/node/03a858314a8b0bda32475cb90c34056d3a4faeb00a88489f4fd7689cc39b208c84?section=General