feat(contract_manager): add near chains and contracts #2331
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
| return { id: outcome.transaction.hash, info: outcome }; | ||
| } | ||
|
|
||
| getCurrentGuardianSetIndex(): Promise<number> { |
There was a problem hiding this comment.
so there is no way to check this out? strange.
There was a problem hiding this comment.
Yes, there is no method for this.
| throw new Error( | ||
| "near contract doesn't implement getGovernanceDataSource method" | ||
| ); | ||
| } |
There was a problem hiding this comment.
do you know how the upgrade is going to work? we initially execute governance instruction, but what can we do after it :?
There was a problem hiding this comment.
Looks like we'll need to call a permissionless method update_contract with the new wasm file as input.
| @@ -19,6 +19,7 @@ export const RECEIVER_CHAINS = { | |||
| aurora: 9, | |||
| fantom: 10, | |||
| celo: 14, | |||
| near: 15, | |||
There was a problem hiding this comment.
well we are not using our own version of wormhole receiver here, right?
There was a problem hiding this comment.
No, I think we're using wormhole's own contract.
There was a problem hiding this comment.
well this one has the list of the ones that we manage the wh contract. (see the comment above)
There was a problem hiding this comment.
Moved it to a separate section with a comment.
Riateche
force-pushed
the
contract-manager-near
branch
from
3d44f78 to
6201e3f
Compare
No description provided.