You more or less described IPFS. Of course, IPFS grinds my gears because despite oodles of money and time, they still don't have a cohesive ecosystem SDK, haven't rebased on a Rust base, just squandering attention in the space, imo.
I don't see why they'd need to rebuild IPFS in Rust. Go is plenty fast. The problem is that the current IPFS network and design just don't scale very well.
Take a look at Matrix and what the ecosystem is doing. The entire ecosystem is rebasing on the Rust SDK and bindings to it. It's a massive reduction in duplication of effort, and means there's fewer bugs with interoping clients because they're increasingly all using the same SDK.
It's considerably more flexible, more easily embedded than node or Go.
And yet, it's not the first or last project to choose to build a base SDK in Rust and provide bindings on top. And an effort being taken by a company quickly trying to iterate, build a polished product, and bring revenue in on the edges.
And you can already look at various projects and see the positive impacts.
I'd elaborate on why, but we've all heard it a thousand times and the folks that don't want to believe anything they hear about Rust still won't hear it.
