Go to file
microwavedcola1 359c6ab814 rename
Signed-off-by: microwavedcola1 <microwavedcola@gmail.com>
2022-03-01 20:55:10 +01:00
.cargo suppress known issues 2022-03-01 06:16:10 +01:00
.github/workflows github workflows 2022-02-28 12:58:39 +01:00
migrations First commit 2022-01-21 19:21:46 +01:00
programs/mango-v4 Tests: Read banks/oracles from address lookup table 2022-03-01 15:12:53 +01:00
py rename 2022-03-01 20:55:10 +01:00
ts prepare for monorepo 2022-03-01 20:48:59 +01:00
.gitignore ignore expanded file 2022-02-28 10:52:07 +01:00
Anchor.toml Enable anchor seeds extraction 2022-02-23 10:55:23 +01:00
Cargo.lock add ix handling for stub oracles 2022-02-28 12:37:12 +01:00
Cargo.toml First commit 2022-01-21 19:21:46 +01:00
README.md Depend on anchor cli 0.22.0 2022-02-22 16:45:13 +01:00
package.json bump anchor ts lib 2022-02-23 11:10:50 +01:00
release.sh prepare for monorepo 2022-03-01 20:48:59 +01:00
tsconfig.json prepare for monorepo 2022-03-01 20:48:59 +01:00
yarn.lock bump anchor ts lib 2022-02-23 11:10:50 +01:00

README.md

Development

  • rustc 1.57.0 (f1edd0429 2021-11-29)
  • anchor-cli 0.22.0
  • npm 8.1.2
  • node v16.13.1

Module structure

As and when we move to a more complete project, we should think of having multiple modules e.g. core/shared, spot, perpetuals, etc., and then each would have its own instructions and state sub module. Goal is that new contributors find relevant code easily and can navigate easily.

programs
└── mango-v4
    ├── Cargo.toml
    ├── Xargo.toml
    └── src
    │    ├── error.rs
    │    ├── instructions # instructions go here, each instruction gets an individual file
    │    │   ├── initialiaze.rs
    │    │   └── mod.rs
    │    ├── lib.rs
    │    └── state # state goes here, each account state gets an individual file
    │       └── mod.rs
    └── tests # rust tests, TODO