orchestration - ICA Controller - Account - Create account on host chain #9064
Assignees
Labels
enhancement
New feature or request
Comments
0xpatrickdev
added a commit
that referenced
this issue
Apr 2, 2024
0xpatrickdev
added a commit
that referenced
this issue
Apr 2, 2024
0xpatrickdev
added a commit
that referenced
this issue
Apr 2, 2024
|
closed as this is a duplicate of ICA - create channel 8880 |
|
Actually the other was closed.. re-opening this one. |
0xpatrickdev
added a commit
that referenced
this issue
Apr 2, 2024
0xpatrickdev
added a commit
that referenced
this issue
Apr 2, 2024
0xpatrickdev
added a commit
that referenced
this issue
Apr 3, 2024
mergify bot
added a commit
that referenced
this issue
Jul 31, 2024
refs: #9064 ## Description - remove getBalance, getBalances, getPurse from IcaAccountKit - cleanup TODO surrounding `UNPARSABLE_CHAIN_ADDRESS` - rename `ChainAccountKit` -> `IcaAccountKit` - `findAddressField` should treat an empty string as an `UNPARSABLE_ADDRESS` - improve testing coverage for `IcaAccount.getPort()` - docs: update exo classDiagram ### Security Considerations n/a ### Scaling Considerations n/a ### Documentation Considerations n/a ### Testing Considerations n/a ### Upgrade Considerations n/a
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
A
Chainobject should be able to create an ICA account on a host chain. The caller of this API should receive exclusive rights to an ocap representing the authority to control the ICA account.This API should support lazy creation - a
providepattern associating a name with the ICA and associating the ICA with the seat/user so the contract can easily say, "Which agoric1/user does this ICA belong to?" and "Which ICA have I created for this agoric1/user?"Description of the Design
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: