Wallets

The Wallets page is a two-tab layout: groups on the left, the wallets inside the selected group on the right. Groups are how you target tasks — you pick a group, not individual wallets, when firing a multi-wallet task.

Groups

Groups are pure tags. A wallet can only live in one group at a time. Use groups to separate purposes:

• funder — your gas wallets.
• mints-base — burners you’ll fire mints from on Base.
• cold — wallets you don’t want to accidentally include in a batch.

Rename, delete, and re-order groups freely. Deleting a group removes its wallets too — there’s a confirm prompt.

Adding wallets

Action	What it does
Generate	Creates a fresh secp256k1 keypair with crypto/rand and persists it.
Paste import	One key per line in the textarea. Accepts 0x-prefixed or bare hex.
Batch import	File picker for a .csv or .txt with the same one-per-line format.
Rename	Per-row inline edit on the name column.
Delete	Per-row, with confirm.

Per-row Send

Each wallet row has a Send button. Pick chain, asset (native or ERC-20), destination, amount, and confirm. Uses EIP-1559 gas defaults from Settings, fails over across your pinned RPCs for that chain.

The Send dialog reads the wallet’s balance live before you submit. If the balance call fails, you’ll see a banner — usually a flaky RPC.

Manage Funds (Disperse / Consolidate)

The big workflow on this page. Click Manage Funds to open the dialog.

Disperse (1 → N)

Pick a source wallet, a destination group, and an amount per recipient. The app dispatches via a Disperse contract (per chain — defaults shipped, override in disperse.txt under your data dir).

• Splits in a single tx if the chain has a Disperse contract deployed.
• Falls back to individual sends otherwise.

Consolidate (N → 1)

Pick a source group and a destination wallet. The app sweeps each wallet’s balance into the destination, leaving a small gas buffer behind.

Session history goes to funds-sessions.log (JSONL) next to the .exe so you can audit it later.

Balance fetching

Per-chain native + ERC-20 balance reads happen in parallel JSON-RPC. A 100-wallet group resolves in seconds, not minutes. Failures show as - instead of 0 so you can tell “no RPC answer” apart from “wallet empty”.

Where keys live

%LOCALAPPDATA%\zyper-suite\data\wallets.dat — DPAPI-encrypted, sealed to your Windows user. There is no master password, no UI prompt — decryption happens transparently when the app runs as you. Copying this file to another machine or Windows user produces gibberish.

There is no built-in backup. Use the per-row export or copy the key out yourself before you delete anything important.