Upgrading CASP

If you are upgrading CASPClosedUnbound’s Crypto Asset Security Platform (“CASP”) provides the advanced technology and the architecture to secure crypto asset transactions. from a previous release, follow this procedure.

Note
After upgrading CORE and the schema, you cannot create new entities (e.g. vaults, participants) until CASPClosedUnbound’s Crypto Asset Security Platform (“CASP”) provides the advanced technology and the architecture to secure crypto asset transactions. is updated.

  1. Upgrade CORE - Instructions can be found in the CORE User Guide.

    2. Note
    If you upgraded CORE from a release preceding 2.0.2112 to the release 2.0.2112 or higher, you must create a new set of the CASPClosedUnbound’s Crypto Asset Security Platform (“CASP”) provides the advanced technology and the architecture to secure crypto asset transactions. vault-key backup encryption keys. See Prepare for Vault-key Backup and Recovery.

  2. Upgrade the schema - The schema package can be downloaded from the Unbound repository. Uncompress the package and then load the schema file that corresponds to your upgrade:

    • For MySQL:

      mysql -u [username] -p [database] < casp-mysql-upgrade.sql

    • For PostgreSQL:

      psql [database] < casp-postgresql-upgrade.sql

  3. Upgrade the bot (if you are using a bot) - Use the instructions in CASP Bot. If you are upgrading the CASPClosedUnbound’s Crypto Asset Security Platform (“CASP”) provides the advanced technology and the architecture to secure crypto asset transactions. bot and using a directory different from the previous installation, you must copy the key file(s) from the old installation. Key files are found in: <bot directory>/bin/<key>.p12

  4. Install the new package - Use the instructions in CASP Package Installation.

    • For CentOS installations, check the configuration files. During the RPMClosedFile format for software package distributed by RPM Package Manager installation, if there are configuration files that have manual edits, they are not overwritten. Instead, a new file is created with a rpmnew suffix. Check this file and copy any new, relevant configuration information to the original file.

      Note
      During an upgrade, the following warnings can be safely ignored:
      rm: cannot remove ‘//opt/casp/providers/bch/casp-bch-provider.jar’: No such file
      rmdir: failed to remove ‘//opt/casp/providers/bch’: Directory not empty

    • For Ubuntu installations, the installer automatically asks what you want to do with files that already exist.

  5. Built-in Bitcoin configuration - If you are using the built-in Bitcoin wallet and made changes to the default casp-apache.conf file, after upgrading you need to check the Bitcoin ports in the configuration files.
    1. Edit the file /etc/httpd/conf.d/casp-apache.conf.
    2. Change the ports used for Bitcoin to port 3000 instead of 8080.

    3. Restart the Apache service.

  6. CASPClosedUnbound’s Crypto Asset Security Platform (“CASP”) provides the advanced technology and the architecture to secure crypto asset transactions. wallets - To upgrade CASPClosedUnbound’s Crypto Asset Security Platform (“CASP”) provides the advanced technology and the architecture to secure crypto asset transactions. wallets, follow the instructions found here.
  7. Web UI - If you are using the web interface, you must clear the cache in your browser.

  8. Test the installation - Use the instructions in Testing the CASP System.

Note
After upgrading the CASPClosedUnbound’s Crypto Asset Security Platform (“CASP”) provides the advanced technology and the architecture to secure crypto asset transactions. package, check the following to ensure that CASPClosedUnbound’s Crypto Asset Security Platform (“CASP”) provides the advanced technology and the architecture to secure crypto asset transactions. points to the correct SQL driver and check that the driver exists.
1. Check for the driver in /opt/casp/jdbc. For example, for PostgrSQL, a file called postgresql-<version>.jar should exist.
2. In the casp.conf file, check the driver file setting. For example, for PostgreSQL, the casp.conf should contain:
database.driverfile=/opt/casp/jdbc/postgresql-<version>.jar