[feature]: add more parameters to Channel Acceptor about lnd HOT 5 OPEN

So to_self_delay wouldn't be a problem to add because the counter party does send it via the channel negotiation, the other parameters are not negotiated but are part of the Channel_Update Gossip msg, which is only sent when the channel is already confirmed. So I don't think it is feasible, maybe query his other channels before opening a channel to get an idea of their fee strategy and timelock security evaluation ?

from lnd.

exactly fees and timelock are not exchanged during the opening process, so we cannot build this into the channel acceptor.

from lnd.

maybe query his other channels before opening a channel to get an idea of their fee strategy and timelock security evaluation

You're suggesting this as a logic which user can apply, correct? Not something that we might build into channel acceptor

from lnd.

exactly fees and timelock are not exchanged during the opening process, so we cannot build this into the channel acceptor.

Okay, so actually one's script calling Channel Acceptor actually can already do the best we can because we can look at the node_pubkey and then use other RPC calls to query that nodes other channels and then decide what to do before accepting.

However, why does Channel Acceptor provide min_htlc and max_value_in_flight? Are those policies or channel parameters?

from lnd.

However, why does Channel Acceptor provide min_htlc and max_value_in_flight? Are those policies or channel parameters?

The latter, they are channel constraints your peer has to follow when creating the commitment transaction. So his max_htlc amount in his channel policy can never be greater than the max_value_in_flight you negotiated during the channel opening.

from lnd.