sqdgn-migration-brief.md

The first public release of The Terminal will coincide with the start of SQDGN->DSQD token migration. Initially access to The Terminal will be based on this migration and not staking, which will be available only after the migration is finished.

Here's how the migration will look like:

1. We deploy all smart contracts, announce all the dates and details for the community. Migration is in "NotStarted" state.
2. We enable migration deposits. Users can deposit their old (SQDGN) tokens into the migration vault contract. This can be single or multiple deposits per single user. Migration is in "DepositOpen" state.
3. We disable migration deposits, user can no longer deposit SQDGN tokens. Migration is in "DepositClosed" state.
4. We migrate token supply by minting 1B (total supply of SQDGN) DSQD tokens. Migration Vault smart contract will receive 1 DSQD for every 1 SQDGN depositted into it by users. The difference between total supply and tokens migrated (1B - SQDGN balance of MigrationVault) will be sent to project's treasury.
5. We open claims. Users can claim their new (DSQD) tokens - 1:1 for each SQDGN they have deposited. Migration is in "ClaimOpen" state, it will be in this state for at least 6 months.
6. At some point we will finish the migration. Any unclaimed tokens will be either burnt or sent to a treasury. After this happens, claiming is not possible anymore.

During the migration, we will offer migration-based access to The Terminal with a discount. It's pretty simple - if you deposited enough tokens into the MigrationVault, you can mint an access pass. We will also offer 50% discount on all tiers. So for example if Krill tier normally requires 500k tokens, migrating 250k tokens is enough to get this pass. Each user will be able to have only single "migration pass". Those passes will also have 6 month expiration date. Idea is that we incentivize users to migrate tokens with the expiration and give them 6 months until they need to actually stake tokens and get access pass with the "intended" mechanism.

Having above in mind, we need to design UI to let users accomplish both of the steps above. Something very important to keep in mind - there may be some users who are SQDGN holders and will want to migrate their tokens, but are not terminal users. We need to accomodate both terminal and non-terminal users. There should be no roadblocks if you're just a holder and want only to migrate your tokens.

Otherwise the migration UI should tell the user what the status is, what the expected timeline will look like etc. Basically anything you would expect on token migration.