Eden+Fractal Implementation Plan

Introduction

This implementation plan serves as a technical coordination document for reviving the Eden+Fractal consensus process during the second half of Eden Fractal's first season of Epoch 2. After extensive community discussions during our first five events of the season, we are preparing to implement this proven legislative consensus mechanism that will complete our tripartite governance structure alongside ORDAO (executive) and the Respect Game (judicial).

The purpose of this document is to coordinate the technical requirements, specifications, and implementation details needed to successfully launch Eden+Fractal. This is primarily a planning and coordination resource for those actively involved in building and implementing the process. For a general introduction to Eden+Fractal and information about becoming a delegate, please see our community guide at edenfractal.com/plus.

To implement Eden+Fractal successfully, we need to address several technical requirements and create clear specifications for how the process will work with our current bi-weekly event schedule and Base infrastructure. This document outlines these requirements and provides a space for collaborative problem-solving as we work toward implementation.

Table of Contents

1. Introduction
2. What is Eden+Fractal?
3. Historical Context
4. Technical Requirements and Challenges
5. Proposed Solutions
6. Updated Specifications
7. Benefits and Challenges
8. Governance Integration
9. Implementation Discussion Questions
10. Next Steps
11. Resources

What is Eden+Fractal?

Eden+Fractal is an innovative consensus mechanism that elegantly combines two foundational processes from fractal democracy: Eden Elections (also known as upvote elections) and the Respect Game inspired by ƒractally. The process works by having community members both play the Respect Game to measure contributions AND elect delegates during the same breakout room sessions.

Here’s how it works:

1. During each Eden Fractal event, after playing the Respect Game in breakout rooms, each room elects one delegate.
2. These delegates form councils that serve for four events, and we always have four councils active at once.
3. When the community needs to make a decision, it requires approval from at least three of the four councils.

Proposals can only be approved during biweekly Eden Town Hall events, which occur immediately after Eden Fractal Respect Games. This creates a balanced system that is both democratic and efficient, allowing for quick decision-making while ensuring broad consensus.

Historical Context

The Eden+Fractal consensus process was originally proposed by Tadas on October 2nd, 2022, this process was approved by the Eden Fractal community in Meeting 18 and successfully operated for over a year during Epoch 1. The Eden Fractal community successfully implemented the Eden+Fractal process from approximately Meeting 19 through Meeting 80, passing over 10 proposals including meeting time changes, moderator elections, and various community initiatives. You can view the historical record of all delegates and proposals in this spreadsheet, which provides valuable context for our current implementation.

The name "Eden+Fractal" reflects its historical origins, combining the upvote election process pioneered by Eden on EOS with the contribution measurement system the Respect Game (inspired by Fractally). While the original communities that inspired these names have evolved or concluded, the powerful synthesis of their innovations continues to provide value for fractal governance. The comprehensive article at EdenCreators.com/plus provides additional historical context and analysis of the benefits this process has demonstrated.

The process was originally featured in Creator Talk Episode 1, where Dan Singjoy interviewed Tadas about the design philosophy and potential of Eden+Fractal. This conversation, recorded shortly after the initial proposal, explores how the process emerged from months of community discussion and represents a synthesis of the best aspects of various consensus mechanisms.

Recent Developments

More recently, during Eden Fractal Meeting 118, we discussed reintroducing Eden+Fractal as part of our Epoch 2 vision. This discussion highlighted how the process fits into our broader governance framework and explored various options for our legislative needs. In the most recent Eden Town Hall event, we formed consensus on using the Eden+Fractal consensus process. Both of these videos are provided below for context.

Technical Requirements and Challenges

1. Delegate Selection Interface

The Challenge: We currently lack a frontend interface for delegate selection in our Fractalgram implementations. The original EOS version included this functionality directly in the Telegram client, allowing seamless delegate election at the end of each breakout room. However, neither Tadas's current EVM Fractalgram version nor Abraham's web application includes this critical feature.

Why This Matters: Without an integrated interface, the delegate selection process becomes cumbersome and may be forgotten or skipped by breakout rooms. The smooth user experience is essential for consistent implementation and community adoption.

Previous Solution on EOS: The Telegram bot would prompt each room to select a delegate after rankings were complete, recording the selection directly to the blockchain. This created a seamless experience where delegate selection felt like a natural extension of the Respect Game.

Current Status: As of August 2025, we have confirmed that neither Fractalgram implementation includes delegate selection functionality. This represents our most significant technical barrier to implementation.

2. Smart Contract Recording

The Challenge: We need a reliable on-chain mechanism for recording delegate selections on Base. This ensures transparency, prevents disputes, and enables automated proposal tracking.

Previous Implementation: On EOS, smart contracts automatically recorded delegate selections, tracked active councils, and managed proposal voting. This created a trustless system where results were verifiable by anyone.

Current Infrastructure: We have ORDAO deployed on Base, which could potentially handle delegate tracking through custom actions. However, this hasn't been specifically configured for Eden+Fractal's rolling council structure.

Critical Questions: Can ORDAO's existing infrastructure support delegate tracking? Do we need custom smart contracts? How do we ensure the four-council rotation is properly maintained on-chain?

3. Bi-Weekly Event Adaptation

The Challenge: Eden+Fractal was designed for weekly events, where a four-week commitment meant one month of service. With our current bi-weekly schedule, four events span two months, potentially creating a barrier to participation.

Impact on Participation: Asking delegates to commit for two months may discourage participation, especially from community members with uncertain schedules. This could result in incomplete councils and difficulty reaching quorum for decisions.

Design Considerations: The four-council structure is fundamental to Eden+Fractal's balance between efficiency and democracy. Reducing to two councils would fundamentally alter the consensus mechanism and potentially concentrate power too much. We need to carefully consider whether the longer commitment period is acceptable or if we need alternative solutions.

Proposed Solutions

Immediate Workaround (For Potential August 28th Implementation)

Given our technical constraints, we propose the following interim solution that could enable us to begin using Eden+Fractal while we develop more sophisticated infrastructure:

Delegate Selection Process: After completing the Respect Game rankings in each breakout room, participants will navigate to eden.frapps.xyz and create a Custom Signal proposal. The proposal title would follow the format: "Elect [Delegate Name] from Room [Number] - Event 127". All room members would then vote on this proposal before leaving the breakout room.

Tracking and Verification: We'll maintain the existing Google Spreadsheet as our primary tracking mechanism, with on-chain proposals serving as verification. This creates redundancy and allows for easy community review of active councils.

Commitment Flexibility: While we'll ask delegates to commit to four events (two months), we'll establish clear communication channels for delegates who cannot attend specific events. Written votes submitted via Telegram before Eden Town Hall would be accepted, ensuring decisions can proceed even with some absences.

Long-term Technical Development

Fractalgram Integration: Work with Tadas and Abraham to integrate delegate selection directly into both Fractalgram implementations. This would restore the seamless experience we had on EOS and should be prioritized for development during the season.