Add secp validator key to enable pessimistic bridge

Staking validators
30

Summarizing what we have discussed so far:

  • Everyone seems to be onboard with the necessity of adding validator secp key. However, there are some disagreements on the details.
  • For bridge, the exact message to be signed by the secp key is not finalized and I think we can take some more time to mull over this @eatmore @alexatnear @alex.shevchenko
  • For the protocol change, it seems that the consensus is that
    1. it is better to upgrade through runtime directly by swapping the contracts.
    2. There is some disagreement regarding whether we should directly modify Stake action or we should do it in a backward compatible way by introducing Stake2 action and deprecating Stake action later.
    3. We do not want to introduce any BLS key at this point.
  • For changes in tools, it is mostly around near-api-js and near-cli and there is no need to change anything in wallet. The changes in near-api-js and near-cli are mostly around the change to Stake action (or adding Stake2 action).
  • A new staking pool contract and a new staking pool factory contract needs to be written.

Please let me know if I missed something in my summary and we plan to finalize the decision tomorrow after the public meeting.

3 Likes