+ Any r-Stack app can issue tokens to community members through the shared + CRDT data layer — no smart contract deployment, no gas fees, no + blockchain expertise required. +
+ ++ r-Stack tokens are built on Byzantine Fault Tolerant CRDTs + — the same conflict-free data structures that power real-time sync across + every app. Tokens are first-class objects in the shared data layer: they replicate + peer-to-peer, resolve conflicts automatically, and maintain a consistent ledger + across all participants without a central mint or blockchain validator. When your + community is ready to bridge to an on-chain asset, the CRDT ledger provides a + cryptographically verifiable history that can be anchored to any EVM chain + through the Account Abstraction wallet. +
++ A community admin adds members by email address or + EncryptID account to a distribution list. Hit issue, + and each member receives tokens in their r-Stack wallet instantly. Recipients + who haven't signed up yet get an invite link — their tokens are held in + escrow until they create a passkey, at which point the allocation transfers + automatically. No wallet addresses to copy-paste, no chain selection, no + confirmation dialogs. +
++ Because tokens live in the shared CRDT layer, every r-Stack app can read and + write them. rVote can weight votes by token holdings. + rFunds can allocate budgets proportionally. + rWallet can gate treasury access by membership tokens. + rCart can accept community tokens as payment. The + token is a primitive that flows through the entire stack, not a siloed balance + locked inside one app. +
++ Community Admin + | + | 1. Add members (email or EncryptID) + v + ┌──────────────────────────────────────────────────────┐ + | Token Issuance (BFT-CRDT) | + | | + | 2. Define token: name, supply, distribution rules | + | 3. Issue → tokens replicate across CRDT mesh | + | 4. Members receive in r-Stack wallet instantly | + └──────────────────────────────────────────────────────┘ + | + | Tokens are usable immediately across: + v + ┌──────────┬──────────┬──────────┬──────────┐ + | rVote | rFunds | rWallet | rCart | + | weighted | budget | treasury | payment | + | voting | shares | access | method | + └──────────┴──────────┴──────────┴──────────┘ + | + | Optional: bridge to on-chain (ERC-20) + v + EVM Chain (via Account Abstraction wallet) ++
+ Issue a token that represents membership in your community space. Gate + access to private canvases, files, or voting channels. Revoke by removing + the token. No smart contract audit needed — the CRDT ledger + is the source of truth, and permissions propagate in real-time. +
++ Reward members for participation: attending meetings, completing tasks, + contributing content. Credits accumulate in the CRDT ledger and can be + redeemed for governance weight in rVote, budget + allocation in rFunds, or community marketplace + purchases in rCart. +
++ Create a project token, distribute to supporters, and track contributions + transparently. Supporters can see exactly how funds flow through + rFunds and vote on allocation through + rVote. The full history is auditable by + anyone holding the token. +
++ Start with off-chain CRDT tokens for zero friction and zero cost. + When your community needs on-chain guarantees — for DeFi + composability, cross-community exchange, or regulatory compliance — + the CRDT ledger can be bridged to an ERC-20 + token through the Account Abstraction wallet with a single action. +
+