[ANN][MAINNET] QADO - BLAKE3 (account-based L1) | Windows x64 binary

[detnonzero]

Update:


Status
- Mainnet Seed goes online on March, 13, 2026, 19:00 UTC
- Phase: Mainnet (announced)
- Consensus: Frozen
- Chain resets: To be avoided


Release

- Binary (Windows x64): win-x64.zip
- Download / Source: https://github.com/detnonzero/Qado
- Download / Binaries: https://github.com/detnonzero/Qado/releases/tag/latest

Quickstart (1 minute)
1) Download and unzip
2) Run: Qado.exe
3) Allow port forwarding to your computer (TCP port 33333). It helps the network, it is optional though
4) Wait for sync (check height in GUI)


Seeds
- 212.227.21.183 (more may be added)


Chain Specs (Mainnet)
- Model: account-based L1 PoW blockchain
- Decimals: 9
- Block time: 60 seconds
- No premine
- PoW: BLAKE3
- Chain ID: 1
- Network ID: 0x01
- Target format: 32-byte big-endian
- Merkle domain separation: enabled (leaf/node tags)
- Emission: 20 QADO as block reward, halving every 1,000,000 blocks until 1.25 QADO, then tail 1 QADO after block 5,000,000
- Max Supply: Infinite but when tail emission begins there will be 38,750,000 QADO. In the first year of the tail emission initial inflation will amount to ~1.4% per year.

Mining
- Start/Stop mining in GUI


Genesis
- Timestamp (UTC): March, 13, 2026 19:00:00 UTC
- Timestamp (unix): 1773428400
- Nonce: 0
- Target: 000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
- Genesis hash: 018ce0aa2a7243194dc5c43c38c721f7fed84c17060f0772a4d09e80d70aad4c




Bug reports / Feedback / Discord
- GitHub issues: https://github.com/detnonzero/Qado/issues or in Discord in support channel
- Discord: https://discord.gg/z73bqsZZ

[visibleplayer]

Source code is not full and windows wallet with installer? 

[detnonzero]

I just published v0.1.1 with a few important fixes:

- block sync now triggers immediately after a successful connect/handshake
- peer status labels in the GUI (`Connected` / `Cooling down` / `Seen recently` / `Stale`)
- node status header is now fully wired (`Tip`, `Mempool`, `Peers`)
- minor GUI layout fixes

IMPORTANT: this update is not consensus-breaking. 
You can keep your existing `data-testnet` folder and just replace the old `Qado.exe` with the new one from the latest binaries.

Source code is not full and windows wallet with installer?

No installer yet. This is still an early testnet iteration. 
For now: download binaries, unzip, and run `Qado.exe`. 
You can also compile from source.

Also glad to see accounts in the State tab that are not mine.

[detnonzero]

Qado Update: v0.1.3 + v0.1.2 (2026-02-20)

v0.1.3 – Changed

• Peer persistence hardened at storage level: private/non-routable IPv4 endpoints are rejected on insert (PeerStore.UpsertByEndpoint).
• Existing private/non-routable peer rows are removed during prune.
• Block sync catch-up improved: after reaching a remote tip snapshot, tip is re-queried immediately on the same session.
• Sync now continues without waiting for the next outer round if the remote tip advanced meanwhile.
• In-sync idle base delay reduced from 30s to 10s.
• Out-of-order gossip block with missing prev now triggers an immediate sync request.
• UI responsiveness improved after sync/adoption phases: tip adoption is queued on a background worker.
• Account/peer reloads and node-status reads moved off the UI thread (request-coalesced workers).

v0.1.2 – Added

• Automatic startup dialing now targets configured seed plus known peers (GenesisBootstrapper -> ConnectSeedAndKnownPeersAsync).
• Background reconnect loop for running nodes with jittered intervals: fast retries when disconnected, slower steady retries when connected.

v0.1.2 – Changed

• PEX filtering hardened: only public-routable IPv4 endpoints are accepted and advertised.
• Self endpoints are filtered for both inbound and outbound PEX payloads.
• Configured seed endpoint is excluded from inbound and outbound PEX payload handling.
• Bootstrap log message updated to reflect seed+peer dialing and reconnect loop startup.

Compatibility Notice
There are no consensus-breaking changes in v0.1.2/v0.1.3.
No hard fork or chain reset is required.
For this update, replacing the Qado.exe is sufficient (rolling update is possible).

Further stability and networking hardening updates are in progress.

[detnonzero]

Qado Update: v0.1.4 (2026-02-22)

v0.1.4 - Status
- Alpha / testnet phase.
- Not mainnet; do not make mainnet assumptions.

v0.1.4 - Added
- Reorg-aware mempool reconcile: transactions from reorged-out canonical blocks are re-evaluated and requeued if still valid.
- Reconcile result now exposes requeued tx payloads for downstream handling.
- Reorg requeue gossip:
  - requeued transactions are rebroadcast after reorg adoption.
  - dedupe (short-lived LRU), trickle pacing, and per-adoption broadcast cap.
- SelfTest coverage added for reorg + mempool reconcile behavior.

v0.1.4 - Changed
- Block sync transfer mode:
  - windowed in-flight block requests (`QADO_BLOCKSYNC_WINDOW`).
  - enforced clamp range: `360..1440` (default `720`).
- Block sync peer selection hardened:
  - no blind full-list dialing in sync loop.
  - sync now uses exactly one known-dialable peer per pass.
- TIP handling during sync is now chainwork-aware before adoption/catch-up.
- Immediate sync trigger throttling hardened:
  - separate cooldown for handshake-driven triggers.
  - additional per-peer handshake-trigger cooldown.
- P2P inbound block handling hardened:
  - per-peer inbound block rate limiting.
  - orphan buffering/promotion flow for missing-parent arrivals.
  - duplicate "block already known" logs are rate-limited.
- PEX behavior tightened:
  - inbound PEX is announce-only for unknown peers (no `last_seen` refresh on existing rows).
  - outbound PEX only advertises peers with `last_seen > 0`.
  - sent/received PEX logs now use suppression windows to reduce spam.
- Peer persistence defaults:
  - peer TTL fallback reduced from `21` days to `1` day.
- Ban behavior:
  - configured seed host is exempt from fail-ban logic.
- GUI updates:
  - `State` tab entries are hard-sorted by descending balance.
  - peers with unknown `last_seen` are shown as `-`.
  - peer status now distinguishes `Stale (cooling down)`.

Compatibility Notice
There are no consensus-breaking changes in v0.1.4.
No hard fork or chain reset is required.
For this update, replacing the Qado.exe is sufficient (rolling update is possible).
You can keep your existing `data-testnet` folder.

Binaries: https://github.com/detnonzero/Qado/releases/tag/v0.1.4-testnet
Sources: https://github.com/detnonzero/Qado

Genesis Node Availability (February 21 and February 22, 2026)
The seed/genesis node had intermittent downtime today due to restarts and testings during the v0.1.4 rollout.

[detnonzero]

Qado – Network/PoW-parameter Refactor & Chain Reset

The main seed node will be offline for several days due to a networking refactor.

A full chain reset will follow.

This is part of finalizing the core architecture before longer-term continuity. Early-stage resets are expected and intentional.

Impact:
- Temporary network downtime 
- Current chain will be discarded 
- Existing nodes will not remain compatible 
- A fresh chain, updates sources and updated binaries will be released once the refactor is complete 

PoW Adjustment:
Proof-of-Work parameters will be adjusted to improve validation efficiency and overall node performance.

Runtime requirement:
The next release requires the .NET 10 Runtime. 
No self-contained builds will be provided.

The networking model is being simplified and hardened (IPv4-only, public-node based topology) before stabilization.

Further update when the new chain is live.

[detnonzero]

Qado v0.2.0 - Development Update

Hi everyone, quick update for Qado v0.2.0.

I shipped a major sync-stack refactor focused on stability under real peer conditions.

What changed

• Refactored sync pipeline (HeaderSyncManager, BlockDownloadManager, ValidationWorker)
• Reworked header/block sync state transitions and active-plan handling
• Improved peer selection and sync scheduling
• Hardened out-of-order and orphan handling
• Improved replan/recovery for partial and in-flight downloads
• Reduced duplicate sync traffic and redundant processing
• Added stronger guardrails for queue pressure and malformed sync payloads
• New genesis block, new genesis timestamp, and new genesis miner address (public key)

Impact

• More stable catch-up on long/lossy peer connections
• Lower chance of sync stalls and inconsistent in-flight state
• Better resilience against malformed or untimely sync messages

Binaries and sources

• win-x64 binaries: https://github.com/detnonzero/Qado/releases/tag/v0.2.0-testnet
• Sources: https://github.com/detnonzero/Qado
• SHA256SUMS.txt is included for integrity verification

Important

• You need the current .NET Desktop Runtime. You can install it via the .NET 10.0 SDK: https://dotnet.microsoft.com/en-us/download
• If you want to run a publicly reachable full node, enable port forwarding to your machine: TCP 34001

Status

• Project remains in alpha / testnet phase
• Mainnet hardening is still in progress
• If you have questions, feel free to ask

[detnonzero]

Qado v0.2.1-testnet - Release Update

Hi all,

new v0.2.1-testnet binaries are up.

What’s new in this build

• Header sync now uses up to 2 public peers in parallel (works with 1 peer too)
• Block download now uses up to 4 peers per cycle (also works with 1 peer)
• New Try Sync button in the Blocks tab for manual resync/replan
• Public-claim probing improved (higher timeout, more probes per tick, immediate probe on inbound claims, better failure logs)
• PEX peer selection improved (verified peers + small controlled unverified share)
• Optional portable key mode: QADO_KEYSTORE_MODE=portable_plaintext (logs warning when enabled)
• Release script now publishes self-contained single-file binaries again

Important update steps

• Backup your private keys first before changing binaries.
• Delete your existing local binary folder completely.
• Download the full new release package again and use that clean folder.

Infrastructure note

• The seed/genesis node was migrated to a VPS today. New IP address of the seed node: 212.227.21.183
• Because of migration + deep debugging (including WireGuard routing/NAT issues), the node was down for most of the day.
• This was an ops issue, not a consensus change.

Binaries

• win-x64 binaries: https://github.com/detnonzero/Qado/releases/tag/v0.2.1-testnet
• Source: https://github.com/detnonzero/Qado
• SHA256SUMS.txt is included for integrity checks

Status

• Project is still in alpha / testnet phase
• Mainnet hardening is ongoing

Feedback from node operators is very welcome.
Qado v0.2.2-testnet – Patch Update

Quick patch focused on sync robustness (no consensus change, no chain reset).

• Sync now recovers gaps more reliably and falls back cleaner when peers misbehave  
• Header catch-up tuned for larger batches and fewer round trips  
• Non-public/unstable peers are filtered more strictly for sync requests  
• Live sync progress in UI is now clearer (validated height updates continuously)  
• Extra hardening against occasional DB/index errors under heavy sync load  
• Reduced noisy sync logging

Binaries: https://github.com/detnonzero/Qado/releases/tag/v0.2.2-testnet
Source: https://github.com/detnonzero/Qado
Integrity: SHA256SUMS.txt included

Feedback from node operators is very welcome.

[detnonzero]

Qado v0.2.3 Small Patch

• Sync stability fixes.
• Resync triggers are now throttled (prevents HeaderSync loops under gossip pressure).
• Retry path improved for stuck missing blocks.
• Backpressure fallback when validation queue is full (Range -> GetData).

Important: No consensus change, no chain reset, no mandatory user action.
You can update normally.

[detnonzero]

Edit
Qado v0.3.3 is out.
Seed is back online
This update includes a more aggressive block propagation, better parent/orphan recovery, improved side-branch handling, and fixes for initial-sync continuation issues.

Important: all nodes should update together. This release is not intended to run mixed with older binaries. You can user you pivate keys from the days before, chain reset wasn't necessary.

New binaries are available now.

binaries: https://github.com/detnonzero/Qado/releases/tag/v0.3.3-testnet

Edit
Quick Update: Seed will be down for most of the day because of P2P redsign. I will give you an update in the late evening today.

Qado v0.3.1 is out.

Main changes:

• Much faster catch-up block sync. The new sync behavior is genuinely fun to watch now.
• Legacy header-sync code removed
• Old PoW/storage leftovers cleaned up
• GUI status simplified to canonical Height

Important: this release includes schema cleanup, so please delete the old data folder AND replace the old Qado.exe with the new one from the binaries and let the node resync from scratch. Please backup your private keys before deleting the data folder.

Sources: https://github.com/detnonzero/Qado
Binaries: https://github.com/detnonzero/Qado/releases/tag/v0.3.1-testnet

Edit: Qado v0.3.2 is out.

Additional change since the previous update:

• Direct block sync batches increased to 4096 blocks while keeping 64-block chunks.

Updated binaries:
https://github.com/detnonzero/Qado/releases/tag/v0.3.2-testnet

[detnonzero]

Updated the OP regarding mainnet. I will add the binaries to the github repo on March, 13 19:00 UTC.

[detnonzero]

Qado Mainnet seed ist online and v0.4.0 (Mainnet) is now available.

This is the current mainnet binary release.

Highlights in v0.4.0:

• nonce handling was hardened across mempool, validation, and state application
• local instance handling was tightened to allow only one node per machine/network profile
• P2P listener binding and self-peer detection were hardened
• overall focus remains sync stability and resilience

Important note:
Please start this release with a fresh data/ directory.

Binary artifacts:

• Windows win-x64 self-contained single-file build
• SHA256SUMS.txt included for verification
• Download / Source: https://github.com/detnonzero/Qado
• Download / Binaries: https://github.com/detnonzero/Qado/releases/tag/latest

If you are running Qado on mainnet, please use the latest binary and verify the checksum before starting.