Skip to content

docs: Community background and forum discussion index#33

Open
glandua wants to merge 1 commit intomainfrom
docs/community-alignment-evidence
Open

docs: Community background and forum discussion index#33
glandua wants to merge 1 commit intomainfrom
docs/community-alignment-evidence

Conversation

@glandua
Copy link
Contributor

@glandua glandua commented Mar 18, 2026

Summary

Adds docs/community-background.md — indexes 2+ years of community PoA discussions and provides alignment evidence for the M012-M015 mechanism specs.

  • Complete timeline from mainnet launch (Apr 2021) through present
  • Key community positions (Will Szal, Gregory, Max, brawlaphant, James Bettauer)
  • Governance audit findings (65% voting power concentration, 25% turnout)
  • Historical validator set trajectory (50→75→~21→PoA)
  • Current validator reality (all operating at a loss)
  • The founding vision quote: Regen was originally a "consortium blockchain model"

Why This Matters

The mechanism specs are technically excellent but lack community context. New contributors and reviewers need to understand the 2+ years of deliberation behind these proposals. This is the "why" companion to the technical "how."

Source Material

Synthesized from KOI knowledge base searches, direct forum fetches, and Notion document retrieval across:

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces crucial documentation to provide historical and community context for the Regen Network's Proof of Authority (PoA) migration and economic reboot mechanisms. It aims to bridge the gap between the technical specifications and the extensive community deliberation that has shaped these proposals over the past two years, ensuring new contributors and reviewers have a comprehensive understanding of the 'why' behind these significant changes.

Highlights

  • New Documentation: Added docs/community-background.md, a new document that indexes over two years of community discussions regarding Proof of Authority (PoA) and economic reboot mechanisms (M012-M015).
  • Historical Context: The document provides a complete timeline of PoA discussions from mainnet launch (April 2021) to the present, including key community positions and governance audit findings.
  • Validator Trajectory and Reality: Included details on the historical trajectory of the validator set, its current state (with validators operating at a loss), and how these factors support the case for PoA.
  • Founding Vision Alignment: Highlighted that the PoA migration aligns with the network's original founding vision as a 'consortium blockchain model'.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new documentation file, docs/community-background.md, which provides valuable historical context and a discussion index for key economic and governance mechanisms. My review focuses on improving the document's usability and correctness. I've identified a potentially broken external link and suggested converting plain text file paths into clickable relative links to enhance navigation for readers.

| Oct 2025 | Governance findings audit published | [#539](https://forum.regen.network/t/regen-s-governance-findings-for-decentralized-and-regenerative-daos/539) |
| Oct 2025 | Tokenomics architecture checklist summary | [#538](https://forum.regen.network/t/regens-tokenomics-architecture-checklist-summary/538) |
| Dec 2025 | **Economic Reboot Roadmap v0.1** — 4 workstreams synthesized | [#567](https://forum.regen.network/t/regen-economic-reboot-roadmap-v0-1/567) |
| Jan 2026 | **Comprehensive Governance & Economic Architecture Upgrade** drafted | [Notion](https://www.notion.so/Draft-Comprehensive-Proposal-Regen-Network-Governance-Economic-Architecture-Upgrade-2fb25b77eda180af8742debdfaed0b3c) |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The Notion link appears to be broken as it seems to be missing the /regennetwork/ path segment. A similar link in another document includes this segment, which is common for shared Notion pages. Please correct the URL to ensure it's accessible.

Suggested change
| Jan 2026 | **Comprehensive Governance & Economic Architecture Upgrade** drafted | [Notion](https://www.notion.so/Draft-Comprehensive-Proposal-Regen-Network-Governance-Economic-Architecture-Upgrade-2fb25b77eda180af8742debdfaed0b3c) |
| Jan 2026 | **Comprehensive Governance & Economic Architecture Upgrade** drafted | [Notion](https://www.notion.so/regennetwork/Draft-Comprehensive-Proposal-Regen-Network-Governance-Economic-Architecture-Upgrade-2fb25b77eda180af8742debdfaed0b3c) |

Comment on lines +114 to +116
- M014 spec: `phase-2/2.6-economic-reboot-mechanisms.md`
- Cosmos Labs x/poa: `docs/cosmos-poa-module.md`
- Bioregional validator framework: `docs/bioregional-validators.md`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To improve usability, the file paths in the "Related" section should be converted to clickable relative markdown links. This will allow readers to easily navigate to these documents. The link for the M014 spec can also be improved to point directly to the relevant section.

Suggested change
- M014 spec: `phase-2/2.6-economic-reboot-mechanisms.md`
- Cosmos Labs x/poa: `docs/cosmos-poa-module.md`
- Bioregional validator framework: `docs/bioregional-validators.md`
- M014 spec: [`phase-2/2.6-economic-reboot-mechanisms.md`](../phase-2/2.6-economic-reboot-mechanisms.md#protocol-specification-m014)
- Cosmos Labs x/poa: [`docs/cosmos-poa-module.md`](./cosmos-poa-module.md)
- Bioregional validator framework: [`docs/bioregional-validators.md`](./bioregional-validators.md)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant