BSV Broadcaster Adds Tools for Managing Customer Access and Usage

Developer Tools, Latest News, Payments Infrastructure

Payments Infrastructure / Developer Tools

In Brief

BSV Broadcaster, which helps wallets and applications submit transactions to BSV Blockchain, has added tools for managing customer access and reporting service usage. Published version 0.21.1 also includes optional controls for how long the service keeps its local transaction records.

News Report

Version 0.21.0 introduced the main changes on November 12 (UTC), followed by version 0.21.1 later that day. Operators enable the new features through Broadcaster’s configuration.

Connecting Customer Access to a Provider

Broadcaster already supported its own API keys—the access codes applications use to call a service. It can now check keys issued and managed by an external provider, such as a customer account or billing service, and apply the service tiers configured by the operator.

Several keys belonging to one customer can share a usage allowance, preventing additional keys from multiplying that customer’s limits. If the provider becomes temporarily unavailable, previously verified, unexpired keys can continue working for a limited period; keys that cannot be checked receive a service-unavailable response.

Reporting How the Service Is Used

Optional usage reporting gives providers totals for requests made with their keys, grouped by UTC date. The reports distinguish successful requests, errors and requests refused by usage limits. Version 0.21.1 adds a network label, helping providers separate activity on the main network from testing environments.

These reports can support customer usage displays or billing calculations, but delivery has a qualification. To avoid counting a batch twice, the system does not resend it when delivery is uncertain. Some failures can therefore leave reported totals incomplete.

Choosing How Long Local Records Remain

Operators using MongoDB can set retention periods for transaction and submission records according to service tier. Automatic expiry is off by default, and existing records without an expiry date are kept. Other supported storage backends do not enforce this retention feature.

Expiry concerns Broadcaster’s own database; it does not erase transactions recorded on BSV Blockchain. Once a local transaction record is deleted under that policy, it can no longer be looked up through that service, and later status updates can be dropped.

The contributor reports automated integration tests and live checks against provider endpoints using a local Broadcaster instance, alongside tests of record expiry in MongoDB.

BSV TIMES Read

Broadcasting supports the moment a wallet sends a payment. Operating that service for several customers also requires control over access, a view of usage and a storage policy.

This release brings those administrative functions into the same software. Service providers remain responsible for deployment, customer interfaces and any pricing, while the reporting and retention limits matter when deciding what they can promise customers.

Developer Context

Dylan, who contributes on GitHub as galt-tr, authored the changes covering external-provider access, usage reporting, record retention and network labeling in the BSV Blockchain organization’s Broadcaster repository.

Source Links

Posted on November 13, 2026 (UTC)