Security and verification
Security
CRNC is designed around minimal contract logic, immutable deployment, fixed supply, public verification, and reduced control surface.
HackenProof Security Review
CRNC completed a security review through HackenProof, where independent security researchers were incentivized to identify potential issues in the contract design.
The review classified findings as low or informational. No critical or high-severity vulnerabilities were identified.
The CRNC token contract remains intentionally minimal and non-upgradeable. No minting, burning, pausing, blacklist, governance, proxy, or administrative control mechanisms exist in the deployed token contract.
Security Model
CRNC reduces security risk by reducing complexity. The token is a fixed-supply ERC-20 asset deployed on Ethereum Layer 1 with no ongoing administrative authority.
- Fixed supply: 21,000,000 CRNC
- No mint function
- No burn function
- No owner-controlled token logic
- No upgradeability or proxy pattern
- No pause, blacklist, tax, fee, or transfer restriction logic
- No governance or parameter adjustment mechanism
The security approach is based on constraint and finality: fewer mechanisms, fewer permissions, and fewer paths for unexpected behavior.
Contract Verification
The CRNC token contract is deployed on Ethereum mainnet and can be independently reviewed through public blockchain infrastructure.
- Etherscan: verified token contract
- Github: source contract code
- Uniswap: CRNC market and liquidity
External Security Tools
CRNC can also be reviewed through automated blockchain security scanners and monitoring tools. These tools do not replace independent due diligence, but they provide useful public references.
- CertiK Skynet: CRNC project profile and monitoring
- GoPlus Token Security: CRNC risk analysis
- TokenSniffer: CRNC token structure analysis
Bug Bounty Status
CRNC does not currently maintain an ongoing public bug bounty program.
The HackenProof review functioned as a time-bound security review and bounty-style process. Following that review, the contract remains intentionally minimal, immutable, and without administrative control surfaces.
Responsible Disclosure
Responsible disclosure of critical issues is encouraged.
Security reports may be submitted by contacting: [email protected]
Please include enough information to reproduce and understand the issue, including affected contract addresses, transaction references, proof of concept details, and potential impact.
