Triton One sets out its own neutrality rules
On 3 November Triton One proposed three conditions for RPC providers and committed itself to them. No trading on order flow, no information advantage, and explicit consent.
On 3 November 2026 Triton One proposed three conditions for RPC providers and committed itself to them. The blog page is marked updated on 3 November 2026. It is part 1 of a series. On X, Triton wrote that the provider sees the transaction before the network does, and that Triton had written rules for that window.
The first condition rules out trading on customer order flow. Unconfirmed transactions are not a trading signal. An affiliated trading desk should not see them before they reach the leader.
The second condition rules out an information advantage before the leader’s scheduler commits. What the provider acts on after that point, others should be able to obtain on published terms.
The third condition requires explicit consent that can be revoked, as an opt-in in plain language. For Triton, a clause in the terms of service does not count as consent.
Triton writes that it does not trade on information from before the scheduler commit. Before any new use of private order flow, Triton says it will explain the use in plain language. It will include transactions only after an explicit opt-in.
According to the blog, Yellowstone Jet and Shield are open source. Jet sends transactions directly to leader TPUs. The blog names Jet’s license as Apache 2.0. Shield decides which validators may receive the transactions.
The page announces parts 2 to 4. Links are to follow once those parts are published.
What to watch
- Whether parts 2 to 4 appear on the page with links.
Sources
- Triton One — Blog, “Neutral Infrastructure Series, Part 1”, updated 3 November 2026
- Triton One — Post, 3 November 2026, 17:58 CET