Replying to #9856a251, a post that isn't indexed yet.
It's still early.
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
136zYTEHSK2xs4gUrpzTPovJA2VCo7BNgK UnverifiedPre-iceberg,
but somehow
post-asteroid.
You don't need Iceberg. Unbounded scaling and scarcity process will do the works.
Just found out the "unbounded scaling" has never been officially confirmed by a third party, something any other chain/coin does without any issues. Which makes me wonder wtf that would be.
So far it's about as real as the "rolling icebergs" and the "asteroid" that was "the only thing that can stop coins from moving after the trial."
Makes me wonder how deeply you researched this. You saw a post from kirk and threw your hands in the air, neglecting some names in the post for you to look up. You'll keep the same narrative untill someone hand delivers you some new information
You mean like this? https://aws.amazon.com/blogs/web3/how-the-bsv-association-built-a-million-tps-blockchain-node-using-aws/
Amazon Web Services How the BSV Association built a million-TPS blockchain node using AWS | Amazon Web Services In this post, we show how BSVA used AWS services to build a distributed node architecture that achieves 1 million TPS across six Regions. This solution demonstrates how organizations can implement cloud infrastructure to solve complex blockchain scaling challenges while maintaining system integrity. This thread is longer than one page shows. Open a reply to see what follows it.