# Security ## Team The Quint Ecosystem is developed and backed by a passionate group of people who want to erect a legacy that will reflect their accomplishments in Life. The Quint team is **doxxed**. ## Audit Security is our priority and no compromise has been done on that account. Team Quint would have completed all following security checks prior to the launch of its flagship token QUINT: 1. Blockchain Protocol Audit 2. BSC Smart Contract Audit 3. Formal Verification 4. Penetration Testing 5. Internal and External Penetration Testing 6. Vulnerability Assessment Services *Note: QUINT is currently being audited by **Techrate** and a second audit by **Certik** will also be completed before QUINT's launch.* ## Multi-sig Wallet The below mentioned Owner Wallets are being held by the Managing Partner and the CTO of QUINT. The Multi-sig Wallet structure was put in place for security reasons and has been publicly announced here in the whitepaper to completely mitigate any centralization-related risks. #### Wallet 1 0x4bD1064c42bf614bCA64A5b8E3DD1Cd3E4B6118c #### Wallet 2 0x7B515e1801B0CD43f29e2175dE02f93379243c78 ![](/files/ww8neQ8a56l5CwS0nGOO) ## Locker ### Token Locker As the price has moved significantly we have unanimously agreed to lock these tokens and increase vesting periods for their release. Private investors have also agreed to a vested release of funds. We will be locking these tokens via DxLock using the following schedule. {% embed url="" %} ### Liquidity Locker --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://whitepaper.quint.io/quint-whitepaper-1/roadmap-and-tokenomics/security.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.