Downloads

Concordium ID

Installation on Android

Installation requirements: Android 8 or newer.

  1. Download the Concordium ID APK to your phone.

  2. You may see a warning about downloading the .apk-file. If you are asked whether you want to keep the .apk-file, press OK.

  3. After opening the .apk-file, you may see a warning saying that your phone is not allowed to install apps from this source. Press Settings, toggle Allow from this source and go back.

  4. You are now asked if you want to install the application. Press Install.

Installation on iOS

Installation requirements: iOS 13 or newer.

Installing the Concordium ID app on iOS requires installation of Apple’s TestFlight app, which is used to distribute beta versions of iOS apps.

  1. Install TestFlight via App Store.

  2. Join our TestFlight beta program via your iPhone (it works best if you click the link directly on your iPhone), and follow the steps shown in there, to add Concordium ID to TestFlight.

  3. Open the TestFlight app on your iPhone and install Concordium ID.

Concordium Node and Client

Concordium node and client software for Open Testnet v4:

Download and extract the archive on your machine.

Read more about the Concordium node and client software in our reference guides.

Requirements

Below are the recommended requirements for running a node. Weaker hardware might still run the node, however you might experience problems.

Linux

Desktop, server or laptop hardware running a recent version of 64-bit linux with:

  • 30 Gigabytes of free disk space

  • 4 gigabytes of ram

Windows

Desktop, server or laptop hardware running 64-bit Windows 10 pro or Windows 10 home version 2004 with:

  • 30 Gigabytes of free disk space

  • 8 gigabytes of ram

Mac

Desktop, server or laptop hardware running a recent version of Mac OS with:

  • 30 Gigabytes of free disk space

  • 8 gigabytes of ram

You need a broadband connection to run our node. It is preferable to run the node continuously. If you use a laptop please be aware that sleep can cause problems with the docker container used to run the node. Refer to our known problems list.