v2.1.2-Nodens

Offerings to Cthulhu v2.1.2-Nodens — "The Valve Un-Welded"

MANDATORY UPGRADE for every node and wallet. This release makes the
emergency-difficulty escape valve functional. The corrected rule accepts
blocks that all prior binaries reject: once the first minimum-difficulty
emergency block is mined, any node still running v2.1.1 or older will
reject it and strand itself on a dead tip. Upgrade before then.

Background — the 2026-08-03 hashrate departure

A visiting miner (>100 MH/s, roughly a thousandfold the resident
hashrate) worked the public pool overnight, drove LWMA-3 difficulty to
~385, and departed at 03:40 UTC. At the resident hashrate that left the
chain producing roughly one block every eleven hours, with LWMA-3's
anti-timestamp-attack solvetime clamp limiting recovery to ~13% per
block — several days of limping, and proportionally worse for any
larger future visitor.

The chain has carried an emergency-difficulty rule since block 989,898:
after a >1 hour gap, a block at minimum difficulty becomes valid,
letting the chain unstick itself. Investigating why it never fired
during the stall revealed it never could (issue #59, PR #60).

Fixes

1. Consensus — the valve was unsatisfiable. IsEmergencyDifficultyBlock
   compared the block's decoded target against ProofOfWorkLimit() by
   bignum value. The proof-of-work limit (~uint256(0)>>20, 236 mantissa
   bits) is not exactly representable in nBits' 23-bit compact mantissa,
   so no encodable block header could ever pass the check — the valve
   shipped welded shut on every binary since v2.0.5. Now compares
   compact-to-compact, matching the reference implementation the rule
   was ported from.

2. Producers never pulled the lever. Block-template construction
   unconditionally stamped the LWMA-3 target; the internal miner grinds
   a template to nonce exhaustion with nothing to interrupt it during a
   stall; the getwork/getblocktemplate caches only rebuild on tip
   change or mempool activity — neither of which happens while stalled.
   New shared EmergencyDifficultyEligible() gate +
   GetNextWorkRequiredForMining() wrapper in every template path, a
   rebuild trigger in the miner's search loop, and emergency-rebuild
   triggers in both RPC template caches.

With both fixes deployed, any hashrate-departure stall self-heals: ~61
minutes after the last block, a minimum-difficulty block becomes valid
and producing daemons mine one within seconds. LWMA-3 then walks the
difficulty back down (~13% per block) and normal 60-second cadence
resumes within days — bounded at one block per hour no matter how high
the departing visitor left the difficulty.

Validation

• New src/test/pow_tests.cpp: eligibility gates (activation height,
  Conclave signed-window skip with inclusive bounds, strict >1h gap),
  miner-side target selection, produce→validate round-trip (the test
  that caught the encoding bug), better-than-powLimit rejection inside
  the gap, fresh-tip rejection at powLimit.
• Full Boost.Test suite green.
• Normal-block validation is byte-identical to v2.1.1: the exemption
  still requires height ≥ 989,898, a height outside the Conclave signed
  window, a strictly >1h tip gap, and exactly the min-diff compact target.

Unchanged

• PROTOCOL_VERSION stays 90003; no wire-format change.
• No new activation height: the rule's existing 989,898 gate governs.
  (The old rule below any candidate height was unsatisfiable dead code,
  so patched and unpatched nodes agree on every historical block.)
• Suffix stays -Nodens; tag is v2.1.2-Nodens.

---

Binaries: this release's files are served from https://23skidoo.info/downloads/ (GitHub assets did not travel with the repository move).

• SHA256SUMS-linux.txt — 0.0 MB
• Offerings-daemon-v2.1.2-Nodens-linux64.tar.gz — 4.9 MB
• SHA256SUMS-windows.txt — 0.0 MB
• Offerings-v2.1.2-Nodens-win64.zip — 23.1 MB
• SHA256SUMS-linux-qt5.txt — 0.0 MB
• Offerings-qt-v2.1.2-Nodens-linux64.tar.gz — 23.8 MB

v2.1.1-Nodens

v2.1.1 — Nodens

Released 2026-07-31. A patch in the Nodens line: the Watcher learns to keep his own vigil. v2.1.0 lit the beacon — the Conclave's authenticated checkpoints went live on mainnet — and the first days on watch surfaced three gaps between the ported machinery and the real topology it runs on. v2.1.1 closes all three, so the checkpoint overlay tends itself: no operator cron, no stale watch after a restart, no waiting for the next broadcast. No consensus changes and no activation height — everything here takes effect the moment you run the binary.

---

What's new

• Self-healing authenticated checkpoints (#50). Three fixes to the Phase-2 ACP overlay, found during mainnet first-light:
  • The broadcaster now re-broadcasts on its own blocks. The tip-advance auto-broadcast only fired on blocks received from peers — blocks the broadcaster's daemon assembled itself (pool submitblock, internal miner) never triggered it. On a topology where the signing node is also the primary block producer, the network checkpoint went stale indefinitely. Fixed; suppressed during initial block download so a syncing broadcaster doesn't sign-and-relay per historical block.
  • The checkpoint survives restarts. The sync checkpoint was persisted to the block database on every accept but never read back — every restart zeroed the node's in-memory view, master and recipient alike, until the next broadcast arrived. It now reloads at startup.
  • New connections receive the current checkpoint at handshake. The ppcoin lineage relays the signed checkpoint message to every newly connected peer; the original 2013-era port dropped that. Restored — a restarted or freshly-synced node reacquires the checkpoint the moment it peers, instead of waiting for the next master broadcast.
  • The regtest harness grew three phases, one per gap, and the operator runbook (contrib/phase2-acp/RUNBOOK.md) is updated — the interim heartbeat-cron mitigation is downgraded to optional belt-and-braces during mixed-version rollout.
• getaddr replies never serve non-routable addresses (#51). v2.1.0's RFC 6598 fix (#44) stopped CGNAT/private ranges from entering the address manager, but entries cached before the fix kept being served to every peer who asked, until natural decay. The reply path now filters for routability — completing the third of the three gossip surfaces — and the selection bookkeeping keeps replies at the intended size while skipping. Ships with the tree's first addrman unit tests.
• OpenSSL evacuation plan published (#47). A full-tree dependency survey and phased implementation plan for removing OpenSSL entirely — research/issue47-openssl-evacuation-plan.md. Planning only; no code in this release.
• Repository hygiene: a stray committed build log and an accidentally-committed backup directory of superseded Qt patches are removed.

---

Do I need to upgrade?

This release is optional. There is no fork, no activation height, and no rule change — v2.1.0-Nodens and v2.0.9-Eldersign nodes remain first-class citizens. The pitch, by role:

• Public nodes, exchanges, explorers — recommended. The restart-reload and handshake-relay fixes mean your node's checkpoint protection is continuous rather than best-effort: after any restart you are re-armed at handshake instead of unprotected until the next broadcast. Nodes whose peers.dat predates v2.1.0 also stop gossiping stale unreachable addresses.
• Checkpoint-broadcaster operators — effectively required. This is the release that makes the overlay self-sufficient. Below v2.1.1 the broadcaster needs an external re-issue mechanism whenever it produces its own blocks.
• Anyone still below v2.0.9 — upgrade regardless, and read the Eldersign notes first. The block-1,055,555 rules are live; v2.0.9 is the mandatory floor and v2.1.1 includes everything since.

PROTOCOL_VERSION is unchanged at 90003 — wire protocol, wallet on-disk format, and RPC dialect are untouched. Your wallet.dat and chain data carry over.

---

Downloads

GitHub release: v2.1.1-Nodens

• Linux x86_64 daemon + cli — Offerings-daemon-v2.1.1-Nodens-linux64.tar.gz (depends/ static, glibc 2.35+)
• Linux x86_64 Qt5 wallet — Offerings-qt-v2.1.1-Nodens-linux64.tar.gz (depends/ static)
• Windows x86_64 Qt5 wallet — Offerings-v2.1.1-Nodens-win64.zip (mingw-w64 cross via depends/)
• SHA256SUMS-*.txt (also bundled inside each archive)

Verifying

$ tar -xzf Offerings-daemon-v2.1.1-Nodens-linux64.tar.gz
$ cd Offerings-daemon-v2.1.1-Nodens-linux64
$ sha256sum -c SHA256SUMS-linux.txt
Offeringsd: OK
Offerings-cli: OK

Upgrading your node (Linux)

sudo systemctl stop offeringsd          # or kill your running daemon
sudo cp Offeringsd /usr/local/bin/
sudo cp Offerings-cli /usr/local/bin/
sudo systemctl start offeringsd
Offerings-cli getinfo | head            # confirm: "version": 2010100

---

Binaries: this release's files are served from https://23skidoo.info/downloads/ (GitHub assets did not travel with the repository move).

• SHA256SUMS-linux.txt — 0.0 MB
• Offerings-daemon-v2.1.1-Nodens-linux64.tar.gz — 4.9 MB
• SHA256SUMS-windows.txt — 0.0 MB
• Offerings-v2.1.1-Nodens-win64.zip — 23.1 MB
• SHA256SUMS-linux-qt5.txt — 0.0 MB
• Offerings-qt-v2.1.1-Nodens-linux64.tar.gz — 23.8 MB

v2.1.0 — Nodens

v2.1.0 — Nodens

Released 2026-07-28. The first release of the post-Awakening era: the Codex is read, the signed window is closed, the Eldersign rules are live — and now a Watcher takes his post. Nodens, Lord of the Great Abyss, is the rare Old One who guards rather than devours; this release carries the machinery that lets the Conclave stand the same watch over the chain. No consensus changes and no activation height — everything here takes effect the moment you run the binary.

---

What's new

• Phase-2 Authenticated Checkpoints — first-light capability (#40). The chain's dormant broadcast-checkpoint stack (Peercoin CSyncCheckpoint lineage, present in the tree since the 2013 fork but keyed to a dead foreign pubkey) is rewired to Conclave Key #1 and brought back to life. When the Conclave's signing node broadcasts a checkpoint, every v2.1.0+ node verifies the signature and hard-rejects any competing chain that would reorg below it — a real-time answer to deep-reorg attacks, complementing the local guards that shipped in v2.0.9 (MAX_REORG_DEPTH=100, rolling checkpoints). This is an overlay, not a consensus change: with no checkpoint broadcast on the wire, a v2.1.0 node behaves identically to a v2.0.9 node. Enforcement of broadcast checkpoints exists only on upgraded nodes — that is the reason to run this release. Positive and negative regtest coverage landed with the wiring; the operator's procedure is public at contrib/phase2-acp/RUNBOOK.md.
• -miningaddress=<addr> for solo miners (#46). Optional daemon flag: the internal miner pays every coinbase to one fixed address instead of drawing a fresh keypool key per block — consolidating the operator wallet's UTXO set and the solo-mining leaderboard rows. Unset (the default) preserves the historical per-block rotation exactly; pool-side templates (-pooladdress / getblocktemplate) are untouched. A typo'd address refuses to start the daemon rather than silently falling back to wallet keys.
• CGNAT / RFC 6598 range treated as non-routable (#44). 100.64.0.0/10 (carrier-grade NAT shared space) is now classed like RFC1918 — it no longer leaks into public addr gossip. Nodes peered over CGNAT or overlay networks keep working via explicit addnode=; the change only stops advertising unreachable addresses to the network. (This fix was previously listed in the v2.0.9 notes as riding by merge-up; the merge landed after the Eldersign tag was cut, so it ships to users here.)
• Fix: crash on first start with a fresh testnet data directory (#48). Every Eldersign-lineage binary asserts in ConnectTip when started against an empty testnet datadir — a dormant checkpoint-initialization mis-port, surfaced by the ACP revival. Mainnet fresh-installs and all existing data directories were never affected. v2.1.0 initializes cleanly from an empty datadir on all three networks; if you must start a fresh testnet node on an older binary, seed the datadir from an initialized testnet3/ first.

---

Do I need to upgrade?

This release is optional. There is no fork, no activation height, and no rule change — a v2.0.9-Eldersign node remains a first-class citizen of the network. The pitch, by role:

• Public nodes, exchanges, explorers — recommended. Broadcast-checkpoint enforcement is the deep-reorg insurance this chain has been building toward, and it only protects nodes that run it. When the Conclave lights the beacon, v2.1.0 nodes are the ones who see it.
• Solo miners — upgrade if you want -miningaddress. Otherwise nothing changes for you.
• Anyone still below v2.0.9 — upgrade regardless, and read the Eldersign notes first. The block-1,055,555 rules (BIP66, BIP65, coinbase maturity 240, rolling checkpoints) are live; v2.0.9 is the mandatory floor and v2.1.0 includes all of it.

PROTOCOL_VERSION is unchanged at 90003 — wire protocol, wallet on-disk format, and RPC dialect are untouched. Your wallet.dat and chain data carry over.

---

Downloads

GitHub release: v2.1.0-Nodens

• Linux x86_64 daemon + cli — Offerings-daemon-v2.1.0-Nodens-linux64.tar.gz (depends/ static, glibc 2.35+)
• Linux x86_64 Qt5 wallet — Offerings-qt-v2.1.0-Nodens-linux64.tar.gz (depends/ static)
• Windows x86_64 Qt5 wallet — Offerings-v2.1.0-Nodens-win64.zip (mingw-w64 cross via depends/)
• SHA256SUMS-*.txt (also bundled inside each archive)

Provenance note — Linux Qt5 tarball. Built by CI from the tagged commit 78c432fe, but taken from a same-commit verification run that preceded the tag: a mirror outage at xorg.freedesktop.org (expired TLS certificate, 2026-07-28) broke the tag-triggered rebuild's dependency fetch. The bundled binaries therefore self-identify as v2.1.0.0-78c432f-Nodens — 78c432f is the tagged commit. SHA256SUMS-linux-qt5.txt (attached and bundled) is authoritative.

Verifying

$ tar -xzf Offerings-daemon-v2.1.0-Nodens-linux64.tar.gz
$ cd Offerings-daemon-v2.1.0-Nodens-linux64
$ sha256sum -c SHA256SUMS-linux.txt
Offeringsd: OK
Offerings-cli: OK

Upgrading your node (Linux)

sudo systemctl stop offeringsd          # or kill your running daemon
sudo cp Offeringsd /usr/local/bin/
sudo cp Offerings-cli /usr/local/bin/
sudo systemctl start offeringsd
Offerings-cli getinfo | head            # confirm: "version": 2010000

Your wallet.dat and blockchain data are untouched. Brief RPC downtime during restart is expected.

Windows — extract the zip, copy the three .exe files into your Offerings Core install directory, launch the new Offerings-qt.exe. Your %APPDATA%\Offering data directory stays in place.

---

Credit

The CGNAT / RFC 6598 fix (#44) is the work of skifdni (@9019x) — continued contributions to the Restoration line.

Source

• Repository: https://github.com/SubGeniusFinance/Offerings-to-Cthulhu
• Tag: v2.1.0-Nodens at commit 78c432fe9bad0a928f2eb6364760776a357b2208
• Commits since Eldersign: Phase-2 ACP wiring + tests + runbook (#40), -miningaddress (#46), RFC 6598 (#44), fresh-testnet-init fix (#48), ACP runbook -checkpointdepth correction.

---

That is not dead which can eternal lie — and that which watches need never sleep. Iä Nodens.

---

Binaries: this release's files are served from https://23skidoo.info/downloads/ (GitHub assets did not travel with the repository move).

• SHA256SUMS-linux.txt — 0.0 MB
• Offerings-daemon-v2.1.0-Nodens-linux64.tar.gz — 4.9 MB
• Offerings-v2.1.0-Nodens-win64.zip — 23.1 MB
• SHA256SUMS-windows.txt — 0.0 MB
• Offerings-qt-v2.1.0-Nodens-linux64.tar.gz — 23.8 MB
• SHA256SUMS-linux-qt5.txt — 0.0 MB

v2.0.9-Eldersign

v2.0.9 — Eldersign

Released 2026-06-22. A coordinated consensus bundle: four rule changes activate together at block 1,055,555 (~2026-07-23 at 60-second pacing). This is the first scheduled consensus event since the Restoration — read the upgrade guidance below carefully, especially if you mine.

---

⚠️ Installing? Read this first — don't wait for main

Install from this tag now. v2.0.9-Eldersign is the release — build and run it directly from this tag. You do not need to wait for it to land on the main branch. During the soft-fork freeze main deliberately lags; the merge into main is post-freeze bookkeeping on our end (~mid-July) and is not a prerequisite for upgrading.

The only deadline that matters is consensus activation at block 1,055,555 (~2026-07-23): miners MUST be on v2.0.9 before that height; validators and public nodes SHOULD. Don't gate your upgrade on the main-merge — it lands only ~3 days before activation.

What activates at block 1,055,555

Four changes, all gated to the same height so the network steps over the line as one:

• BIP66 — strict-DER signatures (#33). Signature encodings must be strict canonical DER at consensus level, replacing the pre-0.10-era lenient helper with a self-contained parser that no longer depends on OpenSSL version quirks. Enforced at both mempool and block validation from the fork height onward. This is the rule exchange- and wallet-integration checklists literally grep the source for.
• BIP65 — OP_CHECKLOCKTIMEVERIFY (#34). The OP_NOP2 slot becomes OP_CHECKLOCKTIMEVERIFY, enabling script-level absolute timelocks — vault patterns, refund clauses, any cooperative-spend output that must not be reclaimable until a given block or time.
• COINBASE_MATURITY 10 → 240 (#32). A freshly-mined coinbase becomes spendable after 240 confirmations instead of 10 — at 60-second blocks, 10 minutes becomes 4 hours. This lifts coinbase maturity comfortably above the existing MAX_REORG_DEPTH=100 finality guard, so a coinbase can never be spent inside the window where its block could still be reorged out.
• Rolling checkpoints, Phase 1 (#6). A self-advancing, persistent finality guard: as blocks gain confirmation depth the node records a rolling checkpoint, hardening it against deep-reorg attacks from a malicious chain (a hostile peer feeding a fresh-syncing node a poisoned longer history, or the old >80%-hash attacker resurrecting a chain from before the current tip). Complements — does not replace — the runtime MAX_REORG_DEPTH=100 guard and the static h=976,000 checkpoint. Local to each node; no interop effect.

Supporting fixes (no separate activation)

• Miner mempool pre-screen (#39). CreateNewBlock now screens candidate transactions with the same script flags block-validation will apply at the next height. Without this, post-fork a transaction valid under mempool's looser flags but invalid under block-validation's stricter flags (BIP65/66) would be placed into a candidate block and then trip the final validation test-pass — ending the mining attempt. Surfaces only at h ≥ 1,055,555; fixed pre-emptively.
• Public testnet (#38). Seed entry, a re-anchored testnet genesis, an h=0 testnet checkpoint, and testnet/regtest mining without peers — so any contributor can join a public OFF testnet and live-test consensus rcs, not just the Conclave in isolation.
• Retarget diagnostics gated behind -debug=pow (#43). The LWMA-3 retarget diagnostics were unconditional and grew a soak daemon's debug.log to 17.5 GB in a few hours on fast testnets. Now silent unless -debug=pow is set. No effect on mainnet behavior.
• CGNAT / RFC 6598 range treated as non-routable (#42). 100.64.0.0/10 no longer leaks into public addr gossip. (Already on main; rides this release by merge-up.)
• Seed resilience. seed6 replaced with 23skidoo.subgenius.vip for cross-zone DNS resilience.

---

Do I need to upgrade? (read this — it differs from Triune/Restoration)

The Restoration (block 1,000,000) and Triune (989,898 / 999,991) were hard forks: an old binary was forked off the chain. v2.0.9 is different. BIP66, BIP65, and the coinbase-maturity bump are soft-fork-style tightenings — they only ever make more things invalid, never fewer. A non-upgraded node will keep following the canonical chain because everything the upgraded majority produces is still valid under the old, looser rules.

That makes the upgrade pitch honest rather than alarmist:

• If you mine — you MUST upgrade before block 1,055,555. A non-upgraded miner can produce a block that violates one of the new rules (a non-strict-DER signature, a CLTV-failing spend, or a coinbase spent before 240 confirmations). Upgraded nodes — which will be the majority — reject that block and orphan it. You lose the reward. There is no grace for miners.
• If you validate, run an exchange, or run a public node — you should upgrade. A non-upgraded node still follows the chain, but it does not enforce the new rules and will relay transactions the network now rejects. If you integrated OFF expecting BIP66/BIP65 enforcement, enforcement only exists on upgraded nodes. Upgrade to actually get what these rules promise.
• Rolling checkpoints (#6) are on by default and purely local — you benefit the moment you run v2.0.9, with nothing to configure.

Bottom line: miners, no exceptions; everyone else, strongly recommended. The whole network on one ruleset is the goal; the asymmetry above just describes who gets hurt if they skip it.

PROTOCOL_VERSION is unchanged at 90003 — the wire protocol, wallet on-disk format, and RPC dialect are untouched. Your wallet.dat and chain data carry over.

---

Downloads

GitHub release: v2.0.9-Eldersign

• Linux x86_64 daemon + cli — Offerings-daemon-v2.0.9-Eldersign-linux64.tar.gz (depends/ static, glibc 2.35+)
• Linux x86_64 Qt5 wallet — Offerings-qt-v2.0.9-Eldersign-linux64.tar.gz (depends/ static)
• Windows x86_64 Qt5 wallet — Offerings-v2.0.9-Eldersign-win64.zip (mingw-w64 cross via depends/)
• SHA256SUMS-*.txt (also bundled inside each archive)

Verifying

$ tar -xzf Offerings-daemon-v2.0.9-Eldersign-linux64.tar.gz
$ cd Offerings-daemon-v2.0.9-Eldersign-linux64
$ sha256sum -c SHA256SUMS-linux.txt
Offeringsd: OK
Offerings-cli: OK

Upgrading your node (Linux)

sudo systemctl stop offeringsd          # or kill your running daemon
sudo cp Offeringsd /usr/local/bin/
sudo cp Offerings-cli /usr/local/bin/
sudo systemctl start offeringsd
Offerings-cli getinfo | head            # confirm: "version": 2000900

Your wallet.dat and blockchain data are untouched. Brief RPC downtime during restart is expected.

Windows — extract the zip, copy the three .exe files into your Offerings Core install directory, launch the new Offerings-qt.exe. Your %APPDATA%\Offering data directory stays in place.

---

Credit

The BIP66, BIP65, coinbase-maturity, and public-testnet issues (#32 / #33 / #34 / #38) were flagged by skifdni (@9019x) on 2026-06-14 as the structural items standing between OFF and exchange/wallet integration. Continued contributions to the Restoration line.

Source

• Repository: https://github.com/SubGeniusFinance/Offerings-to-Cthulhu
• Tag: v2.0.9-Eldersign at commit 6190df2
• Consensus commits: COINBASE_MATURITY (#32), BIP66 (#33), BIP65 (#34), rolling-checkpoint Phase 1 (#6, six commits) + miner pre-screen (#39); ride-alongs #38 / #43 / #42 + seed swap.

---

Binaries: this release's files are served from https://23skidoo.info/downloads/ (GitHub assets did not travel with the repository move).

• SHA256SUMS-linux.txt — 0.0 MB
• Offerings-daemon-v2.0.9-Eldersign-linux64.tar.gz — 4.9 MB
• SHA256SUMS-windows.txt — 0.0 MB
• Offerings-v2.0.9-Eldersign-win64.zip — 23.1 MB
• SHA256SUMS-linux-qt5.txt — 0.0 MB
• Offerings-qt-v2.0.9-Eldersign-linux64.tar.gz — 23.8 MB

v2.0.8.7

---

Binaries: this release's files are served from https://23skidoo.info/downloads/ (GitHub assets did not travel with the repository move).

• Offerings-daemon-v2.0.8.7-linux64.tar.gz — 4.8 MB
• SHA256SUMS-linux.txt — 0.0 MB
• SHA256SUMS-windows.txt — 0.0 MB
• Offerings-v2.0.8.7-win64.zip — 23.1 MB
• SHA256SUMS-linux-qt5.txt — 0.0 MB
• Offerings-qt-v2.0.8.7-linux64.tar.gz — 23.8 MB

OFF v2.0.8.5 — relay-floor wallet fee (PR #30 by 9019x)

---

Binaries: this release's files are served from https://23skidoo.info/downloads/ (GitHub assets did not travel with the repository move).

• SHA256SUMS-linux.txt — 0.0 MB
• Offerings-daemon-v2.0.8.5-linux64.tar.gz — 4.8 MB
• SHA256SUMS-windows.txt — 0.0 MB
• Offerings-v2.0.8.5-win64.zip — 21.5 MB
• SHA256SUMS-linux-qt5.txt — 0.0 MB
• Offerings-qt-v2.0.8.5-linux64.tar.gz — 22.1 MB

OFF v2.0.8.3 — restore UPnP in shipped binaries

---

Binaries: this release's files are served from https://23skidoo.info/downloads/ (GitHub assets did not travel with the repository move).

• Offerings-daemon-v2.0.8.3-linux64.tar.gz — 4.8 MB
• SHA256SUMS-linux.txt — 0.0 MB
• SHA256SUMS-windows.txt — 0.0 MB
• Offerings-v2.0.8.3-win64.zip — 21.5 MB
• SHA256SUMS-linux-qt5.txt — 0.0 MB
• Offerings-qt-v2.0.8.3-linux64.tar.gz — 22.1 MB

v2.0.8.2

---

Binaries: this release's files are served from https://23skidoo.info/downloads/ (GitHub assets did not travel with the repository move).

• Offerings-daemon-v2.0.8.2-linux64.tar.gz — 4.8 MB
• SHA256SUMS-linux.txt — 0.0 MB
• SHA256SUMS-windows.txt — 0.0 MB
• Offerings-v2.0.8.2-win64.zip — 21.5 MB
• Offerings-qt-v2.0.8.2-linux64.tar.gz — 22.1 MB
• SHA256SUMS-linux-qt5.txt — 0.0 MB

v2.0.8.1

---

Binaries: this release's files are served from https://23skidoo.info/downloads/ (GitHub assets did not travel with the repository move).

• SHA256SUMS-linux.txt — 0.0 MB
• Offerings-daemon-v2.0.8.1-linux64.tar.gz — 4.8 MB
• SHA256SUMS-windows.txt — 0.0 MB
• Offerings-v2.0.8.1-win64.zip — 21.4 MB
• SHA256SUMS-linux-qt5.txt — 0.0 MB
• Offerings-qt-v2.0.8.1-linux64.tar.gz — 22.0 MB