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

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:

• Host

• Credentials

• Tokens

• Storage

Frontend configurations

• issuer-portal - the IssuerUrl environment variable should be set, specifying the location where the issuer-portal can be reached at. By default, it is set to http://localhost:8080. For local development, this can be updated in the wallet-frontend .env file:

cd waltid-web-wallet/web &&
echo 'IssuerUrl="http://localhost:8080' > .env

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

database = "db.sqlite"

Postgres Config

database = "db.postgres"

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

hikariDataSource {
    jdbcUrl = "jdbc:sqlite:data.db"
    driverClassName = "org.sqlite.JDBC"
    username = ""
    password = ""
    transactionIsolation = "TRANSACTION_SERIALIZABLE"
    maximumPoolSize = 5
    autoCommit = false
    dataSource {
        journalMode = "WAL"
        fullColumnNames = false
    }
}

Postgres Datasource Config

Can be found in config/db.postgres.conf

hikariDataSource {
    jdbcUrl = "jdbc:postgresql://127.0.0.1:5432/postgres"
    driverClassName = "org.postgresql.Driver"
    username = "postgres"
    password = "postgres"
    transactionIsolation = "TRANSACTION_SERIALIZABLE"
    maximumPoolSize = 5
    minimumIdle: 0
    autoCommit = false
    dataSource {
        journalMode = WAL
        fullColumnNames = false
    }
}

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

• wallet configuration

• push notifications configuration

Wallet configuration

specifies the remote location which web-wallet backend should use to proxy all the credential management, key management, DID management and authentication requests to. The configuration is stored in the wallet.conf file.

e.g. wallet configuration

remoteWallet = "https://wallet.walt.id"

Push notifications configuration

A push notifications service can be configured so that the end-user will receive notifications for both when they receive a credential accept request or a verification request. The configuration is stored in the push.conf file.

e.g. push notifications configuration

pushPrivateKey="{server-private-key}"
pushPublicKey="{server-public-key}"
pushSubject="mailto:dev@walt.id"

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

explorers = [
    {chain = "ethereum", url = "https://etherscan.io/address/%s"},
    {chain = "polygon", url = "https://polygonscan.com/address/%s"},
    {chain = "mumbai", url = "https://mumbai.polygonscan.com/address/%s"},
    {chain = "tezos", url = "https://tzkt.io/%s/operations"},
    {chain = "ghostnet", url = "https://ghostnet.tzkt.io/%s/operations"},
]

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

marketplaces = [
    {chain = "ethereum", name = "OpenSea", url = "https://opensea.io/assets/ethereum/%s/%s"},
    {chain = "polygon", name = "OpenSea", url = "https://opensea.io/assets/matic/%s/%s"},
    {chain = "tezos", name = "Rarible", url = "https://rarible.com/token/tezos/%s/%s"},
    {chain = "flow", name = "FlowVerse", url = "https://nft.flowverse.co/marketplace/%s/%s"},
    {chain = "unique", name = "Unique", url = "https://unqnft.io/market/%s/%s"},
]

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.