Missing blockchain/identity/provenance comparators
BlockA2A, BAID, ClawGang/MeowTrade, Merkle Automaton — the reviewer lists four directly relevant systems that DIE doesn’t engage with.
Cure: This is the biggest single addition needed. Add a Comparative Architecture subsection or table:
| System | Identity mechanism | Memory model | DIE relationship |
|---|---|---|---|
| BlockA2A | DID + smart-contract policy | Runtime policy enforcement | ERC-8004 complements; BlockA2A adds revocation layer DIE lacks |
| BAID | zk-bound code + biometrics | Recursive zk proofs | Stronger cryptographic guarantees, heavier prover cost; Values Passport is lighter, values-oriented complement |
| ClawGang/MeowTrade | TEE-backed memory artifacts | Tradable provenance | DIE’s on-chain anchoring vs. TEE — public verifiability vs. hardware trust boundary |
| Merkle Automaton | Immutable per-transition commitments | ZK inclusion proofs | Formal theoretical foundation DIE could adopt for no-drift memory properties |
Position DIE not as replacing these but as occupying a values-attestation layer that is orthogonal to identity-binding and code-provenance. This is accurate and defensible.
Hybrid proposal (addresses Q7): Acknowledge that “values passport + zk/TEE provenance” is a productive direction — this is actually consistent with DIE’s Phase 2 roadmap and costs you nothing to state.
Strategy first
The reviewer listed four systems — BlockA2A, BAID, ClawGang/MeowTrade, Merkle Automaton — and said DIE doesn’t engage with any of them. This isn’t a small gap. For AAMAS reviewers these are live adjacent systems. The fix has three parts:
- Part A — a new subsection heading within §12
- Part B — the comparative table (4 rows, 4 columns)
- Part C — a positioning paragraph that frames DIE as orthogonal to these systems, not competing
Where it goes
Section 12 — “Relation to Existing Work”
Currently §12 has two paragraphs:
Para 1: “This work builds on multi-agent systems foundations…” Para 2: “No prior work combines dimensional perception theory…”
The insertion goes between these two paragraphs as a new named subsection.
The insertion (markup format)
[END OF EXISTING §12 PARA 1]
...The financial model coherence analogy situates the
framework within 500 years of double-entry bookkeeping
practice [Pacioli 1494].
>>> INSERT HERE >>>
12.1 Positioning Against Blockchain/Identity/Provenance
Systems
Four closely related systems address the agent identity,
memory provenance, and coordination trust problem from
adjacent angles. Table 4 positions DIE relative to each.
[TABLE 4]
Table 4: DIE positioned against adjacent blockchain/identity/
provenance systems. DIE occupies the values-attestation
layer; the other systems address identity-binding,
code-provenance, and memory-market layers.
| System | Identity Mechanism | Memory/Provenance Model | DIE Relationship |
|---------------|-----------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------|
| BlockA2A | DID + smart-contract | Runtime policy enforcement; | Complementary: BlockA2A adds revocation governance |
| [De Rossi | policy layer; selective | Defense Orchestration Engine; | and runtime halting logic DIE does not implement. |
| et al. 2025] | on-chain anchoring | sub-second latency mitigation suite | ERC-8004 Values Passport is a lighter values-oriented |
| | | | credential; a hybrid stack is feasible. |
|---------------|-----------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------|
| BAID | zk-bound agent code + | Recursive zk proofs; zkTLS for | Stronger cryptographic identity guarantees at higher |
| | operator biometrics; | verifiable transport-layer identity | prover cost. DIE's Values Passport is behaviourally |
| | code-level binding | | attested rather than code-bound — orthogonal layers |
| | | | addressable in a hybrid (values attestation + zk |
| | | | code binding). |
|---------------|-----------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------|
| ClawGang / | TEE-backed computation | Memory artifacts as tradable goods; | DIE's VTP substrate provides public-chain verifiability; |
| MeowTrade | receipts | verifiable provenance per artifact | TEE provides hardware-trust-boundary guarantees. |
| | | | Trade-off: public auditability (DIE) vs. confidential |
| | | | execution (TEE). Verifiable computation receipts could |
| | | | strengthen DIE's SS1/SS2 snapshot integrity claims. |
|---------------|-----------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------|
| Merkle | Per-transition cryptographic| Immutable memory with ZK inclusion | Provides a formal automata-theoretic foundation DIE |
| Automaton | commitments; ZK proofs for | and access-control proofs; | currently lacks for "no-drift" memory properties. |
| | inclusion and access | constrained reasoning guarantees | DIE's episodic/procedural memory split maps onto |
| | control | | Merkle Automaton's per-transition model; adoption of |
| | | | this formalism is a concrete Phase 2 target. |
DIE does not compete with any of these systems at their
primary layer. BlockA2A addresses runtime policy
enforcement and revocation governance; BAID addresses
code-level identity binding; ClawGang/MeowTrade addresses
verifiable memory as a market primitive; Merkle Automaton
provides formal memory constraints with ZK guarantees.
DIE occupies a distinct and orthogonal layer: values
attestation — encoding honesty, competence, care, and
empathy as on-chain behavioural credentials that constrain
how an agent maps internal state to observable behaviour,
independent of what code the agent runs or who created it.
The Values Passport is not a substitute for the identity-
binding and code-provenance guarantees these systems
provide; it is a governance layer that operates above them.
A full-stack agent governance architecture combining
BlockA2A's revocation layer, BAID's code-binding,
ClawGang's verifiable memory market, Merkle Automaton's
formal memory constraints, and DIE's values attestation
layer is a concrete and productive direction for Phase 2
collaborative work.
Note on scalability and privacy: default on-chain logging
of agent actions — even as hashes — raises non-trivial
cost, throughput, and metadata leakage concerns at
operational scale. DIE adopts a selective anchoring
strategy: SHA-256 hashes of log entries are committed
on-chain as tamper-evident fingerprints (AgentAction
events on Base mainnet), while bulk artifacts remain
off-chain. Merkle root batching — anchoring the root of
a batch of N events rather than each event individually
— is the planned Phase 2 scalability control, consistent
with the hybrid on-chain/off-chain provenance approach
documented in adjacent systems. Metadata leakage from
hash-only anchoring is acknowledged; GDPR/PDPA
compliance is maintained by ensuring no personal data
travels on-chain.
<<< END INSERT <
[EXISTING §12 PARA 2 CONTINUES AS-IS]
No prior work combines dimensional perception theory...What this fixes
| Reviewer complaint | Status after Fix 3 |
|---|---|
| “Does not substantively engage with BlockA2A” | Addressed in Table 4 row 1 + positioning para |
| “Does not engage with BAID (zk-bound identity)” | Addressed in Table 4 row 2 + hybrid proposal |
| “Does not engage with ClawGang/MeowTrade” | Addressed in Table 4 row 3 + TEE vs VTP trade-off |
| “Does not engage with Merkle Automaton” | Addressed in Table 4 row 4 + Phase 2 target flagged |
| Reviewer Q7 (ERC-8004 vs alternatives) | Fully answered — hybrid stack explicitly proposed |
| On-chain cost/latency/privacy (part of Fix) | Scalability/privacy note closes this simultaneously |
| Missing revocation/governance discussion | BlockA2A row flags this gap honestly |
Bonus: this note simultaneously closes part of Fix 6 from the earlier analysis
The scalability/privacy note at the end of the insertion handles the on-chain cost/latency/privacy concern the reviewer raised — meaning that concern no longer needs a separate fix. One insertion, two reviewer objections resolved.
What is explicitly NOT changed
- The opening paragraph of §12 — all existing foundations citations remain intact
- The closing uniqueness paragraph (“No prior work combines…”) — unchanged, still accurate, now more defensible because the comparative table demonstrates DIE knows the adjacent work
- §9 (Values Passport) and §3.3 (ERC-8004) — no edits needed; they now have a comparative anchor in §12.1
Word count impact
Approximately +350 words including table. Largest insertion so far but concentrated in one location — §12.1 — where reviewers expect exactly this content.