Respect Distribution Governance Considerations
Honoring Genesis Fractal and Eden Fractal Governance via ORDAO
As we prepare for Epoch 2, we have an important opportunity to consider how we honor the foundational contributions that have brought us to this point and ensure our governance represents the full spectrum of valuable contributors to our ecosystem.
Eden Fractal Events 75-120 Recognition
It makes sense to distribute respect for event participation in weeks 75-120 of Eden Fractal. These events were foundational and very important for Eden Fractal's development. Plus, it would be helpful to balance governance power with more recent contributors to Eden Fractal (such as Zaal, EZ, Rosmari, Eric, and others) who have been instrumental in our recent progress.
I believe this should be our highest priority, taking precedence over Genesis Fractal or other communities. It's important to first honor direct contributions to Eden Fractal, and then allow Eden Fractal community members to decide how to distribute respect among other fractals.
Eden Fractal Events 62-83
I recently realized that Eden Fractal hasn't distributed Respect tokens since it’s 62nd event. There are also additional events where we played the Respect Game and posted consensus results without distributing Respect.
After reviewing video timestamps, it appears that we played Respect Games continuously through event #74, skipped playing in events #75-76, then continued played variation of Respect Games for events 77–83. However, due to issues with the Eden Fractal MSIG, Respect has only been distributed on EOS (now Vaulta) up to Event 62.
The record of these activities exists in multiple places: the unapproved proposals in the Consensus Results topic of Eden Fractal chat, video timestamps for each video, and the Eden.Fractal account's onchain transaction history. Given this documentation, I believe we should enable participants to claim their earned Respect from events 62–83.
I could track this by creating a Google spreadsheet based on the youtube videos and EOS onchain results, though I'm uncertain whether we posted results onchain for every event. Alternatively, we might develop a script to count the onchain results more trustlessly, though I’m not sure what is the best approach and would appreciate hearing your feedback. Do you have any thoughts on this best way to handle this situation?
Higher Order Fractal Considerations
Genesis Fractal Integration
We should discuss whether it makes sense to honor Genesis Fractal respect in Eden Fractal governance via ORDAO. The Genesis Fractal community was very aligned with our current mission and foundational to our work. Many great contributors from that community may appreciate the opportunity to get more involved and be able to use their respect earned there. This could also make governance of Eden Fractal more decentralized and dynamic by expanding our governance base with proven contributors.
Other Communities to Respect
Several other fractal communities have made significant contributions to Eden Fractal's mission and development. These communities include Optimism Fractal, ZAO Fractal, AWF, and Aquadac. Integrating these communities into our governance structure could enhance decentralization, foster community growth, and strengthen our ecosystem's collaborative potential.
Proposed Distribution Model
I suggest implementing a percentage-based distribution system across fractals. This would involve increasing Eden Fractal's total respect by a predetermined amount (e.g., 10% or 50%) and then allocating this additional respect among participating fractal communities through a democratic voting process. The percentage distributed could be decided via Eden Fractal ORDAO and legislative consensus process.
While a metrics-based approach has been previously discussed (see Eden Fractal Documents), I believe that Respect Polls with predetermined distribution totals may provide greater flexibility and better leverage our established subjective consensus processes.
Quarterly Respect Distribution Framework
This initiative supports Eden Fractal's evolution into a higher-order fractal organization. I suggest implementing quarterly Respect Polls where community members can allocate Respect tokens to other fractals. Eventually these polls would be preceded by RetroPitch sessions, where representatives from participating fractals can present their progress and contributions during quarterly events. The polls could be onchain using Snapshot X and queried via The Graph, as explored in Retropolls.
For sustainable distribution, it may be helpful to allocate 1-5% of the total supply per quarter, with consideration for a diminishing issuance schedule. This approach would front-load distributions to provide stronger initial support for fractal communities during the beginning of Epoch 2.
Potential Communities
- Genesis Fractal
- Optimism Fractal
- ZAO Fractal
- Eden on EOS
- Established on-chain election processes
- Implemented NFT-based participation tracking?
- Served a foundational role for fractal development
- Could use a simple system, such as x% respect for Chief Delegates, y% respect for Delegates, and z% respect for voters
- Alien Worlds Fractal
- Upscale Fractal
- Aquadac
- Spanish Speaking Fractal
- Upland Aliens
- Respect.Games Distributions
- Participation in Eden Town Hall
- Participation in Optimism Town Hall
For a more comprehensive list of potential communities and their contributions, please visit Optimystics.io/communities.
Democratic Decision-Making Process
These decisions should probably be made by the Eden Fractal community via ORDAO itself. This approach honors the Eden Fractal community first and inherits legitimacy according to our respect game distribution, while also providing fairness and accuracy in recognizing contributions. The Eden Fractal community should seriously consider and probably approve these proposals, though implementation doesn't need to be immediate.
Technical Implementation Approach
It probably makes sense to create separate ORDAOs for Genesis Fractal (and other fractal communities) and for Eden Fractal events 75-120, so they're not confused with the original Eden Fractal distribution. Then we could create a separate aggregate ORDAO that combines them all. This way, all of these communities could still operate independently or be rewarded separately with an evolutionary structure.
We should explore whether this multiple ORDAO approach is technically difficult to implement. We need to consider ways to prevent misuse of funds, or perhaps ensure any funds can be automatically sent back or directed to our planned non-profit structure.
Conclusion
This represents an opportunity to build a more inclusive and representative governance system that honors our entire ecosystem's contributions while maintaining the integrity and legitimacy of our processes.
Riley Brown (@rileybrown) on X - Gemini is the only AI that can analyze videos quickly and accurately. Gemini can watch full 30-minute videos, pay close attention, and analyze them in seconds. It can WATCH the video. This is very useful for content workflows. The problem is that Gemini (right now) is not great at everything else. So at @agentnative_ we bundled that capability into a skill and gave it to Codex. Our editors use this before they start editing, and it makes the process about 2x faster. Which is insane.pro tip: google gemini is GOATED at video understanding you can upload video and it understands motion, progression, dialogue, music, etc astra and fable can’t do that. they’ll take screenshots and transcribe voices and try to understand what’s going on. but it’s not the same since astra and fable 5.1 were clearly trained on blender, they can do some moves that they know look good. but outside of their repertoire of party tricks they can’t really analyze the quality of a video they output. they can only analyze screenshots hook up the gemini api into your agent and tell it to use it for video analysis. you won’t regret itWe've run ~115K videos through Gemini in prod. Here’s what I’d recommend looking out for: 1. Gemini will sample at 1fps by default which misses lots of details, particularly motion related ones. You can configure Gemini to sample at higher fps, we use 10 fps. Just be careful because costs scale with the fps. 2. Gemini downscales your videos to 480p so don’t bother trying to increase the video resolution to get quality gains. 3. BUT if you do want quality gains a hack we’ve found is to send a bunch of high resolution screenshots together with the video file as input into Gemini, though this gets expensive fast. 4. If you’re trying to detect scene boundaries in a video, I highly recommend using ffmpeg for that first, then passing its output into Gemini together with the rest of your prompt. You get way better accuracy this way. 5. We’ve observed that Gemini is bad at being able to time speech, and while the latest agentic changes in Gemini may help, we’ve found that the new API errors out a lot, so in the meantime you can just use STT using a model like Chirp 3 and pass its speech/word timing into the prompt. You get nearly perfect word timing accuracy this way when talking to it. 6. Gemini sometimes struggles to classify audio like when someone is singing vs music is playing vs speaking. You can run a YAMNet model over the audio beforehand, and pass the outputs into Gemini, helping it to understand what kind of audio is occurring when. 7. Gemini sometimes struggles to tell coordinates on screen accurately, especially relating to faces, so you can use a YuNet model for face tracking and pass the outputs into Gemini with your prompt, giving it that capability. 8. I highly recommend adding a bunch of evals if you’re going to be doing this in your software so you can track regressions, otherwise it becomes impossible to know whether an issue you resolved through your prompt broke 20 other things