Skip to content

Feat/issue 302 305 governance and roadmap - #432

Merged
james2177 merged 4 commits into
stellar-vortex-protocol:mainfrom
aladi11isah:feat/issue-302-305-governance-and-roadmap
Sep 30, 2026
Merged

james2177 merged 4 commits into
stellar-vortex-protocol:mainfrom
aladi11isah:feat/issue-302-305-governance-and-roadmap

Conversation

@aladi11isah

Copy link
Copy Markdown

Governance & Roadmap: Treasury, Solver Vetting, Signaling & Public Roadmap

Summary

Implement four foundational governance and community infrastructure items for the Vortex Protocol:

Changes

  • ROADMAP.md — Public roadmap organized by theme (cross-chain proof, solver reputation, governance, monitoring, maintenance, parameters, security, integration, research)
  • docs/treasury-spending-governance.md — Treasury governance process, spending categories, discussion & approval workflows, reporting cadence
  • docs/verified-solver-program.md — Solver vetting criteria, application/review/revocation procedures, public list, application template
  • docs/305-reputation-weighted-signaling.md — Signaling mechanism, message format, Stellar signing, aggregator service, weight calculation, Python reference implementation
  • docs/SOLVERS.md — Public verified solvers list template with on-chain eligible vs. community-vetted distinction
  • tools/signal_aggregator.py — Reference aggregator implementation for signal collection, verification, weight aggregation, and result publishing
  • README.md — Added ROADMAP reference and governance documentation links

Closes

Closes #302
Closes #303
Closes #304
Closes #305

…y-spending governance process

- Create docs/treasury-spending-governance.md defining treasury spending governance
- Specify valid proposal categories (audits, ecosystem dev, research, infrastructure, grants)
- Document proposal process: 14-day RFC discussion, multisig approval, 14-day timelock
- Include time-sensitive expedited path for emergencies (3-day timelock, 0k cap)
- Define multisig approval thresholds and signer requirements
- Establish quarterly transparency reports and post-execution accountability
- Document treasury contract primitives needed from issue stellar-vortex-protocol#37
- Coordinate with issue stellar-vortex-protocol#112 (RFC process) and issue stellar-vortex-protocol#114 (multisig design)
… Solver vetting and endorsement program

- Create docs/verified-solver-program.md defining solver vetting criteria and process
- Vetting is informational only; does not gate on-chain participation
- Application requirements: identity disclosure, track record, operational-security attestation, references
- Vetting review by 2+ independent reviewers (target 10 business days)
- Revocation process for slash events, misrepresentation, or changed practices
- Create docs/SOLVERS.md as public tracker of verified solvers
- Distinguish community-vetted from on-chain eligible solvers
- Integration points: issue stellar-vortex-protocol#13 (solver registry), issue stellar-vortex-protocol#41 (leaderboard), issue stellar-vortex-protocol#57 (tier badge)
…admap notes into public ROADMAP.md

- Create comprehensive ROADMAP.md organizing all forward-looking work by theme
- Themes: cross-chain proof, solver reputation, governance/treasury, monitoring,
  contract maintenance, protocol parameters, security, integration, research
- Map scattered items from SECURITY.md, design docs, and README into status tracking
- Use clear status indicators: 🔄 In Progress, 🎯 Not Started, 🔍 Under Research, ✅ Shipped, 🚫 Out of Scope (v1)
- Document known limitations and mitigation timelines
- Cross-reference each item to related issues and design docs
- Update README.md to link to ROADMAP.md as primary reference
…on-weighted signaling tool

- Create docs/305-reputation-weighted-signaling.md specifying tool design
- Tool accepts Soroban-compatible signed messages from Stellar addresses
- Verifies signatures and aggregates results weighted by governance-weight formula (issue stellar-vortex-protocol#41)
- Output: human-readable sentiment report (JSON) for community proposal input
- Results feed into RFC governance process (issue stellar-vortex-protocol#112) before admin approval
- Support for for/against/abstain signals with optional rationale messages
- Latest-signal-wins deduplication to prevent vote manipulation
- Reference Python implementation: tools/signal_aggregator.py
- Coordinates with issue stellar-vortex-protocol#41 (governance-weight definition) and issue stellar-vortex-protocol#112 (RFC process)
- Non-binding, informational tool; no on-chain enforcement or gas costs
- Supports GitHub-based or HTTP endpoint signal collection
@drips-wave

drips-wave Bot commented Sep 24, 2026

Copy link
Copy Markdown

@aladi11isah Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@james2177
james2177 merged commit 0b98f12 into stellar-vortex-protocol:main Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment