Loading the key
The recommended way is a key file — key material stays out of source code:The recovery phrase is the key: its 256 bits of entropy are used directly as the Ed25519 private key — no derivation path, no passphrase — exactly as the Walley app encodes it at registration. See Recovery Phrase.
Keys, fingerprints, and party ids
TheSigner class converts between representations:
<hint>::<fingerprint>, so the key and the party are cryptographically bound. Identify the party either way:
party_id whose namespace doesn’t match the key’s fingerprint is rejected up front.
Signing arbitrary messages
w.sign(...) produces a signature bundle any verifier can check against the party id — useful for login proofs and off-ledger attestations:
signMessage.
Configuration reference
audience must match the target deployment’s auth configuration, you can override it together with api_base when pointing at a non-production environment.