You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When multiple channels exist for the same peer with the same asset_id, we attempt the first channel. However, if it fails due to the absence of an inbound policy, we stop further attempts.
We successfully fetch the first result, but if a downstream failure occurs due to the absence of an inbound channel policy for a particular channel, all other channels of the same peer become unusable until the problematic channel is closed.
Similar, 1052 wants to even allow more than 1 peer, but this Issue just relates to the fact if we have more than 1 channel witth the same peer, and the first selected has no policy, we will abort and have no ability to use the other channels with the peer (which might have a policy in place)
Is there ever going to be a case where there will be a different quote/rate on different channels from the same peer? Wondering in that case if similar prioritization logic as is suggested in #1052 should be considered?
When multiple channels exist for the same peer with the same asset_id, we attempt the first channel. However, if it fails due to the absence of an inbound policy, we stop further attempts.
We fetch the channels here:
taproot-assets/rpcserver.go
Line 7137 in ee06af7
We successfully fetch the first result, but if a downstream failure occurs due to the absence of an inbound channel policy for a particular channel, all other channels of the same peer become unusable until the problematic channel is closed.
taproot-assets/rpcserver.go
Line 7215 in ee06af7
Expected behaviour:
Try all available channels before reporting an error.
The text was updated successfully, but these errors were encountered: