2QUIC

Search docs

Find a documentation page

Traders: overview

How traders use the marketplace to obtain a leased staked-QUIC connection slot.

What a lease buys you

Booking a lease grants exclusive, time-bounded use of one validator's QUIC handshake signing capacity. During the lease window, your client SDK can complete the TLS handshake with Solana leaders as if it were the validator, which (combined with the validator's stake) earns SWQoS priority.

A lease is per-validator and time-bounded. The exclusion constraint is enforced in Postgres: two traders cannot hold an overlapping lease on the same validator. Booking is idempotent: clients pass an Idempotency-Key (ULID) and may safely retry.

End-to-end flow

  1. List validators (GET /v1/validators) and pick one based on stake, uptime, and effectiveness.
  2. Book a lease (POST /v1/leases) with the slot window you want. The response carries Solana Pay instructions: a transaction-request solana_pay_url, the exact amount, and a unique memo.
  3. Open the solana: link (scan the QR with a mobile wallet or follow the deep link). Your wallet fetches the exact transaction the marketplace built and you sign it. That one transaction atomically pays the validator's payout wallet its share and the platform its fee, carrying the memo. No third-party checkout.
  4. The settlement worker observes the transaction on-chain, validates both legs credited their share, and flips the lease to active (typically seconds after finality).
  5. Issue a JWT against the active lease and start routing transactions through the staked-QUIC path with the SDK.

The next page walks through the integration with concrete code in Rust, TypeScript, and Python.