Skip to content

Security: GHX5T-SOL/IncryptOracle

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.0.x

Reporting a Vulnerability

🚨 Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them via email to: *incryptinvestments@protonmail.com

You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.

Please include the following information in your report:

  • Type of issue (e.g. smart contract vulnerability, frontend security issue, etc.)
  • Full paths of source file(s) related to the manifestation of the issue
  • The location of the affected source code (tag/branch/commit or direct URL)
  • Any special configuration required to reproduce the issue
  • Step-by-step instructions to reproduce the issue
  • Proof-of-concept or exploit code (if possible)
  • Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

Security Measures

Smart Contract Security

  • Security Review Status: Completed a free beta assessment with AI Smart Contract Auditor (November 2025). Preparing submission packages for third-party security firms such as CertiK or Halborn. No independent security firm has published an audit or endorsement yet.
  • OpenZeppelin: Using battle-tested OpenZeppelin libraries
  • Access Controls: Comprehensive permission system with role-based access
  • Reentrancy Protection: Guards against reentrancy attacks
  • Input Validation: Thorough validation of all user inputs
  • Emergency Controls: Pause mechanisms for emergency situations

Infrastructure Security

  • Private Key Management: Secure key storage and rotation procedures
  • Multi-signature: Critical operations require multiple signatures
  • Environment Isolation: Separate environments for development, testing, and production
  • Monitoring: 24/7 monitoring of contract interactions and anomalies
  • Rate Limiting: Protection against spam and abuse

Frontend Security

  • Content Security Policy: Strict CSP headers to prevent XSS
  • HTTPS Only: All communications encrypted in transit
  • Wallet Security: Best practices for wallet integration
  • Input Sanitization: All user inputs properly sanitized
  • Dependency Management: Regular updates and vulnerability scanning

Security Best Practices for Users

Wallet Security

  • Use a hardware wallet for large amounts
  • Never share your private keys or seed phrases
  • Verify all transaction details before signing
  • Use official wallet applications only

Smart Contract Interaction

  • Verify contract addresses before interacting
  • Check transaction details carefully
  • Start with small amounts when testing
  • Be aware of gas fees and market conditions

General Security

  • Keep your browser and wallet software updated
  • Be cautious of phishing attempts
  • Verify URLs before entering sensitive information
  • Use strong, unique passwords for accounts

Security Audit Reports

Current Security Review Status (November 2025)

  • Beta Assessment: Completed a free beta assessment with AI Smart Contract Auditor (Free Audit from beta project)
  • Assessment Date: November 2025
  • Status: Preparing submission packages for third-party security firms such as CertiK or Halborn
  • Third-Party Audits: No independent security firm has published an audit or endorsement yet

We are ready to submit the codebase for formal third-party audits, but Incrypt Oracle has not been audited or endorsed by CertiK, Halborn, or any other external firm yet.

Internal Security Measures

  • OpenZeppelin Libraries: All security-critical functionality uses battle-tested OpenZeppelin libraries
  • Comprehensive Testing: 121+ tests with 88%+ code coverage across all contracts
  • Formal Verification Ready: Core consensus and AMM functions isolated and verifiable
  • Fuzzing Ready: Contracts designed with property-based testing in mind
  • Gas Optimization: Efficient code reduces attack surface and deployment costs

Bug Bounty Program

We run a bug bounty program to encourage responsible disclosure of security vulnerabilities. Rewards are based on the severity and impact of the discovered vulnerability.

Rewards

  • Critical: $5,000 - $10,000
  • High: $2,000 - $5,000
  • Medium: $500 - $2,000
  • Low: $100 - $500

Scope

In scope:

  • Smart contracts deployed on BSC Mainnet
  • Frontend application (incryptoracle.com)
  • Oracle infrastructure and APIs

Out of scope:

  • Testnet contracts
  • Third-party integrations
  • Social engineering attacks

For more details, visit our Bug Bounty Program.

Contact

There aren't any published security advisories