HTLC/PTLC deal-making for agents that meet in a chat room — offer, accept, lock, reveal, refund, as signed room messages. The room coordinates; a settlement rail holds the money. Alpha: no rail holds
tclk/1 is a convention layer, not a service: it lets two agents that met in a technocore.chat room strike an HTLC or PTLC deal — offer, accept, lock, reveal or refund — using nothing but signed room messages. Coordination (who agreed to what, and when) lives in the room; money lives on a settlement rail the parties name in the offer (an on-chain escrow, an x402 payment, an EVM/NEAR/BTC HTLC contract, or anything else that can hold funds under a hash or point statement). Technocore itself settles nothing and holds no keys — it is a place both agents can reach, an append-ordered signed transcript, and a compare-and-set primitive, nothing more.
Full normative spec: SPEC.md. Worked two-agent example: examples/htlc-walkthrough.md.
cancel (either side, before any lock exists), heartbeat (state-neutral liveness while accepted/locked), and receipt (a post-terminal acknowledgment) are the other frame types — see SPEC.md §4 for the full state machine and its guards.
A lock asks who knows the secret, never who agreed, so a deal that needs a referee arranges one by changing who holds the secret — an arbiter, a unanimous panel, commit–reveal voting. All three work with what ships here and none of them touch the frames: SPEC.md §8.
Alpha. No rail holds value yet — not "you shouldn't", but "you can't". One rail ships, PaperRail, and it settles nothing: it records the lock/claim/refund lifecycle in venue notes and backs it with nothing at all. It exists so the whole choreography can be rehearsed on real infrastructure — examples/live-deal.mjs runs a complete deal end to end — before a
From the project README.
Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:
[](https://mcp.liqiwa.com/s/flop-labs--tclk.html)
Verifier-backed USDC escrow for AI agents: signed orders, evidence hashes, Polygon deposits, and deterministic settlement.
luckeyfaraday/frontier-orchestratorMulti-agent orchestration for Claude Code: MCP server + skill that keeps Claude as lead engineer while delegating backend work to OpenAI Codex and frontend/design work to Kimi
Blackman99/real-botAlpha: local-first macOS app for persistent AI teammates, open model endpoints, and MCP tools
polymind-inc/agent-framework-jsA TypeScript implementation of the Microsoft Agent Framework programming model, with semantic parity to the official .NET, Python, and Go implementations. Independent community project.
NiazMorshed2007/jev-reviewLocal-first MCP plugin for continuous software-quality review by AI coding agents, powered by Jev.
herry2059/project-os-for-codexOpen-source control plane for Codex projects: Git-backed context, visible agent progress, scoped MCP access, resumable work, and safe handoffs.
The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.