BitPlan Launches Encrypted, Versioned Plan Documents on BSV Blockchain

Data Applications Watch / Data Infrastructure

In Brief

Open Protocol Labs developer Luke Rohenaz has launched BitPlan, an open-source tool for publishing encrypted, versioned planning documents to BSV Blockchain through a local BRC-100 wallet. Designed particularly for local AI and agent workflows, BitPlan stores the encrypted document as a 1Sat Ordinal rather than placing the readable content on a conventional application server, while successive inscriptions provide a continuing history of the document.

News Report

BitPlan has launched as a browser and command-line application for publishing encrypted planning documents to BSV Blockchain while keeping their readable contents accessible only to authorized users.

Developer Luke Rohenaz introduced the project on August 29 as a tool aimed particularly at private local AI workflows, where agents and coding tools increasingly generate plans, specifications and other working documents that users may not want stored in a conventional hosted service.

The basic workflow starts locally.

A user prepares a plan document and sends it through the BitPlan command-line tool. BitPlan uses a local BRC-100-compatible wallet to encrypt the document and create the transaction that publishes it as a 1Sat Ordinal. The encrypted artifact can later be located through BitPlan’s browser interface and decrypted by an authorized wallet.

This separates the application from the user’s cryptographic keys.

BRC-100 defines a vendor-neutral interface between applications and BSV wallets, including standardized methods for transaction creation, signing, public-key access, encryption and decryption. Applications can therefore request those operations while the wallet retains responsibility for the underlying keys and authorization. (GitHub)

For BitPlan, that means the command-line application does not need to become a separate custodial wallet merely to encrypt and publish a plan.

The storage model also differs from uploading an encrypted document to a normal cloud service.

According to the project, the encrypted document itself is published as a 1Sat Ordinal. Once the transaction has been published and confirmed, the underlying encrypted artifact does not depend on BitPlan maintaining a private database copy of the plan.

The BitPlan website still provides a convenient way to locate and render the material, but the encrypted payload exists independently as blockchain data.

That distinction is important for understanding the privacy model.

The blockchain record is public. Anyone capable of retrieving the transaction can obtain the encrypted bytes. Privacy comes from the fact that the readable content is encrypted before publication and requires the appropriate key capability for decryption.

BitPlan therefore combines public persistence with private content rather than attempting to make the underlying blockchain record itself private.

The project also uses the continuing identity of a 1-satoshi ordinal to provide document versioning.

Under the 1Sat Ordinals model, an individual one-satoshi output can retain a persistent origin as it is spent forward through subsequent outputs. The current 1Sat specification describes the origin as the permanent identifier of that one-satoshi chain while the current outpoint changes as the ordinal moves. (GitHub)

BitPlan builds its document history around that continuity.

A plan begins as an encrypted inscription associated with a 1Sat Ordinal. When the document changes, a subsequent encrypted version can be re-inscribed through the continuing ordinal rather than being treated as an unrelated document.

The result is a persistent document identity with successive versions associated with its transaction history.

Rohenaz says the same mechanism can also be used to change who is able to read a document. A later version can include another identity key so that an intended recipient can decrypt the newly published material, allowing a private plan to be shared without making the plaintext publicly accessible.

That gives BitPlan uses beyond personal archival.

A local AI agent could generate a plan, an authorized user could publish it through a local wallet, and another authorized person or agent could later receive access to an updated version. The public blockchain provides the persistent artifact and version history while encryption controls who can interpret its contents.

The project is particularly targeted at agent-generated planning documents.

Rohenaz contrasted BitPlan with hosted planning services where an agent’s plan may ultimately reside in a provider-controlled database. Even if an application does not publicly expose the page, the service operator still holds the underlying content.

BitPlan instead places the storage layer outside the application provider:

local document → wallet-controlled encryption → encrypted 1Sat Ordinal → browser retrieval → authorized decryption.

The website and command-line implementation have also been released as open-source software under an MIT license, allowing developers to inspect or adapt the workflow rather than depending exclusively on the hosted BitPlan interface.

The privacy properties should nevertheless be understood conservatively.

Publishing encrypted material permanently to a public blockchain means the ciphertext itself can remain available indefinitely. Confidentiality therefore depends on the strength of the encryption implementation and the security of the user’s keys. BSV TIMES has not independently audited BitPlan’s cryptographic implementation.

The launch nevertheless provides a functioning example of BRC-100 wallet services, encryption, 1Sat Ordinals and browser-based retrieval being combined into a single application for private document workflows.

BSV TIMES Read

BitPlan is interesting less because an AI agent can generate a plan than because of where that plan lives afterward.

Many AI applications are still built around the familiar cloud model: generate information locally or through an agent, send it to an application server, and rely on that service to preserve both the document and access to it.

BitPlan separates those responsibilities.

The wallet controls encryption and transaction authorization. BSV Blockchain provides persistent publication. The browser provides a convenient interface for retrieval and reading. The application itself does not have to become the permanent custodian of either the document or the user’s keys.

The versioning model adds another useful property. Instead of treating every revision as an unrelated file, a single 1Sat Ordinal can provide continuing identity while new inscriptions represent changes over time. The transaction history then becomes part of the document’s history rather than something maintained solely by an application database.

This does not remove the need for good encryption, secure keys or useful software interfaces. It does show a different division of responsibility: public infrastructure can preserve the encrypted artifact while the user retains control over who can read it.

For AI and agent workflows that increasingly generate valuable private working material, that is a practical example of blockchain functioning as data infrastructure rather than simply as a payment rail.