Created by: Simon Kapenda, Creator of $ENGLISH
- All smart contracts located in
contracts/are actively maintained and audited. - Always use the latest release from the GitHub repository.
If you discover a security vulnerability or exploit in $ENGLISH smart contracts, DAO, or associated platforms, please do not create a public issue.
Instead, report it directly via email to:
Include:
- Detailed description of the vulnerability
- Steps to reproduce the issue
- Potential impact
- Suggested mitigation (optional)
- The security team will acknowledge receipt within 24 hours.
- We will assess and prioritize the report based on severity.
- Contributors who responsibly disclose verified vulnerabilities may receive recognition in the project’s community updates.
- Review smart contract code for known vulnerabilities (reentrancy, overflow/underflow, improper access control).
- Ensure all tests pass before submitting a pull request.
- Do not include private keys, API keys, or sensitive credentials in the repository.
- Follow OpenZeppelin and Ethereum/BNB Smart Chain best practices.
While $ENGLISH employs rigorous testing and third-party audits, cryptocurrency projects are inherently risky. Users participate at their own risk and are responsible for securing their wallets and private keys.
Best regards,
Simon Kapenda
Creator, $ENGLISH