-
Notifications
You must be signed in to change notification settings - Fork 215
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
Install RUN Protocol Preview release in devnet on April 22 #5062
Comments
@arirubinstein and I just did a dry run: OK:
not OK:
some details: The Makefile in
So we made some one-off shell scripts in a |
at least one reason PSM didn't work was the following; that fix wouldn't solve it, though, so I'll leave it for later... modified packages/run-protocol/src/core-proposal.js
@@ -334,7 +334,7 @@ export const getManifestForPSM = ({ restoreRef }, { installKeys, denom }) => {
return {
manifest: PSM_MANIFEST,
installations: {
- runStake: restoreRef(installKeys.runStake),
+ psm: restoreRef(installKeys.psm),
},
options: {
denom, |
IBC connected between cosmos testnet and Agoric stageI'm not sure this IBC denom is suitable for ATOM; that might need to be connected to Oracle stuff. @michaelfig ? But we could use this (or the equivalent on devnet) for USDC: @arirubinstein got a relayer working; we see 1000uphoton were transferred to
For reference, the command to do a transfer is:
|
@dtribble found a problem; I marked it as a blocker above:
|
@dtribble , @jessysaurusrex , @arirubinstein and I reviewed status yesterday evening. @arirubinstein made good progress on IBC, but I had not managed to do as much testing in stage as we planned. @dtribble was still working on liquidation. @michaelfig reported good progress on Oracles. So it seemed just as likely that all the parts would be ready at once. We agreed to use the developer's interpretation of "Friday", that is: before Monday. I notified |
Launch in stage worked!Launching the 10 contracts to agoricstage-23 worked! @dtribble and I made a recording. Passcode: It did involve some code that is not on master.
Then in the REPL:
in particular, re runStake:
|
I used the following changes from master, and master from a few days ago, for the launch above. p.s. I reviewed these and separated them into:
|
VaultFactory, Liquidation ready as of 2b2c966For vaultFactory, @dtribble @Chris-Hibbert and @turadg all show: For liquidateIncrementally, @Chris-Hibbert got: @turadg was building from git version 2b2c966 I'm struggling to confirm. |
We'll use these hashes, all derived from the same git commit above, 2b2c966:
@turadg , @kriskowal and I were all able to compute these, after zapping |
PSM smoke test passed on agoricstage-24with @michaelfig ... re-launched the PSM with a real IBC denom traded 25 IBC AUSD for...
full transcript: https://gist.github.com/dckc/0e0e917728a774b3f55e5d0ea4f40a18 |
https://devnet.explorer.agoric.net/proposals/2 is out for votes. txhash: |
the proposal passed! the contracts are running:
oracle stuff seems connected:
|
to get past "no collateral types": moved to #3924 (comment) |
Let's track the remaining work
and close this. |
What is the Problem Being Solved?
We have committed on our public roadmap to deploy RUN Protocol RC0 (aka preview) in April, 2022.
See also:
Description of the Design
Goal: support...
Initial launch of 10 contracts:
Runbook: RUN Protocol Preview · Agoric/agoric-sdk Wiki
contractGovernor / committee / binaryVoteCounter
runStake
AMM
Vaults
Error#1: value for LiquidationInstall must be an Installation, was Object [Alleged: Installation] {}
reserve
startRewardDistributor
PSM
AUSD
,psm
inagoricNames
(deja vu)Follow-on proposal(s) enable collateral in vaults:
Security Considerations
Test Plan
E(E(home.agoricNames).lookup('instance')).getEntries()
and look for details TBD. Move these details to the runbook?The text was updated successfully, but these errors were encountered: