Open Crypt-iQ opened 2 years ago
ChannelAcceptAcceptor (we need a new name)
ChannelAcceptController
ChannelFlowController
ChannelAcceptApprover
The problem is we have the ChannelAcceptor
which accepts/denies an open_channel
message. Ideally we'd rename the rpc to ChannelOpenPredicate
and this one would be ChannelAcceptPredicate
. I don't think those names are distinct enough from the name/intent of ChannelAcceptor
Could the existing channel acceptor RPC just handle both cases? Maybe you could pass an argument to it to also catch own opens?
Could the existing channel acceptor RPC just handle both cases? Maybe you could pass an argument to it to also catch own opens?
I think so
We can currently intercept incoming channel opens to the lnd node. What we cannot do is intercept the
accept_channel
message if we are the initiator. It is harder to sanity check that their parameters are safe for us to use without turning knobs. TheChannelAcceptAcceptor
(we need a new name) would interceptaccept_channel
messages at the fundingmanager-level and give them to the rpc-layer. The functionality should be essentially identical to theopen_channel
acceptor. Alternatively, a general message-interceptor could probably take on the role ofChannelAcceptor
&ChannelAcceptAcceptor
and we could refactor some of the current logic. However, a general message-interceptor is probably a larger code lift in the short term.