Canonical: https://heartbank.net/positions/community-currency-design · Licence: CC0 1.0
Why Money and Time Are Complementary Scarcities — and Why a Single-Currency Community Economy Is Structurally Incomplete
A community has two principal scarcities: money and time. Conventional community-currency experiments — local exchange trading systems (LETS), time banks, mutual-credit currencies, dual-token cryptocurrency designs — typically operate on one of these scarcities at a time, treating the other as either out-of-scope or as something to be approximated by the chosen substrate. The result, after several decades of practice, is a family of community-currency designs that each address one scarcity well and the other not at all, producing structurally incomplete circulation.
HeartBank's institutional position: money and time should be treated as complementary scarcities in a single architectural pattern, not as substitutes within a single-currency system. A community-currency infrastructure that handles only money under-serves the time-poor; one that handles only time under-serves the materially scarce. The dual-currency reciprocity architecture — money and time as complementary primitives within one coordinated system — is the institutional pattern HeartBank endorses, builds toward, and commits to operating under.
Money and time are not the same kind of scarcity. Money is alienable, transferable, and accumulable; time is non-alienable, non-transferable (in the strict sense — only its use is exchangeable), and non-accumulable (an hour spent cannot be saved for tomorrow). The two scarcities require structurally different circulation primitives, and treating either as a proxy for the other produces characteristic distortions.
A dual-currency reciprocity infrastructure — money-as-currency operating on the Treasury surface, time-as-currency operating on the Chronicle surface, both mediated by a single autonomous-AI executive (Miss Aquarius) operating under the same dharmic substrate — is the architectural pattern that respects the distinction. The research paper Dual-Currency Reciprocity Infrastructure specifies the mechanism; this position paper states why HeartBank commits to it institutionally.
Three operational commitments follow.
First, HeartBank's product surface includes both Treasury (money) and Chronicle (time) primitives from inception, not Treasury alone with Chronicle deferred. The two are designed as complementary surfaces from the architectural level down; deferring one to later phases would entrench the single-currency-substitute pattern HeartBank's position rejects.
Second, HeartBank's mediator — Miss Aquarius — operates across both currencies with consistent dharmic substrate. The autonomous-AI executive does not have separate "money policy" and "time policy" decision functions; it operates the integrated system whose two surfaces share the same underlying ethical analysis.
Third, HeartBank's institutional partnerships engage existing community-currency efforts (LETS, time banks, mutual-credit networks) as complementary substrate rather than competitive replacement. The dual-currency pattern absorbs the lessons of each single-currency tradition; HeartBank's contribution is the architectural integration, not the displacement of prior community work.
HeartBank's position is not that prior single-currency designs were wrong. Each has been pressure-tested against real community conditions and has surfaced real insight about its specific scarcity. HeartBank's position is that the architectural integration of money and time as complementary scarcities is the next move the field can make — and that the move is technically feasible today using contemporary smart-contract infrastructure plus autonomous-AI mediation, in a way that prior eras of community-currency design could not have implemented.
The dual-currency pattern is offered to the commons. Other community-currency projects are welcome to adopt it; HeartBank's institutional commitment is to building one specific implementation, not to gatekeeping the pattern.
A community currency that circulates gratitude produces, in aggregate, a second-order signal: a picture of where kindness flows through a community — which businesses, which neighborhoods, which relationships generate the most freely given thanks. That aggregate picture is a genuine civic good. It can help a community find and support the people and places already doing the most good, the way a map of a commons helps the commons tend itself.
HeartBank's position is that this civic signal is legitimate only inside strict boundaries, and that naming those boundaries first — before the signal exists at scale — is part of designing a community currency responsibly rather than discovering its hazards after deployment. The signal must be aggregate-only (never a score attached to a named person), anonymous (no participant identifiable from it), opt-in (participation in the currency is not conscription into a measurement system), and patron-not-watcher in posture (the institution is a patron of the kindness it surfaces, not an auditor grading citizens). The same aggregate visibility that lets a community celebrate its kindest actors would, misused, let an authority rank and discipline them; a gratitude commons must therefore never become a social-credit system or an instrument of state surveillance. HeartBank commits to the patron posture and disclaims the watcher one explicitly, because a dual-use civic sensor is safest when its refusals are declared at design time. The companion mechanism paper The Gratitude-Riding Currency Tag specifies this civic-beneficiary frame and its anti-surveillance commitments in full.
The traditions this position calls incomplete have long records, and they are sobering. LETS schemes and time banks have run in many countries since the 1980s. They have persisted, done real good, and overwhelmingly stayed small and locally bounded — with recurring difficulty matching supply to demand, sustaining participation without a paid coordinator, and retaining members past the initial enthusiasm. ⚠️ The honest reading is not that they failed by addressing one scarcity. It is that community currencies are hard for reasons a second currency does not obviously fix.
Adding a rail adds coordination cost: two units of account, two liquidity problems, and an exchange question a single-currency system never has to answer. This design answers it by refusing convertibility — doctrinally clean, and operationally meaning a participant rich in one rail and poor in the other cannot help themselves across, which is precisely the person the dual design was meant to serve. And the notable scaled success is single-currency: Sardex, the Sardinian business-to-business mutual-credit circuit, whose lesson is about dense reciprocal demand within a bounded community rather than the number of scarcities addressed.
⭐ What would change this: participants using only one rail. If in live use they transact overwhelmingly on one and treat the other as ornamental — or if the time-poor and the money-poor turn out to be the same people rather than complementary populations — the complementarity is asserted rather than real, and the architecture is a single-currency system carrying an unused second ledger. That is measurable early and should be measured before this position is argued further.