• add the math solve the x*y=k invariant for a given change in x

Users should be able to swap one asset for another based on the amm curve. For v1, we only want to support simple swap scenarios, i.e. constant product on pools with 50/50 weights.

• #143
• #144
• #146
• #147
• #197
• #255
• #256

• feat: NeededCollAmtGivenGov
• test: In $90 MTRX @ 10% collRatio -> Out $10 COLL
• test: In $10 MTRX @ 90% collRatio -> Out $90 COLL
• test: One case where the integer gets chopped off (perhaps 70% collRatio).
• docs: Document the function.

OS information

cat /etc/os-release

NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"

Description of the error

I regenerated the binaries for the CLI using make install. make localnet also runs fine.

matrixd keys list returns [], so I needed to make a key to mint and burn stablecoins.

On @matthiasmatt's machine, this works fine with a command like matrixd keys add test and populates the key list. On my machine, I'm getting

Error: No such interface “org.freedesktop.DBus.Properties” on object at path /

References

• Keyring - Cosmos SDK docs
• [BUG] terracli keys add panics · Issue #389
• panic when run desmoscli keys add ${wallet_name} #232
• Versent/saml2aws#561 (comment)

Solution

The solution is to use a different keyring backend. For local development, it's sufficient to simply append

--keyring-backend=test

to the end of any command that would've raised this error.

In: USDM
Out: MTRX and COLL

• #76
• #81
• #106
• #107
• #108
• #109
• #110
• #111

How fees on MintStable and BurnStable work and where they're distributed

When a mint or burn transaction fee is taken out, it goes to two places: the Treasury and the Ecosystem Fund (StableEF)

ability for user to join with a single asset

• do a single asset swap under the hood
• calculate maximum number of lp shares factoring in the price impact
• add single asset joins to the remaining coins after a multi-asset join

(refactor-idea) You can extract the fields from the MsgBurnStable proto and pass them individually into Keeper.BurnStable, so that the function signature doesn't have ugly proto messages when its imported to other modules.

Originally posted by @MatrixHeisenberg in #61 (comment)

You can have the keeper functions be proto-less so that you can import them to other modules without using Msg* objects.

Should also check that the module account has enough COLL to send to the user. I'm not sure what the proper error handling would be in this case, so maybe we'd have to panic(err).

@VimDiesel-Cosmos do you have any idea on what we should do in this case?

Originally posted by @MatrixHeisenberg in #61 (comment)

Basic join pool functionality for a v1 on testnet.

• #92
• #93
• #94
• #95
• #96
• #100
• #152
• #195

Create some tests for mint and burn logic in stable-coin module. Test edge case for:

• Insufficient balance
• Need price feed price for the assets: governance and collateral
• Invalid asset
• Token decimal precision required that's too high (above 18)
• etc.

For opening long and short perpetual positions

We need to setup continuous integration testing to:

• Verify the make build works properly. -> PR test: add 'make build' to CI workflow
• (Deprecated) Verify that make proto-gen runs properly.
• All x/... tests run with go test ./... -> feat/add-gh-test-workflow

• #157
• #175
• #64
• #194
• #138
• #90

Hi! @sbneo2022 @godismercilex the code that exists in sdk-go repo is just the types. Looks like the node source code is not open.

when a user LPs to a pool, calculate the max number of coins they can deposit given the pool's ratio and the deposit ratios.

Add ability for the dex module to track and update the total liquidity in the dex.

• read specific denom's liquidity
• write specific denom's liquidity
• read all liquidity
• write all liquidity
• add liquidity
• remove liquidity

Perpetual protocol vAMM has a concept called baseAssetDeltaThisFunding, that is updated on updateReserve.

Understand the concept and implement it on updateReserve.

SwapOutput is the contrary of swap input. We give Base asset to obtain Quote Asset.

https://github.com/perpetual-protocol/perpetual-protocol/blob/511d5c203af73482bb0f549dfc8c62d0c212c07b/src/legacy/AmmV1.sol#L239

Define the AMM interface so we can split the implementation in two groups, one for AMM the other for the clearing house.

• Golang installation in a container
• Verify that the setup instructions for matrixd (INSTALL.md) work on a fresh clone and update them if not.

Integrate logic to get oracle values into the repository to update the price of the protocol. This price will be used in several components.

Pool cannot be created if assets are not whitelisted.

The Perpetual protocol has a concept called Reserve Snapshot. Not sure is this is something that is a consequence of using a Solidity smart contract, or is crucial to implement for the protocol to work.

Needs investigation.

The lockup module is only concernerd with locking and unlocking users tokens based on some pre-configured parameters. Other modules will call this module to lock tokens for different use cases, e.g. pool incentives and/or voter escrow. See the osmosis lockup module for inspiration.

• #105
• #234
• #235

Collateral Ratio

• GetCollRatio: Method for querying the collRatio, an sdk.Dec between 0 and 1.
• SetCollRatio: Manually set the collRatio without any dependence on the Controller.

In all the keeper tests we use a constructor to build a keeper.

func AmmKeeper(t *testing.T) (Keeper, sdktypes.Context)

We have decided that the consistent way would be to use a the simapp as other modules.

See x/stablecoin/keeper/needed.go

• #159
• #127
• #150
• #160
• #196
• #211

On swapping, perp protocol uses a fluctuation Limit. We need to clarify how it works, and in case is needed implement.

Liquidity pools should have target weights (even stableswap pools) because stableswap pools behave like constant product amm pools when the liquidity is too far off balance.