pull down to refresh

0 sats \ 0 replies \ @bartoli OP 17 Nov \ parent \ on: For those whho think rebalancing is mandatory.. lightning
Woops, you made me realize my script always set the negative inbound fee to -1. Now the discount can go further. So, thanks!
Well, I do update my channels' max htlc size depending on my available liquidity. Is that what you mean?
For me, it has 2 advantages:
-For the network: nodes only attempt payments through me when I advertise I have the available liquidity. The don't lose any routing attempts because of me.
-For me, it fees like I don't get 'blacklisted' by pathfinding algorithms anymore, since most nodes never 'fail' to route through me often enough
Well, i do use negative inbound fees in my own script that periodically updates my channel's fees. I would say it helped organic rebalancing for me. Not sure i have more to add to the subject.
I see 10096 is merged, but not 10033. For those still with 0.18.5, would you recommend updating to 0.19.3 or not yet?
Thanks for sharing this! I thought of doing something similar for my node, but my numbers are far lower than you.
One question I would have is, did you at some point consider moving to cln for performance reasons? And why did you not?
I think at some point the owner of zerofeerouting sais he had had too, for the size of logs alone (but as far as I know, this has been improved in LND).
Slide 21 of 'what is bitcoin' has 7 seed words in the background of the video, but those are probably unrelated
I tried a script looping for combinations that start with abstract and end with those, but stopped after a while of not finding any combination where the last word would be a correct checksum of the rest
How often will that 1M product be bought?
Do not forget that for you to be able to receive 1M, the other side of the channel has to have 1M of his sats stuck in the channel.
They must have an interest to keep it that way (bigger channel with not everything on their side, open for routing that brings them some fee,..)
I'm ok with it not being optional (although even zeus allows to not provide one!), but i would like it to at least accept the self signed tls.cert of my LND node. Right now, this gitves a 'self signed' error in the SN logs, and my LND node gets the similar error that remote rejected it.
Is there a real reason to not accept self signed certificate of LND instead of having to provide a 'trusted' one?
I mean, worst case, if I did not give a safe certificate, AND some one spoofed my node's IP, they would receive my zaps. I should be able to accept that risk?
There's no real risk for SN, or is there?
Thanks everyone, lots of interesting things to think about.
Indeed, new channels don't actually affect me as long as liquidity is on their side. And when they start having some of my liquidity on them, i should decide if this is really a problem for me, and what i will do to limit it it if it is.
The problem i was seeing is that if there are too much remote channels, thay could each potentially stuck my liquidity on them, unbalancing the other channels i carefully selected to be somewhat orcanically rebalancing as long as they have balanced liquidity
I think i will start by modifying my peer selection tool, to not only find interesting new peers, but also evaluate which existing peers are not interesting enough. So i can close some channels or reallocate their balance to other ones.
By then it should be clearer in my mind what i should do each time i have new funds to put on LN
Even the early electronics where quite différent.
I have had to replace the 'logic' that drove the electric motors of a drilling rig built only 35 years ago. About a hundred of buttons and seniors came, as as many wires, 24v or 0v for 1 or 0, in 4 electrical cabinets, each bigger that a fridge. In there, there where hundreds of big old relais, doing all the AND, OR, NOT, boolean operations to combine all those conditions
All this for 4 motors.
We replaced it by a simple industrial PLC, about the size of à computer, smaller that just the terminals the connect all the inbound and outbound signals.
It was fun retro engineering the logical conditions from the relay wiring, then rewriting them
If you need help on getting faster results, i'd ve happy to help! Mine (www.lnshortcut.ovh) used to take 30+ secondes to give recommandations, and now does yet more things in less that 1 second. Optimizing it was the most fun part!
You can use lnshortcut.ovh as another metric. It is originally for routing nodes to find good peers to connect to, but you can also use it with a routing nodes' pubkey, a transaction size and max fee to test, and get an idea of how much of the oublic network that transaction could reach in each directions from that routine node