This document describes the Security Process for Obol Network, including vulnerability disclosures and its 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.
To submit a finding, please follow the steps outlined in receiving disclosures section.
Obol 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 Obol'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.
Obol 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.
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, Obol has the following main points of contact:
| Contact | Public key | Keybase | |
|---|---|---|---|
| obol security | PGP | security at obol.tech | |
| eth2devops | PGP | eth2devops at obol.tech | @eth2devops |
Include all contacts in your communication, PGP encrypted to all parties.
You can also reach out informally over keybase encrypted chat to one or more of the contacts as per the details above.
In the case where we become aware of security issues affecting other projects that has never affected Obol, 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 Obol 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.
Obol does not currently have any established bilateral disclosure agreements.
Obol's bug bounty policy is published here
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 Obol, 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 the Obol project including disclosures, signatures and PGP public keys can be found in the obol-security repository.
Parts of this document were inspired by Grin's security policy.