Developer Tools / Network & Protocol
In Brief
ProjectBabbage has introduced a public interoperability laboratory to test how independently developed BSV Blockchain wallets, applications, and supporting services work together. The open-source project already provides runnable testing tools and recorded experimental results for Yours Wallet 5.1.0, while broader testing programs remain under development.
The initiative aims to give developers a shared method for identifying compatibility problems, reproducing results, and improving how different implementations exchange transactions, proofs, and application data.
New Report
ProjectBabbage announced the Transaction Processing Network Interoperability Laboratory (TPNIL) on November 2, 2026, opening a public GitHub repository under the p2ppsr organization.
The project addresses a practical challenge for an expanding application ecosystem: independently developed software may support the same published standards but still behave differently when connected.
For example, an application might successfully create a transaction through one wallet but encounter a problem when retrieving that transaction, restoring its records, or handling a rejected submission through another wallet.
TPNIL is designed to make such differences observable and reproducible.
Rather than relying solely on demonstrations or compatibility claims, the laboratory defines test procedures, expected results, software versions, and evidence requirements.
The repository is publicly available as experimental release 0.5.0. Its original software materials are published under the Apache 2.0 license, with separate permissions applying to certain third-party software submitted for evaluation.
Four Areas of Interoperability Testing
The laboratory organizes its work into four Interoperability and Standardization Initiatives, identified as ISI-1 through ISI-4.
ISI-1 examines complete transaction-processing workflows, following activity across applications, wallets, transaction submission, and supporting infrastructure.
ISI-2 concentrates on overlay services, which help applications organize, exchange, and retrieve particular kinds of blockchain records. Its planned checks include whether independently developed services remain synchronized.
ISI-3 addresses remote wallet storage, including recovery, synchronization, and continuity when storage services change or become unavailable.
ISI-4 focuses on interactions between production wallets and applications using BRC-100, the standard interface through which applications request wallet operations.
The programs use defined testing environments, beginning with ITCVE-1, which provides controlled services and conditions for examining how the components behave together.
All four programs are currently designated as drafts. The laboratory has implemented substantial testing infrastructure, but complete evaluations across independent products are not yet available for every program.
First Experimental Wallet Results
The most concrete published results currently come from ISI-4.
The laboratory reports two matching experimental runs involving the unchanged Yours Wallet 5.1.0 Chromium extension and a ToDo application in a controlled testing environment.
The initial workflow examines whether a wallet can initialize, receive test funding, create an encrypted task, restore the task after the application is reloaded, and complete the task by spending its associated output.
The laboratory records successful outcomes for these first four test groups.
Two additional groups did not meet the laboratory’s specified expectations. One examined permission decisions and separation between application origins. The other examined transaction-submission behavior when a controlled service rejects a transaction and the wallet must preserve or recover its state.
Two further groups remain blocked because the laboratory has not yet completed the required testing arrangements for replacing storage providers and evaluating the full range of BRC-100 operations.
These results are specific to Yours Wallet 5.1.0, the selected testing environment, and the laboratory’s published criteria. They do not establish that other versions or deployment configurations behave identically.
The laboratory also distinguishes controlled-service transaction outcomes from acceptance on BSV Blockchain mainnet. Although the wallet operates in its ordinary mainnet configuration, the initial tests use isolated services and test funding rather than public-mainnet transactions.
The findings remain experimental evaluations, not product certification or a comprehensive security assessment.
Other Wallets and Applications
The repository also identifies BSV Desktop, Metanet Explorer, and BSV Browser as candidates at different stages of testing.
BSV Desktop 2.8.5 has undergone installation and initialization checks on clean macOS environments, including tests of its local BRC-100 connection. A complete scored interoperability result has not yet been published.
Metanet Explorer 1.1.10 has been examined in four controlled Android runs. Those tests progressed through account activation, funding, and publication of wallet-related records, but the ToDo task workflow stopped while waiting for a response from the native wallet.
BSV Browser 1.6.1 has reached an engineering testing stage using a source-based build. A production result remains pending because the laboratory requires an appropriate publisher-provided software artifact.
These distinctions are part of the project’s testing approach. Preparing a wallet for evaluation, successfully running a particular component, and completing an entire interoperability test are recorded as different achievements.
What Developers Can Use Today
The public repository includes executable testing code, machine-readable test definitions, infrastructure configurations, instructions, and retained evidence from completed runs.
Its basic testing tools use Node.js and Python 3. Developers can run local checks, inspect the expected behavior of test cases, and verify published evidence records.
More extensive wallet and infrastructure tests require the relevant software versions, prepared environments, and controlled supporting services.
The project also uses GitHub Actions for automated checks. Public workflow records show completed runs, although a successfully executed workflow does not mean every compatibility test within it passed.
The laboratory’s current documentation distinguishes software self-tests, infrastructure checks, application testing, and experimental conformance results.
The project has not yet established a certification program. ProjectBabbage describes formal certification or accreditation as a possible future direction.
BSV TIMES Read
Interoperability becomes increasingly important as BSV Blockchain applications move beyond isolated demonstrations.
A shared standard gives developers a common interface, but practical compatibility depends on how each implementation handles the full sequence of operations.
Consider a user creating an encrypted record through an application. The wallet must authorize the operation, construct the necessary transaction, preserve the relevant information, and make it available when the application returns.
If the user later changes devices, restarts the application, or connects through a different compatible service, the record should remain accessible under the intended permissions.
An interoperability test can examine that entire sequence instead of checking only whether the first transaction was created successfully.
TPNIL’s significance lies in establishing a public method for investigating these relationships. Its published tests and supporting records allow developers to identify which operations succeeded, where a process stopped, and which results still need further evidence.
The initial laboratory is incomplete, and the interpretation of its results will require continued scrutiny as additional developers and implementations participate.
Nevertheless, the availability of executable tests and documented outcomes provides a practical foundation for improving compatibility across BSV Blockchain software.
Developer Context
The interoperability laboratory is hosted by the p2ppsr GitHub organization and was publicly introduced through ProjectBabbage.
The repository identifies Ty Everett, Bridget Doran, and RexStarBSV among its contributors.
Its testing programs draw on the BRC-100 wallet interface and related BSV Blockchain standards for transaction handling, proofs, storage, and application interoperability.
The ISI-4 demonstration uses a versioned ToDo application and controlled wallet services. Published evidence includes software identities, test conditions, individual assertions, and recorded outcomes.
The project welcomes technical participation and additional implementations, subject to its published contribution, governance, and software-submission procedures.
Source Link
ProjectBabbage — Interoperability Lab Announcement
ProjectBabbage — ISI-4 Explanation
GitHub — Transaction Processing Network Interoperability Laboratory
ISI-4 — Wallet and Application Testing Program
ISI-4 — Published Yours Wallet Experimental Results
TPNIL — Public Automated Testing Activity
Posted on November 7, 2026 (UTC)

Leave a Reply