A neighbor of mine drives for a delivery app and swears the whole job is just proving you showed up on time. I asked him once whether anyone checks that he delivered the right order to the right door, and he laughed and said nobody really does, the system only cares that the app says delivered. That distinction between proving something happened and proving it happened correctly stuck with me longer than the conversation did.
Keeper networks like Gelato, Keep3r, and Chainlink Automation exist to trigger a predefined action once a condition is met, rebalance a pool, liquidate a position, execute a limit order, and they are genuinely good at that job. What none of them do is prove the underlying decision behind the trigger was itself correct, they confirm the function ran, not that running it was the right call given everything else happening onchain at that moment. Newton's operator network backs every allow, reject, or cap decision with a verifiable proof instead, which is a different question entirely from whether an action fired on schedule.
Keep3r's whole pitch has always been paying keepers for gas-efficient, reliable execution, speed and cost are the metrics that matter there, not judgment. Newton's operator network, by contrast, has to reach quorum and produce a proof before a verdict even counts, which is slower by design and priced accordingly.
So do these compete? Only partly. A vault could use a keeper network to execute a rebalance and use Newton to decide whether that rebalance should be allowed to happen at all, and neither one replaces the other's job. Whether that distinction actually matters to a builder choosing infrastructure today, or only matters once something goes wrong and someone asks why a technically-successful transaction was still the wrong one, is a question Newton's real world usage has not fully answered yet. I lean toward thinking it matters more the moment real money is on the line, but that is a guess, not a settled fact.
@NewtonProtocol $NEWT #Newt $LAB $EVAA
Keeper networks like Gelato, Keep3r, and Chainlink Automation exist to trigger a predefined action once a condition is met, rebalance a pool, liquidate a position, execute a limit order, and they are genuinely good at that job. What none of them do is prove the underlying decision behind the trigger was itself correct, they confirm the function ran, not that running it was the right call given everything else happening onchain at that moment. Newton's operator network backs every allow, reject, or cap decision with a verifiable proof instead, which is a different question entirely from whether an action fired on schedule.
Keep3r's whole pitch has always been paying keepers for gas-efficient, reliable execution, speed and cost are the metrics that matter there, not judgment. Newton's operator network, by contrast, has to reach quorum and produce a proof before a verdict even counts, which is slower by design and priced accordingly.
So do these compete? Only partly. A vault could use a keeper network to execute a rebalance and use Newton to decide whether that rebalance should be allowed to happen at all, and neither one replaces the other's job. Whether that distinction actually matters to a builder choosing infrastructure today, or only matters once something goes wrong and someone asks why a technically-successful transaction was still the wrong one, is a question Newton's real world usage has not fully answered yet. I lean toward thinking it matters more the moment real money is on the line, but that is a guess, not a settled fact.
@NewtonProtocol $NEWT #Newt $LAB $EVAA