Unwriter answers the call, adapts Datapay for safe on-chain data

The road to Genesis, the protocol upgrade which will see Bitcoin returned as closely as possible to its original protocol and vision, will require plenty of little contributions from everyone in the community. Following Steve Shadders’ call to action for all app developers, Unwriter has answered the call.

In a recent Twitter announcement, Unwriter has announced Datapay has been updated to support “safe” mode, the new OP_RETURN standard capable of handling the Genesis upgrade.

As Unwriter notes, this solves “the ‘WRITE’ side of the equation.” With the upgrade, Datapay is now both future proof, and ready for the February 2020 Genesis upgrade, but also backwards compatible, capable of continuing to work with apps that are not yet configured for the protocol change.

He also goes on to explain what other developers need to do to get on board, linking to a past thread that explains the new code and why it’s superior.

That thread is very similar to Shadders’ own call to action, which revealed the need for all app developers to upgrade their OP_RETURN code. He made that call in late July, outlining the exact code that apps would need to implement to keep their program running when February, 2020 arrives. While the code change is fairly simple, it’s an important one to keep applications running when Genesis arrives.

Unwriter wasn’t the first to take up the call to upgrade though. Money Button made the same upgraded to safe on-chain date earlier in August. When making the change, the wallet’s blog celebrated the potential gains in efficiency users and miners could experience from the changes impact.

That marks one of the biggest BSV wallets and one of the BSV communities’ biggest developers taking up Shadders call to action. Shadders made that call with many months to go before change was absolutely required, but the sooner every developer adapts their application to be futureproof, the sooner the community can move on to the next pressing task as Bitcoin moves back to Genesis.

Post to Bitcoin SV blockchain with ‘simplest’ Datapay JavaScript library

Prolific cryptocurrency developer Unwriter is making good on his promise “to build everything on top of Bitcoin”—Bitcoin SV (BSV) to be specific.

On January 2, the eve of the 10th anniversary of the Bitcoin genesis block, Unwriter announced on Twitter the launch of Datapay, the “simplest” JavaScript library for building and broadcasting data transactions to the BSV blockchain. It’s so simple, according to the developer, that “all it takes is 4 lines (of code) to start writing data” to the BSV chain.

Forked from Datacash, the library Unwriter wrote for the BCH, Datapay uses BSV Explorer as its default RPC. It’s also powered by bsv, a library for cryptography, key management and transaction building for Bitcoin SV. But unlike the conventional Bitcoin transaction libraries, which focus on sending money, Datapay is designed with a different philosophy—send data as simple as possible.

To do this, the Datapay library only has two methods: build, for building a transaction but not broadcasting it to the network; and send, for sending a transaction.

Unwriter explained on GitHub, “Datapay was created in order to make it dead simple to construct OP_RETURN related transactions, but you can even use it to build regular transactions. Also Datapay exposes datapay.bsv endpoint which you can use to access the underlying bsv library.”

In December, Unwriter announced that he would be transitioning all his projects to use the bsv library, which is being maintained by Money Button for the BSV ecosystem. The crypto developer’s move is in line with his decision “to build everything on top of Bitcoin.” Unwriter, who was behind a number of the useful infrastructure projects in the Bitcoin Cash ecosystem, noted in a Medium post that Bitcoin SV is the real Bitcoin, explaining, “I feel 100% safe operating on SV because the protocol hasn’t changed at all, there has been no behind-the-doors centralized collusion.”

Unwriter, however, believes app developers have a common goal. He points out, “Regardless of what BCH has become, I see all app developers—even those who confuse me as evil—as being on the same side, you just don’t realize yet.”