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
refs: #11013
## Description
- feat(fast-usdc): `ChainHub` update interfaces
- fix(fast-usdc): prepare to repair Noble Account
- feat(fast-usdc): core eval to update chainInfo, noble ICA
- feat(builders): to reconfigure Fast USDC
- test(boot): start fastUsdc using fast-usdc-beta-1 release
- chore(boot): cache fast-usdc-beta-1 release artifacts
- test(boot): upgrade Fast USDC; update noble ICA
- test(boot): oracles accept before upgrade
### Security Considerations
~~`creatorFacet.getChainHub()` increases the surface area of the contract.~~
### Scaling Considerations
none, I think.
### Testing Considerations
- unit tests for chainHub methods
- bootstrap test for upgrade
for a later PR:
- a3p, multichain-testing: #11060
### Upgrade / Documentation Considerations
OCW operators have to accept their invitations before the upgrade, since their invitations are attached to ephemeral offer handlers. Consideration of addressing that is postponed to...
- #11057
What is the Problem Being Solved?
Redeeming an OCW operator invitation will fail if the contract was upgraded first.
Description of the Design
Use a durable offer handler instead of a closure:
agoric-sdk/packages/fast-usdc/src/exos/transaction-feed.js
Lines 109 to 118 in f83e5a9
Security Considerations
some robustness / availability improvement
Scaling Considerations
difference should only be in small constant factors
Test Plan
Upgrade Considerations
On mainnet, all OCWs have accepted their invitations. So this issue is only relevant if a new instance of the contract is deployed.
The text was updated successfully, but these errors were encountered: