Troubleshooting
If you have a problem with either the CASP
Unbound’s Crypto Asset Security Platform (“CASP”) provides the advanced
technology and the architecture to secure crypto asset transactions. server or a device running CASP
Unbound’s Crypto Asset Security Platform (“CASP”) provides the advanced
technology and the architecture to secure crypto asset transactions., use the following steps to help troubleshoot the issue.
- Check that the CASP
Unbound’s Crypto Asset Security Platform (“CASP”) provides the advanced
technology and the architecture to secure crypto asset transactions. server and other components are healthy.
Run the checks described in Testing the CASP System. - Follow the instructions in Participant replaces a phone if any of these situations occur:
- The app is removed from the device.
- The user resets the app data.
- The user gets a new phone.
- For the mobile app:
- Check that the URL of the CASP
Unbound’s Crypto Asset Security Platform (“CASP”) provides the advanced
technology and the architecture to secure crypto asset transactions. server is correct.
See Settings in the Mobile App. - Check that the internet connection from the mobile device is working.
- Check that the mobile device can access the server. You may need to check that the device has a valid certificate for the server.
- If the user removes the pin and biometric authentication, no operations will be able to be approved. The user must set a new pin or biometric authentication.
- Check that the URL of the CASP
- If a participant
A member of any of the quorum groups. was deactivated and then activated, the participant
A member of any of the quorum groups. will not be able to approve any operations until they are re-added to all relevant vaults. - For Built-in Wallets:
- For both Bitcoin and Bitcoin Testnet, when retrieving the balance on a BIP44 vault with sub-accounts, you may encounter a situation where the Blockset BTC/BTCTEST token limit is reached. It returns an error code such as:
API calls limits have been reached.
The following parameters can be specified in the configuration file, production.yaml, to control the behavior of Blockset requests.Blockset:
maxConcurrentRequests: 10 // # of requests allowed to be sent at once to Blockset
minRequestTimeMs: 100 // The minimum time between one request and another
maxRetries: 10 // # of times to retry once a request to Blockset fails with 429 - too many requests
- For both Bitcoin and Bitcoin Testnet, when retrieving the balance on a BIP44 vault with sub-accounts, you may encounter a situation where the Blockset BTC/BTCTEST token limit is reached. It returns an error code such as:
- Vault creation:
- You cannot generate a new activation code for a user if there is a pending request to join a vault. This means that if you create a new vault and have a participant
A member of any of the quorum groups. that lost his phone before approving to join the vault, you need to cancel the vault creation operation.
- You cannot generate a new activation code for a user if there is a pending request to join a vault. This means that if you create a new vault and have a participant
CASP Restore SO Password
The password for the CASP
Unbound’s Crypto Asset Security Platform (“CASP”) provides the advanced
technology and the architecture to secure crypto asset transactions. so user may become locked if the incorrect password is used a number of times. In such a case, you can reset the password with this script.
Syntax:
casp_restore_so \
--conf-directory=<location_of_files>
The script has this parameter:
| Parameter | Required | Descrption |
|---|---|---|
| conf-directory | optional | Location of the casp.conf and CORE certificate files. |
The response on success is:
Restore so user was successful
Contact Support
If you are still having the issue, contact Unbound Support.