Whitepaper v1.0

Tamechain

A Privacy-Preserving, Incentive-Aligned Consensus Protocol
for Decentralized Romance Infrastructure

Authors: Asavan Mitra, Ekaki Yatrika

Document Version: 1.0 (Pre-Mainnet)

Release Date: March 17, 2026

Contact: paper@tamechain.xyz

Status: Draft

Abstract

Modern dating platforms operate as centralized clearinghouses for romantic intent, extracting value through attention monetization, asymmetric information control, and engagement-maximizing algorithms that are fundamentally misaligned with user outcomes. We present Tamechain, a proof-of-stake consensus protocol for coordinating mutually acknowledged romantic interest between network participants. By introducing Proof of Attraction (PoA), a novel Sybil-resistant signaling mechanism backed by staked $FLAME tokens, combined with zero-knowledge identity verification, a validator-confirmed match consensus layer, and a mandatory cooling-off epoch, Tamechain replaces the extractive Web2 dating model with a transparent, user-sovereign, and incentive-aligned romance infrastructure. The protocol is designed to solve the long-standing Byzantine Generals Problem of modern dating: "does the other party genuinely reciprocate interest, or are they simply farming engagement?" We formalize the match-finality model, describe the $FLAME token economy, and outline a roadmap toward cross-chain interoperability and zero-knowledge flirting.


The Problem: The Trust Crisis in Digital Dating

The global online dating market is projected to reach $12.25 billion by 2030. Yet the industry suffers from systemic, structural failures that erode user trust and produce progressively worse outcomes for participants. These failures are not bugs, they are features of the prevailing business model.

Perverse Incentive Structures ("Engagement Farming")

Existing platforms are financially incentivized to keep users single, swiping, and paying. A successful match that leads to a lasting relationship is, from the platform's perspective, a lost customer. Revenue models built on subscriptions, boosts, and premium visibility create a zero-sum game between platform profit and user satisfaction. The result is algorithmic suppression of high-quality matches in favor of engagement-maximizing dopamine loops.

The Bot & Scam Epidemic

Fake profiles, romance scams, and catfishing are rampant across every major platform. The FTC reported over $1.3 billion in romance scam losses in 2022 alone. Traditional verification methods, phone, email, basic photo review, are trivially bypassed by both automated bots and determined bad actors.

Data Exploitation & Privacy Erosion

User data including photos, messages, sexual orientation, behavioral patterns, and location history is harvested, monetized, and frequently breached. Users surrender intimate personal information with no sovereignty over how it is stored, processed, or sold.

The Byzantine Generals Problem of Romance

In distributed systems theory, the Byzantine Generals Problem describes the difficulty of achieving consensus among parties who cannot fully trust each other or the communication channel. Modern dating is a direct instantiation of this problem: two participants must independently decide to commit (swipe right) without knowledge of the other's decision, through a channel (the platform) that may be adversarial to their success.


Our Solution: Protocol Overview

Tamechain inverts the extractive dating model by placing user sovereignty, privacy, and aligned incentives at the core of its architecture. The protocol consists of five interdependent layers:

Layer Component Function
L0 Identity & Verification ZK-proof age/identity verification via DID, Sybil resistance
L1 Swipe Mempool Pending attraction signals with staked $FLAME collateral
L2 Match Consensus Engine Validator committee confirms mutual signatures & stake locks
L3 Cooling-Off Epoch 24–72 hr mandatory waiting period before match finalization
L4 Romance Ledger Immutable record of finalized matches, reviews, & reputation
┌─────────────┐     ┌──────────────┐     ┌────────────┐     ┌───────────┐     ┌──────────────┐
│  L0: DID /  │────▶│  L1: Swipe   │────▶│ L2: Match  │────▶│ L3: Cool  │────▶│ L4: Romance  │
│  ZK Identity│     │   Mempool    │     │ Consensus  │     │  -Off     │     │    Ledger    │
└─────────────┘     └──────────────┘     └────────────┘     └───────────┘     └──────────────┘
   Verify once        Stake $FLAME       12 validators       24-72 hrs         DMs unlocked
   use forever        signal intent       confirm sigs       mandatory         reviews enabled

Proof of Attraction (PoA) Consensus

Formal Definition

We define Proof of Attraction as a Sybil-resistant signaling mechanism in which a participant $P_i$ expresses romantic interest in participant $P_j$ by broadcasting a signed, stake-backed transaction to the Swipe Mempool.

$$\text{SwipeTx}(P_i \rightarrow P_j) = \{ \text{sig}_i, \; \text{stake}_i, \; \text{timestamp}, \; \text{nonce}, \; H(\text{profile}_j) \}$$

A match is proposed if and only if complementary swipe transactions exist:

$$\text{MatchProposal}(P_i, P_j) \iff \exists \; \text{SwipeTx}(P_i \rightarrow P_j) \;\wedge\; \text{SwipeTx}(P_j \rightarrow P_i)$$

Stake Requirements

Each swipe requires a minimum stake of $s_{\min}$ $FLAME tokens, burned from the participant's wallet and locked in a match escrow contract. The stake serves three purposes:

  1. Spam Deterrence — economic cost prevents indiscriminate swiping
  2. Signal Quality — higher stakes optionally signal stronger interest (Super Swipe)
  3. Validator Incentives — a portion of forfeited stakes rewards the validator committee

$$s_{\min} = \beta \cdot \frac{1}{R_i + 1}$$

where $\beta$ is the base stake constant and $R_i$ is the reputation score of $P_i$.
Higher reputation → lower minimum stake. New accounts face higher friction.

Validator Committee & Consensus

Match proposals are validated by a randomly selected committee of $k = 12$ validators drawn from the active validator set via verifiable random function (VRF). Validators confirm:

  • Both signatures are cryptographically valid
  • Both stakes meet or exceed $s_{\min}$
  • Neither participant is in a conflicting active match (fork prevention)
  • Both DIDs pass liveness verification

Consensus is achieved when $\geq \lceil 2k/3 \rceil + 1 = 9$ validators approve the match proposal. Stakes are then locked for the duration of the cooling-off epoch.

Cooling-Off Epoch

To prevent impulsive chain reorganizations (colloquially, "never mind, actually"), Tamechain enforces a mandatory waiting period $\tau$ before match finalization:

$$\tau = \tau_{\text{base}} + \delta(\text{hour})$$

where $\tau_{\text{base}} = 24\text{h}$ and $\delta(\text{hour})$ is a penalty function that extends the cooldown for swipes initiated between 1:00 AM–4:00 AM local time (the "late-night regret modifier").

During the epoch, either party may broadcast an UnmatchTx, which returns stakes minus a small cancellation fee $\epsilon$ distributed to validators. After $\tau$ expires without cancellation, the match is finalized, the DM channel is unlocked, and a MatchBlock is appended to the Romance Ledger.


Network Architecture

Swipe Mempool

The Swipe Mempool aggregates pending attraction signals awaiting stake confirmation. Transactions in the mempool are encrypted with the recipient's public key, the target participant cannot see who swiped on them until a mutual match is proposed. Mempool entries expire after 7 days (configurable via governance) to prevent stale interest accumulation.

Match Blocks

Batches of validator-confirmed mutual interactions are aggregated into Match Blocks. Each block contains up to 256 match proposals, validator attestations, stake lock receipts, and epoch timer initializations. Block time targets 30 seconds during peak hours (Friday 7 PM – Saturday 2 AM) and 5 minutes during off-peak.

Romance Ledger

The Romance Ledger is an append-only, immutable record of finalized matches, post-date peer reviews, and reputation state transitions. Data is stored on decentralized storage (IPFS/Arweave) with on-chain anchors for integrity verification. Users retain full data sovereignty, profile data and chat history are encrypted with user-held keys and never accessible to the protocol operators.

Messaging Layer (Post-Finalization)

Upon match finalization, a peer-to-peer encrypted DM channel is established using the Double Ratchet Algorithm. Messages are ephemeral by default (auto-delete after 30 days) unless both parties opt into persistence. The protocol cannot read, moderate, or monetize message content.


Identity & Privacy Layer

Identity verification is a critical prerequisite to network participation. Tamechain employs a layered approach combining Decentralized Identifiers (DIDs) with Zero-Knowledge Proofs to ensure that every participant is a verified, unique human without requiring the upload of identity documents to any centralized server.

ZK-Proof Age Verification

Participants generate a zero-knowledge proof attesting that their age $\geq 18$ without revealing their exact date of birth, government ID, or any other personal data to the network. The proof is verified on-chain and bound to the participant's DID.

Sybil Resistance

Each DID is bound to a unique biometric attestation (e.g., iris scan, liveness check) processed locally on the user's device. The attestation produces a commitment hash stored on-chain — no biometric data ever leaves the device. This prevents one human from operating multiple accounts (the "alt-account catfish" attack vector).

Selective Disclosure

Participants control exactly which profile attributes are visible to potential matches via Verifiable Credentials. For example, a user may prove "I live within 30km of you" without revealing their address, or "I hold a university degree" without disclosing the institution.


Tokenomics: $FLAME

The $FLAME token is the native utility token of the Tamechain ecosystem. It serves as the economic backbone for staking, incentive distribution, governance participation, and premium feature access.

Token Utility

Use Case Description
Swipe Staking Required collateral for each attraction signal
Super Swipe Optional higher-stake signal indicating elevated interest
Validator Rewards Committee members earn $FLAME for confirming match consensus
Reputation Rewards Users with high peer-review scores earn periodic $FLAME airdrops
Premium Features Profile boosts, advanced filters, extended match history
Governance Voting power in protocol parameter proposals (see §8)
Virtual Gifting Micro-tip roses, drinks, and other tokenized gestures

Token Distribution

Total Supply: 1,000,000,000 $FLAME (fixed, non-inflationary)

Allocation % $FLAME Vesting
Community & Rewards 30% 300,000,000 Released over 48 months
Ecosystem & Grants 20% 200,000,000 DAO-governed treasury
Team & Advisors 20% 200,000,000 12-month cliff, 36-month vest
Validator Incentives 15% 150,000,000 Released per epoch
Public Sale 10% 100,000,000 TGE unlock
Reserve 5% 50,000,000 Emergency / liquidity

Deflationary Mechanics

A percentage $\phi$ of all cancellation fees, expired mempool stakes, and premium feature payments are permanently burned, creating deflationary pressure proportional to network activity:

$$\text{Burn}_{epoch} = \phi \cdot \left( \sum \epsilon_{\text{cancel}} + \sum s_{\text{expired}} + \sum f_{\text{premium}} \right), \quad \phi \in [0.05, 0.20]$$

$\phi$ is adjustable via governance vote.


Security Considerations & Threat Model

The protocol's threat model accounts for both technical attack vectors and social-layer exploits unique to romance-oriented networks.

Attack Vector Description Mitigation
Swipe Spam Mass indiscriminate swiping to maximize match probability $FLAME stake requirement; escalating cost per swipe/day
Catfishing / Sybil Fake identities or duplicate accounts DID-bound biometric attestation; ZK identity proofs
Ghosting Unilateral post-match disengagement without signaling Cooling-off epoch rollback; reputation penalty for no-response
Love Bombing Excessive Super Swipes to manipulate visibility Daily stake cap; diminishing returns on consecutive signals
Reputation Manipulation Collusive fake reviews to inflate scores Reviews weighted by reviewer reputation; anomaly detection
Validator Collusion Coordinated match approval/denial VRF-based random selection; slashing conditions
Relationship Fork Participant maintains multiple concurrent active matches Configurable concurrency limit (default: 3 active matches)

Open Problems

The protocol does not yet fully mitigate the "met someone better on Friday" attack, the "still not over their ex" persistent state bug, or the "said they were 5'11" but were actually 5'8" " oracle problem. These remain active areas of research.


Reputation & Peer Review System

Following any interaction (date, video call, or extended DM exchange), both participants may submit a structured peer review. Reviews are stored on the Romance Ledger and contribute to an exponentially weighted moving average reputation score.

{
  "reviewer":     "did:swipe:0x...",
  "reviewee":     "did:swipe:0x...",
  "epoch":        184729,
  "scores": {
    "punctuality":    4,       // 1-5
    "conversation":   5,       // 1-5
    "honesty":        3,       // 1-5
    "photo_accuracy": 2,       // 1-5  (new)
    "respectfulness": 5        // 1-5  (new)
  },
  "vibes":          "immaculate",  // optional freetext, max 140 chars
  "would_rematch":  true,          // boolean
  "proof":          "zk-snark-review-attestation-hash"
}

The reputation score $R_i$ for participant $P_i$ is computed as:

$$R_i = \frac{\sum_{j=1}^{n} w_j \cdot \bar{s}_j}{\sum_{j=1}^{n} w_j}, \quad w_j = R_{\text{reviewer}_j} \cdot \lambda^{n-j}$$

where $\bar{s}_j$ is the mean score from review $j$, $w_j$ is the weight (reviewer reputation × recency decay $\lambda \in (0,1)$), and $n$ is total reviews received.


Governance

Tamechain is governed by a Decentralized Autonomous Organization (DAO) in which $FLAME holders vote on protocol parameters, treasury allocation, and ecosystem upgrades. Governance follows a time-weighted voting model where longer staking duration amplifies voting power, discouraging short-term speculation.

Governable Parameters

  • Base stake constant $\beta$
  • Cooling-off epoch duration $\tau_{\text{base}}$
  • Late-night regret modifier $\delta(\text{hour})$
  • Burn rate $\phi$
  • Maximum concurrent active matches
  • Validator committee size $k$
  • Mempool expiration window
  • Review submission deadline

Proposal Lifecycle

Draft → Discussion (7d) → Voting (5d) → Timelock (48h) → Execution

Quorum: 4% of circulating supply. Approval threshold: 66%.


Roadmap

Q2 2026

Phase 1 — Spark (Testnet)

  • Core PoA consensus on testnet
  • DID + ZK age verification integration
  • Swipe Mempool and basic match flow
  • $FLAME testnet faucet
Q4 2026

Phase 2 — Flame (Mainnet Beta)

  • Mainnet launch with $FLAME TGE
  • Encrypted P2P messaging layer
  • Reputation & peer review system
  • Mobile app (iOS / Android)
Q2 2027

Phase 3 — Inferno (Expansion)

  • Zero-Knowledge Flirting (ZKF) — express interest with provable deniability
  • Cross-Chain Dating — bridge matches across EVM-compatible networks
  • DAO-governed Date Venue partnerships (on-chain reservations)
  • Layer-2 Situationship Scaling — lightweight channels for casual connections
Q4 2027

Phase 4 — Eternal Flame (Maturity)

  • AI-assisted compatibility oracles (on-chain, privacy-preserving)
  • Multi-party match consensus (group dating protocol)
  • Decentralized breakup mediation via arbitration DAO
  • Full protocol decentralization — team keys burned

Conclusion

The current digital dating landscape is defined by misaligned incentives, centralized data exploitation, and an epidemic of fraudulent participants. Tamechain presents a fundamentally different paradigm: a protocol where users own their data, stake real value behind their intentions, and operate within a transparent, validator-secured consensus framework designed to reward genuine connection over engagement extraction.

By formalizing romantic intent as a cryptographically signed, stake-backed transaction and subjecting it to community validation and a mandatory cooling-off period we create the conditions for a dating ecosystem where trust is not assumed but proven.

The road ahead is long, and some problems remain unsolved (see §7: Open Problems). But we believe that if blockchains can coordinate billions of dollars of economic activity through trustless consensus, they can coordinate something far more important: two people who actually like each other, admitting it at the same time.


References

  1. Nakamoto, S. (2008). Bitcoin: A Peer-to-Peer Electronic Cash System.
  2. Buterin, V. (2014). Ethereum: A Next-Generation Smart Contract and Decentralized Application Platform.
  3. Lamport, L., Shostak, R., Pease, M. (1982). The Byzantine Generals Problem. ACM TOPLAS, 4(3).
  4. Perrin, T., Marlinspike, M. (2016). The Double Ratchet Algorithm. Signal Foundation.
  5. Federal Trade Commission. (2023). Romance Scams Report.
  6. Goldwasser, S., Micali, S., Rackoff, C. (1985). The Knowledge Complexity of Interactive Proof-Systems.
  7. Your Therapist. (2026). "Maybe Try Meeting People in Real Life." Private Communication.

Disclaimer

Tamechain is an experimental decentralized romance protocol provided on an "as-is" basis. This whitepaper is for informational and entertainment purposes only and does not constitute financial, legal, or relationship advice.

Risk Disclosure: Participation in the Tamechain network may result in loss of staked tokens, loss of dignity, emotional instability, unsolicited situationships, or the sudden realization that your ex was right about you. Past romantic performance is not indicative of future results.

Validators are not responsible for bad dates. The protocol makes no guarantees regarding match quality, long-term compatibility, or whether they will text you back.

$FLAME tokens have no inherent romantic value. Not available in all jurisdictions. Void where prohibited by heartbreak.