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
currently covenants assume that parties are interchain (non-neutron). this may not always be the case.
this will have impact on the inflow and outflow of funds from the covenant.
for inflows, we should skip the instantiation of ibc-forwarder for any native parties. the deposit address for that party will be the holder. lets combine this with using instantiate2 for the covenant instantiation flow as neutron will be launching it later this month.
for outflows, lets introduce the notion of native receivers on the interchain router. this is probably easiest by having an enum for both cases.
The text was updated successfully, but these errors were encountered:
currently covenants assume that parties are interchain (non-neutron). this may not always be the case.
this will have impact on the inflow and outflow of funds from the covenant.
for inflows, we should skip the instantiation of ibc-forwarder for any native parties. the deposit address for that party will be the holder. lets combine this with using instantiate2 for the covenant instantiation flow as neutron will be launching it later this month.
for outflows, lets introduce the notion of native receivers on the interchain router. this is probably easiest by having an enum for both cases.
The text was updated successfully, but these errors were encountered: