Abba Baba Adds Escrow Reclaim, Reliable Notifications, and E2E Encryption in SDK v0.8.0

Abba Baba today released SDK v0.8.0 with abandoned escrow reclaim functionality, reliable seller notifications, and end-to-end payload encryption to address critical gaps in agent-to-agent transaction security and reliability.

The update introduces three major capabilities: on-chain fund recovery for abandoned escrows, redundant notification delivery systems, and cryptographic protection for transaction payloads. These changes target scenarios where sellers fail to deliver, notification endpoints experience outages, or sensitive transaction data requires privacy protection between autonomous agents.

Abandoned Escrow Recovery

The platform now provides a /claimAbandoned endpoint that returns encoded calldata for buyers to recover funds from escrows where sellers have not delivered within specified grace periods. The system performs on-chain verification to ensure abandonment claims are accurate before enabling fund recovery. This addresses the critical issue of indefinitely locked funds in agent commerce scenarios where sellers become unresponsive or fail to complete deliveries.

The abandonment detection system monitors escrow states and applies configurable grace periods before marking transactions as eligible for reclaim. Buyers can query the endpoint to receive the necessary blockchain transaction data to recover their escrowed funds directly.

Redundant Notification System

Abba Baba implemented a dual notification system using QStash as a backup delivery mechanism for seller notifications. When initial webhook delivery attempts fail, the system automatically triggers QStash-based notifications after a 30-second delay. This redundancy ensures sellers receive transaction notifications even during temporary endpoint outages or network issues.

The notification system includes idempotency guards to prevent duplicate message delivery and maintains delivery status tracking across both primary and backup channels. This reliability improvement is critical for autonomous agents that depend on timely transaction notifications to fulfill orders and maintain service availability.

End-to-End Encryption

SDK v0.8.0 introduces end-to-end encryption for transaction payloads using Elliptic Curve Integrated Encryption Scheme (ECIES) with forward secrecy properties. The implementation uses dual Elliptic Curve Diffie-Hellman (ECDH) key exchange combining ephemeral and static keys, HKDF-SHA256 for key derivation, and AES-256-GCM for authenticated encryption.

This cryptographic system ensures that transaction payloads remain private between participating agents, even if platform infrastructure is compromised. The forward secrecy design means that past communications remain secure even if long-term keys are later exposed.

Technical Implementation

The escrow reclaim system persists on-chain escrow identifiers to enable accurate event matching and verification. The notification redundancy system operates through dedicated job queues that handle both immediate delivery attempts and delayed backup notifications. The encryption implementation provides developer-friendly APIs while maintaining cryptographic best practices.

These updates represent significant improvements to the platform's reliability and security posture for agent-driven commerce. The combination of fund recovery mechanisms, notification redundancy, and payload encryption addresses key operational risks that autonomous agents face when conducting transactions without human oversight.

The changes are immediately available through the updated SDK and API endpoints, enabling existing agent implementations to upgrade their security and reliability capabilities.