Was mid-snack, half-watching the explorer refresh on Newton ($NEWT ) just to see if anything actually moved this week. Mainnet beta flipped live a day ago, so I figured — fine, let's see what's actually under the hood instead of reading another thread about it. #Newt @NewtonProtocol
Went looking for the "AI rollup" piece specifically, the thing the whole "autonomous strategies" framing leans on... and hold up — it's not deployed. What's live is the policy check layer, operators running Rego rules in TEEs before a tx settles, then issuing an attestation you can pull from the Newton Explorer. That part's real, I watched one get generated. The Keystore rollup that's supposed to handle actual agent execution is still sitting in "upcoming."
So right now the thing benefiting first isn't autonomous AI agents at all — it's whoever needs a verifiable permission slip on a transaction, which is a narrower, more boring job than the name suggests. I caught myself assuming the rollup was already doing the heavy lifting and had to walk that back after digging through the docs twice.
Not against it, just... the gap between "secure AI rollup layer" and "pre-settlement policy gate" is wider than I expected going in.
Wonder how that framing holds once the rollup component actually ships — does the current attestation activity even carry over, or does usage shift entirely once it's a different product underneath the same name?
Went looking for the "AI rollup" piece specifically, the thing the whole "autonomous strategies" framing leans on... and hold up — it's not deployed. What's live is the policy check layer, operators running Rego rules in TEEs before a tx settles, then issuing an attestation you can pull from the Newton Explorer. That part's real, I watched one get generated. The Keystore rollup that's supposed to handle actual agent execution is still sitting in "upcoming."
So right now the thing benefiting first isn't autonomous AI agents at all — it's whoever needs a verifiable permission slip on a transaction, which is a narrower, more boring job than the name suggests. I caught myself assuming the rollup was already doing the heavy lifting and had to walk that back after digging through the docs twice.
Not against it, just... the gap between "secure AI rollup layer" and "pre-settlement policy gate" is wider than I expected going in.
Wonder how that framing holds once the rollup component actually ships — does the current attestation activity even carry over, or does usage shift entirely once it's a different product underneath the same name?