openoms / lightning-node-management Goto Github PK

Okay, I think I've now wasted enough cycles misusing bos rebalance that I've narrowed down how you're actually supposed to use it. First off, it will only try to rebalance in small amounts, so unless you want to spend eons of time running it manually you should specify capacity targets. It will then keep trying to route circular payments until the channel hits your target. You can only set either an inbound target capacity or an outbound one.

if [[ ${OUTBOUND_CAPACITY} < ${INBOUND_CAPACITY} ]];then
    LIMIT_REBALANCE="--in-target-outbound $(expr ${INBOUND_CAPACITY} / 2)"
else
    LIMIT_REBALANCE="--out-target-inbound $(expr ${OUTBOUND_CAPACITY} / 2)"
fi
   
bos rebalance --out ${OUTBOUND_PUBKEY} --in ${INBOUND_PUBKEY} --max-fee-rate ${INBOUND_FEERATE} ${LIMIT_REBALANCE}

INBOUND_CAPACITY being the capacity of your --in channel.
OUTBOUND_CAPACITY being the capacity of your --out channel.

I know this is not at all concise enough of an explanation to go into the markdown article, but perhaps you can paraphrase.

Anyway, thanks for all your efforts @openoms. I haven't actually been using the raspi-stuff, but stumbled across various git issues you've opened in other repos that I found to be informative.

A list of known altruistic Lightning Network watchtowers will be shared here in the format:
<watchtower-pubkey>@<host>:<port>

Guide to set up (please read through before posting): https://www.lightningnode.info/advanced-tools/watchtower

Aim to keep these nodes online to benefit your peers. Check the settings after all system updates and edit the details if there is a change.

Offline towers should be removed by the owner and will also moderate as needed.

Keep in mind that sharing your public IP or dynamicDNS exposes the physical location of the node so the use of Tor is encouraged.

I start:
02b745aa2c27881f2494978fe76494137f86fef6754e5fd19313670a5bc639ea82@67dhenmvdyylregpdqdswdaymqxcqsn7tg7iwp25mglpf7ryob4y4oad.onion:9911
Update: it became unfeasible to keep this watchtower running. It was online for more than 2 years and many peers have utilised it.
The watchtower.db has grown above 14 GB and the CPU load is significant on the hosting RPi4. Will be down until at least the hardware is scaled up.

set channel fees based on policy:

https://github.com/accumulator/charge-lnd

I followed the guide:

https://github.com/openoms/lightning-node-management/blob/master/lnd.updates/README.md

updated to version v0.12.0-beta... after this i checked my channels and some are not going active anymore....

I am able to connect to this peers manualy but the peers are disappearing shortly after doing this....

do i miss something? do i need to do anything or o i just need to wait some time?

i allready tried the follwing:

updated also bitcoin version to latest version (0.21)
updated raspblitz to latest version (1.63)
updated thunderhub to latest version (0.12.7)

but don'T think this was needed.....

In the inbound liquidity section, would be lovely to see a section (in my opinion, should be high up, due to it's non-technical simplicity and directness) that covers strategically-oversized-outbound-channel-opening balanced by personal ordinary spending. Sample text could be:

If you already pay online for purchases (app store/smartphone app and subscription purchases, PS/Xbox/Switch game console downloads, Amazon purchases, cell phone payments, etc.)

1. Open an outbound Lightning channel, double the size you wish it to ultimately be, to a node you like from 1ml.com / etc. that is well-ranked for uptime, etc.

2. Use Bitrefill or similar sites to pay routine and personal expenses, ultimately using half of the funds from this channel.

Now you have a balanced channel simply by spending what you would have anyways. For example, you can buy Apple App Store or Google Play store cards for subscriptions you would have paid for anyways monthly, and they will just successively deduct what you leave on there. So if you wish to have $XXX in inbound capacity, and know you will spend that this year, you can buy gift card codes on Bitrefill in advance if you wish to speed up your inbound capacity. Or do it as-you-go and it grows gradually.

المملكة العربية السعودية

ded
https://github.com/openoms/lightning-node-management#lndash

https://ashemery.github.io/malware-tools/index.html

Is it recommended to install LND fees management via the original source on https://gitlab.com/nolith/lndfeesmanager. Or is there a plugin in Raspiblitz 1.6.3, or BOS ?

Running the install script returns an error at line 130...it might just need the entire file name.

admin@raspberrypi:~ $ wget https://raw.githubusercontent.com/openoms/lightning-node-management/master/lnd.updates/bonus.chantools.sh
--2021-02-06 01:35:32--  https://raw.githubusercontent.com/openoms/lightning-node-management/master/lnd.updates/bonus.chantools.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.112.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.112.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5581 (5.5K) [text/plain]
Saving to: ‘bonus.chantools.sh’

bonus.chantools.sh  100%[===================>]   5.45K  --.-KB/s    in 0.002s

2021-02-06 01:35:34 (2.19 MB/s) - ‘bonus.chantools.sh’ saved [5581/5581]

admin@raspberrypi:~ $ bash bonus.chantools.sh on
bonus.chantools.sh: line 130: unexpected EOF while looking for matching `}'
bonus.chantools.sh: line 168: syntax error: unexpected end of file
admin@raspberrypi:~ $