c8be9d7414
- Add Prometheus metrics for marketplace API throughput and error rates with new dashboard panels - Implement confidential transaction models with encryption support and access control - Add key management system with registration, rotation, and audit logging - Create services and registry routers for service discovery and management - Integrate ZK proof generation for privacy-preserving receipts - Add metrics instru
5.2 KiB
5.2 KiB
title, description, layout
| title | description | layout |
|---|---|---|
| AITBC Governance | Community governance and decision-making for the AITBC protocol | default |
AITBC Governance
Welcome to the AITBC governance hub. This site serves as the central location for all governance-related information, including RFCs, decision records, and community participation guidelines.
Quick Navigation
- RFC Process - How to propose changes to AITBC
- Active RFCs - Currently under discussion
- Accepted RFCs - Approved proposals
- Community Calls - Meeting schedule and recordings
- Governance Framework - Roles and responsibilities
- Decision Log - Historical decisions and rationale
Latest Updates
Recent RFCs
| RFC | Title | Status | Date |
|---|---|---|---|
| RFC-001 | Multi-tenant Architecture | Accepted | 2024-01-15 |
| RFC-002 | Ecosystem Certification Program | Accepted | 2024-01-15 |
Upcoming Events
- Community Call: 2024-01-22 at 14:00 UTC
- RFC Review: 2024-01-24 at 16:00 UTC
- Governance Meeting: 2024-01-29 at 15:00 UTC
How to Participate
1. Stay Informed
- Join our Discord server
- Subscribe to the governance mailing list
- Watch the rfcs repository
2. Contribute to RFCs
- Review draft RFCs on GitHub
- Comment with technical feedback
- Submit implementation proposals
- Join community discussions
3. Join Community Calls
- Weekly technical syncs (Tuesdays 14:00 UTC)
- Bi-weekly governance meetings (alternating Mondays)
- Monthly RFC reviews (last Thursday)
4. Vote on Decisions
- Informal voting via GitHub reactions
- Formal governance votes (when applicable)
- Delegate participation if unable to attend
Governance Structure
Current Model: Benevolent Dictator
- AITBC Foundation holds final decision authority
- Community input strongly considered
- Transparent decision-making process
- Gradual decentralization planned
Transition Plan
- Phase 1 (Current): Foundation-led with community input
- Phase 2 (After 100 RFCs): Delegate voting system
- Phase 3 (Future): Full on-chain governance
Roles and Responsibilities
AITBC Foundation
- Maintains core protocol
- Ensures network security
- Facilitates community growth
- Holds veto power (with sunset clause)
Core Team
- Technical review of RFCs
- Implementation of accepted proposals
- Network operations
- Security oversight
Community Contributors
- RFC proposals and reviews
- Code contributions
- Documentation
- Testing and feedback
Delegates
- Represent stakeholder interests
- Vote on governance decisions
- Participate in working groups
- Communicate with constituencies
Working Groups
Protocol Working Group
- Core protocol improvements
- Consensus mechanisms
- Cross-chain functionality
- Network parameters
Ecosystem Working Group
- SDK standards
- Connector specifications
- Certification requirements
- Developer experience
Governance Working Group
- Process improvements
- Election procedures
- Community guidelines
- Transparency initiatives
Security Working Group
- Security audits
- Vulnerability disclosure
- Best practices
- Incident response
Decision Making Process
Types of Decisions
Protocol Changes
- Require RFC process
- Technical review mandatory
- Security assessment required
- Implementation timeline specified
Governance Changes
- Require RFC process
- Community consultation required
- 30-day comment period
- Supermajority approval needed
Operational Decisions
- Made by Core Team
- Documented in decision log
- Community notification required
- Appeal process available
Voting Mechanisms
Informal Voting
- GitHub reactions on RFC PRs
- Discord polls for minor decisions
- Show of hands in community calls
- Non-binding but influential
Formal Voting
- Token-based voting (Phase 2)
- Delegate voting (Phase 2)
- Multi-sig wallet approvals
- On-chain execution
Transparency and Accountability
Decision Records
- All decisions documented
- Rationale clearly explained
- Alternatives considered
- Implementation status tracked
Financial Transparency
- Foundation treasury reports
- Grant program updates
- Expense documentation
- Annual financial statements
Performance Metrics
- Network statistics
- Developer activity
- Ecosystem growth
- Governance participation
Get Started
- Read the RFC Process - Understand how to propose changes
- Join the Community - Connect with other contributors
- Review Active RFCs - Participate in current discussions
- Attend a Call - Join the next community meeting
- Contribute - Start with documentation or testing
Contact
- Governance: governance@aitbc.io
- RFC Process: rfcs@aitbc.io
- Security: security@aitbc.io
- General: community@aitbc.io
Archives
This governance site is maintained by the AITBC community. Last updated: 2024-01-15