Digital Product Passport Project Merges Wallet-Signed Publisher Registration

Enterprise / Developer Tools

In Brief

The BSV Blockchain Digital Product Passport project has added a way for an application to ask an index to accept the product records it signs. The application’s wallet signs the request, and the index operator decides whether to admit the publisher automatically or review the request first.

The feature merged into the reference software on November 3. Developers can build it from source; the published package and the hosted reference index still use the October version.

News Report

A digital product passport can record what happens to a product over time, from manufacture to repair or transfer. An index makes those records discoverable. When an index restricts who can publish, it needs a way to recognize a new application’s signing key.

The project introduced that registration process in pull request #185, merged on November 3, 2026, at 02:41 UTC. It builds on a November 2 change that gave each publisher its own access credentials.

How an Application Joins an Index

The application sends a signed request naming its public key, the index it wants to join, the blockchain network and the custody rules it uses. The index checks the signature and those details, and requires the request time to fall within a ten-minute window. A request signed for one index cannot be reused to register at another.

Once the operator accepts the request, its software signs an updated list of authorized publishing keys. The application receives two credentials: one for submitting or retracting record announcements, and one for notifications from the transaction broadcaster. Each credential is restricted to its designated key and purpose.

Registration is off by default. The current implementation supports passport publishers on an index running the project’s standalone, single-operator configuration. An operator can refuse a request or later retire a key and revoke its credentials. A policy can hold up to 256 publisher entries, including retired entries.

What Developers Can Use Today

The project lists registration in its November source candidate, which specifies @bsv/dpp-overlay version 0.4.0-beta.13. On November 3, npm still listed 0.4.0-beta.12, published October 16, as the latest version. The hosted reference index also reported beta 12 in its public capability document.

Developers can therefore try registration by building the November code and enabling it on their own index. Installing the published package does not provide the new workflow.

BSV TIMES Read

Consider a manufacturer and a service partner whose applications publish equipment updates to the same index. The operator can withdraw one application’s access without replacing the other’s credentials. That matters when a service contract ends but the manufacturer still needs to publish updates for the same equipment.

The wallet signature establishes that the applicant controls the publishing key. An operator that also needs to establish that the applicant is an authorized service partner can use approval mode to check that relationship. After admission, the records themselves still have to pass the index’s checks.

Developer Context

Mohammad Jaber, who contributes as mo-jaber, authored both the registration change and the preceding work on publisher credentials. Jaber identifies himself as Head of Solutions at the BSV Association and co-founder of Elas.

The implementation uses the BRC-100 wallet signing interface and BRC-42 key derivation to bind each request to the intended index while keeping the publisher’s private key in its wallet.

Source Links

Posted on November 3, 2026 (UTC)