BRC-229 Wallet Module Fixes Flaw That Could Let Apps Read Encrypted Data

BRC-229 Wallet Module Fixes Flaw That Could Let Apps Read Encrypted Data
, ,

BRC / Wallets & Identity

News Report

Wallet providers that enabled the optional BRC-229 module now have a fix for a flaw that could let an app read encrypted data without the wallet owner’s approval. Version 0.2.0 was published on November 20 (UTC). The maintainers gave the flaw a high severity rating and said they had observed no exploitation. It did not expose the private keys used to spend BSV tokens.

The module lets an app ask a wallet to perform a calculation and receive the result while the wallet keeps its secrets private. In versions 0.1.0 through 0.1.4, an app could also learn a secret used to protect other data. If the app had a copy of that data in encrypted form, it could use the secret to read it.

The maintainers advise wallet providers to update or disable the module until they can. Changing permission settings alone does not fix the flaw. The written BRC-229 standard was amended later the same day so developers building their own implementations can follow the corrected method.

BSV TIMES Read

BRC-229 gives the example of an online card game in which the players’ wallets help shuffle a deck without revealing the cards. A card concealed with the old module cannot be revealed with the new one, so a game switching versions mid-hand would need a fresh deal. The same limit applies to other apps that use the module to conceal a value and later reveal it.

Developer Context

Connor Murray wrote BRC-229 and BRC-206, a separate wallet signature standard that the advisory says is unaffected. Ty Everett submitted the BRC-229 amendment. He also wrote BRC-42, which describes how wallets derive keys, and coauthored BRC-100, the interface between wallets and apps, with Tone Engel and Brayden Langley.

Source Links

Posted on November 21, 2026 (UTC)

Leave a Reply