ChainboxThere is a number most trading platforms will not tell you: how long it actually takes to get filled. Not how long the animation runs. How long it takes from the moment you press Buy to the moment the position is really yours.
We know ours, to the millisecond, because we measured every stage of it. Today we are announcing a partnership with Amazon Web Services to attack the part of that number we control.
What actually happens when you press Buy
A perp order on Chainbox is not one event. It is a relay race, and each leg has its own clock.
First the order is built. Then it is turned into a transaction your wallet can sign, which on a gasless venue means negotiating with a sponsor and a bundler. Then it is signed. Then it is broadcast. Then the chain registers it. Then an oracle prices it. Then a keeper fills it.
Seven legs. Some of them are ours. Some of them belong to the market itself. Knowing exactly which is which is the whole job, because you cannot engineer away physics and you should not tolerate anything else.
The half we do not get to argue with
Arbitrum produces a block roughly every 0.253 seconds. That is not a vendor estimate, it is what we measured across a million consecutive blocks.
On High Leverage, opening a position is deliberately two transactions rather than one. The first registers your order. A separate keeper fills it once the oracle has priced it. We measured that callback across three thousand executed mainnet opens: about one second at the median, about one and a half at the ninetieth percentile. Stocks and ETFs settle roughly a block slower than crypto, which is exactly what you would expect from the way their feeds update.
That is market structure, not a defect. Any venue settling on the same rails pays the same toll, whether or not they publish it. We would rather publish it.
The half we do control
The other half is ours, and until now it has been running out of a single modest server in one European city.
Measured across eighty eight client traces, the submit path sits near 1.9 seconds at the median. Building the transaction costs about 370 milliseconds, most of it a round trip to our origin. Preparing the sponsored user operation costs about 530 milliseconds, because it makes three sequential hops to a sponsor and a bundler plus a nonce lookup. Signing costs about 600 milliseconds. The actual broadcast costs 163.
Look at that list again. Not one line on it is a law of nature. Sequential hops can be made concurrent. A nonce can be held warm instead of fetched. A round trip to a box in Paris is a round trip we chose, and one that every user outside Europe pays for twice.
That is the number this partnership exists to cut.
Why AWS
Because the controllable half of a latency budget is mostly a geography problem and a capacity problem, and those are the two things hyperscale infrastructure is genuinely good at.
Moving our hosting and compute onto AWS puts the order path close to the venues and the data instead of a single fixed point on a map. It gives us room to run the pieces that should never have been sharing a machine: the order path, the market data pipeline, the pricing workers, the feeds. It replaces a server we have to nurse with infrastructure that scales when a market decides tonight is the night.
It also gives us the data layer the rest of the product needs. Real time market data across perps, the options data that powers our intelligence tooling, and the time series behind every chart and every position have very different shapes and very different appetites. Running all of them properly is an infrastructure commitment, not a side effect.
What it unlocks
Chainbox is built to be one account for markets that were never meant to live together. Stock, crypto, index and meme perps. High leverage and low leverage, side by side. Predictions. The data and intelligence layer that sits over all of it.
Every one of those is another demand on the same backbone, and each new venue makes the latency budget harder rather than easier. Building the financial superapp we have been describing means the plumbing has to be finished first, quietly, before anyone notices it was ever a constraint.
This is that work.
Trade without limits
The best infrastructure is invisible. You will not see an announcement banner when a hop goes from sequential to concurrent, or when your order stops crossing a continent before it reaches a bundler. You will notice that the fill lands sooner, and that it keeps landing sooner when everyone else shows up at once.
We will keep measuring it, and we will keep publishing what we find.