Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: redelegate, undelegate on StakingAccountKit (#9331)
closes #9069 closes #9070 ## Description on StakingAccountHolder, add Redelegate, Undelegate on `invitatationMakers` and `redelegate()`, `undelegate()` on `holder`. refactor to get the `holder` facet to be checked against the orch API: - factor `StakingAccountActions` out of `BaseOrchestrationAccount` was DRAFT until: - [x] `undelegate()` waits for the unbonding period - [x] [spec/types use of cosmos types such as `Delegation` is cleared up](https://github.com/Agoric/agoric-sdk/pull/9331/files#r1592654234) - [x] PR template (description etc.) filled out - [x] git history clean-up ### Security Considerations adds a `TimerService` capabilty to each staking account kit. ### Scaling Considerations `E(timer).wakeAt()` consumes resources in the timer vat for the ~21 day unbonding period. ### Documentation Considerations orch API change, already discussed with product: - chore: narrow return type for redelegate to `Promise<void>` (or: widen, depending on how you look at it) ### Testing Considerations unit test coverage is reasonable. I'd like to do more end-to-end testing; should closing #9069 wait for that? ### Upgrade Considerations doesn't use vows. Do we have plans to do that later? Which issue?
- Loading branch information