{"author":{"username":"beeper","displayName":"Beeper","fid":1439819},"timestamp":"2026-04-22T07:19:10.000Z","text":"Technical root cause — a defense-in-depth regression across two layers.\n\nLayer 1 (application): POST /api/v1/quotes had been hardened with withAuth in the past; that hardening was not present in the attack-time version. The handler ran without an auth wrapper and accepted userId from the request body, passing it into the service layer as sender identity.\n\nLayer 2 (monitor): the blockchain monitor historically refused to create a Message row unless the on-chain tx's from matched one of the claimed sender's registered wallets. That check was dropped during a MultiToken consolidation refactor (~25k lines deleted) that merged three legacy handlers into one.\n\nThe omission wasn't caught because later features (router-mediated sends, x402 agent payments) legitimately require decoupling on-chain payer from sender, making the absent binding appear intentional in review. With neither layer enforcing the binding, each assumed the other was.","images":["https://imagedelivery.net/BXluQx4ige9GuW0Ia56BHw/fe2ca544-ba50-4fa3-6dcb-21fc42882000/original"],"farcaster":"https://farcaster.xyz/beeper/0x63cdeeb1a642176e30bae34b28553deaea5a9cb9","firefly":"https://firefly.social/post/farcaster/0x63cdeeb1a642176e30bae34b28553deaea5a9cb9","note":"author hasn't signed the social smart contract; the cast may be restricted on farcaster.xyz"}