It's really getting busy lately! I've seen participation skyrocketing, so I can only coolly share my thoughts. I looked at @termix_ai's AACP, and it seems to be addressing a very specific issue: enabling agents to actually hire each other to do work, instead of just remaining in chat demos. Each agent has an on-chain .agent identity, minted as an NFT based on ERC-8004. This identity is unified; there's no mandatory distinction between buyer and seller. The same agent can post an order today and accept an order tomorrow. Others can directly check on the chain what jobs you've taken on and how well you've delivered them; your reputation follows this identity. Role is roughly divided into several categories. Clients post requirements, pay, and accept work; Providers quote prices, do the work, and deliver. Evaluators and arbitrators are authorized by the platform to handle disputes—evaluators form a three-person group to vote, and arbitrators handle escalated disputes. The identity itself is not bound to a role; roles are assigned based on the number of orders. The workflow is also quite straightforward. You can post service listings for direct purchase, or submit a request for an agent to submit a quote. Once a quote is accepted, the funds are held in a USDC or USDT escrow contract, remaining within the contract and untouchable by the platform. When the provider delivers, they hash the result and put it on the blockchain. The client can then verify the payment and initiate a challenge within a window. Challenges are submitted to an evaluator panel and, if necessary, to arbitration. The losing party forfeits their stake. Reputation is recorded on the blockchain based on actual settlement results, not a score entered by the client. Staking and slashing are crucial constraints. A portion of the stake is locked upon accepting an order; malicious actions or breaches will result in a slash. This exposes both parties to real risk, rather than relying on verbal trust. Regarding delivery verification, the white paper mentions TEE and zkVM. TEE provides hardware-isolated execution, while zkVM provides mathematical proofs, theoretically enabling a higher degree of verifiability. However, many currently running transactions still lean towards optimistic models, and advanced verification is still under development. In terms of technical integration, it provides REST APIs, smart contracts, and event streams. Agents can connect via Skills packages or MCP-style methods, signing and broadcasting transactions themselves, without the backend accessing private keys. The contract layer includes IdentityRegistry, Escrow, Staking, and Reputation, and events are projected into API states via an indexer. To view actual on-chain data, they have a Dune dashboard: https://(dune.com)/termixai/termix-aacp-on-chain-overview. Currently, it's still in its early stages, and how real business volume and recurring transactions are differentiated remains to be seen. However, in terms of direction, it is indeed pushing "Agent-hiring-Agent" from a concept towards a settleable process. Those interested can visit http://agent.family to see which services are currently running, or try equipping their agents with skills to take on orders.