Feelancer21's avatar
Feelancer21
npub17hpz...4zs6
I'm trying to learn coding with Python and develop a Lightning Fee tool
Feelancer21's avatar
Feelancer21 1 year ago
Hashrate is going to the moon ๐Ÿš€ . A new difficulty ATH in 2 days is very likely.
Feelancer21's avatar
Feelancer21 1 year ago
Is freedom of speech actually okay for people who are close to the money printers and the monopoly on violence?
Feelancer21's avatar
Feelancer21 1 year ago
The ETHBTC ribs are also no longer what they used to be.
Feelancer21's avatar
Feelancer21 1 year ago
I think last week a hedge fund had to close its MSTR-BTC spread trade, which led to a short squeeze in MSTR and a long squeeze in BTC. If the MSTR premium now tightens again as spot demand increases, that would be incredibly bullish.
Feelancer21's avatar
Feelancer21 1 year ago
Ok, there is no second best. But what if there is a third or fourth best?
Feelancer21's avatar
Feelancer21 1 year ago
When seeing the activity in the Lightning Network these days: image
Feelancer21's avatar
Feelancer21 1 year ago
I see an interesting game theory emerging if we ever have negative fees in the Lightning Network. What could happen: On larger channels, it already makes sense to charge higher outbound fees than on smaller ones, as larger HTLCs command a certain premium. However, inbound discounts will likely be smaller on larger channels, or the (negative) inbound fee rates higher, meaning a node with a large channel will tend to achieve a larger margin. For smaller payments, there's automatically an incentive to use smaller channels, particularly on the inbound side. This also means that liquidity in smaller channels can be more effectively managed through fee rates in the case of negative fees. Larger channels, on the other hand, will need to be actively rebalanced.
Feelancer21's avatar
Feelancer21 1 year ago
Hello, my name is Feelancer and my mission is a better automatic fee control for routing nodes. This year I built a PID controller that adjusts the outbound and inbound fee rates according to the channel depletion. It uses the current status and moving averages. However, the tool is still pretty nerdy and difficult to configure for the normie user. The next milestone is the automation of the parameterization based on profit and loss figures of the channels. The basic idea is to understand forwards and rebalancing as a liquidity trade, i.e. liquidity is bought at certain funding costs and then sold with margin plus funding costs. Ideally, the funding costs should be identical between buying and selling, but as with share trading, a price effect is realized. The aim is to optimize the margin together with the adjustment speed of the PID controller in such a way that a routing node has a stable return with limited risk. The approach with negative forward fees would be particularly interesting. However, there is still a long way to go until then, as this is only a hobby project so far. https://github.com/feelancer21/feelancer
Feelancer21's avatar
Feelancer21 1 year ago
Wow! CoinGate is force closing its dead channels. Every noderunner should do this! Because if your peer is dead and you need to use the SCB, there's no chance of getting your sats back with it. image
Feelancer21's avatar
Feelancer21 1 year ago
BTC price rises by about $14,000 in just three weeks and it doesn't feel unhealthy.
Feelancer21's avatar
Feelancer21 1 year ago
We should start pricing our satoshis in joules or hashes per sat because fiat currencies are only temporary. What counts in the end is the energy you get for a satoshi. If the game theory around Bitcoin works, this amount will rise forever.
โ†‘