Arcade Becomes BSV Broadcaster in v0.19.0 Release

Payments Infrastructure / Developer Tools

In Brief

The Arcade transaction-broadcasting project has published version 0.19.0 under the name BSV Broadcaster. The release appeared on October 26 at 16:35 UTC.

The change reaches beyond the project’s name. It updates deployment identifiers, configuration defaults, monitoring metrics and storage locations, giving existing operators a migration to review before upgrading.

News Report

BSV Broadcaster provides a transaction-submission and status-tracking service for applications using Teranode. It follows transactions through the network and supplies notifications and Merkle proof information needed by wallets and other clients.

Version 0.19.0 incorporates the rebranding work merged through pull request #380, alongside a Docker Compose dependency update. The repository now resides at bsv-blockchain/broadcaster; the former Arcade repository address redirects there.

BSV TIMES’ October 26 report covered Arcade support merged into the Python Wallet Toolbox. This release concerns the broadcasting service itself, including the settings operators use to connect it to databases, message queues and monitoring systems.

New Names Across the Deployment

The executable is now bsv-broadcaster, and the container image uses ghcr.io/bsv-blockchain/broadcaster. Go applications importing the project also receive a new module path.

Configuration environment variables move from the ARCADE_ prefix to BSV_BROADCASTER_. Existing variables remain supported through a compatibility layer, with explicitly configured new names taking precedence. The old configuration directory remains searchable, and either legacy mechanism produces a deprecation warning.

That compatibility preserves explicit settings. Values an operator previously left unset receive the new defaults, including renamed Kafka topics and consumer groups, database identifiers and local storage paths.

Existing State Needs Explicit Attention

The migration guide identifies two consequences of relying on changed defaults. A service can connect to a new, empty database or local store, while a new Kafka consumer group can replay or skip transaction-status and block-processing messages.

The project therefore directs existing operators to preserve the relevant settings for the storage backends and messaging infrastructure they actually use. Moving stored data or queue names to the new naming scheme can be handled separately.

Monitoring also changes. Prometheus metrics now begin with bsv_broadcaster_, and the old metric names have no compatibility aliases. Dashboards and alerts need corresponding updates. Webhook receivers that restrict accepted User-Agent prefixes must account for the new broadcaster name.

For Kubernetes deployments, the documentation calls out a further migration step: the old Chaintracks process must finish shutting down before its replacement writes to the shared header store. Renamed Deployments can otherwise run alongside their predecessors, allowing two writers to corrupt checkpoint metadata.

Published Release and Build Evidence

The release’s GitHub test workflow completed successfully, including unit tests, linting, static checks and fuzz tests. Its container build workflow also passed for Linux amd64 and arm64.

During this check, the public container registry returned the v0.19.0 image manifest without account credentials, listing both architectures. This confirms that the release image is available through the new repository path.

BSV TIMES has not independently run the image or tested an upgrade against an existing production deployment.

BSV TIMES Read

Broadcasting services connect application submissions with network progress and confirmation evidence. Their operational settings determine whether wallets continue receiving useful status information as infrastructure changes.

This release makes the BSV Broadcaster name part of the software’s deployment interface. The practical significance for existing users lies in preserving stored state, message-consumption positions and monitoring coverage during that transition.

The published migration guide gives operators a concrete basis for planning the upgrade, while the successful builds and publicly accessible image establish a release milestone beyond the repository rename.

Developer Context

The rebranding contribution was authored by galt-tr, whose public GitHub profile lists the name Dylan. The work includes configuration compatibility, deployment updates and migration documentation in the BSV Blockchain organization’s broadcaster repository.

Source Links

Posted on October 27, 2026 (UTC)