The Web-Wallet, our custodian wallet white-label solution, with which you can enable users to receive, share and store Verifiable Credentials, manage DIDs and their related keys and view tokens from different blockchain ecosystems. All in one place.

Getting Started

Depending on your preference, start exploring with the deep dive or jump directly to the setup.

Quick Start

- Start the app in your local environment and receive the first VC.

Try it out!

- start issuing and verifying your own credentials.

Full Guide

- Detailed presentation of the wallet app and its dependencies.

Deep dive

- The wallets components and which walt.id libs are used under the hood.

- An overview of all the functionality offered by the wallet.

- Adjust settings to fit your needs.

Get the Project

Make sure you have installed on your machine.

Several options are available when it comes to using the web-wallet, depending on specific use-case:

• source code - when a higher level of customization is desired

• docker images - when a packaged solution is good enough

The host configuration can be found in config/web.conf. It describes the host address and port number.

Example Config

webHost = "0.0.0.0"
webPort = 4545

Users can login with two options

1. Email

2. Web3 Accounts

   1. Ethereum - Learn more about Sign in with Ethereum here.

   2. Tezos - Learn more about Sign in with Tezos .

   3. Near - Learn more about Sign in with Near .

   4. Polkadot - Learn more about Sign in with Polkadot .

   5. Flow - Learn more about Sign in with Flow .

   6. Algorand - Learn more about Sign in with Algorand .

Considering the context, web-wallet offers the following functions:

• - functions related to verifiable credentials

• - functions related to crypto collectibles

• - display and manage cryptographic keys

All our products are open source under the permissive license. This means:

• You can use, modify and distribute our products for free and without strings attached.

• You can use our products to build pilots or even production systems.

Credential configurations set up the environment for functions related to authorization, credential, DID and key management. Currently, the following configurations are available:

All our products are open source under the permissive license. This means:

• You can use, modify and distribute our products for free and without strings attached.

• You can use our products to build pilots or even production systems.

• You can deploy, run and manage our products on-premise or in your own cloud environments.

Project setup

Pull the docker images:

1. wallet-backend

Web-wallet consists of 2 modules (both part of the same repository):

• frontend - customer facing user interface that enables user interaction with wallet's main functions

• backend - providing the required support for frontend, such as:

Token-related configurations hold token auxiliary data mapping. Currently, there are 2 configurations available:

• chain explorer configuration

• marketplace configuration

• NFTKit configuration

Chain explorer configuration

Chain explorer configuration holds the mapping of chains to their respective explorer location. It is stored in the chainexplorer.conf file.

e.g. chain explorer configuration

Marketplace configuration

Marketplace configuration holds the mapping of chains to their respective marketplace location. It is stored in the marketplace.conf file.

e.g. marketplace configuration

NFTKit configuration

In order to be able to fetch NFT data for owner addresses, the NFTKit dependency should also be configured for the desired chains.

Refer to for details about NFTKit configurations. The walt.yaml configuration file should be mounted under the project's root folder: waltid-web-wallet/walt.yaml.

Storage configuration describes which database should be used for data persistence and the connection string required to connect to the database. This information is organized in 2 separate configuration files:

1. db.conf - database configuration

2. db.<database>.conf - datasource configuration

Database configuration

Database configuration holds the datasource configuration filename (with no extension). The content of this configuration file will then be loaded and used as the connection string for the database. The filename should have the following format: db.<database> The database configuration is stored in the config/db.conf.

SQLite Config

Postgres Config

Datasource Configs

They hold the connection string used to connect to the chosen database.

Sqlite Datasource Config

Can be found in config/db.sqlite.conf

Postgres Datasource Config

Can be found in config/db.postgres.conf

Backend configurations

Web-wallet backend is configured with a set of files describing the configuration using the Hocon format (Human-Optimized Config Object Notation). Things that can be configured relate to:

We offer our products as a managed cloud service for clients who do not want to deploy, manage and run our products by themselves.

The Cloud Platform includes:

• All products

• Enterprise use cases

Web-wallet is built as a monolithic repository were both the backend and frontend are part of the same repository.

Project requirements

• JDK 17+ - for wallet-backend

  • gradle v7.5.1 - to build the wallet-backend

• Node v.16+ - for wallet-frontend

  • pnpm v.8.1.0+ package manager - to run the wallet-frontend

Project setup

1. Clone waltid-identity

1. Change into web-wallet backend folder

1. wallet-frontend source folder

Building the project

• wallet-backend

• wallet-frontend

Runtime configurations

Refer to from the section.

Running the project

The modules referenced in the section from need to be available before starting the web-wallet, so that all functions are enabled. Otherwise, the web-wallet will offer only account management functions (sign in / sign up, profile and settings).

1. start wallet-backend:

   • extract the build output (either .tar or .zip)

Wallet-backend is available at: (the port number configured in web.conf).

Wallet-frontend is available at: .