Skip to main content
This guide takes you from pip install to a committed transaction. It assumes you already have a Walley wallet - if not, create one in the app first and back up its recovery phrase.

Install

Store your key in a file

Put the wallet’s 24-word recovery phrase (or an exported PKCS#8 PEM) in a file only your process can read:
The SDK detects the format — PEM, mnemonic, or a hex/base64 raw key — so there is nothing to configure.
The key file is the wallet. Anyone who reads it controls the party and its funds. Keep it out of source control and CI logs; prefer a secrets manager in production.

Sign in

The party id is derived from the key’s fingerprint, so a wrong key for a given party_id is rejected before any request is made. Configuration can also come from the environment — WALLEY_KEY_FILE, WALLEY_PARTY_HINT, and WALLEY_API_URL — which keeps scripts credential-free.

Look around

Reads authenticate automatically with your key — no passwords, API keys, or tokens to manage.

Send a transaction

The built-in transfer flow prepares the commands, quotes the network fee, signs locally, submits, and waits for finality:
Or run your dApp’s own commands through the same machinery:

Next steps

Transactions & Fees

Fee quotes before you sign, and how deferred fees settle.

Ledger API

Read active contracts and other ledger state directly.