Open anilhelvaci opened 1 year ago
Basically, below is what I've in mind;
LendingPool
contract with 100k units of governance tokens to be minted.getGovernanceInvitation
method) fetch their governance tokens.const riskControls: {
borrowable: false,
usableAsCol: false,
limitValue: 1_000n, // We only care about the limit of the collateral pool but we've to state an initial value for every pool anyway
}
BORROWABLE
.USABLE_AS_COLLATERAL
.Above is what I've in mind for demonstration. Please let me know if there's another case you'd like to be showcased. Or, since last time took a little bit too long(AMM Stop-Loss) you might want to keep this one a little bit shorter. Please feel free to let me know @rowgraus
With the newer version of agoric-sdk
deploying an AMM instance requires access to the feeMintAccess
which third party dapps do not have. For the local test environment we might be able to get that access during the bootstrap. But if decide to deploy this dapp to a testnet we'll have to deal with this again. So I'm changing the compareBrand
to be IST.
We need an ammInstance
because our LendingPool
protocol execute liquidations via AMM. In order to be able to liquidate a loan, a liquidity pool in the AMM where the centralBrand
is the compareBrand
and the secondaryBrand
is the underlyingAsset
in our protocol pool should exist in the AMM. So on every setup, either it's unit test or actual deploy, we add two liquidity pools to the AMM.
We should construct a scenario that showcases the behaviors in the Work Plan.