My issue is that I don't know the format of these addresses
they are not exactly addresses, they are invoices and they are encoded using Bech32 encoding with the HRP=lnbc and they include a lot of other thins such as timestamp, payment info,.... it looks like this (this is an example, don't send anything here!):
lnbc1pvjluezpp5qqqsyqcyq5rqwzqfqqqsyqcyq5rqwzqfqqqsyqcyq5rqwzqfqypqdpl2pkx2ctnv5sxxmmwwd5kgetjypeh2ursdae8g6twvus8g6rfwvs8qun0dfjkxaq8rkx3yf5tcsyz3d73gafnh3cax9rn449d9p5uxz9ezhhypd0elx87sjle52x86fux2ypatgddc6k63n7erqz25le42c4u4ecky03ylcqca784w
read more about it here:
https://github.com/lightningnetwork/lightning-rfc/blob/master/11-payment-encoding.mdTo elaborate on the thought, and explain it more to pooya, Lightning doesn't just offer the ability to create an invoice. You need to think more of a usecase that involves a LOT of transactions. It doesn't have to be, but that's the optimal way to work with the lightning network.
It works mainly with payment channels, where both you and the other party of the channel, commit a bunch of funds to the channel. For example you commit 1 BTC, and i commit 0. We can then both exchange this 1 btc as fast as lightning, with hundreds and thousands of transactions per second, not transactions, but "invoices".
Once you feel that there is no longer the need to keep sending or receiving money with me, we can both close the channel, with whatever we both agree was the final transaction.
For OP, you need another lightning node, not just an address. You could hypothetically open a private channel with another node of your own, and exchange as many funds as you'd like to commit.
