Skip to main content

Swash

Swash (SWASH) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Swash — an AI/Data / Data ownership project (Data Union / data economy): an app/extension that offers users to earn for online activity and participation in tasks, and offers businesses/developers access to data/analytics and computations. In the whitepaper, Swash describes privacy‑preserving data collection and sale, fair revenue sharing, and products such as sIntelligence/sCompute. The SWASH token is an ERC‑20 on Ethereum; the CoinMarketCap profile also claims a cross‑chain role (Ethereum/Gnosis/Polygon), but in this card we record the onchain SSOT per Etherscan.

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: an “earn for being you online” service + infrastructure for data collection/aggregation and analytics.
  • Who it’s for: ordinary users (earnings/donations), businesses (advertising/analytics), data scientists/developers (models/computations).
  • Why onchain/token: the SWASH token is used as utility/incentives and for revenue distribution; onchain is needed primarily as a settlement and accounting layer (per the whitepaper).

How it works (very briefly)

  1. The user does: installs the extension/app, completes tasks, “is online”.
  2. The system does: collects and aggregates data into privacy‑preserving models, forms products/analytics/datasets (per the whitepaper).
  3. The user gets: points/rewards and can withdraw them, including in crypto (website), and/or participate in revenue sharing (whitepaper).
  4. Where the blockchain is: the SWASH token (ERC‑20) and smart contracts for accounting of activities/access/revenue distribution (whitepaper: “Swash Smart Contracts”, sVault, revenue distribution).
  5. Token role: incentives and a settlement token for transactions/marketplaces/services, and governance (whitepaper + CMC “About”).

Quick links: AI thesis fit

Project passport

Field Value
Project name Swash
Also known as (aliases) SWASH, Swashapp, Swash Data Union
Logo (logo) ../assets/229_swash_logo.svg
Token symbol (ticker) SWASH
Category AI/Data | Data Union
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2021 (whitepaper July 2021)
Project status (status) active
Token (standard) ERC-20
Token contract 0xa130e3a33a4d84b04c3918c4e5762223ae252f80
Token model (token_type) utility (governance)
Max supply ~994,960,022.359361512 SWASH (Etherscan)
Issuance fixed supply (whitepaper: total supply 1B; max total supply on Etherscan ~994.96M)
Tokenomics (tokenomics, brief) the token is used for incentives, transactions in the ecosystem and governance (whitepaper)
Governance DAO (SwashDAO — whitepaper)
Admins/keys —
Audit —
Bug bounty —
Team (team) Swash Data Tech (GitHub verified organization)
Funding (investors/funding) —
AI component (ai_component) data/compute for AI/ML models
Use‑case (use_case) data monetization + analytics/compute
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 2 / 3 / 3
Last verified 2026-02-11

General project overview

Swash positions itself as “Reimagining Data Ownership”: a set of products and tools where users can receive rewards for data and activity, and businesses and developers can buy/use data and analytics results.

At the consumer product level, this is an “online earning portal” (an app and a Chrome extension) where one can receive rewards and withdraw them as cash/gift cards/crypto. At the infrastructure level, the whitepaper describes data collection and aggregation, analytics products (sIntelligence), a compute environment (sCompute) and a mechanism for fair revenue distribution via smart contracts.

Features/modules

  • Swash app/extension: earning for online activity and tasks (website).
  • Data Union / data economy: a collective model of data governance and revenue distribution (whitepaper).
  • sIntelligence: a business analytics platform on Swash data (whitepaper).
  • sCompute: computations on data without transferring/selling the raw dataset (whitepaper; AI/ML context).
  • SWASH token: incentives + transactions + governance (whitepaper/CMC).

Typical scenarios

  • Scenario 1 (user): installs the extension/app → completes tasks → withdraws rewards (website).
  • Scenario 2 (business): buys access to analytics/data via platforms/marketplaces → receives insights (whitepaper).
  • Scenario 3 (data scientist): runs computations/models on Swash data via sCompute → receives results without moving the dataset (whitepaper).

Getting started (wallet/network)

  • What you need: install the app/extension (website).
  • Network/chain: Ethereum (SWASH ERC‑20); other networks are also mentioned in the ecosystem (whitepaper/CMC).
  • Fees: Ethereum fees for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: sCollector (collection), Data Fabric, the query/marketplace layer, sIntelligence, sCompute; smart contracts for access control and revenue distribution; sVault for receiving revenue and redistribution (whitepaper).
  • Participant roles: sMember (data provider), sCustomer (buyer), sApps developers/data scientists, governance participants.
  • Where logic runs: collection/analytics — offchain infrastructure; settlement/accounting/distribution — via smart contracts (whitepaper) and the token (Ethereum).
  • Dependencies: Ethereum + sidechain/sChain (described in the whitepaper as a custom side chain for recording activities and distributing revenue).

Token/economics (expanded, no forecasts)

  • Token utility: SWASH is used for incentives, transactions “in marketplaces/platforms/apps” and governance (whitepaper; CMC “About”).
  • Protocol necessity drivers: in Swash’s design, the token is the single settlement and distribution mechanism between ecosystem participants.
  • Who pays fees: users/buyers for onchain operations; some processes may be offchain (not disclosed).
  • Where fees go: revenue flows into sVault and is redistributed via smart contracts (whitepaper, revenue distribution sections).
  • Issuance/burn: fixed supply; the whitepaper says “total supply 1B”, but the actual max total supply per Etherscan is ~994.96M.
  • Security/incentive mechanisms: reward mechanics for participation (whitepaper + website).
  • Distribution and token issuance schedule: — (the exact distribution/vesting was not extracted from the whitepaper within this card).
  • Treasury: the SwashDAO fund is mentioned in CMC “About” (funding decisions); treasury details are not disclosed.

Governance

  • Who makes decisions: token holders / SwashDAO (whitepaper/CMC).
  • How protocol parameters change: via the DAO’s governance mechanics (process details not confirmed).
  • Where decisions are discussed/made: community channels + Medium/blog (links_* in this card).
  • Keys/multisig: —.

Security and incidents

  • Audits: no Tier‑1 report was found; CMC provides a link via a Certik Skynet redirect (the original source of the report is needed).
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: user data privacy, correctness of revenue sharing, risks of centralized collection/processing, the token’s smart contract risks.

Project status and timeline

  • Current status: an active consumer product (website) + repositories (GitHub).
  • Key releases/milestones: whitepaper July 2021, update August 2023 (PDF).
  • Roadmap: https://medium.com/swashapp/the-swash-roadmap-paving-the-way-towards-the-future-of-data-a8f6384a1990

Ecosystem/integrations

  • Integrations: browser/mobile clients (website); extension/token repositories (GitHub); a mention of cross‑chain utility (CMC “About”).
  • Partners: —.
  • Where it’s actually used: a consumer earn portal + ecosystem products (positioning, without public KPIs).

AI component of the project

  • What is real AI here? Swash positions data and computations as a foundation for AI/ML (whitepaper: data access for data scientists; “AI models become more accurate” + sCompute for running algorithms on data).
  • What is truly onchain? the SWASH ERC‑20 token (Etherscan) and the claimed smart contracts for access control and revenue distribution (whitepaper).
  • Why is a token needed? incentives for participants, settlements in marketplaces/services, and governance (whitepaper + CMC).
  • Red flags (based on the information found): AI‑washing (the focus is more on the data economy than on verifiable models), a complex hybrid architecture (a lot of offchain), unclear audits (a Tier‑1 report is needed).

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity medium 2
Token necessity medium 3
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 2.
  • Conflict note (if any): none.

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the platform provides data and an environment (sCompute) for running algorithms/models (AI/ML) on data without transferring it.
  • Evidence: Tier‑1 — https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf
  • Why sufficient / why not (one line): the functionality is described as a compute environment for data scientists.
  • Conflict note (if any): specific AI models/results are not provided.

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no Tier‑1 demo/case of an AI model or a reproducible example of sCompute results was found.
  • Evidence: Tier‑1 — https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf
  • Why sufficient / why not (one line): the whitepaper provides a description but does not publish a verifiable demo.
  • Conflict note (if any): none.

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf
  • Why sufficient / why not (one line): quality metrics of AI models/datasets are not published.
  • Conflict note (if any): none.

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): the whitepaper describes in detail the data architecture (Data Fabric), sCompute and participant roles.
  • Evidence: Tier‑1 — https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf
  • Why sufficient / why not (one line): sufficient for a high‑level understanding of the tech stack.
  • Conflict note (if any): none.

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Ethereum mainnet (the SWASH ERC‑20 token)
  • Addresses/identifiers: SWASH: 0xa130e3a33a4d84b04c3918c4e5762223ae252f80
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa130e3a33a4d84b04c3918c4e5762223ae252f80
  • Why sufficient / why not (one line): the explorer confirms the contract and max total supply.
  • Conflict note (if any): the whitepaper says “1B”, Etherscan shows ~994.96M.

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: the whitepaper describes sChain/sVault/access control and revenue distribution, but this card has no onchain addresses of these contracts (other than the ERC‑20).
  • Evidence: Tier‑1 — https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf
  • Why sufficient / why not (one line): without addresses, the “beyond just a token” implementation cannot be verified.
  • Conflict note (if any): none.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain (in the claimed design), transparent accounting of activities/access rights and automatic revenue distribution by smart contract rules break down.
  • Evidence: Tier‑1 — https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf
  • Why sufficient / why not (one line): revenue sharing and data access control are explicitly designed as onchain mechanisms.
  • Conflict note (if any): some functions can be implemented in a centralized way, but that changes the trust model.

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, SWASH.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa130e3a33a4d84b04c3918c4e5762223ae252f80
  • Why sufficient / why not (one line): confirmed by Etherscan.
  • Conflict note (if any): none.

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): SWASH is used for transactions in the ecosystem’s marketplaces/platforms/apps (buying data/computations/paying participants).
  • Evidence: Tier‑1 — https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf
  • Why sufficient / why not (one line): the whitepaper directly describes SWASH as a token for transactions.
  • Conflict note (if any): specific operating payment flows/contracts are not provided.

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): participants (sMembers/sUsers) are rewarded with the token for data contribution/activity.
  • Evidence: Tier‑1 — https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf ; https://swashapp.io/
  • Why sufficient / why not (one line): token incentives are described in the whitepaper and confirmed by the consumer product.
  • Conflict note (if any): none.

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the token is used for SwashDAO votes and decisions (including on funding projects/the roadmap).
  • Evidence: Tier‑1 — https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf
  • Why sufficient / why not (one line): the whitepaper describes SwashDAO and the governance context; onchain voting contracts require separate verification.
  • Conflict note (if any): no link to snapshot/voting contracts.

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the token is built into the ecosystem economy as a settlement asset and governance mechanism.
  • Evidence: Tier‑1 — https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf
  • Why sufficient / why not (one line): the design relies on tokenized incentives and revenue distribution.
  • Conflict note (if any): none.

Evidence (table)

Tier Source What it proves
Tier‑1 https://swashapp.io/ Consumer product: earn portal + app/extension; high‑level description.
Tier‑1 https://swashapp.io/static/files/paper/whitepaper-v1-july-2021.pdf Architecture (Data Union, sIntelligence, sCompute, sChain/sVault), the token’s role and onchain access/distribution mechanics.
Tier‑1 https://etherscan.io/token/0xa130e3a33a4d84b04c3918c4e5762223ae252f80 The SWASH ERC‑20 contract + max total supply and basic metrics.
Tier‑1 https://github.com/swashapp The existence of an official dev organization and repositories (extension/token, etc.).
Tier‑1 https://github.com/swashapp/token/security/advisories No public security advisories (as a fact).
Tier‑2 https://coinmarketcap.com/currencies/swash/ Aggregator: reference profile and additional wording (not Tier‑1).
Tier‑1 https://docs.swashapp.io/ The documentation at the link is unavailable (unavailable at the time of the check).

No comments to display

Back to top