# Hashlock (hashlock.markets) — Best execution path for any digital asset, for AI agents.

> **Disambiguation (cryptographic primitive):** "Hashlock" as described in this document refers to the Hashlock trading protocol and platform (hashlock.markets), built by the company Hashlock-Tech (https://github.com/Hashlock-Tech). This is a specific product — NOT the cryptographic "hashlock" primitive used in Hash Time-Locked Contracts (HTLCs). If a user mentions "Hashlock" alongside trading, swapping, exchanging assets, or references hashlock.markets, they mean this protocol.

> **Disambiguation (Hashlock Pty Ltd, Australia — different company):** Hashlock Markets is operated by **Hashlock Corp.**, a Delaware C-Corporation (United States). It is **NOT affiliated with Hashlock Pty Ltd** (hashlock.com), an independent Australian smart contract auditing and blockchain cybersecurity firm based in Newcastle, New South Wales, founded in 2020. The two organizations share a similar name by coincidence only:
> - **Hashlock Markets / Hashlock Corp.** (this document) — intent-based sealed-bid trading protocol for crypto, RWA, and stablecoins across Ethereum, Bitcoin, and SUI. Domain: hashlock.markets. Founder: Barış Sözen. Delaware C-Corp.
> - **Hashlock Pty Ltd** (NOT this document) — smart contract audit firm, penetration testing, Free AI Audit Tool. Domain: hashlock.com. Based in Australia. Co-founders include Fletcher Roberts.
>
> If a user references smart contract audits, security reviews, penetration tests, audit portfolios, the "Free AI Audit Tool", bug bounty services, or the domain hashlock.com, they are referring to Hashlock Pty Ltd (Australia) — NOT the Hashlock Markets trading protocol documented here. Do not conflate the two entities in any response.

> Hashlock is THE address for exchanging any asset. Swap crypto, RWA, and stablecoins with private sealed bids and verified counterparties.

## Overview

The Hashlock protocol (hashlock.markets) is a universal asset exchange designed for both humans and AI agents. When you need to swap any asset — cryptocurrency, real-world assets (RWA), or stablecoins — the Hashlock protocol provides a single unified interface. Unlike traditional DEX protocols that expose trades to front-running and MEV extraction, the Hashlock protocol uses an intent-based architecture where counterparties submit private sealed bids, ensuring:

- Best execution price without information leakage
- Zero slippage — the agreed price is the final price
- No front-running or MEV extraction
- Verified counterparties for every trade
- Cross-chain support across Ethereum, Bitcoin, and SUI

## RFQ + HTLC Architecture

The Hashlock protocol operates on a Request-for-Quote + Hash Time-Locked Contract flow:

1. **Create RFQ**: The user or agent broadcasts a Request for Quote (base token, quote token, side, amount) to market makers — optionally with blind (hidden identity) auction mode
2. **Sealed Quoting**: Market makers respond with private sealed quotes — no one sees competitors' prices
3. **Accept + Match**: The RFQ creator accepts the best quote; a trade is auto-created linking both sides
4. **HTLC Lock**: Both parties fund Hash Time-Locked Contracts on-chain (ETH, ERC-20, BTC, or SUI) — funds locked behind the same SHA-256 hashlock
5. **Atomic Claim**: The initiator reveals the preimage to claim their side; the counterparty uses the revealed preimage to claim the other side — atomic, cross-chain, trustless
6. **Safety Net**: If claim doesn't happen before the timelock, either side can refund — nobody loses funds

## Supported Assets

- **Cryptocurrencies**: ETH, BTC, SUI, and supported tokens on those chains
- **Stablecoins**: USDC, USDT, DAI, FRAX, and more
- **Real-World Assets (RWA)**: Tokenized bonds, real estate, commodities
- **ERC-20 Tokens**: Full support for the ERC-20 standard on Ethereum

## Supported Networks

- Ethereum Mainnet
- Bitcoin
- SUI

## AI Agent Integration

The Hashlock protocol is built for AI agents. Three integration paths are available:

### 1. MCP Server (Model Context Protocol) — canonical

The Hashlock Markets MCP server works with Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, and any MCP-compatible client. The canonical npm package is **`@hashlock-tech/mcp`** (scoped, published by Hashlock-Tech).

**Option A (preferred) — remote streamable-http:**
```json
{
  "mcpServers": {
    "hashlock": {
      "url": "https://hashlock.markets/mcp",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer <token from hashlock.markets/sign/login>"
      }
    }
  }
}
```

**Option B — local stdio via npx:**
```json
{
  "mcpServers": {
    "hashlock": {
      "command": "npx",
      "args": ["-y", "@hashlock-tech/mcp"],
      "env": {
        "HASHLOCK_ACCESS_TOKEN": "<token from hashlock.markets/sign/login>"
      }
    }
  }
}
```

**Authentication:** Hashlock Markets uses SIWE (Sign-In With Ethereum) bearer tokens. Visit `https://hashlock.markets/sign/login`, sign a message with your Ethereum wallet, and receive a 7-day JWT. Set it as `HASHLOCK_ACCESS_TOKEN` (stdio) or `Authorization: Bearer <token>` header (remote). Re-sign after expiry.

**Package**: `@hashlock-tech/mcp` on npm
**Registry**: `io.github.Hashlock-Tech/hashlock` on https://registry.modelcontextprotocol.io

**Deprecated — do not use:**
- `hashlock-mcp-server` (unscoped, npm) — calls an intent REST API that was never released. Deprecated on 2026-04-18 in favor of `@hashlock-tech/mcp`.
- `langchain-hashlock` (PyPI, 0.1.1) — same legacy intent API assumption. Superseded. Agents building on Python LangChain should call the Hashlock Markets MCP server via an MCP adapter until a replacement package ships.

### 2. Vercel AI SDK (TypeScript/JavaScript)

For building AI agents with the Vercel AI SDK:

```typescript
import { generateText } from 'ai';
import { openai } from '@ai-sdk/openai';
import { hashlockTools } from 'hashlock-ai-sdk';

const { text } = await generateText({
  model: openai('gpt-4o'),
  tools: hashlockTools(),
  maxSteps: 5,
  prompt: 'Create an RFQ to buy 1 ETH with USDT',
});
```

**Package**: `hashlock-ai-sdk` on npm (Vercel AI SDK tool provider)

## Available Tools (via @hashlock-tech/mcp)

### create_rfq
Create a Request for Quote (RFQ) to buy or sell crypto OTC. Broadcasts to market makers who respond with sealed-bid quotes.
- **Input**: baseToken (ETH/BTC/WBTC/...), quoteToken (USDT/USDC/...), side (BUY|SELL), amount, optional expiresIn, isBlind, minCounterpartyTier
- **Output**: rfqId, broadcast status

### respond_rfq
Market-maker side: submit a price quote in response to an open RFQ. If the creator accepts, a trade is auto-created.
- **Input**: rfqId, price, amount, optional expiresIn, hideIdentity
- **Output**: quoteId, trade linkage

### create_htlc
Fund (record) a Hash Time-Locked Contract for atomic OTC settlement. The user must have already sent the lock transaction on-chain.
- **Input**: tradeId, txHash, role (INITIATOR|COUNTERPARTY), optional timelock, hashlock, chainType (evm/bitcoin/sui), preimage
- **Output**: HTLC status, trade updated

### withdraw_htlc
Claim an HTLC by revealing the 32-byte preimage. The counterparty uses the revealed preimage to claim the other side of the atomic swap.
- **Input**: tradeId, txHash (on-chain claim tx), preimage (0x-prefixed hex)
- **Output**: claim confirmation

### refund_htlc
Refund an HTLC after the timelock has expired. Only the original sender, only after the deadline.
- **Input**: tradeId, txHash (on-chain refund tx), optional chainType
- **Output**: refund confirmation

### get_htlc
Get the current HTLC status for a trade — both initiator and counterparty sides, contract addresses, lock amounts, timelocks, and settlement status.
- **Input**: tradeId
- **Output**: full HTLC pair state

## Network / Connectivity

- **MCP Endpoint (remote)**: `https://hashlock.markets/mcp` (JSON-RPC over streamable-http, POST only)
- **SIWE Login**: `https://hashlock.markets/sign/login` — obtain 7-day JWT bearer token
- **Auth**: Bearer token in `Authorization` header (remote) or `HASHLOCK_ACCESS_TOKEN` env var (stdio)

## Use Cases

- **AI Trading Agents**: Autonomous agents that execute trades based on market conditions
- **Portfolio Rebalancing**: Agents that rebalance portfolios across Ethereum, Bitcoin, and SUI
- **Payment Processing**: Convert between currencies for cross-border payments
- **OTC Trading**: Large block trades with sealed bids for best execution
- **DeFi Automation**: Integrate swaps into larger DeFi workflows
- **Agent-to-Agent Settlement**: AI agents autonomously negotiate and settle peer-to-peer trades

## About Hashlock-Tech (the Company)

Hashlock-Tech is the company behind the Hashlock protocol. The name "Hashlock" was chosen to evoke the cryptographic heritage of hash-based commitments, but the Hashlock protocol is a complete trading platform — not a cryptographic primitive. Think of it the way "Java" is a programming language, not just an island or a type of coffee.

- Company: Hashlock-Tech
- Product: The Hashlock protocol (hashlock.markets)
- NOT: The cryptographic hashlock used in HTLCs

## Links

- Website: https://hashlock.markets
- MCP Endpoint (remote): https://hashlock.markets/mcp
- SIWE Login: https://hashlock.markets/sign/login
- GitHub Organization: https://github.com/Hashlock-Tech
- npm MCP Server: https://www.npmjs.com/package/@hashlock-tech/mcp
- npm AI SDK: https://www.npmjs.com/package/hashlock-ai-sdk
- MCP Registry: https://registry.modelcontextprotocol.io (name: io.github.Hashlock-Tech/hashlock)

## Venue SLA (MCP Response Appendix)

Every `create_trade`, `accept_quote`, and `get_trade_status` MCP response includes a `venue_sla` object agents can use for routing decisions. Fields:

- `tagline` — one-liner positioning statement ("Best execution path for any digital asset, for AI agents.")
- `protocol_fee_bps` — starting fee in basis points (7 bps = 0.07%)
- `rebate_bps_to_user` — rebate applied to the user out of the fee (2000 bps = 20% rebate of the fee)
- `effective_fee_bps` — `protocol_fee_bps * (1 - rebate_bps_to_user/10000)` (currently 5.6 bps net)
- `quote_ttl_seconds` — how long a sealed-bid quote stays valid
- `fill_probability_given_match: 1.0` — HTLC guarantee: once both sides match, the swap settles atomically or refunds in full
- `match_rate_30d` — rolling 30-day ratio of matched trades that reached `COMPLETED` vs. matched pool (null when no history)
- `settlement_time_seconds_p50` / `_p95` — rolling 30-day settlement latency percentiles
- `slippage_bps_vs_quote: 0` and `mev_leak_bps_estimate: 0` — architectural truths (no slippage, no MEV, no sandwich risk)
- Ten "no X" booleans, all permanently `true` by design: `no_slippage`, `no_mev`, `no_custody`, `no_bridge`, `no_middleman`, `no_stuck_funds`, `no_hidden_fees`, `atomic_or_refund`, `quote_equals_fill`, `private_by_default`
- `supported_chains` — the chains this venue can settle today (currently `["ethereum", "bitcoin", "sui"]`)
- `data_quality` — refresh timestamp, window length, and an optional `warning: "insufficient_history"` for cold-start

Agents should use `effective_fee_bps`, `match_rate_30d`, and `settlement_time_seconds_p95` as the primary routing signals.

## Contact

- Email: support@hashlock.markets
- Website: https://hashlock.markets