Qubic Dev @QubicDev

Core tech team of @_Qubic_ · what we're building. Protocol · OC/OM · SC tooling · science. Docs: https://t.co/xDCeeWt2fB github.com/qubic Distributed Joined July 2026

Tweets

52
Followers

837
Following

10
Likes

1

Qubic Dev @QubicDev

a week ago

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/th… Design intent, in code, on-chain.

0 10 49 495 1

View Details

Qubic Dev @QubicDev

a week ago

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 280 0

View Details

Qubic Dev @QubicDev

a week ago

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/emission…

5 30 162 5K 3

View Details

Qubic Dev @QubicDev

2 weeks ago

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.

0 4 22 222 1

View Details

Qubic Dev @QubicDev

2 weeks ago

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 257 0

View Details

Qubic Dev @QubicDev

2 weeks ago

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 102 2K 4

View Details

Qubic Dev @QubicDev

2 weeks ago

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.

0 2 25 263 0

View Details

Qubic Dev @QubicDev

2 weeks ago

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 338 0

View Details

Qubic Dev @QubicDev

2 weeks ago

"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 125 3K 2

View Details

Qubic Dev @QubicDev

3 weeks ago

Full technical explanation + decision framework: 📖 docs.qubic.org/computors/upgr… 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/blo…

0 6 25 297 1

View Details

Qubic Dev @QubicDev

3 weeks ago

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 258 1

View Details

Qubic Dev @QubicDev

3 weeks ago

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 ↓