Mobile Signer

Install and register the io.sign app on a supported iOS or Android device

The io.sign Mobile Signer lets a person hold a key share for a vault, review requests, and participate in threshold signing from a supported iOS or Android device.

Requirements

PlatformSupported baseline
iOSiPhone running iOS 26 or later
AndroidAndroid 14 (API level 34) or later with a hardware-backed Keystore

Enable secure biometric authentication and keep the operating system current. iPad and macOS availability in the App Store does not imply official io.sign support.

Install the app

Download the current io.sign Mobile Signer binary from an official store:

📘

The current store listing is named io.finnet while the signing product transitions to the io.sign brand. Verify that the developer is Io FinNet Group, Inc. before installing.

If your organisation uses customer-cloud, on-premise, or air-gapped io.sign, connect the app to that service before signing in. See Connect to a custom environment.

Confirm with your administrator that the installed version supports your io.sign environment and the custom-environment flow.

Register the signer

  1. Open the app and sign in with the account issued for your io.sign environment.
  2. When prompted, register the device as a new signer.
  3. Review the generated device name. You can change it later in your profile.
  4. Set an app password of at least 12 characters, and enter it again to confirm. The app password protects everything the app keeps on the device, including your key shares.
  5. Choose whether to unlock the app with biometric authentication, such as Face ID or a fingerprint. You can still unlock it with the app password.
  6. Complete the recovery setup and store the recovery material according to your organisation's security procedure.

After registration, an administrator can add the Mobile Signer to a vault and assign its weight.

Review and approve requests

  1. Open the request notification or the app's request list and select the pending operation.
  2. Check the organisation, vault, operation type, and the details shown. For a signing request, review its payload or decoded transaction and any warnings. For vault creation or resharing, review the proposed signer membership, weights, and threshold.
  3. Approve only if the request matches the operation you expect. Complete the app's local identity verification when prompted. Otherwise, choose Reject and confirm.
  4. Keep the app connected while the signing ceremony runs, and check the final request status. An approval alone does not mean the request completed or a transaction reached a blockchain.

A request can complete without your approval if another eligible signer set meets the threshold. If your approval is not enough, additional eligible signer weight must approve and remain reachable.

If the app cannot decode a payload, verify the exact data through an approved independent process before deciding. A warning acknowledgement is not a validation of the payload.

Troubleshoot signing

SymptomWhat to check
No pending request appearsCorrect environment and organisation, signer membership, request expiry, and network access. Open the app rather than relying only on push notifications.
A request is waiting after approvalEnough eligible signer weight must approve and remain reachable to meet the threshold. Ask your administrator to check the signer's connectivity to io.sign.
An update is requiredInstall the compatible version supplied through your organisation's approved distribution channel.
Device lost or replacedRestore from your latest backup files and their secret phrases. A fresh registration doesn't restore existing key shares.

Protect recovery material

Each time you export a backup, the app generates a new 24-word secret phrase. That phrase is the only way to open that backup, which you need to recover your key shares if the device is lost or replaced. Keep a record of which phrase opens which backup.

  • Store each phrase separately from the device, its cloud account, and the backup file.
  • Do not photograph it, paste it into a password field, or send it through chat or email.
  • If you lose both the device and your backup files or secret phrases, that signer can't take part in its vaults.
  • Anyone who has a backup file and its secret phrase can recover the key shares in it. Apply your organisation's access-control and custody requirements.

The app password is separate from your account password and from your backups' secret phrases. You can't recover it if you forget it, so store it according to your organisation's security procedure.

Backup files

In Settings, tap Export backups to export your key shares as an encrypted backup file, secured by a new 24-word secret phrase. Save the file wherever your organisation permits, for example the device's files, iCloud Drive, or Google Drive. The file stays encrypted wherever you store it, and io.finnet never sees the phrase.

To restore your key shares on a new device, install the app, choose Restore from backup, import the backup file, and enter its secret phrase.

If the app shows Backup syncing needed, the device is missing the latest key shares for the vaults it lists, and can't sign for them. Import the latest backup files for those vaults to fix this.

Confirm that your chosen storage location is permitted by your organisation before you save a backup file there.

Resharing a vault

Resharing can add or remove signers or change their weights without changing the vault's public key.

🚧

Resharing does not necessarily make every historical copy of an old key share cryptographically unusable. If vault membership changes because a signer or key share may be compromised, create a new vault and move to its new public key instead of relying only on resharing.

Next steps


Did this page help you?