# FlowProxy: Approaching Optimality

**URL:** https://collective.flashbots.net/t/flowproxy-approaching-optimality/5459
**Category:** BuilderNet
**Tags:** article, links
**Created:** [January 5, 2026, 11:43am UTC](https://collective.flashbots.net/t/flowproxy-approaching-optimality/5459 "2026-01-05T11:43:47Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![mempirate](https://collective.flashbots.net/user_avatar/collective.flashbots.net/mempirate/32/3529_2.png) [@mempirate](https://collective.flashbots.net/u/mempirate)
#### Post date: [January 5, 2026, 11:43am UTC](https://collective.flashbots.net/t/flowproxy-approaching-optimality/5459/1 "2026-01-05T11:43:47Z")

</div>

In [**Introducing FlowProxy**](https://collective.flashbots.net/t/introducing-flowproxy/5341), [Chainbound](https://chainbound.io/) collaborated with Flashbots to deprecate its [original orderflow proxy](https://github.com/flashbots/buildernet-orderflow-proxy) implementation in Go in favor of a new one built in Rust, created with the goal of reducing end-to-end latency, improving efficiency, and increasing observability in [BuilderNet](https://buildernet.org/)’s networking layer. This first collaboration aimed at bringing it to production-ready quality and ready for deployment, already observing good improvements in networking and processing latency.

This second collaboration expanded on the _Next Steps_ section outlined in the previous report, with success. It includes a quantitative analysis of order losses and latencies across BuilderNet, and extensive work to improve the transport layer to reduce both CPU and memory usage. We encountered a couple of non-obvious learnings that we outline below, and we hope this will be useful to the community.

Since the article contains interactive graphs, I’ll link to it here: [FlowProxy: Approaching Optimality | Chainbound Blog](https://engineering.chainbound.io/flowproxy-approaching-optimality)