IKS capability: FVSD

[Parsh]

IKS and even SS as any Fully Verifying Signing Device(FVSD):

• Like a hardware wallet that is always connected. Rest should be the same. Use CC or FD as an example.
• Instead of the user providing the pin to access the device they have to provide m-1 SD details
• And for signing, they need to also wait 4 weeks for the request to be approved.
• The IKS/ SS fully verifies the signature requested with descriptor details like CC/ FD.
• Provide SD details (MFP, xPub etc.) for Vault Creation - based on descriptor details provided. This will not have a check on SDs but rather create a new record.
• Provide SD details (MFP, xPub etc.) for Restore - based on m-1 SD confirmations. This is checking against the record and confirming/ sending back the data.
• Same as above but for Health Check - ping initiated from the app to check is the IKS is alive, IKS responds back with xPub that the app confirms matches what it has. This applies to SS as well.
• For now m-1 will have to be limited to m=3. This is one way of restricting IKS to Level 3 only form the backend. No one can modify the code and use IKS on prior levels.
• This also implies that the way data is stored in IKS and SS, it should have all aspects of a Descriptors
• Change SD/ descriptor details - the way CC/FD would handle it is registration of a new Vault with new details as in 5 above. I think we should do the same.
• Signing - same as SS/ FD - verify all details in the PSBT then sign
• Retrieve Descriptor - same as CC/ FD - when requested share if the user provides m-1 SDs and waits 30 days. Here the user will not need the Descriptor file.

Dependencies:

• 2826

[Parsh]

As per the latest, we're not doing FVSD and therefore would also not require descriptors for verification(we should be able to do the verification using signer-id). And the BSMS that we would be storing, upon asking the user, would be for facilitating easy restoration.

@antuz123 Right?

[antuz123]

Yes that is correct. SIDs are for identification of the Vault. Approval/ verification is automatic after the delay.