₿itĐaddy

Bitcoin SV has been restored to re-enable full functionality and scale. BSV is an unbounded Bitcoin protocol we can all use and build upon.

[Light @LightBSV]

The 1BSV Layered Multicast solution is now interfacing directly with Teranode, and it didn't require forking the code. I've built teranode-bridge.
It uses the same functionality in the node, but importantly, leverages the efficiency of the network fabric.
https://t.co/wdRYORVTzV

[Deggen @deggen]

BSV Browser v1.5.6 hit the Play Store for Switzerland's birthday. iOS still pending review, due any day now.
https://t.co/Q0L20UmqKY

[Deggen @deggen]

BSV Desktop v2.3.0 release now available.

⚠️ Critical update for anyone on v2.2.8 ⚠️

Please upgrade as soon as you can to avoid the regression. Earlier versions are unaffected, but upgrading is still recommended.

[Team Winnaar @TeamWinnaar]

Building the tools to onboard every enterprise and government on the BRC stack. Watch me

Should I open source it so you could too?

[Siggi @___siggi___]

Runar now has a DeepWiki, next to the docs site (https://t.co/CAHId3Z4Ol) and playground (https://t.co/dqx4VD3uaB).

Check it out: https://t.co/ov0arwlNQd

[Siggi @___siggi___]

A privacy-first browser with a built-in web3 wallet. Try it out: https://t.co/QraY8QsQoE

"A free, open source web browser for iOS and Android that does everything your current browser does — plus three things it can't: hold a wallet, prove who you are, and pay fractions of a cent for anything."

[Deggen @deggen]

Latest BSV Desktop v2.2.0 released

Firstly, shout out to one of the top contributing devs of our ecosystem @ishaan_lahoti for two new features merged into this version:
- Payment Requests - complete system over MessageBox
- Wallet Diagnostics suite within settings page, to help users with janky transactions jamming up their wallets. Scan for issues, resolve them.

In other news, the latest version has removed a few new account setup config options. Namely WAB and UMP. I think these are cool concepts, but will leave others to implement them. More on this momentarily.

Existing users will have ability to login with those WAB and UMP key recovery types, but new users will only be able to manage their own keys. This removes some confusion I've seen between mnemonic presentation key with UMP; and mnemonic root key encodings. The latter being what will be supported for new wallets hereon. This forces mnemonic backup on creation, if you don't bring your own key at least.

The hope is that this will mitigate repeat episodes I've seen in a handful of instances where people have lost funds during a failed / abandoned signup process.

Thanks for those who reported it. Sincere apologies for any loss made through this confusing UX. The latest version reduces the rate of failure and removes total loss from the equation entirely since it'll force backup your mnemonic. This way I can always help you recover if you have issues. Previously we relied on users taking actions to save their own funds, which just doesn't work because not everyone is a developer.

[BSV Association @BSVAssociation]

Time to enjoy the Bitcoin protocol as originally intended.

Scalable. Intuitive. Limitless.

Builders: Over to you. Show us what you can do.

https://t.co/yXQuPqBC1U

[Connor Murray @Bitcoin_Beyond]

Chronicle is live and activated!

The original Bitcoin protocol has been restored.

Here is the activation transaction: https://t.co/Z5f2hq8KU1

Feel free to claim the 0.05 BSV by broadcasting your own v2 transaction.

So many people that deserve so much thanks and gratitude for all the work that went into this.

[Kurt Wuckert Jr @kurtwuckertjr]

🚨 URGENT 🚨

Per @d_vul & @0xblacklight, The axios npm package was compromised today.

80 million weekly downloads. If you're a developer who ran npm install in the last 24 hours, you need to check your system right now.

Here's how.

🧵👇

[Connor Murray @Bitcoin_Beyond]

Get all of the technical information for Chronicle here:

https://t.co/eyPRLKztZA

[Connor Murray @Bitcoin_Beyond]

Chronicle activates April 7th.

I want to take a moment to explain why this upgrade matters - not just technically, but personally.

First, huge thanks to everyone involved. The developers who did the actual work, and the community members who contributed to ensuring the scope was as airtight as possible while promoting stability. Maintaining stability while restoring the original protocol was a delicate balance, and the final release reflects all the hard work that went into ensuring that.

Why restore the original protocol?

This isn't just about completion for its own sake. Over the years, a lot of restrictions were added to Bitcoin. And in the same way that central planning can destroy an economy, centrally planning and limiting developer creativity means we have no idea what possibilities the original protocol actually enabled. We know it allowed more flexibility. We imagine that as better Bitcoin scripting engineers emerge and people learn more about the underlying protocol, they'll take advantage of use cases we can't even predict yet. Chronicle removes those artificial constraints. This is the core of the BSV Association's mandate. There should be no central person or group of people that tell you how you can build on top of the protocol.

Original Transaction Digest Algorithm (OTDA)

One of the most significant changes is the restoration of the Original Transaction Digest Algorithm. BSV will now support both the OTDA and the current BIP143 digest algorithm. Developers can opt into OTDA by setting the new CHRONICLE sighash flag (0x20). If you do nothing, existing behavior is preserved - BIP143 continues to work exactly as before. This gives developers the flexibility to choose which digest algorithm fits their use case, whether that's maintaining compatibility with existing systems or leveraging the original protocol's behavior.

Transaction malleability

Transaction malleability has been treated as this big scary problem throughout Bitcoin's history. There were a lot of patches added to Bitcoin over the years specifically to prevent it. But in doing so, they limited developer flexibility significantly.

Here's the thing: transaction malleability itself isn't actually a problem. It was only perceived as one because of how people were doing payments in Bitcoin - which was always wrong. Payments in Bitcoin were always meant to be peer-to-peer, then broadcast directly to the mining network. This is outlined in the Simplified Payment Verification section of the white paper. The work that has been done on all of the development tooling and the BRC-100 standard has enabled users and developers to utilize SPV.

Transaction malleability was a concern based on a misunderstanding of the payment flow, and a misunderstanding of nodes themselves. Because they misunderstood how payments should work and are convinced that miners will behave irrationally, they put in a bunch of restrictions on developers.

And here's the clever part: this is opt-in. Transactions using version 1 keep all existing restrictions. Only transactions with version > 1 get the relaxed rules. Existing applications remain completely unaffected. So if you are reading this and think "no way Connor is right about this" - then you can continue to ensure payments made with your wallet or application are not susceptible to malleability.

Restored opcodes

Chronicle re-instates several opcodes that were disabled years ago. Of note:

• OP_VER, OP_VERIF, OP_VERNOTIF — access the transaction version directly in script
• OP_LSHIFTNUM, OP_RSHIFTNUM — numerical bit shifting (restored to mimic the original behavior of OP_LSHIFT and OP_RSHIFT)

Business continuity

In line with BSV's commitment to stability: if you do nothing, nothing breaks. Existing applications using BIP143 without the CHRONICLE flag remain completely unaffected. The changes are all opt-in. This was deliberate - we needed to restore the original protocol while respecting that real businesses depend on the current state.

Personal note

I've been in BSV since day one. The uniting goal, shared with other community members, was always restoring the Bitcoin protocol and locking it. Set in stone. I'm proud to have played my part in that, and to have been involved in the actual work being done by the developers to enable it.

The work of the Association in doing this restoration is finally done. The protocol Satoshi designed is back.

This is cause for celebration. Let's build.

[Kurt Wuckert Jr @kurtwuckertjr]

Hey, OceanChain and/or CarbonChain, get in touch!

We have some stuff we want to test out with you. The old Arc and SVnode endpoints are inefficient for what you're doing.

Please share.

[CoinGeek @RealCoinGeek]

Rúnar: Compiler making Bitcoin Script more enterprise-ready
https://t.co/pxxMd7Bbn6

[Siggi @___siggi___]

https://t.co/qloyJSp6z0

[Centbee @Centbee]

Important Announcement:

Centbee will be closing on April 1, 2026. Please withdraw all your BSV from the app before this date. For assistance, contact [email protected]. We thank our users & backers for their support.

Read the full statement: https://t.co/SofGKKITmf

[Jake Jones @MonkishRex]

My time with the BSV Association has come to an end after 4.5 years. It has been a phenomenal 4.5 years; I'm grateful to have had the opportunity to work with so many exceptional people and travel to so many beautiful places, and I know they're going to continue pushing blockchain forward.

I'm now shifting my focus entirely to the integration of AI + Blockchain. I've been busy building over the past weeks:

- Shad (Shannon's Daemon) -- a fast semantic search engine that uses Recursive Language Models (RLMs) strategically to effectively eliminate the AI context window problem so every session is a continuation of the previous: https://t.co/ntodvERxO7

- Edwin (named after physicist Edwin Jaynes) -- a personal AI that uses Shad for its memory system and takes a new approach to security so you don't have to choose between safety and utility anymore; it's like OpenClaw but secure and continuously coherent.

Please have a look at my website: https://t.co/z8xOlfrAge . I've added a simple AI chat that you can use to find out more about my experience and whether we'd be a good fit if you're looking to hire.

I'd appreciate it if you could share this for visibility

Cheers

hashtag#AI hashtag#Blockchain hashtag#IPv6 hashtag#Agents hashtag#Shad hashtag#Edwin hashtag#OpenClaw hashtag#ClawdBot hashtag#MoltBot

[Deggen @deggen]

Heads up my fellow BSV devs and users. We’re about to release a new major version of the TypeScript SDK.

https://t.co/zQmv0SZ2YG

We expect there to be a few apps which may raise new errors as they migrate from older versions since there is a low level breaking change. If you leave the whole stack alone, it’ll still work, but if you update the backend without updating the front you’re likely to see errors.

We’ll do our best to update all the demo apps and production apps in the wild over the next few days. Please report any errors in this thread or with the developers of the app in question.

Chronicle features will hereon be supported. Testnet already live. April 7th on Mainnet.

Thank you for your attention to this matter!