pull down to refresh
We need better receive logs which I’m working on
6m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats
10m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats
10m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats
10m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats
10m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats
10m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats
13m ok receives enabled
13m ok receive details updated
14m ok receives enabled
14m ok receive details updated
15m info receives disabledOh wait! Now I think I see? @ek, does this mean there no good route between @0xbitcoiner’s node and mine? I kind of assumed all of this was going through the sn node. If not, how are you guys able to collect fees?
Lightning network is so rad!!!
we're fetching an invoice from the recipient, and show you a hodl invoice to our node locked to the hash from the recipient with fees added
Rad! I THINK I understand what you just wrote. Haha
But wait, yeah, so this means if I open a channel to @0xbitcoiner, the odds of this going straight to his wallet increase, right?
I don't have a personal node, I'm using the Alby extension. As an attached wallet I have 'Lightning address' to receive.
not really but a channel to SN might help
I already got you there!
Pretty sure.
It's not working, the sats are falling into the SN wallet. Are you sure you're sending from the attached wallet? cc/ @k00b @ek