DeSocial WEB Whitepaper v1.0

Full Whitepaper V.1

DeSocial Protocol ·WEB Whitepaper v1.0 · Solana · DSP Proof System

Earn While You Scroll

A proprietary-proof social participation layer built natively on Solana — converting everyday Facebook, Twitter/X, YouTube, and Instagram activity into DSC SPL token rewards.

DeSocial converts fragmented social engagement into a verifiable, on-chain participation system. Users install one app, link existing social accounts, and passively earn DSC SPL tokens as they engage with content they already consume. Every event is processed through the proprietary DeSocial Proof (DSP) system and settled permanently on Solana.

1B DSC

Total Supply

5+

Platforms

usage-based

Reward Epochs

1%

Team Allocation

Principle 01

Invisible to the user

Install the DeSocial app,keep using existing socail apps like Facebook, instagram,X, YouTube as normal. DSP proofs work seamlessly with zero battery drain.

Principle 02

Proprietary proof — no personal data

The DeSocial Proof (DSP) system attests you participated without revealing your social handle, post content, or privacy, secured by DSP protocol.

Principle 03

Solana-native & fully auditable

Every reward is settled as a DSC SPL token on Solana (~400ms, <$0.001). Every event is permanently on-chain. No admin key. No trust required — only the ledger.

Executive Summary

DeSocial is built natively on Solana — sub-second finality (~400ms), fees below $0.001, and throughput exceeding 50,000 TPS make it the only L1 capable of handling the micro-event volume generated by millions of daily social media participants without batching delays or prohibitive costs.

The DeSocial Proof (DSP) system is a proprietary cryptographic proof architecture designed in-house — not generic ZK. DSP combines Pedersen commitments (Ristretto255), a Schnorr sigma protocol, and Fiat-Shamir transformation to produce compact, non-interactive proofs in ~18ms on mid-range mobile hardware at ~256 bytes per proof.

Every reward is settled as a DSC SPL Token via an immutable Solana program. Every participation event is logged permanently on-chain. No admin key. No manual verification. No trust required — only the ledger.

⚠ Research draft only — not financial advice. DSC tokens have not been issued.

Problem, Solution & Architecture

Why it exists and how it works on Solana

From the engagement extraction problem to a five-layer Solana architecture with a proprietary proof engine.

02 — Problem Statement

The global social media economy generated over $220 billion in advertising revenue in 2023, with leading platforms extracting $64.60 in average annual revenue per user — yet participants who create that value receive nothing. Platforms capture 99+% of it; contributors capture ~1%.

Even regular users who don't create content still generate massive value — they watch ads, engage with posts, provide data, and contribute to network effects. The average user now spends over 2.5 hours daily on social platforms, yet their attention and engagement remain completely uncompensated. Only established creators see any revenue — and even then, only those meeting stringent thresholds:

03 — How DeSocial Works

Install once. Use your apps. Earn DSC SPL tokens on Solana.

  1. 1Download the DeSocial mobile app (iOS or Android).
  2. 2Connect your Solana wallet.
  3. 3No need to Link social accounts. No passwords are shared with DeSocial.
  4. 4Continue using Facebook,X, YouTube, Instagram, TikTok, Reddit as normal.
  5. 5The DeSocial SDK passively only captures participation signals from linked apps upon used.
  6. 6Each qualifying action is hashed, commitment-sealed, and submitted to the DSP engine.
  7. 7DSP generates a proprietary participation proof — verified.
  8. 8Verified events accumulate as points; settled as DSC SPL tokens at epoch closure.

Diagram A — DeSocial Proof (DSP) Verification Flow

APPUser ActionFB / TW / YT / IG
SDKSDK CaptureEvent hash created
DSPDeSocial ProofProprietary proof
SOLSolana ProgramOn-chain log
DSCRewardSPL token credited

DSP = DeSocial Proof (proprietary) · SOL = Solana Program · DSC = SPL Token reward

Supported Platforms at Launch

PlatformTracked ActionsVerification
Facebooktime = usage = pointDSP engine
Xtime = usage = pointDSP engine
YouTubetime = usage = pointDSP engine
Instagramtime = usage = pointDSP engine
TikToktime = usage = pointDSP engine

Diagram B — Platform Architecture (5 Layers on Solana)

Application LayeriOS · Android · Web Dashboard
Identity LayerSolana Wallet · Referral Graph · User Profiles
Verification LayerDSP Engine · Proprietary Circuits · Campaign Logic
Reward EngineSPL Token Ledger · Balance Tracking · Audit Logs
Crypto TransportAES-256 · SHA-256 · Ed25519 · Solana TLS

Identity Layer

Anchored to a Solana Ed25519 wallet (256-bit pubkey). Social account linkages stored as SHA-256-hashed associations in Solana PDA/ATA accounts — raw OAuth tokens are never persisted beyond capture TTL. Referral relationships are recorded as a directed Merkle graph in a dedicated PDA/ATA.

Verification Layer (DSP Engine)

Every event passes through the DeSocial Proof (DSP) engine — proprietary, purpose-built for OAuth stream verification at mobile scale. The DSP proof is submitted to the Solana Verifier program, which validates it and emits a ParticipationVerified instruction into the ledger.

Reward Engine (Solana Program)

Native Solana program written in Rust (Anchor framework). Maintains a PDA/ATA ledger, accumulates points per epoch, and executes DSC SPL token transfers at epoch closure. No upgrade authority after mainnet launch — immutable by design.

Crypto Transport Layer

All data in motion is encrypted with AES-256-GCM over TLS 1.3. Message integrity uses SHA-256. All Solana instructions are signed with Ed25519 — consistent with Solana's native account model and the Ristretto255 group used in DSP commitments.

DSP Proof System & Audit Logs

Proprietary cryptography and Solana-native transparency

The DeSocial Proof (DSP) system — construction, proof structure, nullifiers, and three-tier audit logs.

05 — Why the DSP System, Not Generic ZK?

Generic ZK-SNARK frameworks (Groth16, PLONK, STARKs) carry overhead unsuitable for DeSocial: general-purpose trusted setups, circuit compilation measured in minutes, and proof sizes optimised for financial transactions rather than high-frequency social micro-events.

DSP vs Groth16

40–80× smaller proof size

10–50× faster proof generation

No trusted setup required

DSP on Solana

~256 bytes per proof

~18ms proof gen (mobile)

~12,000 CUs to verify on-chain

DSP Construction — Three Primitives

1

Pedersen Commitment

Over Ristretto255 — a prime-order group derived from Curve25519, consistent with Solana's Ed25519 keys. Binds wallet identity to the proof without revealing the public key.

2

Schnorr Sigma Protocol

Proof of knowledge of the OAuth event signature and wallet blinding factor. Proves the action occurred without revealing the event payload or social identity.

3

Fiat-Shamir (SHA-256)

Transforms the interactive sigma into a standalone non-interactive proof. SHA-256 acts as the random oracle — no trusted setup, no ceremony required.

DSP Cryptographic Primitives Summary

PrimitiveAlgorithmRole in DSP
Commitment schemePedersen / Ristretto255Bind wallet to proof without revealing pubkey
Proof of knowledgeSchnorr sigma protocolProve knowledge of OAuth sig without revealing it
Non-interactivityFiat-Shamir (SHA-256)Convert sigma protocol to standalone proof
Platform sig proofEd25519 PoKAttest event was genuinely platform-signed
Replay preventionSHA-256 nullifier PDA/ATAPrevent double-submission on Solana
TransportAES-256-GCM / TLS 1.3Protect proof in transit to Solana RPC

06 — Three-Tier Audit Log System

1

Tier 1 — Client-Side Log (Device)

AES-256-GCM encrypted log on the user's device. Each entry records timestamp, platform, action type, DSP proof IPFS CID, nullifier, and Solana transaction signature. Exportable as JSON for independent cross-referencing with on-chain data.

2

Tier 2 — Verification Server Log (IPFS + Solana PDA/ATA)

Append-only signed log anchored to Solana mainnet every 100 slots (~40 seconds) via Merkle root commitment in a dedicated PDA/ATA. Log is pinned to IPFS and publicly readable. Retrospective alteration is computationally infeasible once the root is on-chain.

3

Tier 3 — On-Chain Solana Program Log

Every verified event emits a ParticipationVerified Anchor event. Every epoch settlement emits RewardDistributed. Permanently recorded in the Solana ledger — queryable by any wallet via RPC, no DeSocial intermediary required.

Tokenomics & Security

DSC SPL Token model and cryptographic privacy

Solana SPL Token supply, distribution, vesting schedule, encryption standards, and Solana program security.

07 — DSC SPL Token Overview

Token NameDeSocial Token (DSC)
BlockchainSolana Mainnet-Beta
Token StandardSPL Token (Token-2022)
Decimals9 (Solana standard)
Mintablefixed supply
Epoch Duration100 days (usage-based)
Total Epochs36 epochs
Per-Epoch Pool22,222,222 DSC
Total Supply1,000,000,000 DSC

Token Allocation

80%User Participation
5%Ecosystem & Growth
10%Liquidity Provision
4%Protocol Reserve
1%Core Team

Distribution Schedule

Allocation% ShareDSC AmountVesting
User Participation80%800,000,000Continuous epoch distribution
Ecosystem & Growth5%50,000,000DAO-governed grants
Liquidity Provision10%100,000,000DEX liquidity,
Protocol Reserve4%4,000,00024-month lock
Core Team1%1,000,000cliff-vesting

Why SPL Token (Token-2022)?

  • ▸Native to Solana — transfers settle in one slot (~400ms), fees below $0.001.
  • ▸Token-2022 confidential transfer extension enables privacy-sensitive reward distribution.
  • ▸Transfer hooks enforce vesting rules directly on-chain via Solana program logic.
  • ▸No bridging required — DSC lives and moves entirely within the Solana ecosystem.

08 — What DeSocial Never Stores

  • ✓Raw OAuth access tokens — discarded after event hash capture, never persisted server-side.
  • ✓Social media usernames, handles, or profile identifiers in plaintext.
  • ✓Content of posts, comments, tweets, or any user-generated material.
  • ✓IP addresses linked to participation events.
  • ✓Private keys or seed phrases — user controls Solana wallet exclusively.
  • ✓Unmasked wallet addresses in on-chain logs — only Pedersen commitments are recorded.

Encryption & Cryptographic Standards

LayerAlgorithmKey SizePurpose
Data at rest (device)AES-256-GCM256-bitLocal participation log
Data in transitTLS 1.3 + AES-GCM256-bitApp to DSP server comms
Wallet / tx signingEd25519256-bitSolana tx auth + DSP proof
Commitment (DSP)Pedersen/Rist255255-bitWallet identity binding
Proof challenge (DSP)SHA-256 (F-S)256-bitFiat-Shamir random oracle
Nullifier derivationSHA-256256-bitReplay prevention token
Merkle log anchoringSHA-256 tree256-bitAudit log integrity on Solana

Solana Program Security

  • ⚑No upgrade authority on Reward Engine after mainnet — immutable by design.
  • ⚑Any upgrade requires DAO multisig (5-of-9) + 7-day on-chain timelock.
  • ⚑DSP circuit logic reviewed by two independent cryptography teams pre-launch.
  • ⚑Formal verification using Soteria and Anchor constraint model.
  • ⚑Continuous bug bounty — up to $50,000 DSC for critical vulnerabilities.
  • ⚑Annual third-party audit of DSP system, Solana programs, and mobile SDK.

Growth, Roadmap & Conclusion

Network growth model and Solana deployment phases

On-chain referral graph, anti-Sybil measures, three-phase roadmap, and closing statement.

09 — Referral Graph (On-Chain Solana PDA/ATA Merkle Tree)

When a new user onboards via referral link, their Solana wallet is recorded as a leaf in the referrer's Merkle subtree PDA/ATA. Referral rewards are calculated at epoch closure across up to 3 levels deep, with a decay function to prevent pyramid incentive dynamics.

Referral LevelReward MultiplierDecay Function
Level 1 (direct)100% of referee pointsNone
Level 1+ (twoway)100% of referee pointsNone

Anti-Sybil Measures

  • ▸Each Solana wallet permitted only one linked account per social platform.
  • ▸DSP proof requires a valid platform-signed OAuth event — bots cannot fabricate this.
  • ▸Anomaly detection flags wallets with statistically improbable participation velocity.
  • ▸Rate limiting enforced at SDK level and Solana program level per epoch per wallet.

10 — Roadmap

Phase 1

Protocol Foundation & SDK Development

Jan – Mar 2026
  • ▸Core identity infrastructure and Solana wallet integration (Phantom, Backpack, Solflare).
  • ▸SDK development: Facebook, X, YouTube, Instagram API integration.
  • ▸DSP proof system design and internal security audit.
  • ▸Solana devnet deployment for initial testing.
  • ▸Referral Merkle tree PDA/ATA architecture implementation.
  • ▸Public bug bounty program launch on Solana devnet.

Phase 2

App Launch & User Onboarding

Apr – Jun 2026
  • ▸Official app launch on iOS and Android.
  • ▸Public registration opens — username creation + wallet connection.
  • ▸Campaign participation features live (connect social accounts).
  • ▸DSP proof system mainnet deployment.
  • ▸Referral program goes live — unique referral codes for all users.
  • ▸Early user rewards tracking begins (points accrual).

Phase 3

Reward Engine & Token Generation

Jul – Sep 2026
  • ▸Reward Engine Solana program mainnet deployment.
  • ▸DSC SPL token generation event — 1,000,000,000 total supply.
  • ▸Rule-based verification logic activated.
  • ▸On-chain audit anchoring: IPFS + Solana PDA/ATA Merkle roots.
  • ▸Campaign analytics dashboard for community organizers.
  • ▸First claim window preparation.

Phase 4

Epoch 1 Launch & Initial Rewards

Oct – Dec 2026
  • ▸EPOCH 1 LAUNCH — First 100-day reward period begins.
  • ▸25,000,000 DSC allocated for epoch 1 rewards.
  • ▸Users begin earning real DSC tokens for social engagement.
  • ▸Points-to-token conversion mechanism activated.
  • ▸First wave of reward distributions to early adopters.
  • ▸Community leaderboards and achievement badges.

Phase 5

Ecosystem Expansion & Governance

Q1 2027+
  • ▸Public developer API for third-party DeSocial apps.
  • ▸DAO governance launch — on-chain multisig control of Reward Engine.
  • ▸Solana Mobile (Saga) native integration.
  • ▸Enterprise community campaign tools and white-label SDK.
  • ▸Formal peer-reviewed paper on DSP proof system.
  • ▸Cross-program composability with Solana DeFi protocols.
  • ▸Epoch 2+ rewards continue with ~22.2M DSC per epoch.

11 — Conclusion

DeSocial represents a fundamental rethinking of the relationship between social media platforms and their participants. The combination of Solana's high-throughput permanent ledger and the proprietary DeSocial Proof (DSP) system creates a participation infrastructure that is simultaneously mobile-native, privacy-preserving, cryptographically verifiable, and economically fair.

The protocol does not require users to change their behaviour. It intercepts the value signal that currently flows entirely to platform shareholders, and routes a meaningful portion back to the people who generate it — verified by a proof system they can inspect, settled on Solana in ~400ms, and held in a wallet only they control.

DeSocial Foundation Team · desocialorg@gmail.com · desocial_app
Public research draft. DSC tokens have not been issued. Not financial advice.