@QubicDev

Core tech team of @_Qubic_ · what we're building. Protocol · OC/OM · SC tooling · science. Docs: https://xitter.cf/t.co/xDCeeWt2fB

 Distributed
github.com/qubic
Joined July 2026
  • Tweets52
  • Following10
  • Followers861
22Media
This is @QubicDev — the technical account for the @_Qubic_ Core Tech Team. What we're building, how it works, and what didn't work when we got it wrong. Here's what to expect:
3
41
3
194
6,605
SWATCH — one piece of qubic-network:native burn mechanism. Approved by quorum as the "Emission SC / Supply Watcher": responsible for burning QU per Qubic's emission schedule. Infrastructure SC. Anyone can send QU to it — it burns them. Full mechanism: docs.qubic.org/learn/emissio…
5
30
2
161
4,816
more replies
The name earns itself in Phase 2: SWATCH will read existing ecosystem burns (SC IPO, dust filter, Ecosystem-driven) and adjust its own burning accordingly, keeping the emission schedule on target. Watch the supply. Balance the burn.
1
4
26
291
Sources: → contracts/SupplyWatcher.h — the SC itself (~65 lines) → qubic.cpp endEpoch() — the revenue-routing loop that feeds SWATCH → Original approved proposal (2024): qubic.org/blog-detail/the-ne… Design intent, in code, on-chain.

The New Emission Model Proposal with 80% Supply Cut

The New Emission Model Proposal with 80% Supply Cut

qubic.org
10
48
504
EP227 begun today. What "the halving" actually is at the code level: One entry in GQMPROP's revenueDonation table, voted in by quorum: destination = SWATCH millionthAmount = 775000 (77.5%) firstEpoch = 227 That's the whole change. Here's how it burns ↓
4
26
2
102
2,294
more replies
Read the code: → contracts/GeneralQuorumProposal.h — revenueDonation table, vote flow, cleanup → contracts/SupplyWatcher.h — burn sink (BEGIN_EPOCH only) → qubic.cpp endEpoch() — the sequential donation loop with system.epoch >= firstEpoch filter github.com/qubic/core
1
4
21
261
Verify the table yourself — same on-chain source-of-truth: → GUI: Qubic .NET Toolkit → Governance → Revenue tab → CLI: qubic-cli -gqmpropgetrevdonation → Full guide (CLI, RPC, TS/.NET SDK): docs.qubic.org/learn/inspect… Screenshot below is EP226 mainnet.
4
22
225
"Halving" isn't one moment. It's spread across epochs: → EP226: UPoW scores accrue per pubkey (via mining) → End of EP226: top 676 become computors for EP227 → EP227: those computors validate + run consensus → End of EP227: revenue by performance — more of it burned
2
30
1
125
2,716
more replies
If half of this is unfamiliar terminology — fair. It's dense. SWATCH, GQMPROP, the routing table — each gets its own mechanism post. Follow @QubicDev to catch them.
1
2
29
341
Sources: → whitepaper §5 (consensus + computor election by UPoW score) → whitepaper §11 (epoch lifecycle + END_EPOCH revenue distribution) → qubic/core: contracts/GeneralQuorumProposal.h (routing) + contracts/SupplyWatcher.h (burn sink) Read the code. That's the receipt.
2
25
265
Every Wednesday at 12:00 UTC, @_Qubic_ 's epoch rolls over. Seamless: tick N ends the old epoch, tick N+1 starts the new. No gap. Coordinated restart: a tick-number gap while nodes re-sync. The mode isn't operator choice. It's dictated by what the network agrees on every tick ↓
1
28
3
139
4,714
more replies
Seamless is possible on two paths: A. Change doesn't touch consensus — tooling, RPC, logging. Nodes update whenever. B. Change IS consensus-touching but gate-guarded: if (system.epoch >= 103) new(); if (system.tick  >= N)   new(); All nodes flip together.
1
3
17
262
Full technical explanation + decision framework: 📖 docs.qubic.org/computors/upg… Why some Wednesdays the epoch flips without you noticing, and others need a hard restart — with the actual code patterns behind it. 💻Nerd must read: github.com/qubic/core/blob/m…

Upgrading | Qubic Docs

Qubic's network evolves through regular software updates. Some updates flow through the network without interrupting ticks; others require every node to activate the new code at the same moment....

docs.qubic.org
6
25
298
Load more