Points-to-airdrop redemption

01 / Points redeem for a token airdrop

Slipvio uses valid contribution points to allocate its first token airdrop. Accounts meeting the threshold and review requirements redeem a proportional share of the season pool. The proposed genesis pool is 5% of total token supply, fully unlocked at claim with no later vesting.

This is redemption design v1; claiming has not started. Total supply, ticker, chain and contract address remain to be set. The actual pool quantity must be published and fixed before the season opens. Claim contracts, eligibility lookup and appeals remain to be integrated; the calculator is not an allocated balance.

02 / Earning points

The first season lasts 42 complete UTC calendar days. Each validated receipt earns 100 PTS. An account may submit up to 10 receipts per day, earning at most 1,000 PTS daily or 42,000 PTS across the season. Daily limits reset at 00:00 UTC. Failed, rejected, duplicate and pending-review receipts earn no points. A receipt counts once.

No check-in, follow, referral or spending-amount bonuses apply in season one. All categories receive equal points. Points cannot be bought, transferred or merged across accounts. Corrections earn no extra credit; invalid credited records are reversed. Quotas follow submission dates, and delayed approvals belong to the original campaign.

03 / Redemption eligibility

Accounts qualify with at least 1,000 final eligible PTS (10 valid receipts), a signature-bound wallet and a passed contribution review. Each participant uses one contribution account; multiple wallets must not be used to resubmit receipts or fabricate purchases. A wallet signature proves address control, not unique personhood.

Points below the threshold remain in contribution history but are excluded from this season’s denominator and do not roll into later redemption seasons. Basic duplicate checks and manual review address anomalies. Disqualification requires an explainable reason and an opportunity to provide evidence during appeals. A shared network alone is not grounds for exclusion.

04 / Formula and worked example

Individual allocation = season pool × individual final eligible points ÷ total final eligible points across qualifying accounts. Allocation is rounded down to the token’s smallest unit; rounding dust follows the unclaimed-balance policy. Only qualifying, reviewed accounts enter the denominator. Each point has equal weight.

Illustrative example only: a pool of 1,000,000 tokens, 10,000,000 total eligible PTS and your 5,000 PTS yield a 0.05% share, or 500 tokens. These are not issued quantities or return promises. The ratio changes during collection and becomes fixed only with the final snapshot.

05 / From collection close to final snapshot

T is the collection deadline. From T to T+7 days, resolve remaining extraction, review and anomalous records. At T+7, publish individual preliminary points and eligibility and open a 7-day appeal window. From T+14, resolve appeals before freezing the final snapshot. Unresolved reviews delay freezing with revised dates announced; reviews are not silently skipped.

The snapshot records campaign, rule version, recipient address, eligible points and allocation. Retain review history and publish total eligible points, the funded pool and allocation verification summaries, not private receipt images. Eligibility lookup and appeals interfaces must be completed before launch; the current snapshot export is only the foundation.

06 / Claiming and unlock

First claims target Q1 2027 with a 90-day window. Eligible users connect the snapshot address, verify their allocation and claim through the distribution contract, fully unlocked in one claim. Sign-in requires no gas; onchain claiming may require network gas. No payment to the project or approval to spend existing tokens is required.

The engineering plan uses a fixed allocation list and Merkle-proof verification, with per-campaign and address replay prevention. Fund the full pool before opening claims. Do not arbitrarily replace the finalized list. Pauses are limited to announced incident handling and extend affected claim deadlines. This contract has not yet been developed, reviewed or deployed.

07 / Exceptions and unclaimed balances

After the claim window, unclaimed tokens and rounding dust return to a publicly disclosed future-contribution reserve, not as a top-up for existing claimants. Publish amounts and onchain records. If no accounts qualify, no division or allocation occurs; retain the entire pool and announce its future use.

After settlement, mark points as used for this allocation while preserving their ledger history. The same points cannot be redeemed again. Recipient addresses cannot change after the snapshot. Changes during appeals require the original address’s signature and review; verbal claims of lost keys cannot transfer an allocation. If token or contract readiness is delayed, retain the snapshot and announce a delay rather than showing a false claimable balance.

08 / Campaign publication checklist

Before opening, publish the actual pool amount and percentage, the 42-day UTC interval, 100 PTS scoring and 10-receipt daily limit, the 1,000 PTS threshold, anomaly review rules, appeal channels, snapshot schedule and token-and-claim readiness. Do not retroactively reduce a launched season’s pool or scoring. Later seasons use separate rule versions.