This document describes the Security Process for Kinto, including vulnerability disclosures and the ongoing Bug Bounty program.
We are committed to conduct our Security Process in a professional and civil manner. Public shaming, under-reporting, or misrepresentation of vulnerabilities will not be tolerated.
For any vulnerability not in the scope of the bug bounty program, please follow the section as the team might also be interested on it.
Kinto follows a community standard for responsible disclosure in cryptocurrency and related software. This document is a public commitment to following the standard.
This standard provides detailed information for:
- Initial Contact: how to establish initial contact with Kinto's security team.
- Giving Details: what details to include with your vulnerability disclosure after having received a response to your initial contact.
- Setting Dates: how to agree on timelines for releasing updates and making details of the issue public.
Any expected deviations and necessary clarifications around the standard are explained in the following sections.
Kinto is committed to working with researchers who submit security vulnerability notifications to us, to resolve those issues on an appropriate timeline, and to perform a coordinated release, giving credit to the reporter if they would so like.
<>
Kinto will launch a Bug Bounty program to encourage security researchers to spend time studying the protocol in order to uncover vulnerabilities. We believe these researchers should get fairly compensated for their time and effort, and acknowledged for their valuable contributions.
In case of a vulnerability not in the scope of the bug bounty please reach out the team directly.
In these cases, Please submit issues to all of the following main points of contact for security related issues according to the initial contact and giving details guidelines.
For all security related issues, Kinto has the following main points of contact:
| Contact | Public key | Key ID | |
|---|---|---|---|
| Security | PGP | security at kinto.xyz | 4C0552D8 |
Include ALL contacts in your communication, PGP encrypted to ALL parties in the same email.
In the case where we become aware of security issues affecting other projects that has never affected Kinto, our intention is to inform those projects of security issues on a best effort basis.
In the case where we fix a security issue in Kinto that also affects the following neighboring projects, our intention is to engage in responsible disclosures with them as described in the adopted standard, subject to the deviations described in the deviations section of this document.
Kinto does not currently have any established bilateral disclosure agreements.
For exact smart contracts, please check the list at:
Kinto list of deployed smartcontracts can be found below:
Note: Other contracts, outside of the ones mentioned above, might be considered on a case by case basis, please, reach out to the Kinto development team for clarification.
The standard describes reporters of vulnerabilities including full details of an issue, in order to reproduce it. This is necessary for instance in the case of an external researcher both demonstrating and proving that there really is a security issue, and that security issue really has the impact that they say it has - allowing the development team to accurately prioritize and resolve the issue.
In the case of a counterfeiting or fund-stealing bug affecting Kinto, however, we might decide not to include those details with our reports to partners ahead of coordinated release, as long as we are sure that they are not vulnerable.
Additional security-related information about Kinto including disclosures, signatures and PGP public keys can be found in the kinto/security repository.
Parts of this document were inspired by Yearn Finance security policy, Babylon Finance, as well as it is inspired by Grin's security policy.