Skip to content

Security: jiayaoqijia/eth2030

SECURITY.md

Security Policy

Supported Versions

Please see Releases. We recommend using the most recently released version.

Version Supported
Latest Yes
Older No

Reporting a Vulnerability

Please do not file a public issue for security vulnerabilities.

To report a vulnerability, email security@altresear.ch with:

  • Description of the vulnerability
  • Steps to reproduce
  • Affected package(s) and version
  • Potential impact assessment

Response Timeline

Stage Timeline
Acknowledgment Within 48 hours
Initial assessment Within 1 week
Fix development Depends on severity
Public disclosure After fix is released

Scope

In Scope

  • EVM interpreter vulnerabilities (core/vm/)
  • State transition bugs (core/, geth/)
  • Cryptographic implementation issues (crypto/, crypto/pqc/)
  • Consensus logic errors (consensus/)
  • P2P protocol vulnerabilities (p2p/)
  • Engine API security issues (engine/)
  • Transaction pool manipulation (txpool/)

Out of Scope

  • Issues in reference submodules (refs/) — report these to their upstream projects
  • Issues requiring physical access to the machine
  • Social engineering attacks
  • Denial of service through expected resource usage

Responsible Disclosure

We ask that you:

  1. Give us reasonable time to fix the issue before public disclosure
  2. Make a good faith effort to avoid data destruction and service disruption
  3. Do not access or modify data belonging to others
  4. Act in good faith to avoid degrading our services

We commit to:

  1. Acknowledging your report promptly
  2. Keeping you informed of our progress
  3. Crediting you (if desired) when we publish the fix
  4. Not pursuing legal action against good-faith security researchers

There aren’t any published security advisories