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
We have an audit issue #2439 where our current V0 message format uses constant Weight to Fee conversion instead of Adjusted Weight to Fee.
Adjusted Weight to Fee conversion uses TransactionPayment::next_fee_multipler so that fee is dynamic. We also want to remove the relay fee and instead use a fee multiplier so that it can cover fees on both src and dst chain as the both chains will lead to different adjusted weight to fee multipler.
Below is the outlined migration path for Taurus. For mainnet, there are no domains to migration is not required
We have an audit issue #2439 where our current V0 message format uses constant Weight to Fee conversion instead of Adjusted Weight to Fee.
Adjusted Weight to Fee conversion uses
TransactionPayment::next_fee_multipler
so that fee is dynamic. We also want to remove the relay fee and instead use a fee multiplier so that it can cover fees on both src and dst chain as the both chains will lead to different adjusted weight to fee multipler.Below is the outlined migration path for Taurus. For mainnet, there are no domains to migration is not required
The text was updated successfully, but these errors were encountered: