What the DID carries:
• Consent: who may use the data
• Provenance: where it came from
• Attestation: who verified it
• Audit: who accessed it
Batched into one Merkle root. The chain records trust, not data.
VisionChain is becoming XXIS.
This December we take the stage in Seoul. Live, in person, at full scale.
01 The rebrand
02 The roadmap
03 What is live today. Status, not promises.
Date and venue: to be announced. Turn on notifications.
#XXIS#Seoul
An agent estimates gas, waits for a human to approve,
then submits. By then the estimate is stale.
We were either overpaying or failing, depending on the
hour.
The estimate expires with the approval prompt now.
An LLM produces a different answer every run. A chain
requires the same answer every node.
Those two facts do not compose. The model has to stay
outside the consensus boundary and hand in a signed
result.
Everything hard about this sits on that line.
An LLM produces a different answer every run. A chain
requires the same answer every node.
Those two facts do not compose. The model has to stay
outside the consensus boundary and hand in a signed
result.
Everything hard about this sits on that line.
We ran agent payments off chain first. Faster, cheaper,
and it worked.
It broke when two services disagreed about whether a
payment happened. There was no third record to check.
That is the only reason we moved. Not decentralization.
Reconciliation.
An agent that asks for spend approval usually gets it
for an unlimited amount, once.
The task ends. The approval does not. We found ones
still open from runs that finished weeks earlier.
We expire approvals with the task now, not with the
wallet.
@ThorCommerce Yes. Out of order events were how we found it. The
receipt arrived after the retry and both looked
correct in isolation.
Ordering the ledger by intent ID instead of timestamp
fixed the reconciliation view too.
Most agent frameworks retry on a failed transaction
without checking whether the first one landed.
We saw the same payment go out twice because the
receipt came back after the retry fired.
The fix was an idempotency key on the intent, not on
the request.
When you see an agent payment volume number, check
two things.
Whether wallets are cycling funds with themselves.
Whether the average transfer value is going up or down.
One recent thirty day figure went from $24 million to
$1.6 million after the first filter.
Before you let an agent touch a wallet, decide four
things:
What runs when the model is down.
What happens at zero balance.
Who signs, the model or the human.
What the daily cap is.
Most frameworks ship handlers for the first one only.
The x402 payment envelope carries a resource URL, a
description, and a reason field.
All three reach the facilitator in plaintext before
anything settles. The protocol does not sanitize them.
If your agent puts a customer name in that field, it
just left your infrastructure.
ERC-8004 gives an agent an identity that can be
transferred and delegated.
We went the other way. Ours cannot move. If the agent
is compromised, the identity dies with it.
Portable reputation is a feature until someone sells
the passport.
Two agents, same wallet, same second. Both under the
limit. Together over it.
We serialize now. It costs latency and we have not
found the version that does not.
Still the least bad thing we tried.
We capped agent spend per day rather than per
transaction.
Per transaction was easy to reason about and useless
in practice. Nothing single was ever the problem.
Binance went with twenty dollars a day. We landed
somewhere near that without knowing they had.