https://github.com/blockworks-foundation/mango-v4

mango-v4 monorepo, contains program, ts client, and py client
https://github.com/blockworks-foundation/mango-v4

Last synced: 14 days ago
JSON representation

mango-v4 monorepo, contains program, ts client, and py client

• Host: GitHub
• URL: https://github.com/blockworks-foundation/mango-v4
• Owner: blockworks-foundation
• License: other
• Created: 2022-01-21T18:21:28.000Z (almost 3 years ago)
• Default Branch: dev
• Last Pushed: 2024-04-12T12:27:27.000Z (8 months ago)
• Last Synced: 2024-04-12T18:47:37.230Z (8 months ago)
• Language: Rust
• Homepage:
• Size: 41.6 MB
• Stars: 59
• Watchers: 4
• Forks: 42
• Open Issues: 7
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE
  • Audit: audits/Audit_OtterSec_Mango_v0.17.0.pdf
  • Security: SECURITY.md

Awesome Lists containing this project

• awesome - blockworks-foundation/mango-v4 - mango-v4 monorepo, contains program, ts client, and py client (Rust)

README

        
_work in progress_

## License

See the LICENSE file.

The majority of this repo is MIT licensed, but some parts needed for compiling

the solana program are under GPL.

All GPL code is gated behind the `enable-gpl` feature. If you use the `mango-v4`

crate as a dependency with the `client` or `cpi` features, you use only MIT

parts of it.

The intention is for you to be able to depend on the `mango-v4` crate for

building closed-source tools and integrations, including other solana programs

that call into the mango program.

But deriving a solana program with similar functionality to the mango program

from this codebase would require the changes and improvements to stay publicly

available under GPL.

## Development

See DEVELOPING.md and FAQ-DEV.md

### Dependencies

- rust version 1.69.0

- solana-cli 1.16.7

- anchor-cli 0.28.0

- npm 8.1.2

- node v16.13.1

### Deployments

- devnet: 4MangoMjqJ2firMokCjjGgoK8d4MXcrgL7XJaL3w6fVg

- mainnet-beta: 4MangoMjqJ2firMokCjjGgoK8d4MXcrgL7XJaL3w6fVg

- primary mango group on mainnet-beta: 78b8f4cGCwmZ9ysPFMWLaLTkkaYnUjwMJYStWe5RTSSX

### Release

For program deployment, see RELEASING.md.

Here are steps followed while performing a npm package release

note: the UI currently uses code directly from github, pointing to the ts-client branch

- use `yarn publish` to release a new package, ensure compatibility with program release to mainnet-beta

- fix the tag auto added by yarn to match our internal convention, see script `fix-npm-tag.sh`, tags should look like this e.g.`npm-v0.0.1`, note: the npm package version/tag should not necessarily match the latest program deployment