FEP stands for Fun Enhancement Possibility.
FEPs are the blueprints, protocols, and playful prototypes shaping the next chapter of the internet under the Web of Fun (WoF) initiative. They exist to document ideas, standards, and open-source experiments aimed at taking back ownership of the web and building fair, decentralized digital experiences.
Anyone can write and submit a FEP. Right now, the process includes a minor manual check to prevent spam, which will eventually be replaced by a permissionless Proof-of-Work (PoW) system.
Here is how to get your FEP published and discussed:
- Draft it: Fork this repository and create a new Markdown file for your proposition. Name it according to the next available number (e.g.,
12.md). - Open a PR: Open a Pull Request (PR) to this repository (
flokiorg/feps). - Share it in Discord: Join the Lokichain Discord and drop your PR link in the 💬 #discussion channel.
- Get the Role: A maintainer will do a quick validity check (we are not judging the idea, just filtering spam) and grant you the
@FEP Authorrole. - Publish & Discuss: Use your new role to create an official thread in the 🧩 #feps Discord forum.
Note for Authors: Once your FEP is live, you are responsible for maintaining your Discord thread, answering community questions, and updating your GitHub PR/Spec as the idea evolves.
| FEP | Title | Status |
|---|---|---|
| FEP-00 | Sharenote Protocol | Draft |
| FEP-01 | Zap Protocol | Draft |
- Draft: The FEP is currently being written, reviewed, or actively discussed in the Discord forum.
- Active: The FEP is considered a standard or a live experiment currently in use by the community.
- Final: The FEP is complete, successfully implemented, and no longer subject to major changes.
- Obsolete: The FEP has been superseded by a newer FEP or is no longer relevant.
- Rejected: The FEP was abandoned or deemed unworkable.
A good FEP should be concise, well-formatted, and easy to read. While we don't enforce a strict template, your Markdown file should generally include:
- Title & Author: At the very top.
- Abstract: A short, simple explanation of what the FEP does.
- Motivation: Why is this needed? What problem does it solve in the Web of Fun?
- Specification: The technical details, logic, or blueprints of how it works.
- Implementation (Optional): Links to any existing code or proof-of-concept.
All FEPs submitted to this repository must be placed in the public domain or licensed under CC0 1.0 Universal to ensure they remain free and open for anyone to build upon.