Why Builder’s Week Is Worth Reading

Craig Wright’s recent article, “The Builder’s Week: A Working Bitcoin Stack Appears, One Repository at a Time,” is worth a close read.

The focus is on practical building blocks: micropayments, verifiable accounting, selective disclosure, encrypted access control, and transaction-native applications. It is written as a builder’s report. The repositories are presented with their intended purpose, how they fit together, and, importantly, their current limitations.

One of the repositories demonstrates sub-satoshi payment channels. Since BSV Blockchain records value in whole satoshis, the system allows smaller accounting units to exist inside a channel and later reconciles the final balances back into whole satoshis at settlement. The purpose is to support very small-value activity, such as tiny API or data charges, where the economic unit may be smaller than one satoshi even though the final on-chain settlement must remain in whole satoshis.

This also connects with a broader question I have thought about before: if one satoshi represents much more economic value over time, node operator fee policy may also evolve. For example, a node could choose to price certain high-volume business relationships in batches, such as charging one satoshi for many small transactions, depending on demand, competition, and the value of the BSV token at the time. That is not the same mechanism as a sub-satoshi payment channel, but both ideas point to the same underlying issue: useful digital activity may eventually require economic units smaller than one satoshi at the application level, even while final settlement remains grounded in whole satoshis on BSV Blockchain.

Another repository focuses on verifiable accounting. Using Merkle proofs and selective disclosure, specific records can be proven as included and unchanged without exposing an entire dataset. This allows auditors or regulators to verify particular information while preserving privacy for unrelated records.

This is an important distinction. The objective is not complete transparency of all data. The objective is verifiable disclosure when disclosure is required.

The article also introduces an overlay broadcast encryption system. This provides a way to manage access rights efficiently for groups of users while allowing membership changes and revocations to be handled through cryptographic mechanisms. Potential applications include subscription services, private content, business records, and controlled-access data systems.

The final example is a dealerless card-game protocol. While card games themselves may not be the main attraction, the repository demonstrates how application logic, commitments, encrypted information, and state transitions can be represented through transactions rather than being controlled entirely by a central operator.

Micropayments, audit evidence, selective disclosure, access control, and application logic are all pieces that developers repeatedly need when building real systems. Seeing these capabilities presented as a connected stack is more interesting than seeing them as isolated technical demonstrations.

The article is also careful about what these repositories do not yet provide. They are research projects rather than polished consumer products. Integration remains incomplete in places. Some components are still under development. The accounting system, for example, can prove that records were committed and preserved, but it cannot prove that the original information entered into the system was truthful.

**The Builder’s Week: A Working Bitcoin Stack Appears, One Repository at a Time — Craig Wright**