DeBond

Research preview · Built on IOTA

Real-time messaging, without the chain tax.

DeBond is a privacy-first, decentralized messenger inspired by Telegram — designed for IOTA's distributed network where micro-interactions and near-instant settlement finally make on-chain social possible.

Feeless heritage
Tangle-era design; Rebased mitigations via sponsored txs
Session-first
Chat-native, not another post feed
E2E by design
Minimal on-chain footprint

Why now

Post-based on-chain social was never enough

Existing decentralized social products optimize for async posts — timelines, likes, and NFT profiles. None were built for the hard problem: live conversations at Telegram scale.

  • Fees kill real-time chat

    Every message as a paid transaction breaks UX and economics. High-throughput messaging needs feeless or sponsored micro-settlement — a gap IOTA's Tangle heritage was built to address.

  • Signing friction blocks flow

    Wallet popups per keystroke destroy conversation rhythm. DeBond anchors trust on-chain while keeping the chat layer fast and familiar.

  • Posts ≠ conversations

    Session-centric apps need presence, delivery receipts, groups, and media — a different architecture than post feeds on Ethereum or Lens.

How distributed

No single owner of your conversations

DeBond combines encrypted real-time transport with IOTA for identity, membership, and verifiable commitments — so no one company sits in the middle of your social graph.

1

Your devices

Mobile and web clients you control. Keys stay with you; history syncs through encrypted channels.

2

Encrypted relay / P2P

Messages travel off-chain over WebSockets or peer relays. Near real-time delivery without writing every word to the ledger.

3

IOTA network

Identity, group membership, message anchors, and optional micropayments settle on IOTA — leveraging DAG heritage and Rebased finality (~400ms).

DeBond architectureClientsRelay / P2PIOTAanchors

Network challenges

Hard problems we're building for

Real-time on-chain social failed before because teams underestimated these constraints. DeBond names them openly — and designs around them from day one.

  • Fees & sponsored transactions

    IOTA Rebased may charge fees; feeless micro-messages at global scale need a sustainable model.

    DeBond approach

    Sponsored txs, batched anchors, and off-chain transport so users rarely sign per message.

  • Privacy vs. transparency

    Public ledgers leak metadata — who talks to whom, when, and how often.

    DeBond approach

    End-to-end encryption, minimal on-chain payloads, optional private groups.

  • Spam & scams

    Cheap or free transactions attract bots, phishing, and abuse at scale.

    DeBond approach

    Reputation layers, rate limits, optional verification, and client-side reporting.

  • Wallet & key UX

    Seed phrases and per-tx signing can't match Telegram's phone-login simplicity.

    DeBond approach

    Passkeys, embedded wallets, and social recovery on the roadmap after MVP.

  • Storage & media

    Blockchains are the wrong place for photos, voice notes, and chat history.

    DeBond approach

    Off-chain encrypted storage with on-chain hashes and commitments only.

  • Moderation & regulation

    Fully decentralized apps still face abuse reporting and legal expectations.

    DeBond approach

    Client-enforceable policies, transparent group rules, and abuse channels without central surveillance.

Telegram-scale goals

Inspired by Telegram, built for ownership

We respect what Telegram achieved for billions of users. DeBond pursues similar speed and simplicity — with a different foundation: user-owned identity and verifiable decentralization on IOTA.

Telegram today

  • Fast, familiar chat UX
  • Centralized infrastructure
  • Phone-based identity
  • Platform-controlled rules

DeBond direction

  • Session-first, real-time messaging
  • Distributed validators & open rules
  • Wallet or optional verified identity
  • E2E encryption + on-chain trust anchors

Roadmap

From research preview to mainnet

We're building in public toward an MVP, then testnet integration with IOTA — with grants and ecosystem partners after we prove the model.

  1. 01

    MVP

    Core messaging prototype, E2E layer, and IOTA identity anchors on testnet.

  2. 02

    Testnet

    Group chats, sponsored transactions, and spam-resistance experiments with real users.

  3. 03

    Ecosystem

    IOTA Foundation and partner outreach for funding, audits, and mainnet launch.

Help shape DeBond

We're assembling early supporters, builders, and grant partners. Leave your email to get MVP updates — no spam, no token sale.

hello@debond.io

Contact address for early access — copy and reach out on your preferred channel.