iorulezz retweeted
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.
A thoughtful analogy from our very own @spjoleh. An invitation to understand better what we are building and get nerdsniped by @deltadotnetwork.
1/ We’re using zkVMs wrong. We’ve fixated on zkEVM‑style re‑execution, when the real win is proving invariants, not execution.
teapaw.org/spjoleh/status/1959992…
iorulezz retweeted
Smoothing out the boundary between onchain and real-world is this enormous problem that no one is thinking about (except us… and… ripple)
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].
Please find more details in our recent tech overview article:
teapaw.org/deltadotnetwork/status…
Here is the first article in a series on the technology underlying delta
delta.network/articles/delta…
This article is itself an overview, so we will only briefly summarize the key points below 👇
iorulezz retweeted
Here is the first article in a series on the technology underlying delta
delta.network/articles/delta…
This article is itself an overview, so we will only briefly summarize the key points below 👇
iorulezz retweeted
delta's design is exceedingly simple. To get there, you can start with a rollup stack and just delete stuff:
- Remove the need for bridges and 3rd party interoperability services by having all the "rollups" (domains) share state
- Integrate the execution layer with the base layer to further simplify interop by making all tokens "L1-native" by default, regardless of where they're deployed
- Remove ordering consensus
zk settlement enables completely heterogenous execution environments within the global state machine.
Our view is that the ideal permissionless system consists of a minimal, neutral base layer which provides censorship resistance and extreme scale, combined with highly opinionated, customized execution environments.
This system is delta.
This quoted post is unavailable.
iorulezz retweeted
We're super excited to announce our investment into @deltadotnetwork! Having co-led the pre-seed and doubled down in the seed, it is only fair we give an overview of exactly why we're excited.
The marriage of monolithic and modular;
teapaw.org/deltadotnetwork/status…
iorulezz retweeted
NEW: Starting from scratch: A new architecture looks to challenge incumbents
by @yeluacaM
blockworks.co/news/delta-new…
iorulezz retweeted
In this article @riabhutoria and I explore the global financial system of the (near) future, as some tbd very cool tech innovations get out there
iorulezz retweeted
1/ "An organization that could globally guarantee and transfer monetary information in the form of arranged electrons and photons would have a market, every exchange of value in the world"—Dee Hock
This was the dream of Visa's founder. But the rise of the internet and an all-pervasive atmosphere of information has not given us a similar atmosphere for scarce information—money and assets
iorulezz retweeted
A blockchain ecosystem should
A. Vertically scale to physical limits, within a composable domain
B. Horizontally scale by allowing more composable domains, without compromising security or interoperability
Ethereum has done B and is adding A
Solana has done A and is adding B
[Redacted] is doing both A and B from the get go