Under the Surface looks at projects, standards, experiments, and community activity that may not rise to the level of a headline but are still worth noticing. Some are new, some are continuing work, and some are quieter developments that help show what is taking shape across the BSV community.
Content Infrastructure / Conditional Access
BRC-369 explores a different way to control access to digital content.
Instead of keeping the content itself behind a platform login or publishing it in readable form while an application merely hides it from unpaid users, the protocol starts by encrypting the content.
The encrypted bytes can then be distributed publicly.
What remains restricted is the key.
A reader who satisfies a defined condition—such as making a payment or passing an access check—can receive the key needed to decrypt the material.
That changes what the platform has to control.
A conventional paywall typically keeps access alive through a database entry. The service remembers that a particular account has paid and continues serving the content while that account and service remain available.
BRC-369 instead allows the recipient to end up holding both the encrypted content and the key required to read it.
Once obtained, continued access does not require the original application to remain online.
The content can be checked before payment
The proposal also separates availability from secrecy.
Encrypted content does not need to be hidden.
Because the ciphertext can be public and addressed by its hash, a prospective buyer can first establish that the promised object actually exists, can be downloaded and matches the material committed to by the publisher.
The buyer still cannot read it without the key.
That means an application can check availability and integrity before asking the user to pay rather than requiring payment for an object whose continued existence is known only to the seller.
The publisher also commits to the content key in advance.
When a releaser later supplies a key to a qualifying recipient, the recipient can verify that the key corresponds to the earlier commitment and that it successfully authenticates and decrypts the committed ciphertext.
Those checks separate several possible failures.
A mismatched content hash indicates that different ciphertext was supplied.
A failed key commitment indicates that the releaser supplied something other than the committed key.
If those checks pass but authenticated decryption fails, the evidence instead points back toward the publisher having committed to a key that did not encrypt the published object correctly.
The purpose is not merely to detect that something failed, but to make different failure conditions distinguishable.
The releaser is still part of the system
BRC-369 does not claim to eliminate every trusted or online participant.
Someone still has to determine whether the recipient satisfied the stated condition and deliver the key.
The protocol calls that party the releaser.
The releaser is identified through signed information, its authority can be bounded and revoked, and the key delivered to a recipient can be checked against the publisher’s earlier commitment.
But the releaser still has to be reachable when a new recipient requests access.
That limitation is important.
The design is not a mechanism in which encrypted content somehow unlocks itself without an online decision point. It is instead an attempt to narrow what that decision point controls.
Once the legitimate recipient obtains the key, the releaser no longer needs to remain available for that recipient to continue reading the material.
Distribution can make the encrypted object more durable
Because the ciphertext itself is not secret, multiple hosts can store the same encrypted object.
Recipients can also retain and redistribute the ciphertext without giving away access, because possession of the encrypted bytes alone does not reveal the content.
That creates an unusual availability property.
The content does not have to disappear simply because the original publisher stops hosting it. As more legitimate recipients obtain copies, more copies of the encrypted material can potentially remain available.
What stays controlled is key release rather than possession of the ciphertext.
BRC-369 also defines a separate model for gated groups, where membership changes require new encryption keys so that someone leaving a group cannot continue decrypting future material. Previous access is deliberately not retroactively removed: a participant who legitimately possessed an earlier key retains access to the material available during that period.
The proposal remains a protocol specification rather than evidence of broad application adoption.
But it addresses a useful distinction for portable digital content.
Paying for access does not necessarily have to mean renting a permission entry in somebody else’s database.
It can instead mean obtaining verifiable access material that the recipient can retain independently, while the encrypted publication itself remains portable across storage providers and applications.
Source References
BRC-369 original specification
Update — September 14, 2026
Leave a comment