Security Model
CTpot is designed with security-first principles.
All critical logic is enforced on-chain by smart contracts, not by people, servers, or permissions.
Core Security Principles
CTpot follows these rules:
Code over trust
No custody
No manual control
Minimal permissions
Fully verifiable execution
If a rule is not in the contract, it does not exist.
Non-Custodial Design
Users interact directly with the smart contract
CTpot does not hold private keys
No team wallet controls user funds
All CHOGTARD used for tickets is controlled by the contract logic only.
No Admin Fund Access
There is no function that allows:
Withdrawing the prize pool
Redirecting funds
Draining balances
Interfering with payouts
Admins cannot touch user funds under any condition.
Immutable Ticket Logic
Ticket price is fixed: 10,000 CHOGTARD = 1 Ticket
Ticket ownership is recorded on-chain
Tickets cannot be edited, revoked, or transferred
Once a ticket is created, it is final.
Automated Execution
CTpot does not rely on:
Backend servers
Cron jobs
Manual draw calls
Human execution
All critical actions (draw + payout) are executed automatically by the contract.
Winner Selection Safety
Winner selection uses on-chain data
No external randomness providers
No manual overrides
No re-rolls
Results are deterministic, final, and verifiable.
Atomic Payouts
Winner selection and prize distribution occur in one execution flow
If any step fails, the entire transaction reverts
No partial states or stuck funds
This guarantees consistency and safety.
Common Protections
The smart contract includes:
Reentrancy protection
Strict input validation
Safe token transfers
Controlled execution paths
There are no hidden or unused functions.
What CTpot Does NOT Do
CTpot does not:
Store user data
Require KYC
Freeze wallets
Pause user withdrawals
Offer refunds
Participation is permissionless.
Known Risks
Despite security measures, risks still exist:
Smart contract bugs
Blockchain congestion
Wallet or user errors
Network-level issues
Users participate at their own risk.
User Responsibility
Users should:
Verify contract addresses
Use trusted wallets
Understand ticket pricing
Never interact with unofficial links
Security is shared between code and users.
Final Note
CTpot minimizes trust by removing it.
The protocol does not promise safety — it enforces rules transparently on-chain.
Last updated