Validate oracle tree currencies and pools on migration
Closed this issue · 0 comments
gmanev7 commented
We aim to eliminate a human error at protocol migration, specifically unknown currency tickers already used in the oracle's swap tree.
Scenario: drop support of a currency that is still in use at the swap tree.
Expected: Proposal would fail
The solution is to validate the swap tree at oracle's migration.