Features

With _features.conf you can control which Wallet API v2 features are enabled. They are managed via the feature manager.

Available Features

Base Features

Base features are always enabled and do not need to be listed in _features.conf.

  • wallet-service — Core wallet service (wallet, key, DID, and credential APIs). Loads wallet-service.conf.

Optional Features

Optional features are opt-in — each is active only when listed in enabledFeatures. The shipped _features.conf enables wallet2-persistence (SQLite); auth and dev-mode are left disabled.

  • wallet2-persistence — SQL persistence (SQLite or PostgreSQL) for wallets, keys, DIDs, and credentials. Loads wallet2-persistence.conf. Enabled in the shipped config. Remove it to keep all data in memory (lost on restart).
  • auth — Email/password authentication and account-to-wallet ownership. Loads auth.conf. When disabled (the default), all wallets are accessible without a token. Not functional in the current release — enabling it prevents the service from starting; see Authentication.
  • dev-mode — Development mode. Loads dev-mode.conf. Currently a no-op — nothing in the service reads it yet (it does not disable authentication); see Dev Mode.

The standard infrastructure features (web server, OpenAPI/Swagger, health checks) are provided by the framework and enabled by default; the web server is configured via web.conf.

Example Setup

_features.conf
enabledFeatures = [
    wallet2-persistence
    # auth
    # dev-mode
]
disabledFeatures = [
    # ...
]

Restart the service after editing _features.conf — feature changes are applied at startup only.

Last updated on July 13, 2026