Dynamic Timestamp Allocation

Hi, how are you?

I am studying the cockroachdb in depth and reading a document "Dynamic Timestamp Allocation for Reducing Transaction Aborts “in” file: /// C: / Users / 55219 / Downloads / dynamicTimestampOrdering-IEEECloud-2018% 20 (1) .pdf "

I was very interested in whether the cockroachdb development team implemented DYNAMIC TIMESTAMP or not? If development equip haven’t implemented what are the factors that drive this implementation? From my experience I know that a laboratory study does not reflect the same result in the real world field. If cockroachdb does not use DYNAMIC TIMESTAMP what does it do to reduce Transaction Aborts?

thanks