Neither would this fix any byte code size or storage problems nor would it meaningfully increase throughput (and it would break the Gas model which you think is unsafe).
Of course we face and acknowledge major challenges and problems with revive. But that per se neither implies our theoretical assumptions being unsound nor our benchmarks being flawed. There is no free lunch and we can and will make trade-offs to overcome obstacles.
I spent a lot of my time and energy here and in other forum threads, trying hard to build a constructive discussion. We are working really hard and in our best faith to deliver a comprehensive smart contract solution.
Yet you keep chiming in on tech talk forums painting bleak pictures by calling our solution not working in absolute terms, the most useless of all ideas, and inherently insecure. Your presented alternatives suffer from the same problems or much worse flaws. Paired with grave accusations of me being unprofessional, not thinking a for a single moment, and, ultimately, only being here to build ivory towers and boosting my ego. This is not very inspiring. I feel discouraged and deeply disappointed.
No. I think you just have a misunderstanding about Ethereum and its execution model. You can ask Paradigm team how they did their revmc and integrated it in Reth.
Vitalik proposed several routes of adding RISCV. All of them still do EVM interpreting so they don’t suffer from the problem of Revive. Again, compiling Solidity/EVM->RISCV on-chain is probably never a good idea because the contract size increase will be at least 4x (theoretical), and right now it’s 10x to 80x. Compiling EVM->Native off-chain is probably the way to go and is already being experimented in several Ethereum L2s.
And we need to stop this appeal to authority.
If you want to a quote that precisely describe the current situation – premature optimization is the root of all evil. Your benchmarks were definitely flawed and the approach taken was definitely wrong. There’s really no question on that. It’s a classic example of premature optimization, and it’s a lesson we’ve learned millions of times since computer was invented.
Your solution should not have been at expense of others in the ecosystem. No one should have needed to take FUD accusations all the time. No one should have been the subject of all those unnecessary political plays. No one should have needed to lose a job to point out such obvious problems in Revive. This is indeed deeply unprofessional and self-centered no matter who you ask.