Skip to main contentSkip to FAQSkip to contact
Reference· 1 minUpdated 4d ago

FAQ#

Every Q&A pair authored across the corpus - in page frontmatter and inline <Faq> components - is collected here and indexed for Google's rich-snippet FAQPage schema. Filter by persona or search the full text to find the answer fastest.

15 of 15 questions

Architecture

  • Does the Travel Rule apply to every trade?+

    It applies to transfers that cross a jurisdictional threshold (EUR 1,000 in EU under MiCA, USD 3,000 in the US). TetraFi enforces Travel Rule data exchange automatically when both legs' jurisdictions require it; the WORM ledger preserves the exchange for audit.

  • How long is a compliance attestation valid?+

    Attestations carry an explicit expiry timestamp written on-chain at issuance. Default is 12 months for individuals, 6 months for institutions; jurisdiction-specific policies can shorten this. Expired attestations block new trades until re-attested.

  • Who stores the KYC documents themselves?+

    The KYC/KYB vendor adapter does. TetraFi's ComplianceRegistry only stores an on-chain attestation hash signed by the vendor - never raw identity documents. The vendor remains the data controller under GDPR/MiCA.

Integration

  • Can I quote on every corridor by default?+

    Yes within your risk-approved pairs, but only if your KYB attestation covers them. Some corridors are restricted to specific solvers by policy (institutional-grade counterparties only) - the API returns corridor_unavailable when a quote targets a restricted corridor you aren't cleared for.

  • Do API keys rotate automatically?+

    No. Rotate manually from the dashboard when a key is suspected compromised. Keys don't expire - you can run a key indefinitely, but regular rotation is strongly recommended for production.

  • Do I need to sign every quote, or just the accepted one?+

    Only the accepted one. The RFQ and quote round-trips are unsigned - they're just price discovery. The EIP-712 signature binds the taker to the specific winning StandardOrder.

  • Do solvers post collateral before filling?+

    Not on the auction side - the escrow sits on the taker's input deposit. Solvers bear only the capital cost of the fill itself (destination-chain outputs). If the fill fails the taker is refunded without solver involvement.

  • How are solver fills proven cross-chain?+

    An oracle adapter (Hyperlane, Wormhole, Polymer, or LayerZero depending on the corridor) attests the destination-chain fill back to the origin. The input escrow releases only on that attestation - which is the atomic DvP guarantee from the solver's side.

  • How do I tell a sandbox key from a production key?+

    Prefixes. Sandbox keys start with tfk_test_ and production with tfk_live_. The API rejects cross-environment calls with an invalid_key error, so accidentally using the wrong one is caught loudly rather than silently.

  • How long does a quote stay valid?+

    Quotes carry an explicit validUntil timestamp (~30 seconds by default). After that the solver is no longer bound and acceptance returns quote_expired. Accept aggressively - don't round-trip to a human approver.

  • What are the default rate limits?+

    Standard tier is 100 req/s per API key with a 1,000 burst. Enterprise tiers negotiate higher ceilings. 429 responses always carry a Retry-After header - honor it with exponential backoff.

  • What happens if no solver responds to my RFQ?+

    The RFQ window closes after the auctionDeadline (default 2 seconds) and returns an empty quotes array. This usually means the corridor is under-served or the size is outside the active solvers' risk appetite. Retry with a smaller clip or different corridor.

Overview

  • What's the difference between an intent and a route?+

    An intent declares what the taker wants (inputs on origin, desired outputs on destination). A route is one specific path a solver uses to satisfy that intent. Takers never specify routes - they compete.

    Core Concepts
  • Who holds funds during settlement?+

    Smart-contract escrow does. TetraFi never takes custody. The input escrow on the origin chain only releases to the solver once the destination-chain fill is oracle-attested - that's the DvP guarantee.

    Core Concepts
  • Why does TetraFi use sealed RFQ auctions instead of open orderbooks?+

    Sealed bids prevent front-running and latency arbitrage. Solvers quote on the intent without seeing competitors' prices, so the best price wins on merit rather than speed.

    Core Concepts

Don't see your question?#

  • Open an issue with the "question" label - maintainers harvest these into authoritative answers here.
  • Ping #docs-questions on Telegram for same-day responses from the TetraFi team.
  • Check the Glossary for terminology; many first-time questions are definitions.