Is Your Community Ready for a Local Node?

You’ve read the playbooks, you’ve got a wallet, and you’re ready to spin up a local node for your town. Before you deploy anything, sit with a harder question: is your community ready, or is it just you?

A local node is a place-based chapter of a regenerative finance network. A regenerative finance (ReFi) node uses crypto tools to fund and coordinate real-world good in one specific place. Think a Greenpill chapter, a community treasury, a timebank, or a local currency. The technology is the easy part. The thing that kills these projects is rarely the smart contract. It’s the gap between the people you imagine showing up and the people who actually do.

This isn’t gatekeeping. It’s the difference between launching from solid ground and burning out in three months, then concluding “community organizing doesn’t work.” It works. But only when the foundations are there first.

Readiness Is a Stage, Not a Yes/No

The Community Readiness Model, developed by the Tri-Ethnic Center for Prevention Research at Colorado State University, maps community readiness across nine stages, from “no awareness” through “preplanning,” “preparation,” “initiation,” and on to “community ownership.” It was built for public health work, but it travels well.

The honest cutoff for launching anything financial is stage 5, “preparation”: leadership has emerged, there’s active planning, and people are mobilizing, not just talking. Below that, you’re trying to push a node onto a community that hasn’t decided it wants one. Above it, the tooling becomes a force multiplier for energy that already exists.

The goal here isn’t to talk you out of building. It’s to tell you which stage you’re actually in, so you spend scarce energy on the right thing.

What Readiness Actually Looks Like

The people

You need at least 5 to 7 people who will actually participate. Not “interested.” Not “might join.” Already showing up. Can you name them right now, with phone numbers?

Cooperative formation tends to fail below five members; there isn’t enough distributed effort to survive one person getting sick, moving, or losing interest. It also fragments above roughly fifteen in the founding phase, before clear governance exists. The workable founding group is 5 to 12 committed people who:

Have shown up to at least three activities together already
Can say why they want this (not “DAOs are cool”)
Bring different skills, not seven developers. You need communicators, organizers, and connectors more than you need more coders.
Include two or three people with real experience managing money or projects

The need

There has to be a shared problem the community already feels without you explaining it:

“We want to trade skills without cash changing hands.”
“We want to keep wealth circulating with local businesses.”
“We want to pool money for projects banks won’t touch.”
“We want transparent control of shared funds.”

If the only answer is “Web3 is interesting,” people leave the moment the work turns tedious, and running a financial system is mostly tedious work.

The culture

Your group needs a willingness to ship something imperfect. Groups that need everything planned before they start spend six months perfecting bylaws no one ever uses. The ones that succeed iterate in public and learn by doing.

This is what adrienne maree brown calls emergent strategy in her 2017 book of that name: complex systems develop through experimentation and relationship, not master plans. Your node will look nothing like your launch plan six months in. That’s adaptation, not failure.

Reading the Signals

Green flags:

Track record: people have built something together before, a garden, a mutual aid run, a savings circle.
Existing coordination: there’s already a group chat people actually read, a regular meetup, a shared calendar.
Distributed enthusiasm: three or four people are genuinely lit up, not one charismatic founder dragging everyone.
Conflict resilience: you’ve disagreed and survived. Groups that have never fought aren’t harmonious, they’re untested.
Financial collaboration: you’ve pooled money before, even informally, splitting an event-space rent or group-buying supplies.

Red flags:

Solo show: one or two people do everything; the rest “support” passively.
Future-tense commitment: “we should do X” that never happens. “I’ll help when…” is a polite no.
Decision paralysis: every choice needs a long consensus process before anything moves.
Unresolved conflict: old tension no one has addressed. It will resurface the moment money is involved.
Tech-first motivation: people want to play with the tooling more than they want the neighborhood to thrive.
No existing community: you’re building the community and the financial system from scratch at once. Pick one. Build community first.

The One Failure Mode to Plan Around

Here’s the pattern that should haunt you. It’s the most common way these projects die, and it isn’t a hack.

Ithaca Hours, the paper local currency launched in Ithaca, New York in 1991, ran for years with over $100,000 worth in circulation at its peak. Then its founder and tireless evangelist, Paul Glover, moved away. Without a full-time networker to “promote, facilitate, and troubleshoot,” circulation slid, and by the 2010s it had effectively stopped. The same arc played out with the Bristol Pound, which withdrew its currency in 2020 and whose successor closed in 2023, and the Brixton Pound, now paused for a governance transition.

The lesson for you, the person standing this up: if the whole thing runs on one heroic individual, that individual is the single point of failure, and that individual is probably you. The fear of burnout you came in with is rational. Design against it from day one by distributing roles, not by working harder.

The counter-example is Sarafu Network, run by the Kenyan nonprofit Grassroots Economics. It supports 26,000+ people across roughly 290 communities, using commitment pools (shared accounts where members issue Community Asset Vouchers, basically promises of future goods or labor) and runs on the Celo blockchain via USSD, so it works on basic phones without internet. It survives because it grew out of community networks that already had trust and coordination, and because no single person is load-bearing. The technology amplified an existing community; it didn’t manufacture one.

The Readiness Test

Run these three before you launch anything financial.

1. Organize one small thing. A monthly potluck where five people contribute and show up. A tool library people actually use. A skill share with three teachers and five attendees. If you can’t reliably coordinate a shared meal, you can’t coordinate a treasury.

2. Handle one small conflict. Manufacture a low-stakes decision people genuinely disagree on (a venue, a meeting format, how to spend a small budget) and watch. Do people listen, compromise, steamroll, or go silent? That’s a live preview of how governance behaves once real money is on the line.

3. Sustain effort for three months. Every project has a honeymoon: high attendance, big dreams. Then someone gets busy, someone gets bored, a holiday lands. The people still engaged at month three are your real founders. If you haven’t hit that threshold yet, keep running low-stakes activities until you have a proven core.

If You’re Not Ready Yet

That’s information, not failure. Launching early wastes energy and leaves a bad taste that makes the next attempt harder; communities remember projects that promised a lot and delivered nothing.

Build the substrate instead: regular meetups (consistency beats content), small collaborative projects, trust-building shared meals and skill swaps, and one communication channel people actually use. The node will still be there in six months. The relationships and shared habits you’re building now are the infrastructure it will run on.

If You Are Ready

Start tiny. Run one simple exchange, a 10-member timebank or a treasury for one specific purpose, not 47 features. Then write things down before money enters: who’s responsible for what, how decisions get made, what happens when a key person leaves, how new members join, and what happens to shared funds if the group dissolves. It doesn’t need to be a legal document. A shared doc is enough. Verbal agreements are fine for cooking together; they are not fine for a treasury.

Then set a review date three months out: is this working, what changes, do we continue, pivot, or pause? A scheduled review gives everyone permission to be honest, instead of waiting for the slow death where no one wants to say it’s not working. Then launch. Done beats perfect. The right time to polish governance is after a month of actually using it.

Try This

Start here: Score your group, today, on a 1-to-5 scale for each: five-plus people who show up consistently; you’ve organized something together before; you’ve survived a disagreement; people can say why beyond the tech; you’ve pooled money before; three-plus people engaged for three months. Total of 25-35, you’re likely ready. 15-24, you have gaps, work the lowest scores. Below 15, build community first.

Go deeper: Run Test 2 for real. Put a genuine low-stakes decision (how to spend a small shared budget) to the group this month and take notes on how the conversation goes. Bring the notes back as your honest governance baseline.

Stretch: Map your single points of failure. List every recurring task that keeps the group alive and write a name next to each. Anywhere the same name appears three or more times, that’s your Ithaca Hours risk. Redistribute at least one of those roles before you launch.

References

Community Readiness Model, Tri-Ethnic Center, Colorado State University - the nine-stage framework and assessment manuals.
Grassroots Economics: Sarafu Network - the living example: commitment pools and Community Asset Vouchers across 290+ Kenyan communities.
adrienne maree brown, Emergent Strategy (AK Press, 2017) - on building through experimentation and relationship rather than master plans.
Ithaca Hours (Wikipedia) - the cautionary tale of a local currency that depended on one person.
Greenpill Network - the local-node network this guide assumes you’re plugging into.