Skip to main content

Prerequisites

Before deploying the Signing Module, confirm that you have everything listed here.

Before you begin​

For sandbox integration, you must have:

Generating your wallet seed, DID and Verkey​

Each connection you establish on the RTGS.global network is backed by an encrypted key pair stored in a wallet database alongside your Signing Module. The master key that unlocks your wallet is known as the seed — a random string of 32 alphanumeric characters.

tip

We recommend generating a Globally Unique Identifier (GUID) without hyphens as the seed value. This provides maximum entropy within the allowed characters and length.

You are responsible for creating this seed value and keeping it secure, preferably in a managed secrets service such as Azure Key Vault. Like a password, you must not share this seed with anyone — RTGS.global cannot recover the value if lost.

Once you have a seed value, run the following Docker command to derive your DID and Verkey:

docker run --rm -it ghcr.io/indicio-tech/did-derive:latest from-seed '<seed>'

The output will look like:

DID/NYM: 2VemhUTQaWQixPhvvtDJgK
Verkey: pEDX3iAwJSzi6aqSoiohcEKC9kCAKkdJankwu4HwkBh
Short Verkey: ~53ZTaTG28YR5sHmY6Jdtgw

During onboarding, you will be asked to provide the DID/NYM and Verkey values. The Short Verkey is not required.

warning

Your wallet seed cannot be recovered if lost. Store it in a secrets manager before proceeding with deployment.

danger

Never re-provision your wallet without the original seed. If the wallet is re-provisioned without a seed — or with a different seed — ACA-Py generates a new DID that is not registered on the Indicio ledger, causing the Signing Module to fail on startup with a seed/DID mismatch error. If you need to restore or re-provision your wallet, always supply the same seed used during initial deployment.