Sharded transactions with snapshot read concern use a historical routing table to target requests to shards that owned chunks at the chosen global read timestamp. If a write is targeted to a shard that used to own a chunk, but no longer does, the write should fail even if there are no write conflicts.