This is a poll to determine priority of topics at the time of period 134 of Eden Fractal. It is part of stage 2 of Synchronous Respect Tree V1 game.

Spread your Respect-weighted votes among topics according to your understanding of what topics are the most important to discuss right now. This will help determine our discussion topics for the upcoming town hall and the following week.

Note

Snapshot only allows me to create 9 choices in the poll and there were 10 topics proposed, so I am merging the topic proposals about 2026 Resolutions and Break Planning in the voting options. I chose to merge these because they had short names (which matters since Snapshot also limits each voting option name to 32 characters) and they seemed like related topics that could be grouped together. I also needed to shorten some of the text in the topic proposals to fit within the 10k character limit on snapshot.

Topic Proposals

From Tadas

TP: Update our ORDAO configuration

Current configuration of Eden Fractal's ORDAO was meant to be temporary to allow old participants to claim their old respect before any contentious ORDAO proposals are executed. Current configuration is also becoming too limiting when we start passing more proposals per week.

I propose to make the these configuration changes: https://hackmd.io/@sim31/ef-ordao-config-update

This will only take a moment to pass and then we can move on to the next topics.

I already made ordao proposals that would implement these changes in 18 days, assuming we don't cancel it before then:

• Set periods
• Set max live yes votes

TP: SRT V1 improvements or feedback

We've already started discussing this in Eden Town Hall 72.

Relevant topic from previous period introduces some of the problems and potential solutions.

Some new key ideas I took away since our last discussions:

⦁ 1. Use SRT V1 as flat issue tracker instead of as a tree?

⦁ 2. Contribution Requests and Contributions are one and the same?

TP: Eden Fractal 2026 Resolutions

As we embark on a new year and a new season, it’s worth taking some time to align on what we hope to accomplish. Eden Fractal is almost four years old, and while we've made tremendous progress in developing fractal governance tools and processes, our core mission of implementing fractal decision-making throughout society remains a work in progress.

See more in the original post: https://t.me/edenfractal/5562/5959

TP: Fractalgram

Fractalgram has been a major topic of discussion over the past several weeks, and our community has been actively working to specify how the next generation of this essential tool should be built. As the primary interface for playing the Respect Game at our events, Fractalgram is central to Eden Fractal's operations and to the broader fractal ecosystem's ability to scale governance processes...

See more in the original post: https://t.me/edenfractal/5562/6193

From Dan

TP: Eden Fractal Community Agreement

Creating a community agreement has been one of our outstanding goals for years, and it's becoming increasingly important as we work toward scaling our processes in the new year. A clear agreement helps set expectations, protect the community, and provide a foundation for scaling — including making it clear that Respect tokens represent community opinions, establishing consent for video recording and content sharing, and defining governance participation expectations.

We've discussed this extensively over the years, including detailed conversations during Eden Fractal events 37 and 38 and in related communities. We now have a legislative consensus process through Eden+Fractal to formally approve such an agreement, which removes a key blocker. I'm working on resources to help us coordinate on this, and this is a great topic for the community to start discussing. The agreement could potentially be stored in Firmament on GitHub as a communally approved document. This is a topic worth discussing at our upcoming town hall as we consider scope, priorities, and next steps.

TP: Eden Fractal Intent Document

Eden Fractal needs its own Intent Document, envisioned as an operating manual for community coordination that clearly defines technical specifications, governance processes, and community expectations. Optimism Fractal's Intent Document provides a strong starting point — it covers Respect Game meeting structure, distribution amounts, the consensus process, council formation, the executive contract, and more, and has been updated multiple times through their community's own consensus process as the community evolved.

As a first step, we can use Optimism Fractal's document as a foundation and then decide what should be tailored to Eden Fractal's unique structure and Epoch 2 operations. The document would be drafted through community collaboration, approved via our consensus process, and include mechanisms for future modifications. This would be a valuable topic to discuss at our upcoming town hall as we consider the scope, structure, and approach.

TP: Eden+Fractal Improvements

Eden+Fractal is our legislative consensus process for choosing delegates, deliberating on decisions, and making community decisions. The process was first introduced around Eden Fractal's 20th event back in 2022, and we've been practicing it consistently for the past six months during Epoch 2. When we started adopting it for Epoch 2, I created an implementation plan to guide how we'd operate it, informed significantly by discussions with Tadas and the community back in August and September 2025.

It's been working well, but there are areas for improvement. More details: https://t.me/edenfractal/5562/6282

TP: Recognizing Prior Contributions to Eden Fractal

Eden Fractal did not distribute Respect tokens between approximately events 63 and 120, which represents roughly a third to 40% of our total 135 events. This is a significant gap given that recognizing contributions is one of our core functions.

There are two distinct periods to consider. For events 63–83, Respect Games were played and consensus results were posted on EOS, but tokens were never distributed due to issues with the Eden Fractal MSIG. Records exist in video timestamps, consensus results posts, and onchain transaction history. For events 83–120, no Respect Games were played, but many people contributed significantly during this pivotal time for fractal governance development and received no Eden Fractal Respect.

Currently, the ORDAO account is controlled primarily by participants from Eden Fractal's first year and a half, with no recognition for contributions from approximately year 2 through year 3. One idea I'm exploring is using an AI agent to review the videos from events with no respect games and generate attendance records to help inform retroactive Respect distribution proposals. I have some draft notes about this and am working on a more detailed article.

We could also begin considering higher-order fractal considerations. See more details here: https://t.me/edenfractal/5562/6283

TP: Break Planning & Daylight Saving Time

We're on the 7th week of events this season, heading into the 4th Respect Game, with the 5th Respect Game of the season on March 12 and the 6th on March 26. Traditionally, we do about 12 weeks of events before taking a mid-season break, so as currently scheduled, a break would come around the end of March.

This is a good time to start discussing the timing and duration of that break - whether to follow the traditional schedule, or perhaps whether it would be better to take the break a bit earlier to focus on infrastructure improvements and preparation for the second half of the season. We'd also want to determine how long the break should be.

Also worth considering: US daylight saving time begins on March 8 (clocks move forward one hour), and Europe's summer time begins on March 29. Between March 9 and March 28, the time difference between the US and Europe temporarily shifts by one hour. For our events scheduled at a fixed UTC time, this means European participants may find the event falls one hour later in their local time after March 29 than it did before. We can discuss whether any schedule adjustments make sense.

TP: Exploring Matrix

I've been learning about Matrix over the past week and wanted to share some of what I've found. Matrix is an open-source, decentralized communication protocol that can do similar things to Telegram or Discord, but it aligns more closely with Eden Fractal's values around openness, decentralization, and composability — meaning we can build with it and on top of it.

Matrix has a spec-driven development process with a governance and proposal system on GitHub that could serve as useful inspiration as we start using spec-driven development ourselves. They also have both a federated version and are building Matrix P2P, a non-federated peer-to-peer version that shares some of the same goals that Dan Larimer's team had with Clarion OS. The project has been in development for over 10 years.

Learn more here: https://t.me/edenfractal/5562/6285