Integration Guide
Get an understanding of the necessary things to leverage the Mean Protocol on your own Dapps

Authentication

Interacting with the Mean Protocol Programs deployed on Solana's DEVNET, and MAINNET doesn't require any authentication. The protocol is completely open and anyone can start using it without having to contact us.
Please refer to the Smart Contracts section and the respective open-source projects that support the different developer SDKs for these programs.

Architecture

Your app can interact directly with any of the Mean Protocol Programs (smart contracts) deployed on-chain, or through the provided Mean SDK, depending on your needs.
NOTE: Server vs Client-side program invocation
Be aware of your use case when deciding between server-side vs client-side program invocation. Consider the limitations on performance and latency when making your decision.
If you are a developer leveraging the Mean Protocol as part of multi-instructional transactions, or from cross-program invocation use cases, we recommend using the Rust API directly against the Solana Sealevel runtime, as it will perform better, and will save you time.
For those wanting to leverage out-of-the-box functionality like creating a treasury pool, or opening a money stream directly from a web or mobile app, the easiest route is to leverage the JS API with the provided Mean SDK, as it abstracts a lot of the complexities and serialization boilerplate required to send queries and commands to Solana. See JavaScript API.

Fees

There are three kinds of fees charged by every Dapp in crypto-land Network Fees, Protocol Fees, and App Fees.

β†’ Network Fees

These are paid to the Solana Network directly to sign transactions and submit them to validator nodes.
The current transaction fee in Solana as of Sept 2021 is:
  • 5,000 Lamports, equivalent to
  • 0.000005 SOL, equivalent to
  • $0.000365 (at ~$73 / SOL)

β†’ Protocol Fees

These are fees paid to different protocols, like the Serum, Raydium, and Mean protocols for using their resources, such as liquidity pools, treasury pools, borrowing, lending protocols, etc.
Please refer to each protocol documentation for the most up-to-date fee schedule. Here's the list of dependent protocols used by ours through cross-program invocations.
To see Mean Protocol Fees, refer to the Mean DAO Revenues section.

β†’ App Fees

There are no App Fees charged by Mean Protocol, but integrators can introduce their own App Fees on the different operations and smart contracts we provide. This is a way to facilitate additional revenue streams through the use of Mean Protocol in your application.
There are no App Fees charged by Mean Protocol
The App Fee is provided in basis points or a flat amount. When basis points are applicable, it's always expressed as a percentage value with base 1 (i.e. 0.2000 = 20% while 0.0020 = 0.2%), which is taken from the token output. When a flat amount is applicable, it's always expressed in Lamports.