This hash-bucket-based sharding would be what I'd call `"Sharding at the Protocol Level"`. If Relays were sharding in this way then client apps would have an even higher probability (or expectation) that the MMBQ algo described in this doc will indeed perform well at the goal of retrieving from multiple relays simultaneously with a guarantee of no duplicate Event data being sent back from any of the relays in the pool.

The only challenge is that the clients need to know which relays are in a Sharded Set, so that they get records that are `"Shard Complete"`, or in other words if you query from a sharded relay you need to know that and query from all relays in the "Sharded Set"