# Securities points

**3.1 No Rugpull Risk**

* Implementation:&#x20;
  * Token liquidity will be locked in a smart contract or with a third-party service (e.g., Unicrypt or Team Finance) to ensure liquidity cannot be drained.
  * Ownership renouncement mechanisms (if required) will be transparent and irreversible.
  * No code allowing direct access to user funds or draining contract balances.

**3.2 No Honeypots**

* Implementation:&#x20;
  * Smart contracts will have no restrictive mechanisms to prevent users from selling or transferring their tokens under any condition.
  * Transparent and well-audited code will ensure users can freely interact with the token as per standard ERC-20 specifications.

**3.3 No External Calls**

* Implementation:&#x20;
  * Token contracts will not rely on or make external calls to unknown or off-chain data sources, preventing unexpected behavior or exploits.
  * External dependency-free design, except for trusted libraries like OpenZeppelin.

**3.4 No Hidden Owners**

* Implementation:&#x20;
  * Ownership of the token contract will be fully transparent.
  * Multi-signature wallets will handle any critical administrative operations.
  * Contract ownership will be either renounced or placed in a DAO treasury after initial setup.

**3.5 No Mintable Tokens**

* Implementation:&#x20;
  * The token contract will not include minting functionality after the initial supply of 224 billion TCN is minted.
  * All tokens will be created at the time of contract deployment.

**3.6 No Reclaim Ownership**

* Implementation:&#x20;
  * Once ownership is renounced or transferred to the DAO treasury, no function will allow the original deployer or other parties to reclaim control of the contract.

**3.7 No Self-Destruct**

* Implementation:&#x20;
  * The token contract will exclude any selfdestruct functionality to prevent accidental or malicious contract termination.

**3.8 No Transfer Pausable**

* Implementation:&#x20;
  * The token contract will not include a pause function to prevent token transfers, ensuring continuous token operability.
