惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

G
Google Developers Blog
Jina AI
Jina AI
大猫的无限游戏
大猫的无限游戏
Martin Fowler
Martin Fowler
博客园 - 司徒正美
云风的 BLOG
云风的 BLOG
C
Cybersecurity and Infrastructure Security Agency CISA
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
S
Securelist
S
Security Affairs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
L
LINUX DO - 热门话题
博客园 - 三生石上(FineUI控件)
T
Threatpost
T
The Blog of Author Tim Ferriss
C
CERT Recently Published Vulnerability Notes
IT之家
IT之家
P
Palo Alto Networks Blog
Microsoft Azure Blog
Microsoft Azure Blog
Spread Privacy
Spread Privacy
Cyberwarzone
Cyberwarzone
腾讯CDC
L
LangChain Blog
Know Your Adversary
Know Your Adversary
C
CXSECURITY Database RSS Feed - CXSecurity.com
GbyAI
GbyAI
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
I
Intezer
T
Tor Project blog
AWS News Blog
AWS News Blog
T
Tenable Blog
NISL@THU
NISL@THU
Security Latest
Security Latest
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
H
Hackread – Cybersecurity News, Data Breaches, AI and More
人人都是产品经理
人人都是产品经理
MongoDB | Blog
MongoDB | Blog
MyScale Blog
MyScale Blog
D
DataBreaches.Net
Microsoft Security Blog
Microsoft Security Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
量子位
美团技术团队
The Cloudflare Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
罗磊的独立博客
The GitHub Blog
The GitHub Blog
阮一峰的网络日志
阮一峰的网络日志
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Stack Overflow Blog
Stack Overflow Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Reactive Intent Markets: a working paper on the submission format atomic settlement makes possible
Baris Sozen · 2026-05-11 · via DEV Community

A note up front: how this was written

Before the argument, the methodology, because the methodology is part of the argument.

This working paper was written with Anthropic's Claude as a research collaborator. The thesis, the framing, the lived experience that the paper draws from — three decades of treasury-desk work, two currency crises lived through — those are mine. What Claude did was sharper: it organized the related-work survey, stress-tested the conjectures against the mechanism-design literature, and pushed back when an argument I thought was tight turned out to be load-bearing on something I had not justified. The paper exists in this form because of that back-and-forth. Sitting on the idea — the alternative — felt like exactly the kind of impedance the autonomous economy this paper describes is supposed to remove.

I am also disclosing this here, in body text, on purpose. The paper proposes a market for AI agents. The paper was helped into existence by an AI agent. If that loop is uncomfortable, sit with the discomfort. It is going to become the default condition under which working papers in this category get written.

The thesis in one paragraph

Conventional market venues require participants to compress their preferences into a single price-quantity submission. That compression is enormous: a function from a high-dimensional state space to a single point on a price line. It happens not because participants have shallow preferences but because the operational environment of conventional venues — settlement that can fail, counterparties that can default — makes deeper revelation reckless. Atomic settlement removes that operational reason. The submission format that becomes possible once it is removed is a richer one: a state-conditional policy, cryptographically committed in private, evaluated at clearing time, revealed only as the aggregate intent the venue clears against. The paper calls this a Reactive Intent Market.

Where it comes from

Two things shaped the seed. The first is George Soros's The Alchemy of Finance (1987), and specifically his notion of reflexivity — that participants' beliefs about the market shape the market, which then shapes their beliefs, in a loop without a clean fixed point. The second is what it felt like to live through the Turkish February 2001 currency crisis and the 2008 global crisis on opposite sides of the trading floor. In both episodes the same thing happened: a market that had been priced under one set of assumptions reached a state where its participants no longer believed those assumptions could hold. The price did not reflect new fundamentals. It reflected the population's posture about its own posture. Mackay had a phrase for this in 1841; modern microstructure has a vocabulary; the working trader has the body memory.

What I never had, on either of those desks, was a mechanism in which the conditional postures themselves could be observed before the cascade. The continuous limit order book records the orders participants chose to place. It does not record the conditional postures from which those orders were drawn. The aggregate signal that something is structurally fragile — the kind of signal a population's collective preference function carries in its higher moments — is invisible to the venue, because the venue never asked for it.

It could have. It just had no way to receive the answer.

What the mechanism asks for

A Reactive Intent Market asks each participant for a function. Formally:

φ : S × T → M(P)

Enter fullscreen mode Exit fullscreen mode

— where S is the space of observable market states, T is a set of timeframes (the participant's short, medium, long horizon — kept abstract on purpose), and M(P) is the space of signed measures on the price axis, with bounded total variation.

The unfamiliar move is the signed measure. A working trader's intent is not "I want to buy here." It is "I want to be long in this band, indifferent in this band, opposite to a position in this band, and explicitly absent from this band." A positive measure captures only the first half of that sentence. A signed measure captures all of it.

This is the central modeling choice of the paper. The argument is that signed measures are not a mathematical curiosity but the right object once participants are no longer compressing their preferences to fit the venue's compressed submission format. The shape of μ(s,τ) = μ⁺(s,τ) − μ⁻(s,τ) — where the mass sits, how it is distributed, the relative weight of the tails — is itself information about the market.

The agent holds φ privately. To submit it, the agent produces a cryptographic commitment c = Commit(φ) using a functional commitment scheme (the literature offers several; the construction is an implementation choice). The properties required are standard: binding, hiding, and an efficient proof of evaluation. When the venue announces a clearing state s*, the agent reveals μᵢ = φᵢ(s*, τᵢ) together with a proof πᵢ that this evaluation is consistent with the committed φᵢ. Nothing else about φᵢ is revealed.

The venue aggregates the μᵢ. Positive parts form aggregate buy intent. Negative parts form aggregate sell intent. The clearing rule — a baseline is the uniform-price double auction — picks the price.

Why atomic settlement is load-bearing, not incidental

The standard story about atomic settlement in cryptocurrency venues is operational: settlement failure is expensive, atomic settlement reduces operational expense, therefore it is desirable. This is true and it understates what is happening.

A single-price RFQ is what you get when a participant who has, in effect, a φ in her head is asked by the venue to compress that φ down to a single price-quantity pair. Why does she do it? Partly because the venue's submission format requires it. But also — and this is the part the operational story misses — because if she submits a richer object to a counterparty who can default, she is teaching the counterparty about her preferences in exchange for a settlement guarantee the counterparty can simply not provide. The compression is defensive, not just operational.

Atomic settlement removes the second half of that sentence. When the cryptographic primitive guarantees that either both legs of the trade execute or neither does, with no possibility of either side defaulting after the price is agreed, the counterparty cannot use information about the participant's preferences against her in the moment between agreement and settlement. The window in which the disclosure is dangerous closes.

What follows is the Revelation Conjecture, the central claim of the paper: the equilibrium quantity of preference information that participants are willing to reveal is strictly greater under atomic settlement than under settlement structures where counterparty default is possible. As the strength of the settlement guarantee increases, the richness of the equilibrium submission increases with it.

This is a behavioural claim, not a theorem. The shape of the formal version exists. I am not the person who will write it down. It is within reach of a competent mechanism-design researcher in a way several of the other open problems are not.

Five conjectures

The paper makes five.

  1. Revelation. Atomic settlement enables strictly richer revelation than settlement structures where counterparty default is possible. (Central. If this fails, the rest of the construction loses its motivation.)

  2. Multi-Timeframe Coexistence. A market that lets participants submit policies indexed by multiple timeframes — without forcing them to be netted into a single submission — will produce price-discovery properties that dominate single-submission markets along at least one dimension. A working trader who genuinely holds different views at different horizons no longer has to choose which to surface.

  3. Reflexivity-as-Feature. A RIM does not merely tolerate reflexive feedback between price and policy; it stabilizes against certain pathological dynamics that conventional venues amplify. Specifically: cascading liquidation has a structural cause in conventional venues (stop-loss orders held off the book, conditional on triggers, materializing only in stress). A market in which stop-loss behaviour lives inside the policy function φ from the start makes the conditional sell pressure visible to the aggregation layer before the trigger fires. (The least certain of the five. The opportunity is real; whether the mechanism captures it depends on aggregation rules left open in the paper.)

  4. Higher-Moments Observability. The shape of aggregate intent — its skewness, its kurtosis, and the time evolution of those moments — carries information about market regime that conventional venues cannot recover. Regime transitions should leave signatures in the higher moments before they show up in the realized price.

  5. Aggregate-Privacy. The privacy structure under which individual policies are hidden and only the aggregate is observable is incentive-compatible with honest revelation. (The closest of the five to a standard mechanism-design claim; probably the most clearly tractable for formal analysis in the near term.)

None of these is proved. All are falsifiable. The paper sets out the structure within which they can be posed clearly; future work will say whether the structure holds.

What is honest about this

A working paper by a practitioner is not a theorem-proof contribution. The paper says so up front. The places where the argument needs sharpening are marked in the Open Problems section rather than papered over. Three families: the formal mechanism-design problems within reach (the Revelation game, the privacy incentive-compatibility analysis, the timeframe-aggregation specification); the engineering problems any specific implementation has to commit to (the class of admissible policy functions, the discretization of state and price, the handling of partial participation, cross-chain settlement timing); and the deeper questions (the equilibrium dynamics of a self-referential mechanism, the precise sense in which higher moments of intent carry regime signal).

What I claim the paper does is set up a structure within which these problems can be posed. Whether the structure is the right one is, in the end, an empirical matter.

What this isn't

It is not a Hashlock product announcement. Hashlock Markets is the settlement infrastructure I have spent six weeks writing about — sealed-bid RFQ + HTLC atomic settlement, five primitives shipped to mainnet under audit-hardening, V2 gated on external audit firm sign-off. The RIM paper is a level above that: a working paper about the submission format atomic settlement makes possible. If a deployed RIM ever runs, it would run on top of a settlement layer of the kind Hashlock builds. The paper is not the product.

It is also not a claim that the mechanism is novel in every part. It is not. Wilson, Klemperer, Hanson, Budish, Diamond–Mortensen–Pissarides, and Duffie–Garleanu–Pedersen all wrote pieces of the answer. What is new, to my knowledge, is putting them together this way — and what is newly possible is doing so under atomic settlement, which did not exist in usable form when most of that literature was written.

A futuristic vision, honestly framed

The futuristic part of the vision is the easiest part to write and the most dangerous part to over-claim. A market in which the participants are AI agents, the submissions are functions, and the settlement is atomic across chains — that is a different object from a 2010-vintage limit order book in the way a 1995-vintage browser is different from a 1985-vintage terminal. The infrastructure to build the new object has matured in the last twenty-four months. The mechanism design is still mostly future work.

The piece you are reading is a step in that direction, written by a practitioner with an AI as a thinking partner, posted as a working paper because the alternative was sitting on it.

If your desk had to submit a function instead of a quote, what shape would it have?

Reading the paper:

Pushback welcome — especially on the Revelation Conjecture, which is the load-bearing one.