Skip to content

Security: CodedBay/zenith-stellar

Security

SECURITY.md

Security Policy

Supported Versions

Currently, only the main branch of Zenith Protocol is supported with security updates.

Version Supported
1.0.x
< 1.0

Reporting a Vulnerability

If you discover a security vulnerability within Zenith Protocol, please do NOT open a public issue. Instead, visit github.com/CodedBay/zenith-stellar and use the security advisory feature, or email the core maintainers at security@zenith-protocol.dev.

We consider security our highest priority and will address all reports promptly.

Scope of Vulnerabilities

Critical vulnerabilities related to the following are eligible for immediate review:

  • Unauthorized fund withdrawal or access
  • Precision-loss or mathematical errors in proportional distribution
  • Re-entrancy or state manipulation attacks
  • Contract initialization or access control bypasses

Please include:

  • A detailed description of the vulnerability
  • Steps to reproduce the issue
  • Potential impact assessment
  • Suggested fixes (if applicable)

Security Best Practices

Smart Contract

  • 128-bit integer math prevents overflow and precision loss
  • Checks-Effects-Interactions pattern mitigates re-entrancy risks
  • Role-Based Access Control (RBAC) enforces authorization checks
  • State mutations occur before external calls

Deployment

  • Contracts are audited before mainnet deployment
  • All deployments use the Stellar CLI v26+
  • Network interactions are verified through Soroban RPC endpoints
  • Private keys are managed via secure Stellar identity configuration

Security Audit

Zenith Protocol has been designed with security-first principles. Community audits are welcomed and encouraged.

There aren't any published security advisories