We mostly develop according to user requests and needs, as of today not a single user has approached us that they are missing Resident Key Slots - in fact I would struggle to name 10 different services that support Resident Key based logins - but anyways we are currently working on extending this number, to be precise the amount will be dynamic in the future to make the best use of the available space. For the announced algorithms, please feel free to name the one you are missing, we just released a test firmware with support for many more algorithms from brainpool to p512. And the number of bugs in github is usually a good sign, please feel free to point out which one you see as the most critical - then we'll do our best to resolve it - we by ourselves are not aware of any which do really block or reduce security for some use-case. Furthermore CTAP2.2 was actually already implemented by us? Which specific use-case are you referring to, why do you need CTAP2.2, please approach us, because as of today it looks like Nitrokey has the only open-source CTAP2.2 implementation available as of today. But it's not yet included into the firmware as a) the specification hasn't been finalized yet, b) we see nearly no realistic use-cases which require 2.2 as of today.