Frequently Asked Questions (FAQ) for Gamma's audits and security measures
Yes, Gamma has been audited several times. Please visit our Audits page to learn more and read our audits. Consensys Diligence and Arbitrary Execution conducted very thorough audits of our protocol.
Yes, Gamma has a bug bounty with Immunefi for up to $50,000. Gamma is happy to discuss minor bugs and fixes case-by-case basis. Don't hesitate to contact us if you want to discuss a bug.
Single-sided deposits have a reputation for being unsafe. They're prone to oracle manipulation. They require the protocol to swap some of the deposited tokens to deposit. This increases the costs associated with depositing. In concentrated liquidity, the pair ratio frequently changes, complicating single-sided deposits even more.
Gamma has some ideas about making single-sided deposits work. We left the option up on our user interface for when those solutions are available. They will be announced when they are.
Gamma goes through extensive testing procedures before and after updates are sent to production. Several individuals worldwide, with different skill levels, ISPs, wallets, browsers, hardware, and funds will evaluate changes before and after release. Everyone on the team is a "tester" and can report results on our testing workspace.
Make sure you are always connecting to the proper URLs. We encourage you to click official links from our trusted pages. See our Troubleshooting / Help page for guides on how to increase your security.
Gamma is non-custodial. We do not control user funds. Gamma's vaults are designed to function in a decentralized manner, with no ability of team members to tamper with or use funds. In a testament to this, we have several legacy versions of our software still open to the public for access.
After Visor merged with Gamma, a lot of operational changes were made.
1) Security audits with reputable firms were done immediately. These audits were intrusive, expensive, and time-consuming. They were also well worth it, and more will come.
2) Testing procedures were created. Extensive testing is now done on every update that pushes to production. Absolutely no updates are done without extensive testing.
3) Additional personnel were brought on, and some staff members were let go. Gamma brought in developers who took security very seriously.
4) The decision-making structure was changed. Clearer roles and responsibilities were given to individuals. The project's leadership was shaken up, and new decision-makers are in charge of Gamma.