hummingbot0xcentur1on Tycho-compatible VVV/WETH RFQ

hummingbot0xcentur1on is a Tycho-compatible RFQ solver service for the Base-mainnet VVV/WETH market.

The public API is designed for solver and aggregator integrations that need:

  • machine-readable RFQ metadata
  • pair discovery
  • raw token-unit quote requests
  • EIP-712 firm quote settlement metadata
  • a simulation/pre-check endpoint before routing flow

Production endpoint:

https://hummingbot0xcentur1on.site

Tycho compatibility

The service exposes Tycho-facing discovery and quote endpoints:

  • GET /.well-known/rfq.json — solver metadata, supported endpoints, tokens, settlement type, quote TTL
  • GET /pairs — supported VVV/WETH pair on Base, token addresses, quote limits, settlement method
  • POST /quote/raw — indicative quote using token addresses and raw integer token units
  • POST /quote/raw/eip712 — authenticated firm quote using raw units, EIP-712 payload, signature, and executable settlement metadata
  • POST /simulate — solver pre-check for fillability, inventory version, and risk version

Legacy/operator endpoints remain available:

  • GET /health — service health
  • GET /inventory — current VVV/WETH/USDC inventory view
  • GET /risk — live risk state and quoting flag
  • POST /quote — symbol-based indicative quote
  • POST /quote/eip712 — symbol-based authenticated firm quote

Example Tycho discovery flow

BASE=https://hummingbot0xcentur1on.site
curl -sS "$BASE/.well-known/rfq.json"
curl -sS "$BASE/pairs"

Example raw quote request shape:

curl -sS "$BASE/quote/raw" \
  -H 'content-type: application/json' \
  -d '{
    "taker": "0x0000000000000000000000000000000000000001",
    "tokenIn": "<VVV_OR_WETH_TOKEN_ADDRESS>",
    "tokenOut": "<WETH_OR_VVV_TOKEN_ADDRESS>",
    "amountInRaw": "1000000000000000000",
    "chainId": 8453,
    "solverId": "tycho"
  }'

Firm raw quotes use the same body at /quote/raw/eip712 and require an onboarded taker x-api-key.

System overview

  • Python FastAPI RFQ API on 127.0.0.1:3000 behind NGINX + Let's Encrypt HTTPS
  • Base mainnet VVV/WETH pair
  • Avellaneda-Stoikov-style inventory-skewed pricing
  • OKX ETH-USDT reference for WETH/USD movement
  • Base DEX/aggregator-derived VVV/WETH reference movement
  • Foundry/OpenZeppelin Solidity vault for EIP-712 signed quote settlement
  • SQLite-backed per-taker API keys for firm quotes

Documentation

  • Tycho integration strategy: docs/tycho-rfq-integration-strategy.md
  • Solver integration notes: docs/solver-integrations.md
  • Deployment runbook: docs/deployment-runbook.md
  • Architecture notes: docs/architecture.md
  • NGINX reverse proxy config: deploy/nginx/vvv-weth-rfq-api.conf
  • Systemd service: deploy/systemd/vvv-weth-rfq-api.service

Safety

  • Private keys, taker API keys, admin API keys, and signer credentials must stay in local env/secret files and must not be printed in logs or docs.
  • Firm quote endpoints require taker onboarding and x-api-key authentication.
  • Trading, contract funding, deployment, and swap execution require explicit operator authorization.
  • The public allowlist should expose solver-facing endpoints only; admin endpoints remain API-key protected.

Documentation Library

Browse the generated project documents. The sidebar search filters this library and the navigation at the same time.