# Slipvio · Whitepaper An AI consumer data network built on consumer contributions. 2026-09-28 ## Abstract Slipvio starts with receipts. It structures everyday purchase records voluntarily submitted by consumers and produces aggregated insights for authorized brands and analysts. The project connects consumers contributing data, organizations asking commercial questions, and operators maintaining extraction, validation and reward rules. The first release uses a browser DApp, wallet identity, AI receipt extraction and an offchain ledger. Eligible points redeem for a token airdrop from a fixed pool, allocated proportionally. The redemption framework is designed; actual issuance, appeals and onchain claims remain to be integrated. ## 01 / From fragmented records to shared value A merchant sees its own transactions; a consumer shops across brands, channels and categories. Slipvio tests the proposition that consumer-contributed receipts can complement a single-merchant view and help teams frame and investigate questions about category mix, spending and purchase frequency. This value depends on authentic contributions, sufficient valid samples and concrete buyer needs. Voluntary submissions introduce selection bias and do not automatically represent a population, region or market. Category proportions within the sample are not presented as market share. ## 02 / Product and participation Consumers sign in with an EVM wallet signature, with no gas required for sign-in. After acknowledging data use, they submit an image and track extraction. Validated records earn points under the campaign rules. Authorized business and research accounts view their permitted datasets. Operators review uncertain records, freeze campaigns and export contribution snapshots. All spending categories are welcome. The first release accepts JPG, PNG and WebP images of paper receipts or digital receipt screenshots. Open category coverage does not guarantee recognition of every language, layout or item. Unreliable fields remain unknown or are sent for review. ## 03 / How data moves Uploaded images pass format and size checks before entering private storage. Background jobs use DeepSeek to extract merchant, date, currency, amount and recognizable line items. Structured results pass field validation and basic duplicate checks before acceptance. Monetary totals are grouped by currency rather than added across currencies. Processing states are queued, processing, accepted, needs review, rejected and failed. Records awaiting review earn no immediate points. Users may correct details for operator approval; failed jobs support limited retries. Image hashes and purchase fields provide basic duplicate detection, not definitive proof of authenticity. ## 04 / The business intelligence layer The initial dashboard shows valid receipt counts, category coverage, category distribution and spending by currency. The database computes statistics; AI explains those aggregates and suggests questions for further validation. Ordinary business accounts cannot browse users’ original receipt images. Brand comparisons, time trends, category combinations, custom research and data APIs are potential extensions, subject to data coverage, authorization and customer demand. The current product does not claim complete competitor transaction data, real-time industry monitoring or attributable marketing outcomes. ## 05 / Contributions and incentives 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. 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. 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. 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. 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. 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. 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. 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. ## 06 / The role of Web3 Wallets provide reusable signature identities and may connect contribution records with future onchain eligibility. Storage, extraction and points settlement currently run on the server. Private receipts and purchase details are not written to a public chain, and the offchain database is not described as a decentralized consensus network. The proposed first points-redemption pool is 5% of token supply, allocated proportionally and fully unlocked at claim. Supply, ticker, issuance chain, remaining allocations and governance powers remain undecided. Before deployment, define permissions, complete review and publish verifiable addresses. Supported sign-in chains do not determine the issuance chain. ## 07 / Business model and ecosystem Potential revenue sources include authorized insight subscriptions, thematic research and custom analysis. Brands, consultancies, data companies and new market entrants are prospective users. Pricing and commercial arrangements require demand validation; unconfirmed customers, revenue or partnership scale are not reported. Consumers create data coverage, operators maintain rules and processing, and business users frame questions and evaluate insights. If recurring business develops, incentive budgets may be adjusted against revenue, operating costs and campaign results. No automatic buyback, dividend or revenue-sharing commitment is currently defined. ## 08 / Data boundaries and limitations Users should submit only receipts they are authorized to share and cover names, phone numbers, membership IDs and payment details before uploading. An external AI service processes images; absolute zero retention is not promised. Original-image access requires authorization, while business users access permitted aggregates. Retention periods, deletion-request channels and operator contact details must be defined before public collection. Extraction errors, duplicate submissions, incentive-driven low-quality samples and service interruptions may affect results. Limits, status tracking, manual review and audit ledgers reduce these effects without guaranteeing perfect recognition, fraud prevention or availability. Demonstration data is presented separately from real contributions. ## 09 / Delivery and current status The local build implements wallet sign-in, receipt uploads and queues, the extraction adapter, points ledger, aggregate insights and operational snapshots. Production use still requires live AI and storage credentials, real-receipt integration checks, hosting, domain configuration and launch verification. Local implementation is not a live public network. The roadmap runs from Q3 2026 through Q4 2027: foundations in Q3 2026, the genesis contribution season in Q4, first airdrop redemption targeted in Q1 2027, business validation in Q2, data-service productization in Q3, and ecosystem collaboration and annual review in Q4. Quarterly goals are plans, not completed results. Exact campaign and claim dates require formal notices. --- # Slipvio · Ecosystem A shared model around purchase records, with a clear role for every participant. 2026-09-28 ## Consumers / Contributors Submit receipts you are authorized to share, review uncertain details and collect contribution points. Track status and ledger entries in your workspace. Participation does not require buying tokens or transferring funds. ## Brands / Business teams Explore category composition and spending within an authorized dataset, using AI summaries to frame research questions. Cross-brand comparisons and finer analysis require sufficient coverage and dedicated products and remain future directions. ## Researchers / Data users Consultancies, data companies and new market entrants are prospective users. Future research may focus on defined categories, time windows and sample boundaries. There is currently no open data marketplace or self-service download of raw consumer records. ## Network operations / Data processing Operators maintain campaign parameters, review disputed records, handle duplicates and failures, and create settlement snapshots. AI and infrastructure providers are technical dependencies, not implied investors or ecosystem partners. ## Future builders / Integrators Research tools, authorized APIs and community campaigns are possible extensions. Developer APIs, third-party nodes and DAO voting are not currently available. Participants and integration arrangements will be announced once confirmed. --- # Slipvio · Points-to-airdrop redemption Season-one framework: a fixed pool allocated in proportion to final eligible points. 2026-09-28 ## 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. --- # Slipvio · Roadmap 2026 Q3 to 2027 Q4: product foundations, contribution redemption, business services and ecosystem collaboration. 2026-09-28 ## 2026 Q3 / Product & brand foundations Build the complete receipt-to-points journey. Complete the local English and Traditional Chinese website, whitepaper and DApp. Define the first redemption season and test wallet, extraction and points flows. ## 2026 Q4 / Genesis contribution season Open a 42-day contribution season and build usable samples. Deploy and verify real receipts; publish campaign dates and the fixed pool amount. Run business pilots, then review contributions and open the results-and-appeals period. ## 2027 Q1 / First airdrop redemption Convert eligible points into verifiable airdrop allocations. Finalize the snapshot and publish eligible totals, allocations and verification instructions. Open a 90-day claim window after token, contract review and pool funding are ready; review season-one data. ## 2027 Q2 / Validate business insights Use consumer data to address concrete business questions. Pilot category trends, brand comparisons and reports where coverage and authorization support them. Test willingness to pay and define the next campaign and budget from season-one findings. ## 2027 Q3 / Productize data services Turn validated analysis into repeatable services. Pilot insight subscriptions, custom research delivery and authorized API access. Improve organization permissions, statistical definitions, sample boundaries and retention controls. ## 2027 Q4 / Ecosystem collaboration & review Let demand and delivered results guide the next stage. Run research or contribution campaigns with confirmed partners and publish an annual product and data report. Review service costs, participation and revenue before publishing the next roadmap and incentive budget. ## Schedule and delivery boundaries These are planned targets, not claims that future features are live. Delays require reasons and revised dates; a launched campaign’s pool and scoring rules cannot be retroactively reduced. Campaign notices specify collection, snapshot and claim times in UTC. The Q4 season targets a collection close by the end of 2026 and first claims in Q1 2027. --- # Slipvio · Data use How receipts are processed and where access is limited. 2026-09-28 ## What you submit Submissions include receipt images and extracted merchant, date, items, amount and currency. A wallet address identifies the contribution account. Submit only receipts you may share and cover personal details and payment credentials first. The system does not read your wallet private key. ## Processing and purpose Images enter private object storage and are processed by DeepSeek for purchase extraction. Structured results support validation, points records and authorized aggregated insights. Business AI summaries use statistical aggregates. External services participate in processing, so data is not described as entirely local or subject to guaranteed zero retention. ## Who can access data Users view their own records. Authorized operators perform review and campaign management. Business accounts see aggregates for datasets granted to their organization. Original images require server-side authorization. There is no public trading or download of original receipts. ## User controls and launch requirements Users can correct records awaiting review. Self-service account and receipt deletion are not currently available. Before public collection, the operator must publish contact channels, retention periods, a deletion-request process and full policies. This page describes current product behavior, not an operating policy that has yet to be defined. --- # Slipvio · Project overview Slipvio’s positioning, product modules and brand resources. 2026-09-28 ## Positioning Slipvio is an AI consumer data network built from consumer contributions. Users upload receipts; the platform structures purchase data, records contribution points and provides aggregated insights to authorized business users. Brand promise: new value in every purchase. ## Product modules The website explains the project. The consumer DApp handles wallet sign-in, uploads and points. The business workspace provides authorized aggregates and AI summaries. Operations handles reviews, campaigns and snapshots. All four belong to one product and require no native app installation. ## Brand identity Always write the name as Slipvio. The symbol forms a T from stacked tally lines, representing accumulated consumer contributions. Forest green #173F35 anchors the identity, with ivory #F7F8F2 and lime #D5E88A. An SVG symbol is available in the resource center. ## Project disclosures The operating entity, public contacts, community accounts, commercial partners and funding details have not been supplied. Unconfirmed names, social links and endorsements are therefore not displayed. Ecosystem roles describe the product model, not signed organizations.