BREAKING: 🇺🇸 President Trump is set to make a “huge” announcement today at 5:00 PM ET.
Sources are speculating it could involve plans to reopen the Strait of Hormuz and a possible new peace deal with Iran. Markets could see major volatility if confirmed.
Why AI Agents Need Guardrails Before They Handle Real Money
Three weeks ago a buddy's "set and forget" trading bot quietly drained about 40% of his stablecoin balance. Turns out someone had slipped a bad instruction into a public prompt template he'd grabbed off Discord. The bot just did what it was told no pushback, no "wait, that doesn't look right." That's kind of the whole problem. I'd more or less forgotten about it until @NewtonProtocol started showing up in my feed, lumped in with the usual wave of "AI agent" tokens. First instinct, honestly? Filed it under "another AI copilot for your bags" and kept scrolling. There's no shortage of bots out there promising to trade better than you can. Then I actually sat down and read the docs and a few of the integration posts, instead of just the landing page. And the framing clicked into place differently than I expected. Most people seem to be grading Newton and AI agents generally on the wrong thing. The question everyone defaults to is "how good is the agent?" Smart enough not to get tricked? Hallucinate-proof? Strategy actually sound? That's the exact question my friend should've asked about his bot, and it probably wouldn't have saved him anyway even a well-built agent can get manipulated by a bad prompt, a compromised dependency, or some edge case nobody thought to test. What Newton's actually built around is a different bet: stop trying to make the agent trustworthy, and just make its judgment irrelevant to whether a bad transaction goes through. Every action a user hands off recurring buy, yield move, whatever gets checked against a policy you set, by a separate network, before anything settles onchain. Each step runs inside a secured enclave and comes back with a cryptographic proof attached, so there's a check before it happens and a trail to audit after. The agent's intelligence or lack of it doesn't really factor in at that point. It's the policy getting verified, not the agent's reasoning. That's a genuinely different philosophy than "build a smarter, safer agent," which is basically the entire AI-in-crypto pitch right now. It's closer to how a bank's fraud system works it's not trying to make every teller trustworthy, it's checking the transaction no matter who's asking. I'm not totally sold this fixes everything, to be fair. I spent maybe twenty minutes building a toy policy myself small spending cap, an approved-payee list and there's real friction in writing good rules. A spending cap is easy. "Only trade if volatility's under X and the yield curve looks healthy" is a much harder thing to define correctly, and a sloppy policy is just as exploitable as a sloppy agent. It just breaks one layer over. Garbage in is still garbage in. I'm also genuinely unsure how decentralized the enforcement side actually is in practice versus on paper. It runs through a network secured by EigenLayer restaking, which sounds solid on paper, but I haven't gone digging into validator concentration myself, and I'd want to before calling "verifiable" the same thing as "safe." NEWT itself isn't exactly inspiring confidence price-wise either it's sitting something like 94% below its all-time high, which doesn't say anything about the protocol's actual engineering, but it does mean the market hasn't bought into this thesis yet, fair or not. (None of this is financial advice, to be clear just what I noticed poking around) What I keep coming back to is that comparing Newton to other "AI agent" tokens on trading performance or model quality is probably comparing it against the wrong category entirely. Makes more sense, maybe, to stack it up against authorization and compliance infrastructure the boring plumbing that gates KYC checks, gas conditions, treasury data before anything fires than against flashy autonomous trading bots, since that's actually the layer it's trying to live in. Whether that framing survives once real capital and more agents start flowing through it, or whether the "policy layer" turns out just as gameable as the "agent layer" once people start poking at it for real I don't think anyone actually knows yet. Worth watching how the next few integrations, and any actual incidents, shake out before deciding which side of that bet makes more sense. $NEWT #Newt
Spent the morning going through Newton Protocol's mainnet beta launch (went live June 23) and one detail kept nagging at me more than the headline numbers.
$NEWT #Newt @NewtonProtocol shipped with two data partners on day one, RedStone and Credora, and the first live use case isn't some agent firing off trades it's Vaults.
A curator sets a price or risk threshold, and when RedStone's collateral data crosses that line, Newton's policy engine locks or liquidates the position automatically, generating a signed receipt anyone can check on the Explorer.
What struck me is the order of operations. I'd expected "authorization layer" to mean unlocking new automated behavior agents buying, swapping, rebalancing on someone's behalf.
Instead the first real stress test is defensive: stopping a transaction or freezing a position before something bad settles. That's a different demand signal than the marketing usually implies. It suggests the early appetite isn't for more automation, it's for automation that knows when to say no.
I'll admit I'm not totally sure whether that's a deliberate sequencing choice or just where the easiest integration partners happened to land first. Both readings feel plausible from the outside.
Still curious what attestation volume looks like a few weeks post-launch, once vault curators outside the founding partners start writing their own policies. Anyone tracking that yet?
AI used to be about who gives the smartest answer. Now it's shifting toward who can prove the answer wasn't tampered with that's the layer people are catching onto. OpenGradient ($OPG , #OPG @OpenGradient ) sits right in that shift, building verifiable inference instead of another model wrapper.
What caught my eye this week wasn't the pitch, it was the market's reaction to a verifiable on-chain print. OPG hit a fresh all-time low of $0.1207 on June 27 the kind of candle that usually empties an order book. Instead, 24-hour volume held around $24.3M against roughly a $26.4M market cap, (CoinMarketCap) and within about a day price had clawed back over 10%.
That volume-to-cap ratio is what stuck with me. A new low on fading volume usually reads as quiet exhaustion. A new low with volume that stays near parity with market cap looks more like active price discovery buyers and sellers actually contesting the level instead of one side just leaving.
I'll admit I expected capitulation when I pulled this up, not contested ground. Whether that's real accumulation or just thin liquidity amplifying small trades, I genuinely can't tell from the outside wallet-level granularity would help but I don't have it.
Anyone watching the flow around that print does this read as demand stepping in, or just noise?
Been sitting with @OpenGradient PIPE architecture docs for a few hours and one thing keeps pulling my attention back.
Most chains treat computation as something that happens inside block execution. PIPE @OpenGradient's parallel inference pipeline flips that entirely. Inferences queue in a dedicated mempool, execute concurrently across nodes, and block building keeps moving on its own timeline. No single slow ML model can hold the network hostage.
What made this land for me wasn't the docs it was the live network numbers. $OPG chain is sustaining 10,000+ daily transactions across 4.2M+ produced blocks, (CoinMarketCap) and block cadence looks stable despite 2,000+ models of wildly varying size sitting on the hub.If PIPE wasn't doing its job, you'd expect heavier inference jobs to bleed into block times visibly. That spikiness isn't showing up in the public data.
The circulating supply also quietly ticked from 190M to 197.59M #OPG as of recent on-chain data probably staking rewards rolling through their linear unlock schedule, but worth watching as the pace changes. I'll be honest I can't cleanly isolate pure inference load from standard token transfers in those 10K daily txs.
That uncertainty is real. But the block-time consistency while the network hosts live applications like BitQuant and MemSync is a more interesting signal than I expected going in. Still sitting with this: is PIPE actually handling heterogeneous parallel inference at scale today, or is most of that daily volume lightweight, uniform calls where the parallel architecture doesn't really get stress-tested?
@OpenGradient has been sitting in my tabs for a few days and the thing that keeps surfacing is the asynchronous proof model.
The design decision that gets less attention: inference runs first, settlement happens after. Full nodes don't re-run the AI computation in real time they verify proofs separately after inference is already complete, which lets the network keep speed comparable to traditional cloud services
While still settling a verifiable record on-chain. (NFT Evening) That sounds like a footnote in the docs but it's actually the whole architecture. Real-time trading agents and DeFi risk models can't hold open a connection while a zkML proof computes. So HACA just decouples them.
This week, OPG dropped 19.4% over seven days and touched within 1% of its all-time low near $0.1278, while 24h volume climbed 18% from the day prior to roughly $32.8M. That divergence is worth sitting with. Volume rising near a floor doesn't confirm accumulation could be liquidations clearing but it does confirm the market isn't just walking away quietly.
Meanwhile the network side doesn't show signs of slowing: 2M+ verifiable inferences logged, with 500K+ zkML proofs and TEE attestations settled on-chain. Protocol activity and price discovery seem to be operating on completely separate timelines right now.
I'm still not sure whether the async proof design matters at scale or only makes sense for narrow latency-sensitive use cases. How much of that inference count is real production load versus teams testing their own pipelines?
Been sitting with @OpenGradient for a few days, and the part that keeps pulling my attention isn't the AI narrative it's the architecture decision behind OPG core design.
OpenGradient separates execution from verification entirely. Inference nodes run the model and return a result fast. Full nodes verify the proof separately, asynchronously. Those two things don't wait on each other.
What made that concrete for me was checking on-chain behavior this week. Even as $OPG dropped roughly 19% over the last seven days, 24-hour volume ticked up around 18% on June 26. Price down, interaction up.
That's a minor divergence, but on Base where inference payments settle in real time through Permit2, it suggests some portion of that volume isn't purely speculative requests are actually hitting the network.
The "verify later" design is what unlocksthis. If every inference had to wait for a zkML proof or TEE attestation before returning a result, latency would kill any real use case. By decoupling the two phases, OpenGradient lets the user get an answer now and the network prove it was honest afterward.
Not a new idea OpenGradient offers a verification spectrum, including zkML proofs and TEE attestations, allowing developers to choose their own balance of cost, speed, and security but applying that tradeoff framework to AI inference specifically is where it gets interesting.
I'm still not sure how proof backlog behaves under real load. Does verification keep pace with execution at scale, or does that gap widen quietly? That's the part I'd want to stress-test before drawing any conclusions.