Announcement center
Bitget Launchpad Deposit Rules
Bitget
2023-04-07 06:54
Global Bitgetters,
Users participating in Bitget Launchpad promotions can calculate the number of tickets and tokens to be allocated according to the following formula:
Allocated tickets = your net deposit / net deposit of all users * total promotion tickets.
Allocated tokens = allocated tickets * tokens per ticket.
The number of allocated tickets is always rounded down. If a user would be allocated 1.9 tickets, they are allocated 1 ticket. If a user would be allocated 0.5 tickets, they are allocated 0 tickets.
Users cannot be allocated more tickets than the individual cap.
For example:
Suppose the total number of tokens sold in a Launchpad promotion is 1,000,000 XYZ, and the prize pool consists of 20 tickets. This means that each ticket represents 50,000 XYZ tokens. Suppose that a total of 7 users participate in a deposit promotion. User A deposits 10,000 USDT worth of crypto, while the other 6 users deposit 30,000 USDT worth of crypto. User A is expected to be allocated 10,000 USDT / 40,000 USDT * 20 tickets = 5 tickets (5 * 50,000 XYZ = 250,000 XYZ).
The allocation of tickets and tokens is outlined below (table 1).
| User | Net Deposit (USDT) | Deposit Percentage | Tickets Allocated | XYZ Tokens Allocated |
| User A | 10,000 | 25% | 5 | 250,000 |
| User B | 9,000 | 22.50% | 4 | 200,000 |
| User C | 8,000 | 20% | 4 | 200,000 |
| User D | 5,000 | 12.50% | 2 | 100,000 |
| User E | 4,000 | 10% | 2 | 100,000 |
| User F | 2,000 | 5% | 1 | 50,000 |
| User G | 2,000 | 5% | 1 | 50,000 |
| Invalid Ticket(s) | - | - | 1 | 50,000 |
| Total | 40,000 | 100% | 20 | 1,000,000 |
Q: Why is there an invalid ticket?
A: The number of allocated tickets is always rounded down.
The number of allocated tickets is always rounded down. If a user would be allocated 1.9 tickets, they are allocated 1 ticket. If a user would be allocated 0.5 tickets, they are allocated 0 tickets.
Individual cap
To manage risk, Bitget sets an individual cap for Launchpad promotions. When users exceed the cap, their excess tokens will be redistributed to other users who have not yet reached their cap.
Using the XYZ project above as an example (table 1), if the individual cap of the project is 4, and user A has reached this cap, then the excess will be subtracted from the original number of tokens and reallocated. The excess tokens can be seen in Table 2.
Tickets and tokens are reallocated after adjustment based on the individual cap rule (table 2).
| User | Net Deposit (USDT) | Deposit Percentage | Tickets Allocated (after individual cap) | XYZ Tokens Allocated(after individual cap) |
| User A | 10,000 | 25% | 4 | 200,000 |
| User B | 9,000 | 22.50% | 4 | 200,000 |
| User C | 8,000 | 20% | 4 | 200,000 |
| User D | 5,000 | 12.50% | 2 | 100,000 |
| User E | 4,000 | 10% | 2 | 100,000 |
| User F | 2,000 | 5% | 1 | 50,000 |
| User G | 2,000 | 5% | 1 | 50,000 |
| Excess | - | - | 1 | 50,000 |
| Invalid Ticket(s) | - | - | 1 | 50,000 |
| Total | 40,000 | 100% | 20 | 1,000,000 |
In Table 2, the excess tokens of user A are 50,000 XYZ. These tokens will be reallocated based on the percentage of investment from other users who have not reached their individual cap.
Tickets and tokens are reallocated as follows (table 3).
| User | Net Deposit (USDT) | Deposit Percentage | Tickets Allocated (final) | XYZ Tokens Allocated(final) |
| User A | 10,000 | 25% | 4 | 200,000 |
| User B | 9,000 | 22.50% | 4 | 200,000 |
| User C | 8,000 | 20% | 4 | 200,000 |
| User D | 5,000 | 12.50% | 3 | 150,000 |
| User E | 4,000 | 10% | 2 | 100,000 |
| User F | 2,000 | 5% | 1 | 50,000 |
| User G | 2,000 | 5% | 1 | 50,000 |
| Invalid Ticket(s) | - | - | 1 | 50,000 |
| Total | 40,000 | 100% | 20 | 1,000,000 |
Taking user D as an example (compare table 1 and table 3), 2 tickets and 100,000 XYZ tokens would be issued if there was no individual cap. With the individual cap, user D is issued 3 tickets and 150,000 XYZ tokens instead.