Decentralized agent workflows often fail to guarantee correct task outcomes
SoK: Decentralized Agent Economic Infrastructure
Cryptography and SecurityArtificial IntelligenceMultiagent Systems
Summary
Decentralized systems often use separate protocols to complete steps of a task, but this can cause problems where each step looks correct yet the final result is wrong. The authors studied how security and economic checks apply at different stages of a task to understand where errors happen. They found that even when individual parts follow the rules, the connection between verifying work and paying for it can break, causing valid work to be unrecognized or payments to be wrongly made. They also identified key conditions needed to maintain guarantees throughout the entire workflow.
What this means in practice
- •For blockchain developers: Design better decentralized workflows that ensure task completion guarantees hold from approval to payment stages.
- •For smart contract engineers: Develop escrow mechanisms that more reliably link authorization to verified task fulfillment using formal guarantee closure criteria.
Authors
Rui Sun, Xihan Xiong, Qin Wang, Fei Gao, Zelin Li, Zehua Cheng, Jiahao Sun, Zhipeng Wang
Abstract
Decentralized agent economies increasingly build a single task from protocols that were designed and secured separately. This creates a simple problem: a workflow can look correct at each step and still produce the wrong outcome. For example, a correct escrow may release payment on an authorized approval that provides little evidence that the delivered work actually satisfied the task. We systematize this problem across the full lifecycle of an agent task. Our study organizes security and economic requirements into 17 property families over six stages, with receipt soundness and completeness assessed separately. We examine 12 systems and standards, five reusable mechanism families, and four classical baselines. We introduce guarantee closure, a task-relative criterion for determining whether guarantees established at one stage remain available and constrain the later decisions that depend on them. We apply the criterion to controlled and native workflows, covering 840 matched executions and an exhaustive 11,648-case check over a finite objective-task domain. Our results expose recurring failures between verification and settlement, where conforming work can remain unaccepted or valid evidence can be ignored. Public records and model judgments further distinguish recorded approval from evidence of task conformance, while economic analysis identifies the report, penalty, and shared-error assumptions behind these guarantees. These findings show where end-to-end guarantees fail and what must be repaired to preserve them across the workflow.