-
Notifications
You must be signed in to change notification settings - Fork 229
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
chore: Update feeConfig.variableRate to 0.5%, i.e. 5n/1000n #11054
base: master
Are you sure you want to change the base?
Conversation
Deploying agoric-sdk with
|
Latest commit: |
9537828
|
Status: | ✅ Deploy successful! |
Preview URL: | https://8bf48287.agoric-sdk.pages.dev |
Branch Preview URL: | https://dc-fu-feeconfig.agoric-sdk.pages.dev |
e96a95a
to
b140a23
Compare
7f9c81b
to
af303c3
Compare
ebf1bd7
to
07f3dae
Compare
af303c3
to
7dab2ca
Compare
@@ -243,7 +243,7 @@ Generated by [AVA](https://avajs.dev). | |||
{ | |||
encumberedBalance: { | |||
brand: Object @Alleged: USDC brand {}, | |||
value: 0n, | |||
value: 750000n, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wonder why this changed 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait... does this mean that an advance didn't finish?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, or we didn't simulate a settle somewhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The contract is restarted in the middle of the test using...
const kit = await EV.vat('bootstrap').consumeItem('fastUsdcKit');
const actual = await EV(kit.adminFacet).restartContract(kit.privateArgs);
and the privateArgs
in fastUsdcKit
weren't updated with the new feeConfig
7dab2ca
to
a55fbc0
Compare
I think the revised connection info should go into |
|
||
const { brand: usdcBrand } = kitPre.privateArgs.feeConfig.flat; | ||
// TODO: update agoricToNoble in kitPost.privateArgs.chainInfo too |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this matter? It looks like privateArgs.(chainInfo|assetInfo)
is only consumed by ChainHub if it's the first incarnation.
Maybe worth a comment in meta.privateArgsShape
above these two fields mentioning this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not a GTM correctness issue, but I was burned once by expecting fastUsdcKit.privateArgs
to be current.
value: 1000n, | ||
}, | ||
numerator: { | ||
brand: Object @Alleged: USDC brand {}, | ||
value: 1n, | ||
value: 5n, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
a55fbc0
to
9537828
Compare
Security / Scaling / Documentation Considerations
lowering the rate changes the incentives a bit: it encourages users while rewarding liquidity providers less on each tx
The fees and such should be discussed in the community governance thread.
Testing Considerations
updated relevant snapshot
Upgrade Considerations
deploys with...