I'm seeing lots of "web3" use-cases proposed that are just plain old public key cryptography, but people think that reusing wallet's private key somehow makes it new and magical.
I'm seeing lots of "web3" use-cases proposed that are just plain old public key cryptography, but people think that reusing wallet's private key somehow makes it new and magical.
In trendy terms, like IPFS where you pin your own signed like messages.
Note that identity verification, forgery prevention, and distribution of messages are done using "web2" technologies, even in blockchain systems. The hard part in blockchains is literally only the double-spend protection, so if your problem is not about spending money, they do nothing.
1. https://ethereum.org/en/developers/docs/consensus-mechanisms... 2. https://ethereum.org/en/developers/docs/scaling/zk-rollups/#....
Ethereum PoS is perpetually "almost there" like Star Citizen and the Year Of Linux Desktop. I don't think anything they say matters until they actually shut down the PoW system (which I don't think they can).
Either way you will still have to pay gas fees to the staking overlords for the permission to do anything on the blockchain they control. I'd rather have a federated/self-hosted system, and drive it down to as close to free-of-charge as possible by improving its efficiency.
I've been following development very closely, and to me, the process is pretty straightforward. They've already run the process several times successfully with production data in shared development environments.