Dear Webseans,
Thank you for your continued support and trust. Based on a comprehensive evaluation of user feedback and system performance data, Websea has completed a strategic restructuring of its Futures Insurance system. We are pleased to announce the official launch of the Dual Insurance Pools—Insurance Alpha (α) Pool and Insurance Beta (β) Pool (hereinafter referred to as the “α Pool / β Pool”). This upgrade introduces refined adjustments and a systematic re-engineering of airdrop allocation, claim cadence, and operational logic across the Futures Insurance framework, further reinforcing its underlying mechanism for long-term stability and sustainable operation.
I. Dual Insurance Pool Mechanism Rules and Description
The α Pool and β Pool are Futures Insurance pools built on distinct structural mechanisms. The α Pool retains the original Futures Insurance operating logic. Users may select one pool to participate in based on their individual preferences and risk management needs.
(I) Core Rules of the Dual Insurance Pools
| Dual Pool / Rules | α Pool (Alpha) | β Pool (Beta) |
| Node Generation | 1 insurance node is generated for every 100 USDT of accumulated insured amount | 1 insurance node is generated for every 100 USDT of accumulated insured amount |
| Airdrop Entitlement per Node | Each node is entitled to a 100 USDT airdrop | Each node is entitled to a 70 USDT airdrop |
| Airdrop Rounds | Fixed at 15 rounds (members may reduce by 1 round | Tiered structure: minimum 9 founds maximum 15 rounds |
| Airdrop Round Reset Mechanism | Fixed rounds reset mechanism | Tiered reset mechanism (adjusts dynamically with valid node counts) |
| Insurance Fee Rate | Tiered fee rate model, current range 10%–30% | Tiered fee rate model, current range 10%–20% |
| Referral Fee Reduction | 1% per referral, up to 5% in total; minimum reducible rate 10% | 0.5% per referral, up to 2.5% in total; minimum reducible rate 10% |
| Membership Benefits | Supported | Not supported |
| Simultaneous Activation | Cannot be enabled simultaneously with the β Pool | Cannot be enabled simultaneously with the α Pool |
*The minimum attainable insurance fee rates are subject to the values displayed on the user interface.
(II) Participation Rules
- Exclusive Pool Participation: Users may participate in only one insurance pool at any given time. The α Pool and β Pool cannot be activated simultaneously, ensuring that duplicate coverage does not occur.
- Unified Insurance Account Balance: The insurance account balance can be used interchangeably to participate in either the α Pool or the β Pool.
- Unified Referral Boost Rules: When User A successfully invites a new user, User B, the referral relationship will be recorded simultaneously for both the α Pool and the β Pool. User B will receive one β Pool reward node and may independently complete fee-reduction boost tasks for the α Pool and/or the β Pool.
Examples:
If User B completes the α Pool boost task, User A’s α Pool insurance fee rate will be reduced accordingly.
If User B completes the β Pool boost task, User A’s β Pool insurance fee rate will be reduced accordingly.
If User B completes boost tasks for both pools, User A’s insurance fee rates for both the α Pool and the β Pool will be reduced.
II. Beta (β) Pool Tiered Airdrop Round Reset Mechanism
With this upgrade, the β Pool introduces a Tiered Airdrop Round Reset Mechanism. Users’ airdrop claim rounds will be dynamically tiered and adjusted based on valid node counts, as determined through a system snapshot mechanism.
(I) Snapshot and Round Confirmation Rules
To ensure that airdrop claim rounds accurately reflect each user’s actual scale of insurance node participation, the system employs a dual snapshot mechanism to calculate valid node counts and determine the corresponding airdrop claim rounds.
1. Snapshot Rules
The system supports two snapshot trigger methods:
(1) Daily Fixed Snapshot
- A unified snapshot will be taken daily at 16:00 (UTC) for all β Pool users.
- The snapshot records each user’s valid node counts for that day.
- Valid nodes include: Queued Nodes, Active Nodes, and Frozen Nodes.
(2) Immediate Snapshot After Airdrop Claim Round Completion
- When a user completes all airdrop claims for the current round, the system will immediately trigger an instant snapshot.
- This snapshot is also calculated based on the user’s current valid nodes.
Round Confirmation Rules:
- Each snapshot result is used to confirm the user’s current or next corresponding airdrop claim round.
- The system updates a user’s airdrop claim round only after a new snapshot has been triggered, based on the latest valid nodes.
Valid Nodes and Airdrop Round Mapping
| Valid Nodes at Snapshot | Corresponding Airdrop Claim Round |
| [0,5] | 9 |
| (5,10] | 10 |
| (10,25] | 11 |
| (25,50] | 12 |
| (50,100] | 13 |
| (100,300] | 14 |
| (300,∞] | 15 |
β Pool Insurance Fee Rates and Activation & Unfreeze Ratio
| Cummulative Nodes | Insurance Fee Rates | Activation & Unfreeze Ratio |
| [0,100] | 10% | 1% |
| (100,165] | 11% | 1% |
| (165,270] | 12% | 1% |
| (270,450] | 14% | 1% |
| (450,930] | 16% | 1% |
| (930,1300] | 18% | 1% |
| (1300,∞] | 20% | 1% |
(II) Tiered Round Adjustment Rules
1. Tier Upgrade Rules
When a user’s valid nodes increases and qualifies for a higher tier:
- The user’s airdrop claim round will be updated after the next scheduled snapshot at 16:00 (UTC).
- From the effective snapshot onward, airdrops will be executed under the new, higher-tier round.
Special Notes:
If the user has already completed all airdrop claims for the current round on the same day, the system will immediately trigger a snapshot:
- If the snapshot results in a tier upgrade, the next airdrop will follow the higher-tier round until the next scheduled snapshot at 16:00 (UTC), after which it will be updated based on the latest snapshot result.
- If the snapshot results in no tier change, the current round will remain in effect until the next scheduled snapshot at 16:00 (UTC), after which it will be updated based on the latest snapshot result.
- If the snapshot results in a tier downgrade, the next airdrop will follow the lower-tier round until the next scheduled snapshot at 16:00 (UTC), after which it will be updated based on the latest snapshot result.
2. Tier Downgrade Rules
When a user’s valid nodes decreases and results in a lower tier:
- The user must first complete one full airdrop claim round under the current tier.
- Upon completion, the system will immediately trigger a snapshot and update the airdrop claim round based on latest valid nodes, which remains effective until the next scheduled snapshot at 16:00 (UTC).
Special Notes:
- If the current round has not been completed, the airdrop tier will remain unchanged.
- The airdrop claim round will be updated only after the original round is completed and a new snapshot is triggered.
Examples:
Assume that User A’s airdrop claim is Round 11 following the snapshot at 16:00 (UTC) on February 6th.
Scenario 1: Current Round Completed
- User A completes all airdrop claims for Round 11 on the same day.
- The system immediately triggers a new snapshot, and the updated round is Round 10.
- The next airdrop claim will be executed under Round 10 until the next scheduled snapshot at 16:00 (UTC), after which it will be updated based on the latest snapshot result.
Scenario 2: Current Round Not Completed
- User A does not complete airdrop claims for Round 11 on that day.
- After the system snapshot at 16:00 (UTC+8) on February 7th, the corresponding round is Round 10.
- However, since Round 11 has not yet been completed, the airdrop claim round remains at Round 11.
- Once User A completes Round 11, the system will trigger a new snapshot and update the airdrop claim round based on the current valid node counts until the next scheduled snapshot at 16:00 (UTC), after which it will be updated based on the latest snapshot result.
Should you have any questions regarding this update, please reach out to Websea Customer Support through official channels.
Thank you for your understanding and continued support.
Websea Team
February 4, 2026
Comments
0 comments
Please sign in to leave a comment.