Skip to content

Commit c249e12

Browse files
authored
Merge branch 'qubic:main' into main
2 parents 373c630 + ab7aa31 commit c249e12

File tree

2 files changed

+204
-0
lines changed

2 files changed

+204
-0
lines changed
Lines changed: 141 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,141 @@
1+
# Qubic Governance & Funding Framework
2+
3+
**Proposal Date:** March 11, 2026
4+
5+
## Question
6+
7+
Do you (the Computors) approve the establishment of an updated Governance & Funding Framework for Qubic as documented and presented to the community?
8+
9+
---
10+
11+
## Voting Options
12+
13+
| Option | Description |
14+
|--------|-------------|
15+
| **Option 0** | **Yes** — Approve the Governance & Funding Framework as documented |
16+
| **Option 1** | **No** — Reject the framework; maintain current state |
17+
18+
---
19+
20+
## Summary
21+
22+
This proposal asks Computors to approve a comprehensive governance and funding framework that establishes:
23+
- Clear structural roles, mandates, and reporting lines for all ecosystem entities
24+
- Strict separation between three funds (CCF, Incubation Fund, Listing Fund)
25+
- Independent financial oversight through a Finance Auditing Entity
26+
- Protocol primacy ensuring technical integrity overrides governance decisions
27+
28+
## Background
29+
30+
The Qubic ecosystem has grown to include multiple workgroups, boards, and funding mechanisms. As operations have scaled, the need for formalized governance structures has become evident. This framework addresses:
31+
32+
1. **Structural Clarity** — Defining who does what, who reports to whom, and what authority each entity has
33+
2. **Fund Separation** — Ensuring funds are isolated by purpose with distinct controls
34+
3. **Accountability** — Establishing independent oversight and public transparency
35+
36+
## Framework Overview
37+
38+
### Fund Structure
39+
40+
| Fund | Purpose | Control |
41+
|------|---------|---------|
42+
| **CCF (Computor Controlled Fund)** | Funds Full Workgroups and approved Projects | Computor approval required |
43+
| **Incubation Fund** | Dedicated to incubation projects only | Incubation Board |
44+
| **Listing Fund** | Exchange listings only | Listing Board |
45+
46+
All three funds operate independently with strict isolation. Only CCF is subject to audit by the Finance Auditing Entity.
47+
48+
### Organizational Entities
49+
50+
**Full Workgroups** (funded by CCF):
51+
- Marketing Workgroup
52+
- Community Management Workgroup
53+
- Qubic Science Workgroup
54+
- Tech Workgroup (with Protocol Primacy)
55+
56+
**Small Execution Workgroups** (funded by Full Workgroups):
57+
- Business Development
58+
- Incubation Management
59+
60+
**Strategy Layer Boards**:
61+
- Strategic Board (WG Leads + Computor Delegates + Advisors) — defines strategic direction, first arbiter for conflicts
62+
- Incubation Board — controls Incubation Fund, defines incubation program strategy
63+
- Listing Board — controls Listing Fund, decides exchange strategy
64+
65+
**Oversight**:
66+
- Finance Auditing Entity — independent oversight of CCF spending, mandatory access to financial records, public transparency
67+
68+
### Key Principles
69+
70+
1. **Fund Separation** — Funds strictly separated by purpose with distinct controls
71+
2. **Decision vs Execution** — Boards decide direction; Workgroups execute
72+
3. **Independent Oversight** — Financial oversight is independent and mandatory
73+
4. **Protocol Primacy** — Protocol rules override all governance decisions; Tech Workgroup must refuse directives that violate protocol integrity
74+
75+
### Conflict Resolution
76+
77+
- **Standard conflicts**: Strategic Board → Computors (final authority)
78+
- **Protocol conflicts**: Tech Workgroup → CFB → Protocol (governance cannot override protocol constraints)
79+
80+
## Documentation
81+
82+
Full documentation is publicly available:
83+
84+
📁 **[Governance Framework Documentation](https://drive.google.com/drive/folders/1DrOYPJ1uEEjsqhYwoI348XzIiHF--SSn?usp=sharing)**
85+
86+
| Document | Description |
87+
|----------|-------------|
88+
| **01_Qubic-Governance-Framework-Overview** | High-level overview — the essentials |
89+
| **02_Qubic-Governance-Framework-Slides** | Presentation for deeper understanding |
90+
| **03_Qubic-Governance-Framework-Whitepaper** | Comprehensive details and specifications |
91+
| **Timeline - Governance-Framework** | Execution roadmap and milestones |
92+
93+
## Implementation Timeline
94+
95+
| Phase | Period | Focus |
96+
|-------|--------|-------|
97+
| **Phase 1** | Now → Mar 18 | Stakeholder alignment, community feedback, Computor approval |
98+
| **Phase 2** | Feb → Apr | Entity establishment (Finance Auditing Entity, full Strategic Board) |
99+
| **Phase 3** | Feb → May | Funding sustainability for Incubation and Listing funds |
100+
101+
**Key Milestones:**
102+
- Feb 5, 2026: Stakeholder presentation
103+
- Mar 11, 2026: Computor proposal
104+
- Mar 18, 2026: Framework approval (target)
105+
- Apr 15, 2026: All entities operational
106+
- May 15, 2026: Fully operational with sustainable funding
107+
108+
## Current State
109+
110+
**Already Active (9 entities):**
111+
- Computors, Tech Workgroup, Qubic Science, Marketing Workgroup
112+
- Business Development, Incubation Management
113+
- Incubation Board, Listing Board, Strategic Board (Interim)
114+
- CCF with steady income (8% Computor donation)
115+
116+
**Gaps to Address:**
117+
- Finance Auditing Entity (HIGH priority)
118+
- Full Strategic Board with Computor delegates (MEDIUM priority)
119+
- Sustainable funding for Incubation and Listing funds
120+
121+
## Benefits
122+
123+
✅ Clear accountability through defined roles and reporting lines
124+
✅ Financial discipline through fund separation and independent audit
125+
✅ Protocol protection through Tech Workgroup primacy
126+
✅ Decentralized governance with Computors as final authority
127+
✅ Transparent operations with public financial reporting
128+
✅ Scalable structure supporting ecosystem growth
129+
130+
131+
---
132+
133+
## References
134+
135+
- [Governance Framework Documentation (Google Drive)](https://drive.google.com/drive/folders/1DrOYPJ1uEEjsqhYwoI348XzIiHF--SSn?usp=sharing)
136+
- Stakeholder Presentation: February 5, 2026
137+
- Community Discussion: Discord #governance channel
138+
139+
---
140+
141+
*This proposal was prepared by the interim Strategic Board following stakeholder presentation and community feedback period.*
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
# Proposal for Quottery v2 update
2+
3+
## Proposal
4+
Allow Deployment of the new Quottery Smart Contract in EP201 on Qubic
5+
6+
### Available Options
7+
8+
> Option 0: No — do not allow deployment
9+
10+
> Option 1: Yes — allow deployment
11+
12+
## Overview
13+
Quottery (QTRY) is a high-performance, decentralized prediction market and binary options exchange designed specifically for the Qubic ecosystem. Unlike legacy prediction platforms, QTRY operates as a fully on-chain order book exchange, allowing users to trade positions on future outcomes with zero counterparty risk.
14+
15+
Built using highly optimized C++ for the QPI, QTRY leverages Qubic’s unique "tick" architecture to provide near-instant matching, automated settlement, and a trustless dispute resolution mechanism powered by the network's Computors. It represents a significant step forward in utility for the Qubic network, offering a distinct financial instrument that drives transaction volume and burns QUs.
16+
17+
## Motivation and Goals
18+
19+
### Motivation
20+
Current decentralized prediction markets often suffer from high latency, excessive gas fees, or centralized oracle points of failure. The Qubic ecosystem currently lacks a native financial derivative layer that can handle high-frequency trading of binary outcomes (Yes/No events) without bloating the state. QTRY addresses this by implementing a lightweight, "set-and-forget" architecture that cleans up its own state, ensuring long-term sustainability.
21+
22+
### Goals
23+
* **Trustless Settlement:** To remove the need for a centralized clearinghouse by using atomic smart contract swaps for all trades.
24+
* **Economic Utility:** To create a consistent "sink" for QUs through trading fees, event creation fees, and an automated burn mechanism.
25+
* **Fair Dispute Resolution:** To utilize the consensus of Qubic Computors as the ultimate "Supreme Court" for resolving controversial event outcomes, ensuring fairness beyond the control of the platform operator.
26+
* **High Efficiency:** To demonstrate the capabilities of QPI by managing up to 2 million user positions and thousands of concurrent events without impacting network tick times.
27+
28+
## Contract Summary
29+
The QTRY smart contract is a self-contained financial engine. Its core architecture revolves around a dual-state order book that manages liquidity for binary options (Option 0 vs. Option 1).
30+
31+
* **Matching Engine:** The contract features an embedded matching engine that supports three distinct trade types:
32+
* **Direct Match:** Standard Ask vs. Bid matching.
33+
* **Merge (Liquidity Exit):** Users holding opposite positions can "merge" them to exit the market and recover collateral.
34+
* **Mint (Liquidity Entry):** Two users with opposing views can simultaneously fund a new position, creating liquidity for the market.
35+
* **Automated Lifecycle:** Events move strictly through a state machine: `Active``Trading Closed``Result Published``Dispute Window``Finalized``Archived`.
36+
* **State Management:** The contract includes aggressive, automated garbage collection in the `END_EPOCH` routine. It ensures that finalized events and settled positions are permanently removed from memory, preventing state bloat—a critical feature for maintaining low operational costs on Qubic.
37+
* **Security:** The contract enforces strict checks on amounts, prices, and dates, and includes "anti-spam" deposits for creating events or raising disputes.
38+
39+
## Governance
40+
QTRY introduces a multi-layered governance model that balances operational efficiency with decentralized oversight.
41+
42+
* **The Game Operator (GO):** A designated entity (initially the developer team) responsible for the day-to-day creation of events and publishing of initial results. The GO must stake capital to perform actions, incentivizing accurate reporting.
43+
* **The Computors (Validators):** Qubic Computors serve as the ultimate oracle. If users disagree with the Game Operator’s published result, they can initiate a **Dispute**. Computors then vote on the correct outcome. If the GO is found to be malicious or incorrect, they are penalized, and the Computors update the result directly on-chain.
44+
* **Shareholder Proposals:** Holders of the QTRY asset have direct control over the protocol's economic parameters. Through a built-in proposal system, shareholders can vote to:
45+
* Adjust fee rates (Operation Fee, Shareholder Fee, Burn Fee).
46+
* Update the "Anti-Spam" and "Deposit" amounts.
47+
* **Replace the Game Operator** entirely if they become inactive or malicious.
48+
49+
## Dividend Distribution
50+
QTRY implements a robust, automated revenue-sharing model designed to benefit all stakeholders in the Qubic ecosystem.
51+
52+
* **Revenue Streams:** The contract collects revenue from:
53+
* **Trading Fees:** A percentage fee (default 1.5%) charged on every matched trade.
54+
* **Hosting Fees:** A daily fee charged to the Game Operator for keeping an event active.
55+
* **Distribution Logic:** At the end of every epoch (approx. every week), the contract automatically calculates the total accumulated revenue and distributes it as follows:
56+
1. **Deflationary Burn:** A configurable percentage (e.g., 10%) is permanently burned (removed from circulation), reducing the total supply of QUs and benefiting all Qubic holders.
57+
2. **Shareholder Dividends:** The majority of the net revenue is distributed pro-rata to all holders of QTRY shares. This creates a yield-generating asset within the Qubic ecosystem.
58+
3. **Operational Costs:** A portion is allocated to the Game Operator to cover server costs, data feed subscriptions, and development.
59+
60+
This "Push" distribution model (automated at `END_EPOCH`) ensures that dividends are paid out regularly and transparently, without requiring users to manually claim or pay fees to receive their rewards.
61+
62+
## Technical implementation
63+
https://github.com/qubic/core/pull/761

0 commit comments

Comments
 (0)