Types of Gatherings for Local Nodes

You’ve decided to start a local node. Now you’re staring at a blank calendar, wondering what to actually do when people show up, and quietly dreading the version where you pour months into events that fizzle, or burn out hosting a weekly meetup nobody asked for.

Here’s the relief: you don’t need one perfect event. You need a small repertoire of formats and the judgment to pick the right one for where your community is right now. A local node (a self-organizing local chapter of a regen network like ReFi DAO or the GreenPill Network, running its own experiments on the ground) lives or dies on how well it gathers. This guide gives you the formats, when to use each, and how to keep them light enough to sustain.

One rule before the menu: the format determines the outcome more than the topic does. A lecture on “community governance” produces passive listeners. The same topic run as a fishbowl discussion produces engaged co-thinkers. Same content, opposite results. Choose the container deliberately.

Informal Gatherings: Building Relationships

These are the foundation. No agenda, no slides, no governance. Just people in a room becoming people who trust each other. Skip this layer and everything you build on top of it wobbles.

The Community Meal

People eat together. That’s the entire format.

Why it works: Sharing food is one of the oldest trust-building mechanisms we have, and the effect shows up in the research. People who eat socially more often report trusting others more, feeling happier, and being more engaged with their local community (Dunbar, 2017), and the causal arrow runs from eating together to bonding, not the reverse. It’s also the lowest possible barrier to entry: everyone already knows how to eat.

This isn’t just theory. ReFi Cape Town, one of ReFi DAO’s first-cohort local nodes, built itself through regular in-person gatherings before layering on its “serious” programming, and those relaxed gatherings are often where the relationships that carry a node form.

When to use it: Early on, before you introduce any web3 concept. After tension or conflict, to rebuild connection. And as a steady baseline: a monthly potluck people can count on.

Make it work:

Use a potluck. Shared effort creates shared investment, and means you aren’t cooking for twenty.
Keep it consistent: same week each month, same rough time, so people can build it into their lives.
No mandatory agenda. The meal is the point.
One person owns venue and reminders. Consistency needs a single owner, not a committee.

The mistake to avoid: turning dinner into a meeting. Resist “while we’re all here, let’s just quickly…”. That instinct quietly kills the thing that makes meals work.

The Walk-and-Talk

A small group of two to six people walks while they talk.

Why it works: Side-by-side movement lowers the intensity of eye contact and makes hard conversations easier. Movement also helps thinking: in a Stanford set of experiments, the large majority of people (between 81% and 100%, depending on the test) produced more creative ideas while walking than while sitting, indoors or out, and walkers roughly doubled their novel responses (Oppezzo & Schwartz, 2014). The walking itself did the work, not the scenery.

When to use it: One-on-one relationship building. Processing a thorny decision before it hits the whole group. Brainstorming a new initiative. Or simply when someone needs to be heard and a formal meeting feels too heavy.

Make it work: Pick a route without traffic noise. Aim for 45-60 minutes. Pairs go deeper; groups of four to six stay lighter. Have a rain backup.

The Open House

A recurring drop-in window (say, Saturday mornings 10am, 1pm at the same café) where people come and go as they like.

Why it works: It removes the pressure of a fixed start time and a commitment to “the whole thing.” People arrive when they can and stay as long as they want. Over time it becomes a heartbeat, a place the node reliably is.

When to use it: When your members have scattered schedules, as a no-pressure on-ramp for newcomers, and as a steady touchpoint once you’re established.

🔄 For node-builders: The open house is your best burnout defense. It costs almost nothing (you show up, you don’t perform) and it keeps the node visible between bigger events. If you commit to only one recurring thing, make it this.

Educational Gatherings: Building Skills

Once people trust each other, they’re ready to learn together. The trap here is defaulting to lecture mode. People don’t gain skills by hearing about them.

The Workshop

A hands-on session where people learn by doing: setting up a wallet, writing a proposal, using a governance tool.

Why it works: Practice builds competence and confidence at once, and a hands-on session is how loose interest becomes a working group. It helps to host in an accessible public space. ReFi Barcelona, for instance, maps the Canòdrom, Barcelona’s public digital-innovation and democracy centre, as an aligned local venue for exactly this.

When to use it: Onboarding members to web3 tools, or closing a specific skill gap that’s blocking participation.

Make it work:

Cap hands-on workshops at around 15 people. One facilitator can’t help more than that.
Pre-install software and create accounts before the session. Don’t burn workshop time on setup.
Pair an experienced member with each newcomer. Peer learning beats lecture.
Budget “things will break” time. Tech always runs long.
Send people home with a takeaway: a cheat sheet or a recorded walkthrough.

The Learning Circle

A group meets regularly to explore a topic together: a short reading, a video, an article. No expert at the front; everyone learns at once.

Why it works: Shared learning builds shared vocabulary. When everyone reads the same piece on, say, quadratic funding, you develop a common language for the decisions that come later. It also relieves you of being the resident expert on everything, a fast route to burnout.

When to use it: Building shared understanding of something genuinely complex (governance, tokenomics, cooperative principles) that none of you has fully mastered.

Make it work: Short readings only, 5-10 pages a session, never a whole book. Rotate facilitation so ownership spreads. Use a few prepared questions to keep it from meandering. Run four to eight sessions on a theme, then switch or pause. Capture the key insights: that record becomes your node’s knowledge base.

The Demonstration Day

Members show what they’ve built, found, or broken. A science fair for community tools.

Why it works: It celebrates progress, spreads useful knowledge, and surfaces quiet experts. When one member figures out how to bridge tokens cheaply, a demo day means everyone benefits instead of just them.

When to use it: Quarterly, when several members are experimenting in parallel, or when the node needs a visible reminder that it’s actually building something.

Decision-Making Gatherings: Choosing Together

This is where the fear of “central overreach” gets real. If decisions feel like they’re handed down from you or from the parent network, people disengage. The formats below exist to make decisions transparently shared, which is the whole point of a node.

The Town Hall

A structured meeting where proposals are presented, discussed, and decided.

Why it works: Visible decision-making builds trust. When everyone can see how a call was made, even people who disagree with the outcome feel respected, and stay.

When to use it: Treasury allocations, policy changes, welcoming new partners, annual planning.

Make it work:

Circulate proposals at least a week ahead. Don’t ambush people with complex decisions.
Use a facilitator who isn’t invested in the outcome.
Time-box each proposal (around 15 minutes).
Use consent-based decision-making, drawn from sociocracy: instead of “Does everyone agree?”, ask “Does anyone object?” and “Can you live with this?”. Consent means no remaining objections, not unanimous enthusiasm (Sociocracy For All). It’s faster than consensus and more inclusive than a majority vote, which is why distributed communities lean on it.
Publish the decision within 24 hours.

💡 Going deeper: Consent-based decision-making is also what most on-chain governance tries to approximate. Practicing it offline, where you can read the room and repair tension live, makes your eventual move to tools like Snapshot or a multisig far smoother, because people already trust the underlying process.

The Retrospective

A structured look back at a project, period, or event: what worked, what didn’t, what we’d change.

Why it works: Teams that reflect improve; teams that don’t repeat their mistakes. The format comes from agile software practice (Norm Kerth’s Project Retrospectives (2001) is the origin text) and rests on one ground rule he called the Prime Directive: assume everyone did the best job they could with what they knew at the time (Agile Retrospective Resource Wiki). That assumption is what makes honesty safe.

When to use it: After every significant event or project, quarterly for general operations, and whenever something went notably right or wrong.

Make it work: Use a simple frame: “What went well? What didn’t? What should we change?” Focus on systems and processes, never on blaming individuals. Commit to specific changes, not vague good intentions. And revisit last time’s commitments before generating new ones, or the retro becomes theatre.

Celebration Gatherings: Marking What Matters

Community work often feels like an endless slog. Celebration is what reminds people it’s real, and it’s the antidote to the slow disengagement that kills nodes.

The Milestone Party

Celebrate concrete wins: your first 50 members, your first treasury allocation, your first funded project, your first year.

Why it works: Celebration reinforces identity and belonging. People need to feel their contributions added up to something. Mark the milestones, or they pass unnoticed and motivation quietly leaks away.

When to use it: Any meaningful threshold (membership, treasury, impact, anniversary), and especially when energy is flagging.

The Open Celebration

A public-facing party that invites the wider community to see what your node is about. Part celebration, part recruitment, part gift to the neighborhood.

Why it works: It lowers the barrier dramatically. People who’d never attend a “web3 meetup” will happily come to a party, and once they’re in the room, they meet the community, not the jargon.

Choosing the Right Format

Match the format to where your node actually is, not where you wish it were.

Node stage	Best formats
Pre-formation (building relationships)	Meals, walks, open houses
Early formation (building skills)	Workshops, learning circles
Active operations (making decisions)	Town halls, retrospectives
Growth (attracting members)	Demo days, open celebrations
Renewal (re-energizing)	Meals, milestone parties, retrospectives

Rhythm matters as much as format. A sustainable node might run:

Weekly: an open house (low effort, high consistency)
Monthly: a community meal plus one focused gathering (workshop or town hall or learning circle)
Quarterly: a retrospective plus a celebration

Notice how little of that is high-effort. ReFi DAO’s own global cadence is one recurring touchpoint, a community call on the third Thursday of each month, and that single steady beat helps hold a worldwide network together. Predictability, not intensity, is what sustains a node without burning out its host.

Moving Forward

Start with what your group already gravitates toward. If they like to eat, start with a meal. If they like to learn, start with a learning circle. The format people naturally lean into is the right place to begin, and a small, real gathering beats an ambitious one that drains you. Then add formats as needs emerge: a town hall when a decision arrives, a demo day when someone learns something useful, a party when energy dips.

The nodes that last aren’t the ones with the fanciest governance tools or the biggest treasuries. They’re the ones that gather regularly, intentionally, and with genuine care for the people in the room. Everything else is infrastructure in service of that.

Try This

Start here: Look at the stage table above and name honestly where your node sits today. Pick the one format that matches, and schedule a single instance of it in the next three weeks. Just one. Don’t build a calendar yet.

Go deeper: Run a community meal as a potluck, then deliberately practice restraint: resist every urge to “make it productive.” Afterward, jot one note on what relationships formed that a formal meeting wouldn’t have produced. That note is your evidence for why the informal layer matters.

Stretch: Run your first town hall using consent-based decision-making on a small, real choice (where to spend $100 of treasury, which café for the open house). Circulate the proposal a week ahead, facilitate with “Does anyone object?” and “Can you live with it?”, and publish the outcome within 24 hours. Then run a 20-minute retrospective on the town hall itself, and let what you learn shape the next one.

References

ReFi DAO, the regen network and its directory of local nodes; the source for the ReFi Cape Town and ReFi Barcelona examples and the third-Thursday monthly community-call cadence.
GreenPill Network, a regen network of local chapters; a sister model to ReFi nodes for grounding the “local chapter” pattern.
Dunbar, “Breaking Bread: The Functions of Social Eating” (2017), UK survey study linking how often people eat socially to trust, happiness, and local community engagement; the evidence behind the community meal.
Oppezzo & Schwartz, “Give Your Ideas Some Legs” (APA, 2014), the Stanford walking-and-creativity experiments behind the walk-and-talk.
Canòdrom, Barcelona’s Ateneu d’Innovació Digital i Democràtica, the public civic-tech venue ReFi Barcelona maps as an aligned local space for workshops.
Priya Parker, The Art of Gathering, the foundational text on designing intentional gatherings; pairs with this node’s “gatherings pattern” article.
Sociocracy For All, Consent Decision-Making, the source and practical how-to for the “Can you live with it?” decision method.
The Prime Directive, Agile Retrospective Resource Wiki, Norm Kerth’s blameless ground rule from Project Retrospectives (2001), the origin of the structured retro.
The World Café, Juanita Brown’s method for participant-driven small-group conversation, useful inside town halls and learning circles.
Open Space Technology, Harrison Owen’s self-organizing format for larger, agenda-less gatherings.
Liberating Structures, a free menu of 33 facilitation microstructures (start with 1-2-4-All) that replace lectures and managed discussion.