pull down to refresh
Currently I update the feed every 15s. There's a ton of ways to do this, including gist.
I just went what's simplest and easiest to me. I run on AWS to begin with so I keep everything I can there.
I wrote coughClaudecough a custom setup for this, roughly as follows
- Go gRPC / HTLC interceptor with a readonly macaroon that grabs all the data and then parses out the things I want the Visualizer to see. It then sanitizes things and pushes it as a feed.json (events) and ring.json (anonymized channels) files to Amazon S3
- Amazon S3 holds only the latest copy of this, and versions it out automatically
- A web frontend built on HTML/JS and hosted as an S3 Static Website
- The actual Visualizer just pulls the updated JSOn files and presents it.
It is on my list to push to Github. Drowning in higher priority life stuff and getting things pushed to OpenSource keeps dropping down the list (my dashboard project/idea, this visualizer, node temperature metrics, network temperature metrics, etc)
AHahahaha I was just coming here to post this, as I tweaked a few security issues.
Thanks for the shoutout :)
EDIT: Those other images of my node health and stuff are still placeholder. As the warning label on the site says, the data's all fake. Need to find time to finish it up
It's been great being a channel partner with you! Best of luck Carsten!
I hope you get bored and come back.
Yes, there is risk if they go offline or their key acts maliciously your funds may be locked until the HTLC timeout (14400 blocks). But, the protection it gives me in busy periods is valuable enough - as having LOOP close during a busy period can be an expensive loss of liquidity while waiting for the channel to refill (naturally and rebalancing). I keep a safety amount in my static address for these busy periods.
There are periods when I have a full 500M drain on my channel.
I use custom code for managing my static loop in. I have not looked at the loopd automation at this time.
I would recommend using static addresses if you're running a node with an active LOOP channel, and want to automate refilling it's liquidity.
OP was - #1530061
More screenshots, github link and info there.
I'm not associated with this project, just providing info.
I'll get you on my next round of opens :) Currently overdeployed
Nice publish, especially with the MIT license, glad to see I'm not the only one working on free dashboarding for Lightning!
Hopefully my own tool will be on GH [soon] so there's more tooling available in the community.
This tool isn't meant to directly provide feedback into configuring rebalancing as that is currently out of scope, as that goes past Monitoring into Actionable Analytics.
Failed HTLC's are in scope to a degree... I've noted down your thought to see if that's a thread I can progress on. As a reminder, there's limited amounts of knowledge on HTLC's that your node is routing, which is one of the privacy features of Lightning.
I think what you're looking for is out of scope for my intention. My goal is to just help provide monitoring frameworks for people who want to run public nodes.
LSP integration could be a facet of it that I didn't consider, so that's now on my list of things to think about. I frankly do not have much insight into private channel management / payment node management. Hopefully yourself and others will be able to provide insight and feature requests as this project matures.
Adding it on my list to delve into! I think your project is a bit more integrated, judging from the readme, than what I'm building, as my goal is purely monitoring.
I'll be posting again once I publish my code on GH, and will happily take any assistance or insights you can provide, beyond me gleaning from your repo!
Release Notes - https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.21.3.md
Keep in mind this is a Release Candidate only