pull down to refresh
Apologist bot sock puppet? I really don't think you would be attacking me personaly in real life.
And not that you care, but what I said is actually valid engagement in "sequential dialog".
Hm... If he is buying CCs, he must use the lightning network.
Are poaters in a forum really "content creators"? Am i a content creator by writing this post?
Do you have have plans to turn or be at least cash neutral and can the territory owner revenue be enough in the future?
I know about async payment (which are not yet developed completely, I've asked before) and that wasn't my question. I specifically asked about partners that trust each other.
So let's paraphrase this. Immagine you owe somebody some sats and when you are both online, he sends you an invoice and you pay it.
What I am basically asking is how hard is it to do this automatically? And by automatically this probbably (i think) means negotiating payment ammount, recording sending node's id, detecting when sending node is online, communicating in some way thet the previously negltiated invoice can be paid (i am not cure whether this can be done through the lightning network, or directly between the two peers using normal tcp or udp connection), and paying the invoice. That's it.
You cannot send 1 sat transaction without paying more than 100% fee in most realistic cases right now. And less than 1 sat invoices are not even supported by the wallets I played with.
I have written about this before for cases where somebody wats to pay for something every seccond, but currently this is not economically possible.
Has anyone tried reticulum? It is way more scalable (doesn't use flooding) and can work both on extremely low bandwidth links and on high bandwidth links.
Is it really? Scanning a QR code is no more cumbersome than tapping your phone. It is even easier since you can do it at a greater distance.
I have heard about PTLC, but I didn't know it can be used for async payments. However as far as I know there is no PTLC implementation yet. Or is it?
The onion message signaling between LSPs will work good enough, but I haven't heard it mentioned in two years. I think it can work well enough, provided nothing better is available.
The first link from voltage is dead. The second one does give hope that the LSP way of async payments may be available soon. I hope Zeus implement it since this is the wallet I am using (although I find it feature rich but very buggy).
I had the se situation before deleting the data and restoring the whole wallet. No amount of reseting the graph or chosing low ping peers fixed that. And yes, the nubmer of channels was incorrect.
After deleting and restoring the wallet yhe zombie channels get cleaned up and are usually below 100.
I am quite sure that this is some kind of a bug in the wallet.
My device seems to be updating properly now. I did delete the data and restored my wallet. I still couldn't pay Kagi. I changed the pathfinding and the payment passed immediately.
So yeah, theoretically bimodal pathfinding shouldn't result in failed payments, but in practice it did in my case. So it seems to be a bug. (Also keep in mind that failed pathfinding results in a message that there is no path, not in timeout with TemporaryChannelFailure in the logs. And while I have no idea how an error in pathfinding will give TemporaryChannelFailure, this has been my experience.)
The problem with bitcoin is that this process can be automated.
Every opportunity to make transactions more untraceable should be explored.