implement transfer() of CosmosOrchestrationAccount #9784
Labels
Comments
1 task
mergify bot
added a commit
that referenced
this issue
Aug 16, 2024
refs: #9193 refs: #9784 ## Description These changes primarily implement the `.transfer` method on `CosmosOrchestrationAccount`. The changes require providing the exo with a `ChainHub` for looking up transferChannel info and `TimerService` for building a default timeout parameter. Notably, the `.transfer()` Promise resolves when the host chain submits the transfer to other remote chain. The `sendThenWaitForAck` logic that `LocalOrchestrationAccount` has is not yet implemented but tracked via #9784. Other changes include: - simplified `transferChannel` lookup logic in `LocalOrchestrationAccount` - `/boot/tools/support.ts` changes to simplify `sendPacket` ack mocks for dibc bridge - bootstrap tests for `LocalOrchAccount.transfer()` using `Transfer` invitationMaker - `/boot/tools/support.ts` changes to ensure mock localChain addresses are unique - `packetUtils` interface guard change for an observed, but seemingly benign, error ### Security Considerations n/a ### Scaling Considerations n/a ### Documentation Considerations - [ ] how to best document the differences between LOA and COA for the interim? ### Testing Considerations Includes unit and boot tests. ### Upgrade Considerations n/a, unreleased code
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
.transfer()is implemented onCosmosOrchestrationAccount, but the promise resolves when the transfer is submitted to the remote chain, not when when the transfer is complete.Description of the Design
TBD
One requirement is,
Dependencies (Maybe?)
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: