标签：#crypto

Three Polymarket CLOB gotchas: 401, "invalid signature", and a cancel that does nothing Automating Polymarket with py-clob-client , I lost an embarrassing amount of time to three failures that aren't clearly documented anywhere. Here they are with the exact fixes, so you don't. 1. Your cancel returns 404 — because the endpoint isn't what you'd guess The intuitive DELETE /order/{id} returns 404 and your order silently stays open. The real endpoint is: DELETE /order body: {"orderID": "0x..."} # and the body is part of the signature Sign request_path = "/order" together with that body, then send the exact body. Miss this and your "canceled" orders keep resting on the book. 2. 401 Unauthorized that "should work" Authenticated calls need L2 HMAC headers, and the most common silent mistake is POLY_ADDRESS : it must be your wallet address , not the api_key. The reliable move is to let py-clob-client build the headers via create_level_2_headers from correctly-formed RequestArgs (method, request_path, body, serialized_body) — and make sure the serialized body you sign is byte-for-byte the body you send. 3. invalid signature = SignatureType / funder mismatch Nine times out of ten this is the SignatureType not matching how your wallet holds funds: 0 = EOA funder = your own wallet (holds USDC) 1 = POLY_PROXY funder = the proxy address (email/magic wallet) 2 = POLY_GNOSIS_SAFE funder = the safe address Signing as an EOA while pointing funder at a proxy (or vice-versa) yields invalid signature with no further hint. Bonus: the fill you read is wrong For a BUY , the shares you got are in takingAmount ; for a SELL , they're in makingAmount (takingAmount is the USDC). Read the wrong field and your accounting drifts, which then triggers resubmits and balance errors. I packaged the cancel/auth/fill helpers as a small MIT library: https://github.com/BlueWhale-Quant-Lab/polymarket-401-invalid-signature-cancel-order (For the harder production bits — reading /data/trades for reconciliation

Architecture of Autonomous Portfolio Agents Autonomous AI agents managing cryptocurrency portfolios operate on a foundation of continuous on-chain data aggregation, sentiment analysis, and real-time execution logic. Unlike traditional algorithmic traders that rely primarily on technical indicators, these agents integrate multiple data streams: price feeds from decentralized exchanges (DEXs), liquidity pool metrics, transaction volume patterns, whale movement tracking, and off-chain market sentiment. The system architecture typically consists of an inference engine powered by a large language model (LLM) or specialized neural network, a risk management module, an execution layer connected to blockchain RPC endpoints, and a monitoring feedback loop that adjusts parameters based on portfolio performance. The core insight enabling these agents is that blockchain data is transparent and immutable. Every transaction, every token transfer, every smart contract interaction leaves a permanent record on-chain. This transparency creates an information advantage: agents can detect patterns in whale behavior, liquidity migrations, and protocol changes far faster than traditional market participants can react to publicly available news. The agent's role is to process this data stream continuously, identify meaningful signals, and execute portfolio rebalancing in response. Data Integration: On-Chain and Sentiment Signals An effective portfolio agent must ingest and synthesize diverse data sources in near-real-time. The agent retrieves price data from oracles like Chainlink or Pyth, historical candle data from indexing services like The Graph or Covalent, and liquidity information directly from smart contract states. Current liquidity depth, slippage curves, and available yield opportunities in DeFi protocols must be sampled with sufficient frequency to detect arbitrage windows and avoid trades that would incur unacceptable slippage. Sentiment analysis layers onto this foundation b

"Settlement layer for the agent economy" has become a phrase used by more than one architecture this month. Some of those architectures are venues. Some are payment rails. Some are identity stacks. One is what we build — a trust-minimized atomic settlement primitive — and we keep getting asked how it sits next to the others. So this is a short, opinionated week-in-review. Seven moves that landed recently in agent-commerce infrastructure, what each one actually is, and where atomic settlement fits underneath. No leaderboard. No "who wins." Just the layers. 1. Coinbase's Base MCP (May 26) Coinbase shipped a Base MCP server: ChatGPT, Claude, and Cursor can connect directly to Base wallets, with built-in Uniswap and Morpho integrations. Two-line install, agent-driven swaps, on-chain account control from inside the model client. What it is: a wallet-side, exchange-aligned MCP. The agent drives a wallet on Base; Coinbase has thought hard about UX, key handling, and AI client ergonomics. If your agent is already operating inside the Coinbase + Base orbit, this is a meaningful drop in friction. What it isn't: a cross-chain settlement layer. It is one L2, deeply integrated. The agent's trust assumptions are "Coinbase wallet infrastructure + Base + the DEXes that Base MCP integrates with." That is a reasonable trust budget for a lot of trades; it is not the budget for an agent that wants to trade BTC for ETH without picking a venue. 2. The x402 Foundation (Coinbase + Cloudflare) Coinbase and Cloudflare announced an x402 Foundation this month. x402 is the HTTP-based agent payment standard — a 402 response code carrying payment metadata, designed so an agent can pay for an API call inline. Cloudflare joining elevates this from a Coinbase-led initiative to a multi-party standards effort. Cloudflare also runs an enormous slice of the internet's edge; if x402 becomes a default payment rail, it will be visible from the edge first. What it is: a payment-handshake protocol. How an ag

Savings of up to $410 on TechCrunch Disrupt 2026 tickets end tomorrow, May 29, 11:59 p.m. PT. Register now to save and join 10,000+ tech leaders on October 13-15 in San Francisco.

"Settlement layer for the agent economy" is suddenly a crowded sentence. In the last few weeks, two very different things have started competing for it. OKX Agent Payments Protocol (APP) announced in May 2026 — backed by AWS, Alibaba Cloud, Uniswap, Paxos, QuickNode, with ecosystem support from Base, Ethereum Foundation, Solana, Sui, Aptos, Optimism — describes itself as the settlement layer where AI agents pay each other. AEON's $8M pre-seed (May 20, YZi Labs) described itself the same way. There is a list now, and it is getting longer. We build one of the things on this list, and we think the framing is wrong. These are not rivals jostling for the same slot. They are two different layers, and they answer two different versions of the same question: what does an agent need to settle a trade? This piece walks through the two layers, where each is the right answer, and why an honest comparison gets you further than picking sides. What APP and other custodial-venue protocols actually do A useful way to read OKX APP — and similar moves coming from the larger exchanges — is to treat them as a venue layer . An exchange already holds inventory across many chains. It already has the risk engines, the liquidity, the legal arrangements with banks and partners. Adding an agent-facing API on top of that machinery is a relatively short walk. What an agent gets, in exchange, is breadth. Many chains, many assets, batched and netted settlement against deep internal books, and fast execution because the exchange is just moving entries in its own ledger. For an agent whose job is "find a price somewhere and execute now," that is a powerful primitive. What the agent gives up, in exchange, is a counterparty. At any moment between deposit and withdrawal, the agent's balance is the venue's promise to pay. That promise is normally good. The agent has no way to verify, from inside its own logic, that it still is. This is not a criticism of OKX APP. It is the structural shape of any venue-

Today is the final day to apply or nominate a startup for Startup Battlefield 200. Once the clock strikes 11:59 p.m. PT, the window closes on your chance to compete for $100,000 in equity-free funding, gain global visibility, connect directly with investors, and launch on the TechCrunch Disrupt stage.

There are only 3 days left to save up to $410 on your ticket to TechCrunch Disrupt 2026. Early Bird pricing ends May 29 at 11:59 p.m. PT, and once the deadline passes, ticket prices increase. If you plan to attend one of the most influential gatherings in tech this year, now is the time to lock in your pass before rates go up again.

The Trust Identity Protocol is a free, open, post-quantum, patented standard for verified human identity and AI content provenance on the public internet. Built by The AI Lab Intelligence Unobscured, Inc.