-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request for a Noble ICA for Fast USDC has yet to settle - misconfigured host #11013
Labels
bug
Something isn't working
Comments
See also pc/fusdc-beta-2. |
This was referenced Feb 18, 2025
mergify bot
added a commit
that referenced
this issue
Feb 27, 2025
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
This was referenced Feb 27, 2025
|
const addr = await E(kit.creatorFacet).connectToNoble(); |
When the contract is upgraded, that promise will reject, resulting in a rejection of the promise for the CORE_EVAL
execution.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The connection parameters we used - from cosmos/chain-registry - seem to be incorrect. We specified
connection-72
for the controller andconnection-40
for the host.agoric-sdk/packages/orchestration/src/fetched-chain-info.js
Lines 139 to 145 in b962ad8
It seems we should’ve used
connection-38
for the host per map of zonesAs a result, while @0xpatrickdev was able to deposit and withdraw to the LP and see the pool and settlement account addresses published, our request for a Noble ICA is stuck.
agoric-sdk/packages/fast-usdc/src/start-fast-usdc.core.js
Line 184 in 214eb2a
To Reproduce
agd query ibc channel end icacontroller-1 channel-157 --node https://agoric-rpc.polkachu.com:443
STATE_INIT
Also:
Expected behavior
I'm not sure
Platform Environment
git describe --tags --always
)Additional context
Add any other context about the problem here.
Screenshots
If applicable, add screenshots to help explain your problem, especially for UI interactions.
The text was updated successfully, but these errors were encountered: