Skip to main content

Signing keys

The CLI can hold two keys:

  • A secp256k1 key (--es256k-key, EBSI_ES256K_PRIVATE_KEY) is mandatory for any command that signs something. It always signs Ethereum transactions, and signs VCs and VPs when no P-256 key is configured.
  • An optional P-256 key (--es256-key, EBSI_ES256_PRIVATE_KEY) signs VCs and VPs only, never transactions. Credentials may be signed with ES256 or ES256K for every scope, but the presentation of did-registry:invite and track-and-trace:authorise must be signed with ES256K, so --sign-alg ES256 fails for those scopes.

When both keys are configured, choose which one signs VCs and VPs with --sign-alg <ES256|ES256K>. The CLI refuses to guess. Commands that sign nothing, such as wallet info or plain reads, work without it.

VCDM 2.0​

The CLI produces VCDM 1.1 credentials and presentations by default. --vcdm-version 2.0 (or EBSI_VCDM_VERSION=2.0, or ebsi config set vcdmVersion 2.0) switches what it signs itself to VCDM 2.0:

  • auth token and ledger write --auto-token present a VCDM 2.0 self-attestation for scopes that need no VC of their own.
  • onboarding issue-vc and onboarding onboard issue a VCDM 2.0 VerifiableAuthorisationToOnboard.
  • A VC passed with --vc decides the version of its own presentation, and --vcdm-version is then ignored.

A node that doesn't enable VCDM 2.0 rejects such presentations with invalid_request (VCDM 2.0 presentations are not supported). VCDM 1.1 is always accepted.