A friend learning to juggle told me the hardest part isn't catching three balls, it's the transition from two to three, because everything that worked with two suddenly breaks under a third variable moving at the same time. He spent months stuck exactly there.
Newton is standing in a similar transition right now. The vision is a multichain Keystore rollup, permissions and agent execution working consistently across many chains at once, with a stated roadmap goal of onboarding third-party validators and scaling through aggregated proof verification to get there. That is the two-ball trick already partly working, TEE execution and ZK verification functioning together. The three-ball problem is making that same verified permission model hold up identically across multiple chains simultaneously, with consistent state, consistent latency, and consistent security guarantees no matter which chain the agent happens to be acting on.
Multichain is where a lot of infrastructure promises quietly stall. It is one thing to verify an agent's action on a single rollup, it is a much harder problem to guarantee that a permission granted on one chain is enforced identically the moment the same agent needs to act on a different one, especially while validator decentralization and proof aggregation are both still being built out in parallel rather than finished first.
Newton isn't claiming the multichain rollup is done, the roadmap treats it as the next major phase, and the gap between the core verification primitive working and it working seamlessly everywhere is what's worth watching, not assuming solved.
@NewtonProtocol $NEWT #Newt $PALU $VELVET
Newton is standing in a similar transition right now. The vision is a multichain Keystore rollup, permissions and agent execution working consistently across many chains at once, with a stated roadmap goal of onboarding third-party validators and scaling through aggregated proof verification to get there. That is the two-ball trick already partly working, TEE execution and ZK verification functioning together. The three-ball problem is making that same verified permission model hold up identically across multiple chains simultaneously, with consistent state, consistent latency, and consistent security guarantees no matter which chain the agent happens to be acting on.
Multichain is where a lot of infrastructure promises quietly stall. It is one thing to verify an agent's action on a single rollup, it is a much harder problem to guarantee that a permission granted on one chain is enforced identically the moment the same agent needs to act on a different one, especially while validator decentralization and proof aggregation are both still being built out in parallel rather than finished first.
Newton isn't claiming the multichain rollup is done, the roadmap treats it as the next major phase, and the gap between the core verification primitive working and it working seamlessly everywhere is what's worth watching, not assuming solved.
@NewtonProtocol $NEWT #Newt $PALU $VELVET