feature request/idea: manage lightning channels in sphinx app

[antonilol]

i imagine something like this would be cool to have this in the app

i edited a screenshot so dont look at the fonts, exact placement, etc...

the green dot indicates if the channel is active (it can also be inactive if the remote node if offline)

a button to close a channel can be added, but of course with a confirmation and show the remote node, and if the pubkey is in contacts, add a name and profile picture

all this data needs to be requested from relay, and i am willing to implement it there

i edited it in the Friends tab, but it can be anywhere, next to feed, behind a button in the menu or somewhere else

[kevkevinpal]

I'm not sure about this one, apps like Zeus already do this really well and I'm not sure if it'll add unnecessary bloat to the app. But maybe there'd be a place for a warning saying if you're low on inbound or outbound liquidity that also could be a good bot to build on sphinx aswell.

Also, a feature like this would only make sense for users who are running on their own nodes as lots of lite users don't need to manage their channels

thoughts from other appreciated

[Evanfeenstra]

I think its a good feature to have, for home node users. Maybe its a little bit hidden so regular it doesn't add complexity to users who dont care about it.

But for sure, admins of large tribes need ways to get notified, and manage their channel liquidity

[kevkevinpal]

@Evanfeenstra @antonilol how would a user define what low liquidity is? Would we just use a slider a user can set as the threshold before getting notified or is there a better alternative?

[antonilol]

@Evanfeenstra @antonilol how would a user define what low liquidity is? Would we just use a slider a user can set as the threshold before getting notified or is there a better alternative?

i think the slider would be the best way, you cant say for someone else what low liquidity is let that be determined by themselves, but a default value can be set to like 10k or 20k sats i would say (but if your or someone else's usage is different from mine another default would be better)

[kevkevinpal]

We can do an opt in approach where you won't get notified till you set the minimum threshold? And at that point the user is aware of the setting they changed and can navigate back to it to change it. This way we don't need to set a limit for them