Cover photo

Crypto 101 | e40: From connections to communities

How Path's private, decentralized proximity can help people who already share a place find each other and organize, from a block party to a fundraiser, without making community membership, identity, or movement data a platform asset.

Crypto 101 is an educational series designed to make complex blockchain and decentralized infrastructure concepts accessible to everyone. Each edition explores a specific topic in depth, combining foundational knowledge with practical implementation examples from the Nodle ecosystem.

Crypto 101 e39 ended at the first encrypted conversation, the moment two people mutually chose to connect through Path. e40 asks what happens when that same mechanism is used by more than two people at once.

Once several people who share a place, a routine, or an interest have each opted in, how can they find one another and organize without a platform owning that discovery?

A community does not need a platform to find itself. It needs a way for people who are already nearby to recognize each other.

The problem with platform-owned discovery

Most community formation today still runs through centralized discovery: a public group listing, a searchable local feed, or an algorithm deciding which nearby event or circle gets surfaced to whom. To find people to organize with, someone typically has to make themselves visible to a platform first, posting a location, joining a public group, or opting into a directory that a company owns and can monetize.

That model puts a company between people who might already cross paths every day. It also means the record of who wanted to organize what, and with whom, sits on a server the participants do not control.

A block party does not need a directory. It needs neighbors who already recognize each other.

Path as the discovery layer for groups

post image

Path, introduced in Crypto 101 e39, was built around one-to-one discovery: two people's devices privately recognize a shared encounter, and a connection only surfaces once both opt in. The same underlying mechanism, built on Nodle's Whisper Connect proximity technology, extends naturally from pairs to groups.apps.apple

Instead of a single mutual match, several people who each opt in and each cross paths repeatedly in the same place, a park, a gym, a street of small businesses, a school pickup line, can be privately signaled that a cluster of nearby people share a recurring proximity. No one's identity is broadcast to the others by default. No central server holds a map of who was where. The decentralized, on-device matching that made a one-to-one Path connection possible is the same principle that lets a small group discover that they already share more than a sidewalk.

The people best positioned to organize something local are usually already near each other. They just have no private way to find that out.

From shared proximity to shared intent

Once several opted-in devices recognize a recurring shared encounter, each person decides independently whether to reveal a small bio and a stated intent, the same consent-based bio model from e39, but now visible to a small cluster rather than a single match. A person might indicate they are open to organizing a cleanup, splitting costs for shared gear, or planning a fundraiser. Only those who separately opt in become visible to each other as a potential group.

This keeps the formation of the group itself decentralized and consent-based. No one is added to a roster without choosing to be there, and no platform decides which nearby people should be introduced to which cause.

A group should form because its members chose each other, not because an algorithm decided they belonged together.

Where encrypted messaging fits in

post image

Once a small group has mutually opted in, they need a way to actually plan together, and this is where messaging becomes a supporting layer rather than the starting point. XMTP, the protocol covered in Crypto 101 e33, added end-to-end encrypted group chat built on the Messaging Layer Security (MLS) standard, the same IETF-ratified protocol used by Signal and WhatsApp, with forward secrecy, post-compromise security, and configurable group permissions. Network nodes relaying the messages cannot read their content and cannot reconstruct who is talking to whom, since group metadata is separately encrypted. Nodle's own v4 app release brought this capability into its wallet and messaging experience, noting that XMTP chats are "faster, cleaner, and now support group chats".xmtp+4

The chat is where a Path-discovered group turns intent into logistics: a date, a task list, who can bring tools, a voluntary contribution for supplies. But the meaningful decentralization happens earlier, in how the group found each other in the first place, not only in how it talks afterward.

It is worth being precise here: this is an enabling combination of proximity discovery and encrypted messaging, not a claim that every community feature, such as fundraising tools, task boards, or event ticketing, already exists inside the Nodle app today.

What this could look like

A handful of neighbors who keep noticing each other at the same park, each having opted into Path, are privately shown that they share a recurring encounter. One indicates an interest in organizing a cleanup. A few others separately opt in with the same intent. Only then does a small group form, and only then does a private, encrypted chat open for them to pick a date and divide tasks.

The same pattern applies to regulars at a climbing gym coordinating a race, parents at a school pickup line arranging a carpool, or small business owners on the same street planning a joint promotion. In each case, the people were already near each other before any app existed. Path's contribution is letting them discover that fact privately, and letting them decide, together, whether to act on it.

The technology does not create the community. It removes the platform that used to stand between people who were already close enough to form one.

The next layer of the sovereign stack

post image

Identity, proximity, consent, messaging, then coordination. Each edition in this arc has added one layer of user control:

Edition

Core question

Layer

e37

What should be public?

Identity

e38

Can people cross paths privately?

Proximity

e39

Can an encounter become a conversation consensually?

Connection

e40

Can consensual connections become communities?

Coordination

The outcome this stack points toward is not social media with crypto attached to it. It is decentralized infrastructure for people who want to find each other and act together, layer by layer, without handing ownership of discovery, identity, or communication to a platform.

The goal is not to replace every group chat with a token. It is to give groups a decentralized way to find each other and a choice about who owns their conversations afterward.

The promise of Path-based coordination is not that every neighborhood becomes a DAO. It is that ordinary people can find the others who are already near them and organize ordinary things, a game, a garden, a fundraiser, a celebration, without a platform standing between the discovery and the doing.

Glossary

Path - A private Nodle app feature that lets participating people discover potential connections after crossing paths, with identity shared only after mutual opt-in

Whisper Connect - Nodle's privacy-first proximity technology that powers Path's on-device, decentralized recognition of nearby participating devices

Decentralized discovery - A model in which people find each other through private, on-device signals rather than through a centralized platform directory or feed

Coordination layer - The part of the stack that lets a consent-based group plan, decide, and act together, sitting on top of identity, proximity, consent, and messaging

MLS (Messaging Layer Security) - An IETF-ratified encryption standard used by XMTP to secure both one-to-one and group conversations with forward secrecy

Forward secrecy - A security property ensuring that past messages remain unreadable even if a current encryption key is later compromised

Group metadata protection - XMTP's design choice to encrypt group welcome messages and membership data so that network nodes cannot reconstruct who is talking to whom