DEEPSPACE Whitepaper
Search…
⌃K
Links

Token

Security is a top concern in DEEPSPACE. Below you will find information on how DPS is protected.
Within this section you will find information on
  • Multi-Sig Wallet protections
  • Liquidity

Multi-Sig Wallet

The DPS Contract is owned by a Multi-Sig vault 0xaCc34268f5D7Cb9B11BfB1ba4D8bD2bc2B49EE4E which is in turn owned by 6 custodian wallets controlled by 6 members of the DEEPSPACE core team.
4 approvals are required for every transaction initiated by this wallet. This means that no one can perform ownership function calls of the token without 4 core team members agreeing to and approving of the transaction. In addition to contract ownership, the majority of company owned tokens and other funds such as BNB, BUSD used for payments, as well as ChainLink or other investments are also protected by this umbrella of protection.
No actions can be taken on any of this without 4 unique approvals by 4 unique custodians from the core team.
What Are Multi-Signature Wallets?
MUO
Additional reading about Multi-Sig Wallets

Liquidity

Liquidity, while not locked in a traditional manner, is also protected by the Multi-Sig wallet described above. This means that no single person controls the liquidity pool and any actions must be approved by 4 or 6 core team members.

Why Liquidity is not Locked

There are a number of reasons not to lock liquidity. To start, this is a long term project. Liquidity cannot be locked forever. Common locking periods are 3, 6, or 12 months, and will always unlock at some point, at which time any action can be taken against it. Rather than locking liquidity, it is locked behind out multi-sig wallet.
Not locking allows a number of benefits
  • Easy migration of Liquidity to a new Liquidity provider, should we ever need to move away from Pancakeswap.
  • Ability to migrate Liquidity to a new version of Pancakeswap, should they roll out a v3.
  • If desired, we would be able to migrate Liquidity to another base token, for example migration to BUSD instead of BNB.
  • In the extremely unlikely event that a security event were to happen, or a need to migrate to a new token contract ever came up, we would be able to address it much faster and with less holder impact than needing to rely on something like a token swap processes