pull down to refresh

My routing stats for the last 24 hours:
START=$(date -d '24 hours ago' +%s) END=$(date +%s) lncli fwdinghistory --start_time $START --end_time $END --max_events 3000 | jq '.forwarding_events | length' --> 1222
lncli fwdinghistory --start_time $START --end_time $END --max_events 3000 | jq '[.forwarding_events[].amt_out_msat | tonumber] | add / 1000' --> 113895745.048 lncli fwdinghistory --start_time $START --end_time $END --max_events 3000 | jq '[.forwarding_events[].fee_msat | tonumber] | add / 1000' --> 350.945**
So, 1200 routes, 1.13BTC (first time >1 bitcoin, woohoo!), and 350 sats of fee
You might think routing fees are low (average routing fee for this is 3ppm), but do not forget this is all WITHOUIT rebalancing, so on days without channel open/closes, this is pure profit
Node is lnshortcut.ovh / 02c521e5e73e40bad13fb589635755f674d6a159fd9f7b248d286e38c3a46f8683 Capacity is 1.8BTC (1/3 on my side) in 52 channels
Can someone please translate this for those who are not that wise in matter of lightning?
reply
this is LN porn :)
reply
ok. :) I have to understand this anyway. maybe in time... :D
reply
80 sats \ 1 reply \ @DarthCoin 10h
ok let me make a TLDR: OP is running a good public routing node:
  • nodeID 2c521e5e73e40bad13fb589635755f674d6a159fd9f7b248d286e38c3a46f8683
  • with 1.8BTC spread in 52 channels
  • he made 1222 routing txs in 24h (pretty impressive)
  • he didn't make any rebalancing (usually is necessary for a public routing node in order to keep incoming txs to be routed so to get more fees)
  • he knows how to use command line to manage that node
Running a public routing node is not easy task and require skills, capital, resources, knowledge. If you want to learn, goood ... but is a long way to the top if you wanna rock'n'roll.
reply
thank you. it is impressive when you put it this way. maybe one day. maybe. skills are learnable. so maybe, maybe.
reply
Pretty cool. What do you think about this? #1277693
reply
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.
reply
Did you also tried the Rene Pickardt valve method ?
reply
100 sats \ 1 reply \ @bartoli OP 10h
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
reply
reply
You are bloating your channel.db, letting other people rebalance through your node for free. One day you will have a power failure or an SSD crapping out that will corrupt this database, so you will have to SCB. The longer you run your node the higher the chance of this happening.
reply
Well, you are right that static channels backup are a major priority for me right now...
reply
SCB will force close all the channels and will take a long time for your 2y old node to scan for on-chain funds. After recovery (of funds, not the channels!), you will be better off to start a fresh node with a new seed/birthday. Backups are trivial to automate, but don't count on them to save your node. Until LND natively supports postgres instead of bolt database, and you configure live replication to another disk, it is risky to route frequent payments.
reply