Closed 0xHansLee closed 1 year ago
I merged #578 into this branch and changed base branch to ft/570/upgrade-endblocker
.
Because both query for oracle upgrade info and proto messages are needed to develop oracle.
I think seperating OracleRegistration and OracleUpgrade is a good choice.
Because required paramter are different for OracleRegistration and OracleUpgrade.
OracleUpgrade is not required oracleCommissionRate
, oracleCommissionmaxRate
and oracleCommissionMaxChangeRate
.
I too think the OracleUpgrade
name is confusing.
But I can't think of a good name. :)
Let's think about this.
close #575
proto messages and skeleton code for the txs and queries.
Apart from
OracleRegistration
, I definedOracleUpgrade
which is a set forMsgUpgradeOracle
for now. When developing functions, if it seems that it is better to combine them, then let's merge them.BTW, the name of
OracleUpgrade
is little bit confusing, so if you have any good idea for this, please feel free to leave your thoughts.