Series: Let’s create a routing LND node
- Part 1 - Preliminaries
- Part 2 - Finalising setup and funding
- Part 3 - Opening some channels
- Part 4 - Unsuccessful looping and rebalancing
- Part 5 - Some successes
- Part 6 - Opening more channels
- Part 7 - Probing routes
- Part 8 - Fees
- Part 9 - Loop costs
- Part 10 - Docker
- Part 11 - More failures
- Part 12 - Should I close some channels?
- Part 13 - Loop problems
- Part 14 - Waiting...
- Part 15 - Where are we now?
Supporting this series
If you want to support this series, you can:
- Use tippin.me to send me a tip.
- Use Tootmoney to ask for a Lightning invoice. On Mastodon, just send a toot like ‘@OpinionatedGeek #TootMoney #send 10000’ to have it reply with an invoice QR code.
- Send bitcoin to this address: bc1qsaampnjm5ykcpd40pstcewt75xrtfy5cxpnpdf
Connecting to Loop
Since I want to have channels with a few ‘destination’ nodes, I thought about opening a hefty channel with Lightning Lab’s Loop node. I think Loop use is likely to increase in time, and it’ll typically be higher payment sizes than the median. Sure, a bunch of others will likely be connected to it, but it might still be useful.
Finding that node was tricky though. Here’s one of the paths a Loop Out took:
"path": [
"02ad6fb8d693dc1e4569bcedefadf5f72a931ae027dc0f0c544b34c1c6f3b9a02b",
"02247d9db0dfafea745ef8c9e161eb322f73ac3f8858d8730b6fd97254747ce76b",
"021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d",
"03fb2a0ca79c005f493f1faa83071d3a937cf220d4051dc48b8fe3a087879cf14a"
]
03fb2a0ca79c005f493f1faa83071d3a937cf220d4051dc48b8fe3a087879cf14a just doesn’t seem to exist on my graph, or 1ml.com’s. Interesting.
021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d exists, with the alias ‘021c97a90a411ff2b10d’ and 33 channels. 5 of the channels are 0.16BTC - pushing the maximum channel size, and the smallest is 4million sats.
The other two nodes in the path are less interesting - 02247d9db0dfafea745ef8c9e161eb322f73ac3f8858d8730b6fd97254747ce76b is an LNBig node that was used for routing, and 02ad6fb8d693dc1e4569bcedefadf5f72a931ae027dc0f0c544b34c1c6f3b9a02b is the rompert.com node whose channel I was looping out.
So it looks like Loop uses a fronting server 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d, along with a private connection to a hidden server. I guess that hidden server is special or has special stuff hooked into it somehow.
I don’t think I’m exposing any big secrets here. Alex Bosworth tweeted about it in March apparently:
You can use the CLI to select the specific channel you want to send out of. The end destination is the Loop service. If you want to help provide liquidity the node is 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d@18.224.56.146:9735 but more nodes may be added
Let’s try opening a big channel with 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d@18.224.56.146:9735
You know what? Let’s try opening the biggest. (I plan on looping some of this out.) So, what’s the biggest I can open?
$ lncli getnetworkinfo
{
"graph_diameter": 0,
"avg_out_degree": 18.098991320666197,
"max_out_degree": 1361,
"num_nodes": 4263,
"num_channels": 38578,
"total_network_capacity": "109731573840",
"avg_channel_size": 2844408.0522577637,
"min_channel_size": "1100",
"max_channel_size": "16777216",
"median_channel_size_sat": "816675"
}
There we go - maximum channel size is: 16777216 sats.
$ lncli openchannel --node_key 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d --connect 18.224.56.146:9735 --local_amt 16777216
[lncli] rpc error: code = Unknown desc = funding amount is too large, the max channel size is: 0.16777215 BTC
Oops. Apparently channels must be less than the maximum, not less than or equal to the maximum. Oh well.
$ lncli openchannel --node_key 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d --connect 18.224.56.146:9735 --local_amt 16777215
{
"funding_txid": "8698e55a535347ba23b994c9c21dd3a3be03a744d93a3b052f94af8bb3eabed6"
}
There we go - a maximally-sized channel to provide some liquidity to Loop. I’m curious if this will get used at all. 1 million sats is the maximum Loop Out handles right now, but I don’t have many other channels that can transfer 1 million sats so for this to work I’ll need some more big channels. But small steps. I’m not in a rush.
Loop costs
I thought I’d try and figure out the costs involved in Loop Out. It may be beyond me.
Here’s a Loop Out from my channel with the swap server:
$ loop out --channel 632366520641650689 --amt 1000000
Max swap fees for 1000000 Loop Out: 61893
CONTINUE SWAP? (y/n), expand fee detail (x): x
Max on-chain fee: 29184
Max off-chain swap routing fee: 20010
Max off-chain prepay routing fee: 509
Max swap fee: 12190
Max no show penalty: 24982
CONTINUE SWAP? (y/n): y
Swap initiated
ID: c3e04cdf6ae9835abab1d05152682a2961bb90937393303dc3d878728bc51e4b
HTLC address: bc1qg3h44cylg47jpl3hlf24k5nq7d4mnrxjxxpl3g7n02wflpp65shqfmm0ht
Run `loop monitor` to monitor progress.
2019-05-09T08:18:17Z LOOP_OUT INITIATED 0.01 BTC - bc1qg3h44cylg47jpl3hlf24k5nq7d4mnrxjxxpl3g7n02wflpp65shqfmm0ht
2019-05-09T08:26:26Z LOOP_OUT PREIMAGE_REVEALED 0.01 BTC - bc1qg3h44cylg47jpl3hlf24k5nq7d4mnrxjxxpl3g7n02wflpp65shqfmm0ht
2019-05-09T08:31:28Z LOOP_OUT SUCCESS 0.01 BTC - bc1qg3h44cylg47jpl3hlf24k5nq7d4mnrxjxxpl3g7n02wflpp65shqfmm0ht
And it succeeded. How much did it cost?
Well, I tried looking at the ‘Max swap fees’ output from the loop command. Looking at the source code, here are the comments on the breakdown:
- Max off-chain swap routing fee is the maximum off-chain fee that may be paid for payment to the server. This limit is applied during path finding.
- Max off-chain prepay routing fee is the maximum off-chain fee that may be paid for payment to the server. This limit is applied during path finding.
- Max swap fee is the maximum we are willing to pay the server for the swap.
- Max no show penalty is the maximum amount of the swap fee that may be charged as a prepayment.
- Max on-chain fee is the maximum in on-chain fees that we are willing to spend.
All figures are output in satoshi, according to answers from the LND Slack chat.
It’s still not entirely clear which fees are paid when. Some of the above fees are paid if the loop is successful, some if it fails badly, and I think the most common failure results in no costs.
In any case, the maximum fee for the swap - the figure given in the initial output - is built from the detail output by:
Max fees := Max on-chain fee + Max swap fee + Max off-chain swap routing fee + Max off-chain prepay routing fee
But it’s still a ‘maximum’ threshold figure - if the costs rise above these the transaction is cancelled. This doesn’t give a good picture of the likely costs.
I’m even more confused by the ‘Max off-chain swap routing fee’. In my run above, it’s 20010 sats! That’s a very, very big routing fee for a Lightning payment. When I asked in Slack I was told ‘it’s a hard limit, you won’t pay anywhere near that, but we need a hard limit so we know when to bail out’.
So how much did it actually cost? Well, unless there’s something else going on, I figure I can look at how much was sent out, and how much came back, and the cost will be the difference in those two figures.
So, what went out? Two payments:
{
"payment_hash": "9735b382d3f62e1db32bf57eae33b766bfaf6dd941e9c92e753904e86a2b1173",
"value": "20819",
"creation_date": "1557389899", // 2019-05-09T08:18:19+00:00
"path": [
"021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d",
"03fb2a0ca79c005f493f1faa83071d3a937cf220d4051dc48b8fe3a087879cf14a"
],
"fee": "1",
"payment_preimage": "0c85c83148e5b67e90615bfc9b9bee639ff3ca613d0cd82c843d21bc0c195074",
"value_sat": "20819",
"value_msat": "20819000"
},
{
"payment_hash": "c3e04cdf6ae9835abab1d05152682a2961bb90937393303dc3d878728bc51e4b",
"value": "989340",
"creation_date": "1557390687", // 2019-05-09T08:31:27+00:00
"path": [
"021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d",
"03fb2a0ca79c005f493f1faa83071d3a937cf220d4051dc48b8fe3a087879cf14a"
],
"fee": "1",
"payment_preimage": "b34864d376ae63086413e5579d28933857277f0a4c756f75c3dc45b86c9be332",
"value_sat": "989340",
"value_msat": "989340000"
}
How much went out?
20819 + 1 (fee)
+ 989340 + 1 (fee)
= 1010161 sats
What came back? One on-chain transaction:
{
"tx_hash": "811f46f096d6525a574a8a8996e48d6bd3b32eaf1ff7c50ba0a3ad0d9ce6783c",
"amount": "990218",
"num_confirmations": 1,
"block_hash": "0000000000000000001d63c493e223a45d1d9f622972539b3ae31d7c1d15dd0c",
"block_height": 575252,
"time_stamp": "1557390679", // 2019-05-09T08:31:19+00:00
"total_fees": "0",
"dest_addresses": [
"bc1qfdszj6ldrenwpd4f4s0a2326snaevwjryedk9j"
]
}
How much came back?
990218 sats
The total cost to me for this loop is the difference between those two figures:
1010161 - 990218 = 19943 sats
19943 sats is a lot less than the 61893 sats quoted as the ‘Max swap fees’ before agreeing to the run, but at $1.22 in today’s terms it’s still hefty.
I do wish I had a better handle on exactly which of the max fees are paid under what circumstances, and how loop arrives at the figures. A ‘Max off-chain swap routing fee’ of 20010 sats is an awful lot higher than the 2 sats actually paid in routing fees. So much so that it has me doubting I know what’s actually going on there.
More channels and rebalancing
I want to open a few channels with smaller nodes as well - they can be the ones most in need of liquidity. I don't know how beneficial this will be for routing, but that's why I'm experimenting in public. If it doesn't work, I can close channels as easily as open them.
I offered to open channels for folks on the LND Developer slack and 'kornpow' and ‘tongokongo’ both replied with connection details, so:
$ lncli openchannel --node_key 03077d02d11d2ade200c7fc5ba4fc66c1c599424fb945e88b3896fee6eedc07147 --connect 64.99.228.35:9735 --local_amt 1000000
{
"funding_txid": "d192294d6e0768d24559290477666a6d7c7aad04582297dc29a33d03598f487c"
}
$ lncli openchannel --node_key 03d40870a931fe2e978f01b26117b64d15d68119f2840c30f1b69b59955b1e7846 --connect 157.230.224.221:9735 --local_amt 1000000
{
"funding_txid": "4fe51a94716e33944db932c1173b51f9ab82cd867d6340ec69de68b3931e8ac6"
}
One of the plans I had with my channel with the Swap server was to loop out some of the funds there and allow me to rebalance multiple channels into that new space. Instead of looping out from each channel individually, I could do fewer loops and just pay Lightning routing fees to rebalance channels.
It’s not really working out.
Probes are failing before it even gets to the swap server:
Probe results for path of 300000 sats from: 632189499363622912 to: 632366520641650689
⚡ OpinionatedGeek ⚡ (22 channels)
✅ Hop 1 (300001 sats): SUCCESS
Channel ID: 632189499363622912, Capacity: 1000000
Src: 023c5b5667b16cd7fcca5591a8c0f47beb76c9405e16a4f2d6b42c7b9904a7f0e6 -
Dst: 0265fae305778b7cb157365f70cf3a2047d2cad5c1ccc5f550c6d8a033084a8ea5
⚡ ln.taborsky.cz (38 channels)
❌ Hop 2 (300001 sats): FAILURE - Temporary Channel Failure
Channel ID: 594369597760339968, Capacity: 2000000
Src: 0265fae305778b7cb157365f70cf3a2047d2cad5c1ccc5f550c6d8a033084a8ea5 -
Dst: 03bb88ccc444534da7b5b64b4f7b15e1eccb18e102db0e400d4b9cfe93763aa26d
⚡ LightningTo.Me (681 channels)
❌ Hop 3 (300000 sats): FAILURE - Temporary Channel Failure
Channel ID: 624561087597182976, Capacity: 4000000
Src: 03bb88ccc444534da7b5b64b4f7b15e1eccb18e102db0e400d4b9cfe93763aa26d -
Dst: 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d
⚡ 021c97a90a411ff2b10d (35 channels)
❌ Hop 4 (300000 sats): FAILURE - Temporary Channel Failure
Channel ID: 632366520641650689, Capacity: 16777215
Src: 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d -
Dst: 023c5b5667b16cd7fcca5591a8c0f47beb76c9405e16a4f2d6b42c7b9904a7f0e6
⚡ OpinionatedGeek ⚡ (22 channels)
I knew some nodes would have difficulties routing but there are a surprising number of failures like the above.
Probing is handy though! I think the output (above) could use a little work - Hop 3 and Hop 4 didn’t really fail, the payment didn’t reach them because it failed at Hop 2. I think I need to make that clearer. In fact I should maybe probe from the source to the destination instead of back from the destination to the source - that would be faster and I could show Hop 3 and Hop 4 above as ‘untried’ instead of ‘Temporary Channel Failure’.
I’d also like a way to automate this probing, to give an indication of how well a channel can route. Then I could run another (nightly?) report showing which channels were useless and should be culled.
Here’s the latest report:
OpinionatedGeek ⚡ - synced: ✅
Total Balance: 48,680,356 satoshi, Wallet: 16,499,900 satoshi (16,499,900 satoshi/0 satoshi)
Fees: 4 this month, 4 this week, 0 today
Channels: 21 active, 1 inactive, 0 pending, containing: 32,180,456 satoshi
Version: 0.6.0-beta commit=v0.6-beta-dirty
URI: 023c5b5667b16cd7fcca5591a8c0f47beb76c9405e16a4f2d6b42c7b9904a7f0e6@95.179.191.59:9735
Pending:
None.
Unbalanced - High:
✅ 👪 1ML.com node ALPHA: 632050960770990080 (Last update: 02:35 UTC on Thursday, 9 May 2019)
Pubkey: 0217890e3aad8d35bc054f43acc00084b25229ecff0ab68debd82883ad65ee8266
Fees: 0+10/40 / 1,000+1/144
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,721 / 0 [capacity: 1,000,000]
✅ 👪 BitMEXResearch: 631655136611991552 (Last update: 14:44 UTC on Tuesday, 7 May 2019)
Pubkey: 0395033b252c6f40e3756984162d68174e2bd8060a129c0d3462a9370471c6d28f
Fees: 0+10/40 / 1+10/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,719 / 0 [capacity: 1,000,000]
✅ 👪 ln.taborsky.cz: 632189499363622912 (Last update: 11:43 UTC on Tuesday, 7 May 2019)
Pubkey: 0265fae305778b7cb157365f70cf3a2047d2cad5c1ccc5f550c6d8a033084a8ea5
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,719 / 0 [capacity: 1,000,000]
✅ 👪 hirish-ln: 632189499363557376 (Last update: 11:43 UTC on Tuesday, 7 May 2019)
Pubkey: 036d81bb87af589f949dec53af1b3121c84048d0913eb56945cbbb62c5cb4fcb6f
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,717 / 0 [capacity: 1,000,000]
✅ 👪 SLL: 632187300239048704 (Last update: 15:49 UTC on Tuesday, 7 May 2019)
Pubkey: 039401f72bc0d40efb58b01de15527a2a5ae1943d7c29067b725a1467a93c7e66f
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,715 / 0 [capacity: 1,000,000]
✅ 👪 ACINQ: 632050960761552897 (Last update: 11:29 UTC on Thursday, 9 May 2019)
Pubkey: 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f
Fees: 0+10/40 / 1,000+100/144
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,715 / 0 [capacity: 1,000,000]
✅ 👪 blackgold: 632112533487681536 (Last update: 22:29 UTC on Monday, 6 May 2019)
Pubkey: 02f40890af885da4673f0ee9725ee74bb2c66d6491cc4334056a2701057993e61d
Fees: 0+10/40 / 250+10/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,715 / 0 [capacity: 1,000,000]
✅ 👪 VIX18: 632187300238983168 (Last update: 04:21 UTC on Thursday, 9 May 2019)
Pubkey: 03f8ab9b7496be92ce370e0224661d5d2de80bca8f505d66f1226d0e6002007d2a
Fees: 0+10/40 / 1,000+100/144
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 984,913 / 0 [capacity: 1,000,000]
✅ 👪 kornpow: 632376416256983040 (Last update: 17:17 UTC on Wednesday, 8 May 2019)
Pubkey: 03077d02d11d2ade200c7fc5ba4fc66c1c599424fb945e88b3896fee6eedc07147
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 984,907 / 0 [capacity: 1,000,000]
✅ 👪 ECRYPTO[LND]: 632502860122357761 (Last update: 11:05 UTC on Thursday, 9 May 2019)
Pubkey: 03d40870a931fe2e978f01b26117b64d15d68119f2840c30f1b69b59955b1e7846
Fees: 1,000+1/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 984,889 / 0 [capacity: 1,000,000]
⭕ 👪 LightningTo.Me: 632050960802447360 (Last update: 22:32 UTC on Tuesday, 7 May 2019)
Pubkey: 03bb88ccc444534da7b5b64b4f7b15e1eccb18e102db0e400d4b9cfe93763aa26d
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 882,321 / 0 [capacity: 1,000,000]
✅ 👪 021c97a90a411ff2b10d: 632366520641650689 (Last update: 14:31 UTC on Wednesday, 8 May 2019)
Pubkey: 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥕🥕] 13,732,256 / 3,029,865 [capacity: 16,777,215]
Unbalanced - Low:
✅ 🚶 03f175627ecd2b736fdd: 631605658598703105 (Last update: 14:20 UTC on Friday, 3 May 2019)
Pubkey: 03f175627ecd2b736fdd29f40414c02169716f884b4b45762483142ed81834141c
Fees: 0+10/40 / 1,000+1/40
Balances: [🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕] 96,416 / 1,033,565 [capacity: 1,144,265]
All Channels:
✅ 👪 1ML.com node ALPHA: 632050960770990080 (Last update: 02:35 UTC on Thursday, 9 May 2019)
Pubkey: 0217890e3aad8d35bc054f43acc00084b25229ecff0ab68debd82883ad65ee8266
Fees: 0+10/40 / 1,000+1/144
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,721 / 0 [capacity: 1,000,000]
✅ 👪 BitMEXResearch: 631655136611991552 (Last update: 14:44 UTC on Tuesday, 7 May 2019)
Pubkey: 0395033b252c6f40e3756984162d68174e2bd8060a129c0d3462a9370471c6d28f
Fees: 0+10/40 / 1+10/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,719 / 0 [capacity: 1,000,000]
✅ 👪 ln.taborsky.cz: 632189499363622912 (Last update: 11:43 UTC on Tuesday, 7 May 2019)
Pubkey: 0265fae305778b7cb157365f70cf3a2047d2cad5c1ccc5f550c6d8a033084a8ea5
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,719 / 0 [capacity: 1,000,000]
✅ 👪 hirish-ln: 632189499363557376 (Last update: 11:43 UTC on Tuesday, 7 May 2019)
Pubkey: 036d81bb87af589f949dec53af1b3121c84048d0913eb56945cbbb62c5cb4fcb6f
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,717 / 0 [capacity: 1,000,000]
✅ 👪 SLL: 632187300239048704 (Last update: 15:49 UTC on Tuesday, 7 May 2019)
Pubkey: 039401f72bc0d40efb58b01de15527a2a5ae1943d7c29067b725a1467a93c7e66f
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,715 / 0 [capacity: 1,000,000]
✅ 👪 ACINQ: 632050960761552897 (Last update: 11:29 UTC on Thursday, 9 May 2019)
Pubkey: 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f
Fees: 0+10/40 / 1,000+100/144
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,715 / 0 [capacity: 1,000,000]
✅ 👪 blackgold: 632112533487681536 (Last update: 22:29 UTC on Monday, 6 May 2019)
Pubkey: 02f40890af885da4673f0ee9725ee74bb2c66d6491cc4334056a2701057993e61d
Fees: 0+10/40 / 250+10/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 985,715 / 0 [capacity: 1,000,000]
✅ 👪 VIX18: 632187300238983168 (Last update: 04:21 UTC on Thursday, 9 May 2019)
Pubkey: 03f8ab9b7496be92ce370e0224661d5d2de80bca8f505d66f1226d0e6002007d2a
Fees: 0+10/40 / 1,000+100/144
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 984,913 / 0 [capacity: 1,000,000]
✅ 👪 kornpow: 632376416256983040 (Last update: 17:17 UTC on Wednesday, 8 May 2019)
Pubkey: 03077d02d11d2ade200c7fc5ba4fc66c1c599424fb945e88b3896fee6eedc07147
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 984,907 / 0 [capacity: 1,000,000]
✅ 👪 ECRYPTO[LND]: 632502860122357761 (Last update: 11:05 UTC on Thursday, 9 May 2019)
Pubkey: 03d40870a931fe2e978f01b26117b64d15d68119f2840c30f1b69b59955b1e7846
Fees: 1,000+1/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 984,889 / 0 [capacity: 1,000,000]
⭕ 👪 LightningTo.Me: 632050960802447360 (Last update: 22:32 UTC on Tuesday, 7 May 2019)
Pubkey: 03bb88ccc444534da7b5b64b4f7b15e1eccb18e102db0e400d4b9cfe93763aa26d
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 882,321 / 0 [capacity: 1,000,000]
✅ 👪 021c97a90a411ff2b10d: 632366520641650689 (Last update: 14:31 UTC on Wednesday, 8 May 2019)
Pubkey: 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥕🥕] 13,732,256 / 3,029,865 [capacity: 16,777,215]
✅ 👪 Bitrefill.com: 631589165900038144 (Last update: 23:16 UTC on Wednesday, 8 May 2019)
Pubkey: 030c3f19d742ca294a55c00376b3b355c3c90d61c6b6b39554dbc7ac19b141c14f
Fees: 0+10/40 / 4,000+40/144
Balances: [🥝🥝🥝🥝🥝🥝🥝🥕🥕🥕] 2,993,649 / 992,071 [capacity: 4,000,000]
✅ 👪 Sagittarius A: 632050960773152769 (Last update: 11:15 UTC on Tuesday, 7 May 2019)
Pubkey: 03a503d8e30f2ff407096d235b5db63b4fcf3f89a653acb6f43d3fc492a7674019
Fees: 0+10/40 / 0+1/40
Balances: [🥝🥝🥝🥝🥝🥝🥕🥕🥕🥕] 685,717 / 300,001 [capacity: 1,000,000]
✅ 👪 rompert.com🔵: 631590265456623616 (Last update: 05:39 UTC on Thursday, 9 May 2019)
Pubkey: 02ad6fb8d693dc1e4569bcedefadf5f72a931ae027dc0f0c544b34c1c6f3b9a02b
Fees: 0+10/40 / 0+1/144
Balances: [🥝🥝🥝🥝🥝🥕🥕🥕🥕🥕] 588,638 / 397,082 [capacity: 1,000,000]
✅ 👪 CoinGate: 631562777641943040 (Last update: 19:58 UTC on Wednesday, 8 May 2019)
Pubkey: 0242a4ae0c5bef18048fbecf995094b74bfb0f7391418d71ed394784373f41e4f3
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥝🥕🥕🥕🥕🥕] 503,664 / 482,056 [capacity: 1,000,000]
✅ 👪 powernode.io: 631589165899972608 (Last update: 21:59 UTC on Wednesday, 8 May 2019)
Pubkey: 02809e936f0e82dfce13bcc47c77112db068f569e1db29e7bf98bcdd68b838ee84
Fees: 0+10/40 / 0+100/40
Balances: [🥝🥝🥝🥝🥕🥕🥕🥕🥕🥕] 993,659 / 992,061 [capacity: 2,000,000]
✅ 👪 LightningPowerUsers.com: 631590265456689152 (Last update: 05:39 UTC on Thursday, 9 May 2019)
Pubkey: 0331f80652fb840239df8dc99205792bba2e559a05469915804c08420230e23c7c
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥕🥕🥕🥕🥕🥕] 493,660 / 492,060 [capacity: 1,000,000]
✅ 👪 ln1.satoshilabs.com: 631652937637363712 (Last update: 11:30 UTC on Thursday, 9 May 2019)
Pubkey: 0279c22ed7a068d10dc1a38ae66d2d6461e269226c60258c021b1ddcdfe4b00bc4
Fees: 0+10/40 / 0+1,000/144
Balances: [🥝🥝🥝🥝🥕🥕🥕🥕🥕🥕] 493,166 / 492,555 [capacity: 1,000,000]
✅ 👪 lightning-roulette.com: 631563877105729536 (Last update: 13:11 UTC on Tuesday, 7 May 2019)
Pubkey: 031678745383bd273b4c3dbefc8ffbf4847d85c2f62d3407c0c980430b3257c403
Fees: 0+10/40 / 1,000+1/40
Balances: [🥝🥝🥝🥝🥕🥕🥕🥕🥕🥕] 483,658 / 502,058 [capacity: 1,000,000]
✅ 👪 ln.BitSoapBox.com: 632113632926957568 (Last update: 05:03 UTC on Thursday, 9 May 2019)
Pubkey: 021607cfce19a4c5e7e6e738663dfafbbbac262e4ff76c2c9b30dbeefc35c00643
Fees: 0+10/40 / 220+21/144
Balances: [🥝🥝🥝🥝🥝🥝🥝🥝🥝🥝] 378,922 / 0 [capacity: 1,000,000]
✅ 🚶 03f175627ecd2b736fdd: 631605658598703105 (Last update: 14:20 UTC on Friday, 3 May 2019)
Pubkey: 03f175627ecd2b736fdd29f40414c02169716f884b4b45762483142ed81834141c
Fees: 0+10/40 / 1,000+1/40
Balances: [🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕] 96,416 / 1,033,565 [capacity: 1,144,265]
Created by on
