io.finnet has two types of signature devices. Both types can be in a vault at the same time.

Mobile Device

Our mobile signer allows users to use their personal devices to store key material and sign transactions.

We support iOS and Android mobile devices, and our application can be downloaded from the app stores:

iOS: https://apps.apple.com/gb/app/io-finnet/id1641136546?platform=iphone

Apple iPhone 12 or later with iOS 17 or later installed (For optimal security, it is essential to enable FaceID on your device and ensure that you keep your iOS version updated to the latest release)

It is possible to find the application available on both iPad and MacOS via the app stores but does not come with official support.

Android: https://play.google.com/store/apps/details?id=com.iofinnet.vault

Android version 12 or later, which corresponds to a minimum API level of 31. Additionally, your device needs to support the Hardware Backed Keystore feature (To maximize the security of your device, it is important to enable secure biometric recognition and regularly update your device to the latest operating system version.).

Backup Syncing

Backup files are sync'd to the users iCloud and/or Google Drive and can be restored on any iOS device with the iCloud login and the decryption key or 24 words.

Mobile Resharing

In the event of losing a device and there are no cloud backups, the old device can be re-shared out of the vault and a new device can be shared into the vault.

Virtual Signer

Our Virtual Signer is a server based runtime that utilises trusted execution environments (TEE) on SGX hardware, and AMD SEV-SNP (Secure Encrypted Virtualization-Secure Nested Paging) [coming soon].

It can be configured to run in 3 modes:

Sign everything - this should not be used in production and only for testing.
API Approval - configured to point towards a secured API endpoint that will be called by the virtual signer and instructed whether to approve or reject.
Smart Contract approval - configured to point towards a smart contract, which can be configured with our transactional policies