👋 Introduction

This guide will walk you through how to set up a yodl community. A curated version of Yodl Pay configured through an ENS domain. The setup makes it easy to create a permissionless, composable space for communities.

Each community consists of a curated set modular yodl mini-apps called Yapps, such as message boards, subdomain claimers, or shops. You can create unlimited sections, decide which yapps to include, how they are organized, and who can access them.

Communities are configured through two ENS text records:

  1. me.yodl.type → community
  2. me.yodl.community → your JSON config

From these two records, yodl renders your community. You can also optionally use EFP (Ethereum Follow Protocol) to define who is a member. Anyone who follows your community ENS on EFP is considered a member and can be granted access to specific sections and Yapps within your community.

Yodl communities are powered using 3 key components:

Tech What it does
ENS Your community’s identity. Stores your configured JSON data.
EFP (Ethereum Follow Protocol) Defines your community members. Followers of your ENS domain on EFP are considered members.
Yapps yodl mini-apps (like message boards, claiming community subdomain, merchant shops, etc.). Each one is tied to an ENS domain.

Live example of a yodl community: https://yodl.me/c/builders.yodl.eth

Screenshot 2025-05-22 at 15.42.10.png

🧠 Understanding your yodl community config

Communities are fully configured and managed permissionlessly using your ENS domain. No frontend or backend deployment needed.

To launch your community, you need to set 2 custom ENS text records on your ENS domain:

ENS text record Value Purpose
me.yodl.type Must be set to community Identifies the ENS domain as a yodl community
me.yodl.community Contains the JSON configuration blueprint for the community. Defines layout, visibility, membership, and feautred Yapps.