Which remains a single point of failure, so to claim there is no single point of failure is incorrect.
Ok makes sense. Technically you are right. Updated the original post with the correct statement.
A multi-sig option at least has the option to use the wallets at different times in different places. SSS does not.
I agree. Though in our product, we can make some changes to enable sharing of the Shamir shares remotely from different places securely which solves the different places problem. Though it does not solve the different times problem, you can always couple the product with a multisig setup if you want that for yourself. Additionally, since with Cypherock X1 you don't need to maintain a seed phrase backup separately, it makes it easier for new users to create their multisig setups.
A noble cause, but you should at least be honest in your marketing and not make factually incorrect statements to appeal to users who don't know any better.
I don't think I made any factually incorrect statement apart from the nuanced take on the single point of failure. Since you mentioned statements, can you point me to others which you feel are factually incorrect?
That's good to hear. What's the time frame for these being released?
3-4 months is what we are seeing right now because we have requests for other other priority features by the current users. You can check our public roadmap here -
https://cypherock.com/roadmapIf an attacker compromises the device with malicious firmware, then they just need to wait for the next time you want to make a transaction and tap one of your cards. Hence, a single point of failure.
As clarified above, the single point of failure is in the context of seed storage. If the hacker attacks any other hardware wallet physically, your assets could be compromised. But not with Cypherock X1, since the hacker will also need to physically find another card, compromise its security and only then he may be able to access the complete seed to compromise the assets.
Even in your example, the card authenticates whether it is communicating with a genuine device. If you have not already, I would recommend you to read the audit report to understand the security threat model of Cypherock X1 -
https://cypherock.com/keylabsThe lack of standardization is a real problem with all SSS schemes. If your codebase disappears, there is a real risk users are unable to recover their coins. To be safe the user needs to personally download and store copies of your codebase, which is a significant hurdle for most average users.
As I said even if the codebase disappears, you can always view the BIP39 seed phrase and back it up separately if you think this is a risk for you on a personal level. You can argue the same risk for any other open source hardware wallet.