crytic / crytic/blockchain-security-contacts
List is subject to single-point-of-failure.
- Dominant language
- No language data
- Stars
- 401
- Forks
- 181
- PR merge metrics
- No merged PRs in 30d
Description
Hey Dan
I'm so glad that this list is coming together so well. I'll add our address (which is currently security@z.cash) soon - but of course it's a single point of failure for all security contact information for the whole industry, so eventually I'd expect it's something better stored by individual projects within their own repos (of course github is still an SPOF but I don't have any clever answer for that).
How about something like this? https://github.com/RD-Crypto-Spec/Responsible-Disclosure
bambam
Contributor guide
Research direction
No files, tests, or implementation entry points are named. Start by reviewing the current blockchain-security-contacts repository and the linked Responsible-Disclosure project, then define a scoped approach for avoiding a single point of failure and a concrete completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100