PAX sells one thing for money: speed through the λ API, bought mainly by market makers. Those buyers measure latency for a living, and right now they find three different stories. The homepage says the on-chip round trip "takes about 40 ns, 500x faster than the 20 µs" of the fastest traditional venues. The Launch YC post, linked from PAX's YC profile, says "30 nanoseconds (1000x faster)" than a "30 microsecond" benchmark, and a product directory repeats the 1000x. The λ API blog post claims "the fastest tick-to-trade at any venue in any asset class" with no number. No page says what is timed, at which percentile, or on which build (the hiring posts say AWS F2 FPGA today, an ASIC later). To a quant team, a number that changes between pages and has no method reads as marketing, not engineering.
First action
Decide which number is current, 40 ns or 30 ns, and write down exactly what it measures.
How to measure it
λ sandbox trials sourced from /latency
- Now
- –
- Target
- 10 market-making firms
- By
- 90 days
Steps
Pick the definition
Name the start and end events of the round trip in plain words, with a diagram.
Co-Founder & CTO 1 day
Measure the current build
Median, p99, p99.9 and jitter on the AWS F2 FPGA build, with the date and version.
Founding Principal Hardware Engineer 3 days
Source the comparisons
Give each external figure (20 µs at traditional venues, 1-10 ms at crypto venues) a public, dated source.
Co-Founder & CEO 1 day
Publish /latency
The number, the method, a histogram, the sources and a changelog.
Founding Software Engineer 2 days
Align every claim
Homepage, Launch YC post, YC profile, λ blog post and directory listings all use the same number and link to /latency.
Co-Founder & CEO 2 days
Add "see it yourself"
Sandbox steps a quant can follow to observe the round trip.
Founding Software Engineer 3 days
Use it in sales
Put the link in the first line of every market-maker email and event follow-up.
Co-Founder & CEO ongoing
Why it works
Publish a /latency page on pax.markets with: one plain definition of the round trip (for example, market event reaching the matching engine to λ order resting in the book); the measured median, p99 and p99.9 on the current FPGA build, with the date and version; how it was measured; a dated, sourced comparison with external order entry at traditional and crypto venues; and a changelog for when the ASIC arrives. Then make the homepage, the Launch post, the YC profile and the λ blog post use the same number and link to the page. Finish with a "see it yourself" section that walks a quant through the self-serve sandbox.
Market makers choose venues on measured latency and on determinism. A number with a method and a way to test it cuts the diligence time on the one sale that earns PAX revenue. One canonical page also stops directories and AI summaries from copying the old 1000x figure.
Ready to use
ChecklistWhat the /latency page must contain
[ ] One-sentence definition of the round trip (start event, end event) [ ] Median, p99, p99.9 and jitter, with build, version and date [ ] Measurement setup (clock source, where timestamps are taken) [ ] Comparison table: λ on-chip vs external order entry, each source dated [ ] Same number on homepage, Launch YC post, YC profile, λ blog post [ ] "See it yourself" sandbox walkthrough [ ] Changelog (FPGA today, ASIC later)
Risks and how to handle them
A new build measures slower
Version every number and keep the history on the page; a transparent changelog builds more trust than a fixed claim.
Rivals pick the method apart
Invite review and follow with the independent audit (idea 20).
Evidence
- Your websiteHomepage: H1 "Trade In Nanoseconds"; "That round trip takes about 20 µs at the fastest traditional venues and 1 to 10 ms at crypto venues"; "On the chip, the same round trip takes about 40 ns, 500x faster than the 20 µs"; fee example "Typical exchange fee −10 bps", "PAX rebate +0.25 bps", "You keep 10.25 bps"; buttons "Sign up" and "Preview markets"; revenue comes from selling λ API access, mainly to market makers; the footer links Team, Blog, Events, Careers, Contact, Docs and Status but no social profiles, and the page does not say where the service is available.Source
- Launch postLaunch YC post (listed as over a year old): "The fastest exchanges today boast a 30 microsecond round-trip latency. PAX crunches that to 30 nanoseconds (1000x faster)"; it claims PAX is faster than NYSE, NASDAQ, Deutsche Börse, EDX, Crossover, Binance and OKX, and describes the model as selling speed and buying order flow.Source
- Directory listingsYC company profile: "Co-located trading facility and matching engine on one chip", describing deterministic nanosecond tick-to-trade latency; W25, founded 2024, team of 6; it links a LinkedIn company page and no X account. A third-party product directory repeats that PAX "reduces exchange response latency by 1000x".Source
- Your websiteBlog: four posts, from "In Crypto, Fees are High and Speeds are Slow" (November 6, 2024) to the PFOF post (February 2025), none since. The λ API post claims "the fastest tick-to-trade at any venue in any asset class" with no measurement.Source
- HiringThree open founding roles on the YC job board, all in Redwood City with visa sponsorship: Founding Principal Hardware Engineer ($200K–$225K, 0.50%–1.00%), Founding Software Engineer and Founding Hardware Engineer ($150K–$200K, new grads welcome). The work: an ultra-low-latency matching engine built as a hardware/software co-design (Rust, SystemVerilog); launch on AWS F2 FPGA instances, then an ASIC combining network aggregation with exchange functions; crypto first with spot and perpetual futures for BTC and ETH, then a U.S. equities ATS, then other asset classes and markets.Source