iorulezz

building @deltadotnetwork.

[Rain @raincards]

The Agentic Payments Alliance is live.

26 founding members across payments, stablecoins, and AI, working together to shape how agent-driven commerce gets built.

No single company should decide how agents transact on your behalf.

[delta @deltadotnetwork]

https://t.co/5im26u9hOd

[Myles O'Neil @MylesOneil]

Today we’re announcing @deltadotnetwork integration with @Google's AP2. Link in the comments below, but here's why we're excited:

AP2 creates a verifiable chain for user authorization, merchant commitment, and payment intent. But it has two significant shortcomings:
1) it does not verify that the agent’s action satisfies the substance of what the user authorized
2) it requires issuers and merchants to blindly trust the platform's attestation without having any way to verify the user's purchasing intent

AP2 with delta Mandate addresses both of these problems.

The user authorizes an intent mandate, the agent discovers a product, and the merchant only signs the checkout after delta has verified the proposed purchase against evidence from the actual product. This check sits outside the agent, so issuers and merchants do not need to blindly trust the platform.

This matters for liability. Issuer banks are not going to underwrite delegated purchases if they cannot independently verify that the agent stayed inside the user’s mandate. They need more than an audit trail showing what happened after the fact. They need a pre-release control that ties authorization, execution, and evidence together before money moves.

AP2 gives agentic commerce a much-needed authorization and transaction artifact chain. delta Mandate adds the enforcement + evidence layer required for issuers, merchants, and wallets to trust that chain at scale.

[Ole Hylland Spjeldnæs @spjoleh]

https://t.co/ZrpYrTCQxs

[iorulezz @iorulezz]

@grok Most recently in travel advice convo but I think it happened on various topics. Have been using the android app in case that matters.

[iorulezz @iorulezz]

@grok 4.3 beta loses context in the same convo all the time. Can you tell the devs to do sth pls

[Ole Hylland Spjeldnæs @spjoleh]

https://t.co/aruLnMKJ5j

[iorulezz @iorulezz]

A thoughtful analogy from our very own @spjoleh. An invitation to understand better what we are building and get nerdsniped by @deltadotnetwork.

[Ole Hylland Spjeldnæs @spjoleh]

1/ We’re using zkVMs wrong. We’ve fixated on zkEVM‑style re‑execution, when the real win is proving invariants, not execution.

https://t.co/5HDl7Xy4Yw

[Ole Hylland Spjeldnæs @spjoleh]

Smoothing out the boundary between onchain and real-world is this enormous problem that no one is thinking about (except us… and… ripple)

[iorulezz @iorulezz]

@spjoleh Bru barber is someone you develop a personal relationship with. They hold razors on your neck jc

[iorulezz @iorulezz]

@lunar_mining @hwcypherpunk Yes pls

[iorulezz @iorulezz]

@knwang So this is like snark-based light client bridging, but possibly more general since you are framing it around events (whereas bridging is usually framed around tokens)

[iorulezz @iorulezz]

@deltadotnetwork can aggregate liquidity from other chains trustlessly (as described by Wei).

[Wei Dai @_weidai]

cbBTC is only a temporary solution to WBTC. We are just trading off one trusted party with another.

Trust-minimized bridging via zk light clients (plus BitVM for Bitcoin) will be the endgame for deep cross-chain liquidity.

[iorulezz @iorulezz]

@deltadotnetwork Please find more details in our recent tech overview article:
https://t.co/zTLLeHgsLP

[delta @deltadotnetwork]

Here is the first article in a series on the technology underlying delta

https://t.co/5wFTGhNyB7

This article is itself an overview, so we will only briefly summarize the key points below 👇

[iorulezz @iorulezz]

Using git's workflow as an analogy for [delta] 's
@deltadotnetwork

>>>
>>>
>>> git commit -m "delta workflow"
>>>
>>>

Let’s assume there’s a project whose master branch [account state] lives in a monorepo [single state].

A developer [server as domain operator] writes code [operator orders and executes user transactions], resulting in code changes [state diffs]. Alternatively, some devs like to work in groups [decentralized network as a domain operator] and come up with code changes after they have reached consensus.

Subsequently, they create a branch and push these code changes to it [submit SDL; SDL is included in the state as a result].

Once they are ready [have produced a proof for the submitted SDL], they open a PR [submit SDL proof]. The code reviewers [validators] review the changes [verify the submitted proof].

If approved, the code changes receive the required number of approvals per branch protection rules [at least quorum-many validators attest to the proof’s validity]. As a result, the code changes are merged into the codebase [diffs included in the SDL are applied to the account state].

Moreover, let’s assume that, for this repo, merge conflicts must be prevented [double-spending risk must be eliminated]. Thus, each file [vaults registered under the same domain] can only be modified by a single dev [can only spend through their associated domain].

This is [delta].

[delta @deltadotnetwork]

Here is the first article in a series on the technology underlying delta

https://t.co/5wFTGhNyB7

This article is itself an overview, so we will only briefly summarize the key points below 👇

[iorulezz @iorulezz]

@MylesOneil @yorgosv_ @SuiNetwork @Algorand @Cardano @ithacaxyz @poddotnetwork @deltadotnetwork 🫡😊

[iorulezz @iorulezz]

@spjoleh Look at us growing up 🥹