What caught my attention was not transaction speed, but how much crypto still quietly depends on APIs behind the scenes.

A lot of systems that call themselves decentralized still rely on centralized services for data, permissions, and verification. APIs quietly sit in the middle of wallets, exchanges, apps, and external services.The problem is that every API still asks users to trust something in the middle, even in systems that were originally built to remove that kind of dependence. @NewtonProtocol #Newt

That seems to be exactly where Newton is focusing with its use of cryptographic proofs.

Instead of simply trusting that a server returned the correct information, the idea is to verify actions and permissions through proofs that can be checked independently. That changes the role infrastructure plays. Verification becomes part of the system itself rather than something users are expected to assume is working honestly.

What makes this more interesting is that it goes beyond security. As AI agents and automated financial systems become more active on-chain, knowing who actually approved an action may become just as important as processing the transaction itself.

At the same time, replacing APIs is probably much harder than it sounds. Existing infrastructure, performance limits, developer experience, and compatibility issues are all real obstacles.

So the bigger question is not whether cryptographic proofs sound better in theory.$TAIKO $VELVET

It is whether projects like Newton can make this model practical without making systems harder to build or operate. @NewtonProtocol $NEWT #Newt

What’s the biggest missing piece for institutional DeFi today?