-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Watchtower list #4
Comments
|
awsome! thx for trying |
@zionsuperfly thank you for sharing, just be aware that knowing the dynamicDNS is the same as knowing your public IP, since the ddns is just a redirect. It is not a problem for me, but I want to make sure that you are comfortable with it. |
0354d80bcc05fc30b0d867238d83645b68b326c59f05303be14c87bcf4e84bd9c9@94.177.171.73:9911 |
028af801e7582c9f6b9b5a78314d7521a0eaef2a88490dc335eb27dc1c127c360a@141.138.142.171:9911 |
Clearnet: |
Clearnet
Tor
Updated addresses - 16th June 2024 |
If you are using watchtowers during a congested mempool state (like now) you need to set the The CSV delay can be set to longer with
|
@openoms the guide link now 404s. |
thanks, updated the domain to lightningnode.info and edited the starting comment. |
How many watchtowers do operators add to be optimum? |
There is no optimum. You just need one to be online at the right time (when your node is off), to have the relevant justice transaction and broadcast it if a malicious peer would attempt a force close with a previous state (and risk losing the whole balance of the channel). |
Clearnet Watchtower and Onion for Lightning Network |
Guys, this is a very appreciate that you offer WT services.
I've tried some of your WT servers and after 2-3 days are going offline, creating huge backlog in LND, loading the memory like hell, trying to connect. In the end I had to restart and sometimes remove at all WT just to avoid these issues. Restarting the node every 3-4 days is not reliable. |
02ba974c048f1ab0aa44095f3d5278076e8731c323c460f57ae4c287fe14c444df@147.182.218.169:9111 |
0307da87218ac661561685318a89272e1d750f2635ba6c009d290efd8931f98cef@141.145.193.235 for core lightning only (not lnd) ! |
Hello there Well maintained LND Clearnet Watchtower est. Block Height: 767071 02b759a578157393d2a70444ff9204f2ca5c0c0dfac01d0873f1b0d57f090685c1@116.202.17.127:9911 I edit/delete if there is a change. |
Strengthened Watchtower Infrastructure LND implementation watchtower 03b06847b0d56c466555f2c6922a08249f60647fce2d39a36ab2dd0309ac5b1b0d@154.26.156.214:9999 LNURL1DP68GURN8GHJ7MR9VAJKUEPWD3HXY6T5WVHXXMMD9AKXUATJD3CZ7322WDUHGNG77AJHZ CLN implementation teos LNURL1DP68GURN8GHJ7MR9VAJKUEPWD3HXY6T5WVHXXMMD9AKXUATJD3CZ7322WDUHGNG77AJHZ |
LND Watchtower |
LND watchtower only node with UPS |
LND Watchtower Germany 24/7
|
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.The text was updated successfully, but these errors were encountered: