{
  "txid": "4dabf3e9a4dc2d02dd9b2c982faeff11ccde6f34cc8e92fd2bc410acc7d36c70",
  "block_height": 952929,
  "time": null,
  "app": "treechat",
  "type": "post",
  "map_content": "100% \u2014 Amazon Said It, Not Us\r\nLast piece, I ended by saying Amazon was the second of two things I found while reading Kurt Wuckert Jr.'s work. The IEEE paper was the first. This is the second.\r\nOn March 31, 2026, a Senior Solutions Architect at Amazon Web Services named Jordan Kramsky published a technical case study on the AWS Web3 Blog. The title was \"How the BSV Association built a million-TPS blockchain node using AWS.\" The subject was Teranode, the new node software developed by the BSV Association. The result was one million transactions per second, sustained for two weeks, across six AWS regions on three continents, with zero transaction loss.\r\nRead that again. Because we have been waiting years for this.\r\nThis was not a BSV press release. This was not a CoinGeek article. This was not a community livestream. This was Amazon Web Services, on Amazon's own corporate platform, written by an Amazon engineer, with Amazon's editorial approval and brand attached, documenting a technical achievement on the BSV blockchain.\r\nThe numbers tell their own story. The previous BSV reference node, SVNode, peaked at around 13,614 transactions per second. Teranode does 66.67 times that. Visa, the largest credit card network in the world, processes around 65,000 transactions per second on Black Friday. Solana claims similar throughput to Visa, but over 85 percent of Solana's transaction volume is reserved for finding consensus, not for moving real value. Teranode is on a different scale entirely.\r\nThe architectural breakthrough behind these numbers is something Kramsky calls subtree broadcasting. To understand why it matters, you have to understand what every other blockchain does. Most blockchains validate transactions in batches. Transactions pile up in a waiting area called a mempool. Then a miner finds a block, and all those waiting transactions get processed at once. Every ten minutes or so on Bitcoin. A few seconds on faster chains. But always in episodes. Always in chunks.\r\nTeranode does something fundamentally different. It continuously broadcasts what are called Merkle subtrees every second. Transactions get pre-validated and pre-assembled in real time, across the entire network, before they ever become part of a block. Block creation stops being an event and starts being a continuous process. The numbers Kramsky reports include subtrees containing up to a million transaction identifiers, with full Merkle path connectivity, all verifiable by other nodes on the network.\r\nThat is the difference between treating a blockchain as a slow ledger and treating it as a real piece of infrastructure. You rethink the problem from first principles, and you build like the future depends on the result.\r\nNow, here is the part I want you to sit with.\r\nA company like Amazon Web Services does not write technical case studies about random projects. They have one of the most carefully protected corporate brands on earth. Anything published on the AWS Web3 Blog goes through editorial review, fact-checking, brand approval, and engineering sign-off. The author of this piece, Jordan Kramsky, is not a random blogger. He is a Senior Solutions Architect for Startups at AWS, focused specifically on blockchain and decentralised systems. His job depends on the technical accuracy of what he publishes. AWS's corporate reputation is attached to every claim in that article.\r\nSo when AWS publishes \"one million transactions per second sustained for two weeks with zero transaction loss,\" that number is not marketing. It is engineering, verified by Amazon engineers, documented for the world to read.\r\nFive years of work led to this. The article describes AWS engineers helping the BSV Association team fine-tune operating system and kernel settings. Iterating through IPv6 Multicast with Transit Gateway. Testing storage configurations. Running Amazon MSK for transaction distribution. Building a custom Kubernetes operator to manage scaling. Using Aerospike on NVMe volumes for low-latency state management. This is the kind of engineering work that no press release ever describes, because press releases are written by marketing people and engineering work is done by engineers. The fact that Kramsky describes it in detail tells you he is writing for engineers, not for crypto traders.\r\nAt the AWS Zurich Summit in 2024, the BSV Association's CTO Siggi Oskarsson publicly thanked AWS for the partnership and said that AWS support is what made a five-year research and development journey possible. That is what real collaboration sounds like. Not a logo on a slide deck. Not a \"strategic partnership\" announcement that means nothing. Engineers from two organisations, working through problems together for half a decade, until they arrive at a result that neither could have produced alone.\r\nThere is also a strategic dimension here that is worth naming, because it explains why AWS would invest five years and corporate brand credibility into a partnership with a blockchain project most of the mainstream crypto industry has ignored.\r\nA serious business does not publish technical case studies about random projects. AWS publishes them with its own market position in mind. Some blockchain projects market themselves as cloud-giant replacements. BSV chose a different posture \u2014 partner with AWS, run on AWS, build on AWS. That choice gave AWS something concrete to point to when customers ask whether they need to leave for an alternative. The blockchain capability is already here. On AWS. Documented by Amazon engineers. Working at scale.\r\nBSV did not have to outcompete other chains for AWS's attention. BSV offered AWS the partnership that solved a problem AWS already had. While some chains pitched themselves as AWS-killers, BSV pitched itself as the chain that runs on AWS. One strategy gets you confrontation with the largest cloud company on earth. The other gets you a five-year engineering relationship and a published technical case study on their own corporate blog.\r\nOne of those strategies, it turns out, was the right one.\r\nWhat this means going forward, I am not certain. The technical case for BSV scaling has now been validated by one of the largest technology companies in the world. That validation cannot be unpublished. It will sit on the AWS Web3 Blog as a permanent reference. Anyone arguing that blockchain cannot scale, that million-TPS throughput is vaporware, that BSV is dead, now has to deal with the fact that Amazon engineers wrote a 1,500-word technical walkthrough of exactly how it was done.\r\nI am not going to promise you that this changes the price of BSV. The crypto market is driven by speculation, narrative, and liquidity flows, not by peer-reviewed papers and AWS blog posts. The technical case being correct does not mean the market rewards it. Being right and winning are different things, and the history of computing is full of better technology losing to worse technology with better marketing.\r\nWhat I will say is this. The technical argument is no longer a community debate. It is a documented Amazon Web Services case study, published by an Amazon engineer, sitting in public on Amazon's own corporate platform. That changes the kind of conversation BSV's defenders can have. The receipts are no longer in a BSV-aligned newsletter. The receipts are on AWS's brand-protected blog. For enterprise procurement teams, for academic researchers, for regulators trying to understand what blockchain infrastructure can actually do, the AWS case study is a citable, defensible, authoritative source.\r\nI went into the weekend thinking I understood where BSV stood. I came out understanding it differently. Not because of marketing, not because of a price move, but because the engineering case has now been validated by people whose corporate reputation depends on the validation being accurate.\r\nThe chain that prides itself on being technical, scalable, and infinitely useful finally has, in public, on the most credible technical platform available, the proof that it is technical, scalable, and useful. After ten years of waiting, the validation arrived.\r\nWhether the project knows what to do with it is a separate question.\r\nLet us ponder this full well.\r\nSuggestions to follow.\r\nAWS case study: How the BSV Association built a million-TPS blockchain node using AWS (AWS Web3 Blog, March 31, 2026)\r\nAuthor: Jordan Kramsky, Senior Solutions Architect for Startups, AWS\r\nKurt Wuckert Jr.'s commentary: kurtwuckertjr.com",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "fiatbroke",
  "channel": null,
  "parent_txid": null,
  "ref_txid": null,
  "tags": null,
  "reply_count": 2,
  "like_count": 2,
  "timestamp": "2026-06-10T10:39:11.000Z",
  "media_url": null,
  "aip_verified": false,
  "thread_root_tx": null,
  "engagement_score": 0,
  "token_ref": null,
  "token_type": null,
  "kind": null,
  "lat": null,
  "lng": null,
  "category": null,
  "has_access": true,
  "attachments": [],
  "ui_name": "fiatbroke",
  "ui_display_name": "fiatbroke",
  "ui_handle": "fiatbroke",
  "ui_display_raw": "fiatbroke",
  "ui_signer": "14aqJ2\u2026oWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}