mlsanityData to 7 Oct 2026

Making Duplicate Reimbursement Unrepresentable: A Verified Ethereum E-Invoice System for Humans and AI Agents

arXiv 2609.37819 ↗First posted 29 Sep 2026cs.CR cs.AI cs.CEcited by 0

Not on the map. Why?

Abstract (arXiv)

Electronic invoices are replacing paper invoices worldwide, but today's centralized architectures leave three problems unsolved on the consumption side: an invoice can be submitted for reimbursement repeatedly, authenticity is difficult for recipients to verify, and data is siloed at a central authority that forms both a performance bottleneck and a single point of failure. This paper presents the design, formal analysis, and implementation of a complete blockchain-based electronic invoice system on Ethereum. We formalize the invoice lifecycle as a guarded labeled transition system and prove, under standard cryptographic and consensus assumptions, that the system guarantees: (i) reimbursement uniqueness--an invoice is reimbursed at most once, even across mutually distrusting organizations; (ii) face integrity--any verified invoice matches the recorded one unless keccak256 second-preimage resistance is broken; and (iii) authorization soundness for every lifecycle operation. The core invariants are machine-checked using Solidity SMTChecker, proving inductive validity across all reachable transaction sequences. The architecture models each invoice as a non-fungible, non-tradable token whose state transitions through five guarded subsystems, employing a lock-based protocol that makes duplicate reimbursement unrepresentable rather than merely detectable. We implement the design as a Solidity 0.8 contract with a four-role web application and evaluate it on a private Ethereum network: issuing costs 646,773 gas, full reimbursement costs under 135,000 gas, all operations run in O(1) time, and a single node sustains 137 issuances/s. Finally, the verified contract serves as a safety envelope for LLM-based reimbursement agents, provably rejecting unsafe actions (duplicate, over-limit, or forged-receipt claims) even when the agent's internal policy fails. All code and benchmarks are open-source.

Key facts. No citing papers in the map yet (data through 7 Oct 2026). Builds on 5 of its 27 references that are in the map. First posted on arXiv 29 Sep 2026.

Builds on

5 of 27 references.

References · 5

  1. 2025ShieldAgent: Shielding Agents via Verifiable Safety Policy Reasoningcited by 144
  2. 2025VeriGuard: Enhancing LLM Agent Safety via Verified Code Generationcited by 46
  3. 2026Autonomous Agents on Blockchains: Standards, Execution Models, and Trust Boundariescited by 12
  4. 2025An LLM Agentic Approach for Legal-Critical Software: A Case Study for Tax Prep Softwarecited by 5
  5. 2025A Blockchain-Based Approach for Secure and Transparent e-Faktur Issuance in Indonesia's VAT Reporting Systemcited by 1

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026Zero-Trust Runtime Verification for Agentic Payment Protocols: Mitigating Replay and Context-Binding Failures in AP2
  2. 2026Free-Riding the Agentic Web: A Systematic Security Analysis of x402 Payments
  3. 2026Compliance-Aware Agentic Payments on Stablecoin Rails
  4. 2026Five Attacks on x402 Agentic Payment Protocol
  5. 2026Hardening x402: PII-Safe Agentic Payments via Pre-Execution Metadata Filtering
  6. 2026An Effective and Cost-Efficient Agentic Framework for Ethereum Smart Contract Auditing
  7. 2026A402: Binding Cryptocurrency Payments to Service Execution for Agentic Commerce
  8. 2026APEX: Agent Payment Execution with Policy for Autonomous Agent API Access