-
Notifications
You must be signed in to change notification settings - Fork 231
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
CLI for FU Liquidity Provider #10328
Comments
Merged
mergify bot
added a commit
that referenced
this issue
Oct 23, 2024
refs: #10328 ## Description Sets up a package for Fast USDC and stubs out its CLI. Finishing #10328 will require a contract that has the offer makers. ### Security Considerations none ### Scaling Considerations none ### Documentation Considerations This will need end user documentation later ### Testing Considerations basic test ### Upgrade Considerations not deployed
mergify bot
added a commit
that referenced
this issue
Oct 30, 2024
refs: #10328 ## Description Following up on package creation. See changes in commit list. Principally renaming the package to have the `@agoric/` prefix. ### Security Considerations `@agoric/` could reduce NPM squatting risk ### Scaling Considerations n/a ### Documentation Considerations none ### Testing Considerations one ### Upgrade Considerations not deployable
1 task
mergify bot
added a commit
that referenced
this issue
Dec 10, 2024
closes: #10657 refs: #10328 ## Description - advancer, settler can operate without a noble account address - creatorFacet method to synchronize on fulfillment of `nobleAccountV` vow - restore fast-usdc a3p-integration test to working order ### Security / Documentation Considerations While the noble account vow has not fulfilled, diagnostics for advancing to non-agoric chains are likely to be obscure. Configuration flexibility leads to possibility of configuration errors. ### Scaling Considerations n/a ### Testing Considerations existing tests, but with `set -e` so that when `fastUsdc` is not in `agoricNames.instance`, we actually notice. ### Upgrade Considerations `nobleAccountV` persists across incarnations, so we won't try to make another one on restart / upgrade. TODO: - [x] what to do if `nobleAccountV` rejects?
was done in #10364 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
Description of the Design
deposit
command that does the public invitation maker. (for now whoever deposits first gets the sole right to withdraw)withdraw
command to withdraw depositsDoes not do anything for "requesting advance". @samsiegart is working on that.
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: