There is an open question about whether LSM trees will need to take timestamps into account when switching chunks. It's likely that there isn't anything to do here, but we should come to a definite conclusion.

The corollary is what LSM does with transaction IDs when switching chunks. It currently switches in a new chunk, but writes updates for old transaction IDs into any previous chunk with an overlapping snapshot ID, so we can reliably detect conflicts.