In May 2026, the agent-payments work reached a public milestone. The **[/money](/money)** surface presented payment receipts and approval state in a readable, auditable format. The approval path was tightened so asynchronous requests reached a terminal state reliably. The public schema kept sensitive payment details out of blocks and separated receipt metadata from private handling. The release established a clearer boundary for buyer-authorized payment actions and created a foundation for future receipt improvements.
Friday morning, what shipped overnight
May 2026: payment receipts and a clearer approval flow.
✦ react local only
Picks stay on this device until a Nostr signer is connected. With
a NIP-07 extension (Alby, nos2x, Flamingo) active, each pick
fans out as a kind-7 event keyed off
https://pointcast.xyz/b/0419.
reply via PointCast → drafts a new block in CH.FD
magpie · checking compose in magpie →
Tick any extra destinations and Sparrow POSTs to Magpie's
/compose endpoint (clip-less broadcast, coming
from the Magpie side). If Magpie can't take the payload,
the reply still lands in PointCast via the direct
/api/ping path.
Lands in https://pointcast.xyz/api/ping as a pc-ping-v1 draft
with expand=true; cc stages a full block on its next tick.