Katika sehemu hiiGetting Started
Security & Verification
Kwenye ukurasa huu
This page is an overview of the Inkryptus security posture. Detailed information lives in the dedicated pages linked below.
Security model
Inkryptus operates on three security layers:
| Layer | Summary | Details |
|---|---|---|
| Custodial infrastructure | Each user wallet is a contract on-chain. Moving funds out of one requires more than one signature under the platform multisig. | Wallet |
| Smart contracts | Built on OpenZeppelin standards, verified source code on BscScan. Hard cap enforced at contract level. | INKY Token Security, Contracts |
| Operational controls | Email-based 2FA, KYC-tiered withdrawal limits, transaction monitoring. | Wallet, Fees |
Audit status
No formal third-party audit has been performed. The current security baseline relies on OpenZeppelin standards, verified source code, automated scanner results (GoPlus, Token Sniffer), and a clean operational track record. Full scanner results are documented in INKY Token Security.
Incident history
Zero security incidents since platform launch (2020). No exploits, no contract pauses, no emergency actions, no fund losses.
Verify independently
- 1
Review source code
All contracts have verified source on BscScan. See Contracts for the full list.
- 2
Run automated scans
Run contract addresses through GoPlus or Token Sniffer.
- 3
Check on-chain state
Use BscScan's
Read Contracttab to verify supply cap, ownership, and minter whitelist.
Related pages
INKY Token Security
Scanner results, flagged items explained, verification steps.
Contracts
All contract addresses and roles.
Wallet
Custodial model, 2FA, withdrawal limits, account recovery.
Risks
Risk categories with mitigations.
What is a Smart Contract?
Learn how smart contracts work and why they matter for platform security.
Ilisasishwa mwisho