First, Chrome and Firefox will shut down.
Then, CLI browsers will emerge.
They only have the DOM and JavaScript. No CSS, no renderer.
Next, the CLI browsers will shut down.
Only the API will remain.
Web standards will only exist in the AGI's outputs.
Under one second in-browser. Proof under 1KB. The key never crosses the wire.
Wrote it up ↓
https://t.co/FB9rp0gbl1
#ZeroKnowledge#Authentication#ZKSNARKs
We removed the key from sign-in. Then the hash. Then even the public key.
What the server now receives: a Groth16 proof that you hold a registered key. Nothing reusable.
Nothing to steal.
Your browser runs a ZK circuit entirely client-side. It produces a proof and a session-bound nullifier: unique to this key and this session, but revealing nothing about the key itself. The server verifies the proof. Replay is impossible by construction.
@CoinbaseDev's account-scoped delegation is the right primitive. Trust402 composes on top: ZK proof per action of valid mandate and spend limit compliance. Verifiable by any counterparty, not just the wallet provider.
https://t.co/i7jjVOUcad
Most AI agents don't need access to the whole wallet.
Account-scoped delegated signing is now available on Coinbase non-custodial wallets, letting users grant agents permission for one account only.
Demo + docs from @jnix2007 ↓
Most AI agents don't need access to the whole wallet.
Account-scoped delegated signing is now available on Coinbase non-custodial wallets, letting users grant agents permission for one account only.
Demo + docs from @jnix2007 ↓
$50M spent by agents on Base — in a single week.
Trust402 adds the missing piece: cryptographic proof of which agents had authority, and on what data.
x402 moves the money. Trust402 proves who had authority to move it.
https://t.co/eHOCM9KmWd
The agent payment stack has a gap at Layer 3.
x402 handles signature verification. AgentCore governs spending. Both are covered by the payment platform side. What's left is proving who's paying whom — without sending raw data. That layer is delegated upstream.
Once PPSI takes effect, stablecoin issuers are on the hook for it. AML/KYC becomes mandatory, not optional.
Lemma's ZK attribute proofs fill Layer 3 — selective disclosure so issuers verify what they need without touching PII.
AI agents can now spend money on your behalf.
Not hypothetically. Right now. With a cryptographic power of attorney that proves who they represent, how much they can spend, and on what data.
No "trust me." This is Trust402.
Here’s the missing piece nobody talks about:
x402 lets AI agents pay for things. Great.
But how does the receiving side know:
→ Who authorized the agent?
→ What’s its spending limit?
→ That the data it received is authentic?
Without that, it’s just an anonymous wallet.
Here’s the missing piece nobody talks about:
x402 lets AI agents pay for things. Great.
But how does the receiving side know:
→ Who authorized the agent?
→ What’s its spending limit?
→ That the data it received is authentic?
Without that, it’s just an anonymous wallet.
Trust402 adds a ZK trust layer on top of x402.
One middleware call = every micropayment becomes verifiable:
→ ZK-proven agent identity & authority
→ Cryptographic data integrity
→ On-chain settlement
x402 is the payment rail.
Trust402 is the certificate authority.
Published: a working demo of pre-execution attestation for cross-chain bridges (Kelp DAO / rsETH scenario) + a blog post on why post-hoc forensics is the wrong layer.
https://t.co/IbR2SYQ4is
Runs locally with no provisioning. Lightweight local proofs for evaluation, then upgrades to production-grade ZK artifacts via SDK. Evaluate first, build later.