Token Security Policy

To enhance token security, we introduce the following token security policies. This policy consists of a combination of Timelock and Multi-signature wallets to increase the safety of contracts and avoid single point failures in private key management.

1. Timelock

A time lock is applied by delaying sensitive tasks to allow them to wait for a specific time. For example, in order to execute the task of distributing the Pool token in a contract, a 48-hour wait period is required after requesting the task. This allows for a period of awareness and review of privileged tasks, and prevents inappropriate tasks from being automatically executed.

1. Multi Signature Wallet

The execution of the token distribution task was restricted by giving a privileged role to the designated signer (signer), not the owner. Token distribution consists of three stages: Propose, Approve, and Execute, and a specific number of signatures are required at each stage. For example, if the signature of ⅔, ⅗ is required, the token is distributed only when two or three signatories participate and approve the work. Through this, it is possible to prevent a single point failure due to private key leakage or hacking, and to strengthen security.

The token security policy applied in this way is taking appropriate measures to improve the safety of contracts and token security. The combination of time lock and multi-signature wallet delays the execution of sensitive tasks and minimizes security risks by preventing single point failures in private key management. In addition, a web page is provided through the link below to share information on multi-signature wallets and time lock contracts: [Links to share multi-signature wallets and time lock contract information] Our token security policy is designed to secure users' assets and strengthen trust with the community.