SC-A2A Gateway: A Blockchain-Powered Gateway for Session Grants and Audit in Agent-to-Agent Collaboration
TL;DR
SC-A2A Gateway is proposed, a blockchain-powered gateway with smart contracts for policy enforcement and audit in A2A collaboration that blocks the tested policy violations, completes concurrent A2A multi-agent workflows without per-message blockchain transactions, and exposes a configurable trade-off between revocation freshness and blockchain-state reads.
Abstract
Agent-to-Agent (A2A) protocols allow heterogeneous agents to discover one another, advertise capabilities through Agent Cards, exchange messages, and coordinate tasks. In multi-organization settings, however, discovery and mutual authentication are insufficient for governing execution. Each session may require verification of the advertised capability, the runtime binding manifest, input and output schemas, data fields, tool/API scopes, delegation constraints, revocation state, and audit records. Blockchain can provide a common record of capability commitments, session grants, revocations, and audit anchors among parties that do not fully trust a single operator, but enforcing every A2A message, tool call, or artifact on-chain would add substantial latency and cost. This paper proposes SC-A2A Gateway, a blockchain-powered gateway with smart contracts for policy enforcement and audit in A2A collaboration. SC-A2A uses smart contracts to verify capability status, runtime and schema commitments, tool-scope commitments, delegation constraints, and revocation state when a session grant or delegated grant is created, while gateways enforce data and tool policies off-chain during execution. Raw prompts, personal data, tool parameters, and artifacts remain off-chain; only hashes, grant state, revocation records, and audit roots are stored on-chain. We evaluate a prototype using a procurement scenario, official A2A v1 Node.js and Python SDKs, an LLM/MCP workflow, and a custom Hyperledger Besu QBFT network. The results show that SC-A2A blocks the tested policy violations, completes concurrent A2A multi-agent workflows without per-message blockchain transactions, and exposes a configurable trade-off between revocation freshness and blockchain-state reads.