Smart-contract security
Quick answer
Each collection contract is ERC-721A with OpenZeppelin Ownable, Pausable and ReentrancyGuard, hardcoded fee caps, and per-phase and global wallet limits enforced on every mint.
The most useful security property of an Elevate contract is that it is small, standard and inspectable. This page lists what it enforces and how to check a deployment.
Who this is for
Developers and collectors verifying a collection contract.
What the contract enforces
- Phase timing, supply caps and per-wallet limits on every mint.
- Exact payment: price × quantity, or the transaction reverts.
- Allowlist signatures from the phase's configured signer.
- Transfer lock until the owner unlocks.
- The marketplace fee cap, fixed at deployment.
What the owner can and cannot do
| Can | Cannot |
|---|---|
| Pause and unpause minting | Mint outside the phase rules |
| Configure phases before they start | Change a phase after it has started |
| Update fees within the hardcoded cap | Raise the cap |
| Unlock transfers | Re-lock after unlocking, or seize tokens |
| Reveal and freeze metadata | Change metadata after a freeze |
Verifying a deployment
- 1Copy the contract address from the collection page.
- 2Open it on Taostats EVM Explorer and confirm chain ID 964.
- 3Check the contract name matches the collection.
- 4Compare the token count with the collection page.
Sources
Written and maintained by the Elevate team. Last updated . Corrections: reach the team on the official Discord.
Related
- Security documentationThe technical controls in the contracts and the platform, and what the owner can and cannot do.
- The Elevate collection contractOne ERC-721A contract per collection, with phases, royalties, transfer lock and reveal built in.
- Security and contract verificationHow contracts are reviewed, audits, user safety.
Ready to mint? View verified Bittensor NFT collections.