StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues Pull Requests 3 Packages Projects Releases Wiki Activity

Bump digibyted 9.26.4→9.26.5 (source-build asset) #43

Merged
sebastian merged 1 commits from vupd/1924-digibyted-v9.26.5 into main 2026-07-27 23:57:01 +00:00
Conversation 0 Commits 1 Files Changed 1 +2 -2
claude commented 2026-07-26 06:39:53 +00:00
Collaborator
Copy Link

Bump digibyted 9.26.4 → 9.26.5 — source-build asset (DigiByte Core v9.26.5)

Release: DigiByte Core v9.26.5 (stable, 2026-07-23) — post-activation maintenance: startup-hang fix + BIP90 burial of already-active deployments.

This PR (asset): digibyte/digibyted.Dockerfile — ARG VERSION 9.26.4→9.26.5, ARG SHA256→37f6bf6a682f99b5966c2bd3f0cfe3013b60b7b55268958663231ebbf9e56773 (verified against the release tarball). digibyted has no upstream Docker image — this Dockerfile fetches and builds the official release tarball.

Companion PR: StakeSquid/vibe-node vupd/1924-digibyted-v9.26.5 bumps context.yml digibyte/digibyted client_version 9.26.4→9.26.5. The rpc gitlink is set to rpc main HEAD at deploy time (never carried in a diff), so the two PRs are independent to merge in either order.

Fork status: No consensus deadline. DigiDollar/AlgoLock soft forks already activated on mainnet at block 23869440 (2026-07-17); v9.26.5 is post-activation.

Breaking changes (consumer-facing RPC only — node upgrade is drop-in):

  • getdeploymentinfo / getdigidollardeploymentinfo (and REST /deploymentinfo) now report taproot/digidollar/algolock as type=buried (active/height); the bip9 sub-object and signaling bits are removed.
  • getblocktemplate vbavailable/version no longer carry signaling bits.
  • Handled as a drop-in node bump — version + Dockerfile SHA only; no reindex, no config/compose changes. Only downstream RPC parsers/dashboards need updating.

⚠️ digibyte is currently dormant in the fleet — not deployed/served anywhere (zero 7-day DRPC market, no running container fleet-wide, empty DRPC node status). It was removed after the 2026-07-04 9.26.4 deploy while the version pin + Dockerfile asset remained in the repo. There is therefore no live host to verify on. This merge updates the dormant pinned asset so the next digibyte-mainnet provisioning builds 9.26.5; the post-merge fleet deploy will be a no-op until digibyte is re-provisioned. If digibyte is being retired, close this — the bump is harmless but unnecessary.

Verify plan (when digibyte is next provisioned): digibyted --version = 9.26.5, healthy getblockchaininfo, no crashloop, getdeploymentinfo returns the new buried shape.

Ref: StakeSquid/vibe-node#1924

## Bump digibyted 9.26.4 → 9.26.5 — source-build asset (DigiByte Core v9.26.5) **Release:** [DigiByte Core v9.26.5](https://github.com/DigiByte-Core/digibyte/releases/tag/v9.26.5) (stable, 2026-07-23) — post-activation maintenance: startup-hang fix + BIP90 burial of already-active deployments. **This PR (asset):** `digibyte/digibyted.Dockerfile` — `ARG VERSION` `9.26.4`→`9.26.5`, `ARG SHA256`→`37f6bf6a682f99b5966c2bd3f0cfe3013b60b7b55268958663231ebbf9e56773` (verified against the release tarball). digibyted has **no upstream Docker image** — this Dockerfile fetches and builds the official release tarball. **Companion PR:** StakeSquid/vibe-node `vupd/1924-digibyted-v9.26.5` bumps `context.yml` `digibyte`/`digibyted` `client_version` `9.26.4`→`9.26.5`. The rpc gitlink is set to rpc `main` HEAD at deploy time (never carried in a diff), so **the two PRs are independent to merge** in either order. **Fork status:** No consensus deadline. DigiDollar/AlgoLock soft forks already activated on mainnet at block **23869440** (2026-07-17); v9.26.5 is post-activation. **Breaking changes (consumer-facing RPC only — node upgrade is drop-in):** - `getdeploymentinfo` / `getdigidollardeploymentinfo` (and REST `/deploymentinfo`) now report taproot/digidollar/algolock as `type=buried` (`active`/`height`); the `bip9` sub-object and signaling bits are removed. - `getblocktemplate` `vbavailable`/`version` no longer carry signaling bits. - **Handled as a drop-in node bump** — version + Dockerfile SHA only; no reindex, no config/compose changes. Only downstream RPC parsers/dashboards need updating. **⚠️ digibyte is currently dormant in the fleet** — not deployed/served anywhere (zero 7-day DRPC market, no running container fleet-wide, empty DRPC node status). It was removed after the 2026-07-04 9.26.4 deploy while the version pin + Dockerfile asset remained in the repo. There is therefore **no live host to verify on**. This merge updates the dormant pinned asset so the next digibyte-mainnet provisioning builds 9.26.5; the post-merge fleet deploy will be a no-op until digibyte is re-provisioned. **If digibyte is being retired, close this — the bump is harmless but unnecessary.** **Verify plan (when digibyte is next provisioned):** `digibyted --version` = 9.26.5, healthy `getblockchaininfo`, no crashloop, `getdeploymentinfo` returns the new buried shape. Ref: StakeSquid/vibe-node#1924
claude added 1 commit 2026-07-26 06:39:53 +00:00
digibyte: bump digibyted Dockerfile 9.26.4 -> 9.26.5 81985dbc98 
Post-activation maintenance release; update VERSION and tarball SHA256.
sebastian merged commit 81985dbc98 into main 2026-07-27 23:57:01 +00:00
sebastian deleted branch vupd/1924-digibyted-v9.26.5 2026-07-27 23:57:01 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude cursor rob sebastian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#43
Delete Branch "vupd/1924-digibyted-v9.26.5"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?