What a week in Miami. Capped it off on the Workshop Stage at @consensus2026 with the first live demo of compliance screening for autonomous agent payments via @ampersend_ai, built with @trmlabs and @chainlink. A wallet linked to Tornado Cash, blocked in real time with a 403 Forbidden. A clean wallet transacted normally. One toggle. Full audit trail. Every enterprise conversation this week came back to the same question: how do you prove the agent didn't just pay a sanctioned entity? Now there's an answer. Coming to ampersend soon. Next stop: Bermuda Digital Finance Forum 2026 hosted by @SALT and @PartnersPenrose.
The themes on the agenda next week from decentralized finance to AI's role in capital markets are exactly the conversations I want to be part of. 

DM if you'll be there 🇧🇲

[Event announcement!!] Merch catalog for tmr’s Doujima!! I will booth at Doujima this weekend (6-7 May) at Singapore Suntec convention hall 403/404. Booth number G66 with @katykatcupcake!!! Do visit us this weekend 💕💕 Cosplan: Ganyu nurse (SAT) and Kobeni nurse (SUN)

Double bunnies for you to get through mid week!!! And!!! [Event announcement!!] I will booth at Doujima with @katykatcupcake this weekend (6-7 May) at Singapore Suntec convention hall 403/404, Booth number G66. Bunny suit: @_RedThorns_ Photo: @changshinvona #bunnygirlcosplay#

last week at @consensus2026 in miami: we showed the live demo of compliance enforcement on autonomous agent payments, first time live, with @trmlabs and @chainlink. here's the unpack 👇 what we demoed two transactions, screening enabled. badclaw, a wallet associated with tornado cash. blocked with a 403 forbidden the moment it hit the screening layer. no funds moved, no human in the loop, no rejection details disclosed so adversaries can't reverse-engineer the logic. goodclaw, a wallet with clean defi history. screened against the same intelligence layer, came back at acceptable risk, transacted normally. one toggle inside the dashboard: every decision logged with risk scores, categories, attributed entities, offending addresses, and timestamps. why this matters agent guardrails have been a half-conversation so far. spend limits cover how much your agent can move. ampersend has handled that since day one with per-agent wallets, limits, topup schedules, and a dashboard for monitoring activity. that's half the problem. the other half is who the agent is transacting with. a clean spend limit doesn't help when the recipient is a sanctioned entity or a ransomware operator, and no regulator is going to be satisfied that the dollar amount was capped. compliance screening closes the second half. spend controls plus screening is what defensible agent commerce actually looks like. why three companies policy, intelligence, enforcement. three separate jobs. 1️⃣ @chainlink ACE writes the policy onchain where regulators can verify it directly. 2️⃣ @trmlabs returns risk intelligence on the counterparty in under 500ms with fedramp high authorization. 3️⃣ ampersend executes the decision before the transaction broadcasts. splitting it across three companies is the point. no single party can weaken the rule, fudge the intelligence, or skip the enforcement. what's next screening ships into ampersend as a fast follow for enterprise customers. roadmap extends to buyer-side gating, world id proof-of-personhood on counterparty owners, and kyc-verified counterparties through chainlink ACE and sumsub. huge thanks to the @trmlabs and @chainlink teams. get started with ampersend:

Status update. Working through the issues users have flagged. Current focus: - Order placement & cancel latency (P0): two fixes in flight. Spam mitigations + improved order intake (ETA Wednesday). More guardrails on top. - "Not enough balance / allowance" on limit sells (and some buys): multiple fixes shipped, first focused on buys. Major source of sell-limit issue identified with patch in QA, releasing tomorrow - Cancel orders right after a restart: shipping in next week's CLOB release. - 403 on API key creation: working directly with Cloudflare and pulling logs from impacted users. - PnL - Some users have been encountering fluctuating PnL. Position values and average prices should now be correct, and daily/weekly PnL will heal automatically at end of day and end of week UTC time. - Withdrawals failing with "something went wrong": down to a handful of accounts. Deposit-wallet deployment edge case. Ping our bug-report channel in Discord if you hit it. - Deposit wallet generated for users with an existing proxy/safe: edge case when the /users call fails. Patch in QA, shipping next release.

this trader hit 370/1 wl and maded $8,931 in 2 weeks. > $1,247 today > $4,318 past week > 99.7% wr. everyone trades BTC 5-min. he found a quieter edge. china weather markets. guangzhou. beijing. wuhan. that's it. his stack: > CMA api (china meteorological administration) > ECMWF for cross-check > claude reads both, compares to polymarket price > enters NO at 90-96c on outcomes already 99% confirmed > Kelly criterion sizes the bet > waits for resolution f* = (p − m) / (1 − m) best trades: - guangzhou 22°C+ no, 94c -> $1.00 ($3,200 -> $3,403) - beijing 8°C+ no, 96c -> $1.00 ($4,150 -> $4,323) - wuhan 15°C+ no, 91c -> $1.00 ($1,890 -> $2,077) each trade pays 4-10%. he runs 25-30 a day. compounds daily. curve hasn't dipped once since april. straight line up. his profile: here's the asymmetry copy traders miss: - 4 trades at 96c copied separately = +4% x 4 = +16% - same 4 stacked into one parlay = +100-300% in one position stop copying his trades one by one. stack them. do it via most consistent weather wallet on polymarket. nobody's watching him yet. don't wait until the spread closes.