bitcoind

3 Commits 1 Branch 0 Tags

3 Commits

Author	SHA1	Message	Date
bitdeals	e0de8701db	ci: allow the publish job to be started by hand Build docker image and push to registry.bitdeals.org / build (push) Successful in 47s Details Also re-triggers the build, which is what this commit is for right now: the first run built the image and then stopped at docker login, because the registry secrets did not exist for this repository yet. workflow_dispatch earns its place beyond that — the image content depends on BITCOIN_VERSION, a build argument, so a new upstream release is a reason to rebuild without a commit to point at.	2026-08-06 13:08:48 +00:00
bitdeals	3a52b5128b	ci: build and publish the image on every push to main Build docker image and push to registry.bitdeals.org / build (push) Failing after 3m16s Details The registry account available on the testnet hosts is pull-only (403 on a blob upload even for an existing repository), so publishing goes the same way every other BitDeals image does: the Gitea runner builds and pushes with the CI credentials. Tags mirror the family — an immutable <version>.<sha7>, a moving <version>, and :latest for compose and Watchtower. The version is read out of the Dockerfile ARG rather than repeated here: a tag that can disagree with the binary inside is worse than no tag.	2026-08-06 12:01:10 +00:00
bitdeals	bf2c2d3508	feat: docker image for Bitcoin Core, configured by environment Replaces lncm/bitcoind, which pins Core 26 — a version that still has legacy wallets, while the code that talks to it (bt's BitcoindClient) is written for the descriptor-only behaviour of 29 and later. The binaries are the official release build, verified by SHA-256 in the same layer that downloads them; a version bump that forgets the checksum fails the build instead of shipping something unverified. uid 1000 and /data/.bitcoin are kept from the image this replaces, so an existing named volume survives the switch without a recursive chown of a synced chain. Verified on testnet2: regtest node healthy in ~12 s, descriptor wallet, 101 blocks mined, sendtoaddress accepted — the last one being the check for BITCOIND_FALLBACKFEE, without which a fresh chain refuses to send.	2026-08-06 11:56:52 +00:00

Author

SHA1

Message

Date

bitdeals

e0de8701db

ci: allow the publish job to be started by hand

Build docker image and push to registry.bitdeals.org / build (push) Successful in 47s

Details

Also re-triggers the build, which is what this commit is for right now: the
first run built the image and then stopped at docker login, because the
registry secrets did not exist for this repository yet.

workflow_dispatch earns its place beyond that — the image content depends on
BITCOIN_VERSION, a build argument, so a new upstream release is a reason to
rebuild without a commit to point at.

2026-08-06 13:08:48 +00:00

bitdeals

3a52b5128b

ci: build and publish the image on every push to main

Build docker image and push to registry.bitdeals.org / build (push) Failing after 3m16s

Details

The registry account available on the testnet hosts is pull-only (403 on a
blob upload even for an existing repository), so publishing goes the same way
every other BitDeals image does: the Gitea runner builds and pushes with the
CI credentials. Tags mirror the family — an immutable <version>.<sha7>, a
moving <version>, and :latest for compose and Watchtower.

The version is read out of the Dockerfile ARG rather than repeated here: a tag
that can disagree with the binary inside is worse than no tag.

2026-08-06 12:01:10 +00:00

bitdeals

bf2c2d3508

feat: docker image for Bitcoin Core, configured by environment

Replaces lncm/bitcoind, which pins Core 26 — a version that still has legacy
wallets, while the code that talks to it (bt's BitcoindClient) is written for
the descriptor-only behaviour of 29 and later.

The binaries are the official release build, verified by SHA-256 in the same
layer that downloads them; a version bump that forgets the checksum fails the
build instead of shipping something unverified. uid 1000 and /data/.bitcoin are
kept from the image this replaces, so an existing named volume survives the
switch without a recursive chown of a synced chain.

Verified on testnet2: regtest node healthy in ~12 s, descriptor wallet, 101
blocks mined, sendtoaddress accepted — the last one being the check for
BITCOIND_FALLBACKFEE, without which a fresh chain refuses to send.

2026-08-06 11:56:52 +00:00