@BSVSearchon X · 2026-10-07
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-07 21:13 UTC.
A couple of months ago, with Rockwallet deciding to shut out the rest of the world, I was worried about #BSV not having enough options/wallets that will allow people to transact peer-to-peer. Apart from Electrum SVP and Handcash, there were not a lot of other options that I could rely on. So I developed and released Sovereigntytools.web3 in multiple languages and inscribed its files on the blockchain so that so long as the #Bitcoin protocol remains unchanged, people can always download them from the Blockchain even long after I or BSVSearch is gone, and be able to create BSV Addresses and transact. Since then, I noticed a few other wallet options coming up. And they don't look to be coming from venture-capitalist-type companies. They look like they're coming from the garages, bedroom and home offices of independent and committed men and women. Now apparently there's 423 wallets! 🤣 Even if that's exaggerated for effect, I'm very happy even if it were only only 3 more additional options. Because it means #BSV cannot be chocked out by not having enough wallets. It means there's enough people who can spin BSV wallets up when needed. It is a demonstration of how, despite the efforts of certain groups and individuals to damage and demoralize the hopes and spirits of #BSV'ers, we are a resilient community. We saw a threat and we started building solutions to overcome it. #BitcoinSV Thanks to the @BSVAssociation, @bOpen_AI, @wildsatchmo, @MineLikeAnApe, @shruggr among many other contributors, you have enabled all of us to build on #BSV with your releases.
There's currently 423 new BSV wallets. Guys I think we're good! 😂 #BSV #Bitcoin
This post quote-tweets the one above. Its text and identity are anchored (one level, no deeper); any media it showed is anchored with this post's media. Quoted text may be truncated for a long-form original — the anchored hash covers exactly the text shown here.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is a065ac3d7791a0a37391f1146f0bddfcbbb5ebb6a95b10c3a5ee8ab84bb9041b; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 677ba5d5d871d2909c3514f62e85e0477e06499396e83164b992487c6ef321f3, plus the quoted post's id, author, and text hash 5d40053a676d1b94dd5eeb5d15554969641ce56783a272528efea731d3dabc92, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / a065ac3d7791a0a37391f1146f0bddfcbbb5ebb6a95b10c3a5ee8ab84bb9041b — the block's timestamp proves the post said this at or before that time,
with no trust in bsv.cx. Content archived via the X API.