blockworks-foundation
/
mango-v3
mirror of https://github.com/blockworks-foundation/mango-v3.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
486 Commits 91 Branches 21 Tags 16 MiB
Rust 99.7%
Shell 0.3%
Go to file
Maximilian Schneider 74387f3c49 add custom error type 2022-05-24 22:35:08 +03:00
.cargo Soteria and Audit updates (#120) 2022-01-27 14:01:56 +01:00
.github/workflows Disable UXD CI until we open source 2022-04-19 10:03:33 -04:00
common upgraded anchor and solana 2022-04-21 10:36:59 -04:00
mango-logs upgraded anchor and solana 2022-04-21 10:36:59 -04:00
mango-macro upgraded anchor and solana 2022-04-21 10:36:59 -04:00
program add custom error type 2022-05-24 22:35:08 +03:00
.gitignore V3.3.0 (#91) 2022-01-16 20:08:54 -05:00
Anchor.toml upgraded anchor and solana 2022-04-21 10:36:59 -04:00
Cargo.lock Fix overflow in SettlePnl 2022-05-14 17:40:11 -04:00
Cargo.toml
…
LICENSE
…
README.md V3.3.0 (#91) 2022-01-16 20:08:54 -05:00
changelog.md update deploy time 2022-05-14 17:40:11 -04:00
consumed_per_instruction_uniq.log Mc/liquidation tests (#133) 2022-02-14 08:17:47 -05:00
cu_per_ix.sh Mc/liquidation tests (#133) 2022-02-14 08:17:47 -05:00
proposals.md added proposals; downgraded syn package in mango-macro 2021-10-12 17:18:41 -04:00
rustfmt.toml
…

README.md

Mango Markets V3 - Decentralized Margin Trading

⚠️ Warning

Any content produced by Blockworks, or developer resources that Blockworks provides, are for educational and inspiration purposes only. Blockworks does not encourage, induce or sanction the deployment of any such applications in violation of applicable laws or regulations.

Contribute

Significant contributions to the source code may be compensated with a grant from the Blockworks Foundation.

Security

Mango is currently unaudited software. Use at your own risk.

You will be compensated by the Mango DAO for privately reporting vulnerabilities to the maintainers of this repo. Email hello@blockworks.foundation

Branches and Tags

  • New development happens on main. Pull requests should always target main by default.

  • Release branches have names like release/3.3.0 and are branched off of main or a parent release branch.

    • Bugfixes for releases should usually be merged into main and then be cherry-picked to the release branch.
    • Only push to release branches after talking to the release owner.
    • When a release is done, the released version is tagged and the release branch is deleted.

  • Release tags have names like v3.3.1.

  • To know what is deployed on mainnet, check the Anchor Builds.