The Idea of how they handle counters is intresting so let's see.
https://developers.yubico.com/OTP/Speci ... tocol.htmlaccording to spec we have 2 counters.
a session counter (I call it SC for now) which goes up each time you plug this thing in and use it for the first time.
and a session use counter (UC) which goes up each touch but resets when the key loses power.
now we have 8 bit (1 byte) for UC meaning 256 uses on each power cycle maximum until the key either has a problem or just ups the session counter.
problem is we have 16 bit (2 byte) for SC, which means we have just 65536 sessions at maximum until we have a problem.
now if you use the yubikey 8 times a day for yubi-OTP and pull it out each time, we have about 22 and half a year to spend. now if you would do that a hundred times each day (each quarter of an hour) it's over in 1 year and 9 and a half months, although that is far from realistic.
if you happen to use it a thousand times on a day on the same device, you are gonna need 4 sessions (almost 45 years of life) so that's gonna last a while, although I think just using one 4 or even 3 byte (16 million) counter would have been nicer instead of this session/use counter system, as this is dropping a lot of numbers. with 3 bytes as counter and not dropping any numbers for the 1000 tries per day you have almost 46 years.