A blockchain for real social interaction and messaging on-chain.
Built on Cosmos SDK v0.50 + CometBFT v0.38.
Since Bitcoin launched in 2009, few blockchains have delivered real utility. Most chains today are financial instruments only—sets of tokens moving between addresses. The promise of "web3 social" has failed for three reasons:
First, storage cost. Every kilobyte stored on-chain costs gas. Social data is high-volume—thousands of messages, posts, media per minute. At $0.10+ per KB, even a simple text post becomes expensive. This isn't social—it's luxury.
Second, innovation stall. Since Bitcoin, we have seen few genuinely new ideas. Most chains are EVM clones with different tokenomics. The "social" chains that exist are just databases with token incentives—not blockchain-native social protocols.
Third, centralization. Web2 social platforms own your data, control your feed, and can ban you at will. Blockchain promised decentralization and ownership. Most "web3 social" projects are just wrapped Web2—same architecture, different token.
Doumina addresses all three. Built for social at the protocol level.
Cosmos SDK application with custom modules:
┌──────────────────────────────────────────┐
│ Doumina App (Cosmos SDK v0.50) │
├──────────────────────────────────────────┤
│ x/messaging │ x/socialhub │ x/identity │
│ x/rewards │ x/eip1559 │ x/zkproof │
│ x/bank │ x/staking │ x/gov │
├──────────────────────────────────────────┤
│ Store: IAVL + ShadowSMT (ZK) │
├──────────────────────────────────────────┤
│ CometBFT v0.38 Consensus │
└──────────────────────────────────────────┘
Storage model: Messages store only SHA-256 hashes on-chain (64 bytes). When X sends to Y, only the hash is stored—the content exists only in the messages between X and Y. The chain stores proof that a message was sent, not the content itself.
Consensus: CometBFT with ZK proofs. Every block includes Nova IVC proof compressing entire chain state. New validators sync in seconds, not days.
A message notary system. When X sends to Y:
1. X computes H = SHA256(message_content)
2. X stores H on-chain with sender, receiver, TTL
3. The hash is recorded—the chain knows a message was sent
4. X delivers content to Y directly
5. Y verifies content matches H
Anti-spam: Bob maintains a whitelist. Whitelisted senders message for free. Non-whitelisted must pay a spam fee. This creates an economic barrier without requiring identity verification—just a wallet decision.
Like smart contracts but for communities—protocol-level community logic built-in:
Human-readable names linked to wallet addresses. Short names cost more (anti-squatting), long names are effectively free. Your username becomes your identity across all Doumina dApps.
Why usernames matter: In a social context, "dou1abc123..." is not social. You cannot mention, tag, or mention someone easily with a raw address. Usernames make on-chain social usable.
1% of validator block provision is set aside for message receivers. Delegators earn staking rewards (via inflation). Active message receivers earn messaging rewards. A 2% community tax supports the ecosystem.
Anti-farming design:
These combine to make Sybil attacks mathematically unprofitable while rewarding genuine users.
AIMD (Additive Increase, Multiplicative Decrease) fee algorithm:
if block_gas > target:
base_fee += 1 (or × overshoot)
elif block_gas == 0:
base_fee ×= 0.995
else:
base_fee unchanged
70% of all fees are burned. As Doumina usage grows, more DOU is removed from circulation—deflationary mechanics.
Every block carries a proof of the state transition. New validators verify the entire chain from a single ~10KB proof rather than replaying all blocks.
Base unit: udou (micro-DOU). 1 DOU = 1,000,000 udou.
DOUMINA uses udou for all on-chain operations—the same way ETH uses wei, or BTC uses satoshis. Gas prices, balances, and fees are denominated in udou for precision.
DOU serves three functions:
Validators and Delegators: DOUMINA uses proof-of-stake with up to 50 validators. Anyone can delegate DOU to a validator to earn a share of block rewards. Delegators choose validators based on commission rate, uptime, and security practices. Validators must run full nodes and (for this chain) generate ZK proofs. There's no "free" option—validators who want to participate must prove.
All numbers subject to community input before mainnet launch. This is a starting point for discussion.
>70% complete. Core infrastructure finished. Remaining: ZK proof integration, testnet, mainnet.
Before mainnet, I'm reachable via email. After mainnet launches, find me on-chain as one of the first users—that's the point.
Ideas about tokenomics, features, partnerships? Talk before we go live.