Community-owned tools for collaboration, governance, and knowledge.
The r-Stack is a suite of interoperable, local-first applications unified by EncryptID — a single secure login that keeps your keys on your device. Every tool shares the same real-time sync layer, so your community's data flows freely between apps without import/export, APIs, or vendor lock-in.
Each tool is independent but stronger together. Log in once, use them all.
A single identity layer that turns a fingerprint or face scan into full-stack access — encrypted storage, signed votes, community treasury, and more — without passwords, seed phrases, or cloud accounts.
EncryptID is built on WebAuthn passkeys — the same standard behind Face ID and fingerprint unlock on your phone. Your identity is bound to your device's secure hardware (TPM or Secure Enclave), so there is nothing to type, nothing to remember, and nothing that can be phished. Registration and login are a single biometric prompt.
When you authenticate, EncryptID derives a full set of cryptographic keys entirely on your device using HKDF. These keys never leave your hardware. Your encryption key protects your files, your signing key validates your votes, and your DID key proves your identity — all without a central server ever seeing your private material. Data syncs peer-to-peer via CRDTs; the server is just a relay, not an authority.
Lost your phone? No problem — and no seed phrase to dig out of a drawer. EncryptID uses guardian-based recovery: you designate trusted people (friends, family, community leaders) as guardians. If you lose access, any 3 of your 5 guardians can approve recovery after a 48-hour time-lock — giving you time to cancel if something seems wrong. Guardians never see each other's identities or your private keys.
EncryptID integrates Account Abstraction (ERC-4337) smart wallets, which means every user gets an on-chain wallet — without ever seeing a wallet address, gas fee, or blockchain confirmation. Your passkey is your wallet signer. A paymaster sponsors transaction fees so users never need to hold ETH. Session keys allow daily operations (voting, micro-payments, content uploads) with a single biometric prompt per session rather than per action. Spending limits and time-locks protect community treasuries.
You (fingerprint / face scan)
|
v
┌──────────────────────────────────────────────────────────┐
| EncryptID |
| |
| Layer 1: WebAuthn Passkey (hardware-backed) |
| | |
| Layer 2: Derived Keys (on-device, HKDF) |
| |── Encryption Key ── rFiles, rNotes, rSpace E2E |
| |── Signing Key ───── rVote ballots, authorship |
| └── DID Key ───────── portable identity |
| | |
| Layer 3: Smart Wallet (Account Abstraction) |
| |── Gasless transactions (paymaster-sponsored) |
| |── Session keys (one prompt per session) |
| └── Community treasury (multi-sig) |
| | |
| Layer 4: Cross-App SSO |
| └── One login for all r-Stack apps |
└──────────────────────────────────────────────────────────┘
|
v
rSpace · rVote · rWallet · rFunds · rMaps · rFiles · ...
Most blockchain tools assume users already know what a wallet is. EncryptID removes that assumption entirely. Here's what becomes possible when identity, encryption, and treasury are invisible infrastructure rather than technical prerequisites.
A neighbourhood association can pool funds, vote on how to spend them, and track every transaction on an immutable ledger — all through the same fingerprint login they use to unlock their phone. No one needs to understand gas, private keys, or blockchain explorers. The wallet is there, it's auditable, and it's invisible.
Co-ops, DAOs, strata councils, mutual aid networks — any group that votes can use rVote with cryptographically signed ballots that are verifiable but private. Because the signing key is derived from a passkey, members don't need to manage keys or install extensions. They just vote.
Files shared in rFiles, notes in rNotes, and canvases in rSpace are end-to-end encrypted with keys that only the community members hold. There's no admin backdoor, no platform that can read your data, and no breach that exposes plaintext. Privacy isn't a setting — it's the architecture.
Your EncryptID is a DID (Decentralized Identifier) that you own. Join a new community, and your reputation, credentials, and relationships can follow you — without creating a new account or trusting a new platform with your data. Leave a community, and your identity stays yours.
Paymaster-sponsored transactions mean a community can run a group purchase in rCart, split expenses in rFunds, or fund a project through rWallet without any member paying gas fees. The smart wallet batches operations, so what would be ten separate transactions becomes one seamless action.
Because data is local-first and identity is self-sovereign, communities aren't tenants on someone else's platform. They can export everything, fork the tools, self-host on their own server, or move between providers. The r-Stack is infrastructure that communities own, not services they rent.
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.