Best practices

 

This article is relevant for all io.vault and io.network subscriptions.

 

Below are some best practices we strongly recommend all users and clients using the io.network and io.vault products to implement:

  • Test transaction: always perform  two test transactions when creating a new vault:
    • First, verify that the deposit address displayed is valid by making a test deposit and confirming receipt
    • Finally, ownership of the vault and underlying public addresses should be verified by performing a test withdrawal
  • Redundancy of Users/Devices: create vaults with redundancy of users and their devices in mind to avoid requiring implementation of the disaster recovery process for instances of a single user losing a signing device
  • Backing up devices: ensure all users are consistently and frequently backing up their device. These backups should not be saved to iCloud or Google Drive in order to ensure additional redundancy to the native functionality of the mobile application. Instead, choose an alternative storage drive for downloading these files.

    At a minimum, each user device should be backed up each time it participates in creation of a new vault or a vault re-share as these processes result in new shares being created locally on the devices

  • Securing your signing device: Please refer to best practices and recommended configurations for securing your personal signing device here