dc4acd0dd7
- Loan origination fees: The previous approach of tracking the reserved amount did not work because OutEvents will also reduce the reserved amount. This means we can't know if it was an OutEvent-cancel or an order execution that caused the reduction. Instead, we now track the amount of borrows that was made (without applying origination fees) in place order. Whenever we try to settle and the amount of tokens on the oo account is less than the potential borrows, we can be certain that the borrow has actualized. - Place order is no longer automatically followed by a settle. This can reduce compute use when people want to place multiple orders in sequence. Now they can use the HealthRegion instructions to place their orders, settle once at the end, and then have health checked. - Vault check: Place order previously rejected valid orders because it didn't consider that there could be free tokens on the oo account. - Tests: Some infrastructure for less verbose serum testing. |
||
---|---|---|
.cargo | ||
.github/workflows | ||
anchor@b52f236146 | ||
anchor-tests | ||
cli | ||
client | ||
keeper | ||
lib/checked_math | ||
liquidator | ||
mango-macro | ||
migrations | ||
programs | ||
py | ||
ts/client | ||
.dockerignore | ||
.eslintignore | ||
.eslintrc.json | ||
.gitignore | ||
.gitmodules | ||
.prettierignore | ||
Anchor.toml | ||
CHANGELOG.md | ||
Cargo.lock | ||
Cargo.toml | ||
Dockerfile | ||
HOW-TO-RELEASE.md | ||
README.md | ||
idl-fixup.sh | ||
mc-release-to-devnet.sh | ||
package.json | ||
release-to-devnet.sh | ||
release-to-mainnet.sh | ||
tsconfig.build.json | ||
tsconfig.cjs.json | ||
tsconfig.esm.json | ||
tsconfig.json | ||
update-local-idl.sh | ||
yarn.lock |
README.md
Development
- rust version 1.59.0 (9d1b2106e 2022-02-23)
- solana-cli 1.9.13
- anchor-cli 0.24.2
- npm 8.1.2
- node v16.13.1
Devnet deployment - m43thNJ58XCjL798ZSq6JGAG1BnWskhdq5or6kcnfsD
For testing latest program changes while developing, just run below scripts in given order form any branch, these set of scripts should more or less always work, bump up GROUP_NUM if you unsure if previous GROUP_NUM has not been cleanly closed or setup with older program code
./release-to-devnet.sh
GROUP_NUM=4 yarn ts-node ts/client/src/scripts/devnet-admin.ts
GROUP_NUM=4 yarn ts-node ts/client/src/scripts/devnet-user.ts
GROUP_NUM=4 yarn ts-node ts/client/src/scripts/devnet-user-close-account.ts
GROUP_NUM=4 yarn ts-node ts/client/src/scripts/devnet-admin-close.ts