Skip to content
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

Daemon mode #5

Open
wamde opened this issue Dec 16, 2018 · 5 comments
Open

Daemon mode #5

wamde opened this issue Dec 16, 2018 · 5 comments
Labels
design_needed Requirements/scope not fully fleshed out.

Comments

@wamde
Copy link
Collaborator

wamde commented Dec 16, 2018

Add a daemon mode where the tool auto rebalances every x hours or whenever an imbalance worth correcting presents itself (what this exactly means TBD)

@C-Otto
Copy link
Owner

C-Otto commented Dec 16, 2018

A cron job might be easier to do

@wamde
Copy link
Collaborator Author

wamde commented Dec 17, 2018

Definitely easier at first, but a built in daemon mode could provide more reactivity. Worth looking into anyway I think, if not just now then a tad later.

@ZapUser77
Copy link

A time based auto-rebalance will be insufficient for even small hubs. Large hubs will likely see 1000's of transactions per second... small hubs will probably see 1-10 per second.
Is there a way to be more interactive with LND? Ideally, whenever channel balance changes, it needs to trigger a "Is this still balanced" and "If not, then rebalance".
I've never worked with RPC nor Python, so I have no idea what is/is not possible.

@wamde
Copy link
Collaborator Author

wamde commented Dec 29, 2018

Yes, scheduled rebalance won't cut it long term when the network matures.
My node is nowhere near that though, but yours may be since you operate a big node. Would you mind sharing stats on tx/s you process, frequency of rebalancing etc?
We can then look into using triggers to make that more reactive, but that is like P2, we need a manually triggered auto mode first I reckon (and that is #4 for now).

C-Otto pushed a commit that referenced this issue Dec 29, 2018
@wamde wamde added the design_needed Requirements/scope not fully fleshed out. label Dec 31, 2018
@xanoni
Copy link

xanoni commented Jul 27, 2021

@wamde maybe this helps: #184

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design_needed Requirements/scope not fully fleshed out.
Projects
None yet
Development

No branches or pull requests

4 participants