jeffemmett
/
rstack-online
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

feat: add BFT-CRDT community token issuance section 

New section covering how r-Stack apps issue tokens via the shared
CRDT layer: email/EncryptID-based distribution, cross-app token
utility (weighted voting, budget shares, treasury access, payments),
and optional bridge to on-chain ERC-20 via Account Abstraction.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Jeff Emmett 2026-02-15 14:38:38 -07:00
parent 3c3cbf949d
commit 210a08f8da
1 changed files with 131 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

131
index.html
View File

@ -698,6 +698,137 @@
</div>
</div>
<!-- Token Issuance -->
<div class="section-full">
<div class="section-inner">
<div class="section-divider"></div>
<h2>Community Token Issuance</h2>
<p class="section-desc">
Any r-Stack app can issue tokens to community members through the shared
CRDT data layer &mdash; no smart contract deployment, no gas fees, no
blockchain expertise required.
</p>
<div class="eid-grid">
<div class="eid-card" style="grid-column: 1 / -1;">
<div class="eid-card-icon">🪙</div>
<h3>BFT-CRDT Tokens</h3>
<p>
r-Stack tokens are built on <span class="hl">Byzantine Fault Tolerant CRDTs</span>
&mdash; 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.
</p>
</div>
<div class="eid-card">
<div class="eid-card-icon">📋</div>
<h3>Issue by Email or EncryptID</h3>
<p>
A community admin adds members by <span class="hl">email address</span> or
<span class="hl">EncryptID account</span> 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 &mdash; 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.
</p>
</div>
<div class="eid-card">
<div class="eid-card-icon">🔄</div>
<h3>Works Across Every App</h3>
<p>
Because tokens live in the shared CRDT layer, every r-Stack app can read and
write them. <span class="hl">rVote</span> can weight votes by token holdings.
<span class="hl">rFunds</span> can allocate budgets proportionally.
<span class="hl">rWallet</span> can gate treasury access by membership tokens.
<span class="hl">rCart</span> 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.
</p>
</div>
</div>
<div class="flow-box">
<pre>
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)
</pre>
</div>
<div class="unlock-grid" style="margin-top: 2rem;">
<div class="unlock-card">
<h3>Membership and access tokens</h3>
<p>
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 &mdash; the CRDT ledger
is the source of truth, and permissions propagate in real-time.
</p>
</div>
<div class="unlock-card">
<h3>Contribution credits</h3>
<p>
Reward members for participation: attending meetings, completing tasks,
contributing content. Credits accumulate in the CRDT ledger and can be
redeemed for governance weight in <span class="hl">rVote</span>, budget
allocation in <span class="hl">rFunds</span>, or community marketplace
purchases in <span class="hl">rCart</span>.
</p>
</div>
<div class="unlock-card">
<h3>Fundraising and grants</h3>
<p>
Create a project token, distribute to supporters, and track contributions
transparently. Supporters can see exactly how funds flow through
<span class="hl">rFunds</span> and vote on allocation through
<span class="hl">rVote</span>. The full history is auditable by
anyone holding the token.
</p>
</div>
<div class="unlock-card">
<h3>Bridge to on-chain when ready</h3>
<p>
Start with off-chain CRDT tokens for zero friction and zero cost.
When your community needs on-chain guarantees &mdash; for DeFi
composability, cross-community exchange, or regulatory compliance &mdash;
the CRDT ledger can be bridged to an <span class="hl">ERC-20</span>
token through the Account Abstraction wallet with a single action.
</p>
</div>
</div>
</div>
</div>
<footer>
<p>rStack &mdash; community-owned, local-first, interoperable</p>
<p style="margin-top: 0.5rem;">