Give your hooks a signal.
Keep your wallet in control.

1. Choose the Zcash account your hooks watch

Install the official Zcash wallet RPC tools and Node.js 22 or later. The companion requires a synced mainnet zcashd-compatible wallet RPC at 127.0.0.1:8232, with rpcuser and rpcpassword configured locally. Keep RPC bound to loopback. Select an existing unified account with at least one receiving address using zcash-cli z_listaccounts.

The companion reads unified-account balances and incoming payments to its known addresses. A Zebra node or lightwalletd server alone does not provide wallet RPC. Mobile wallets can use payment requests without this connection. Never paste a seed or private key into ZecHooks.

2. Pair your account with ZecHooks

Download the companion into a local folder. Set the RPC credentials in your terminal to match your wallet RPC. Set the exact ZecHooks origin if using a different deployment.

PowerShell

$env:ZCASH_RPC_USER = "your-rpc-user"
$env:ZCASH_RPC_PASSWORD = "your-rpc-password"
$env:ZCASH_ACCOUNT = "0"
$env:ZECHOOKS_ORIGIN = "https://zechooks.online"
node ./zechooks-companion.mjs

macOS / Linux

export ZCASH_RPC_USER="your-rpc-user"
export ZCASH_RPC_PASSWORD="your-rpc-password"
export ZCASH_ACCOUNT="0"
export ZECHOOKS_ORIGIN="https://zechooks.online"
node ./zechooks-companion.mjs

Keep this terminal open. The companion prints a temporary pairing token. It only accepts requests from your configured app origin and exposes a read-only snapshot of your selected account (default 0). The account total combines balances across its pools; it is not a per-pool balance view. Sapling and Orchard filters apply to incoming receipts, not liquidity pools. Incoming activity excludes change and shows up to 250 recent transactions; outgoing transactions are reviewed in your native wallet.

3. Create your first ZecHooks rule

Open ZecHooks, select Connect wallet, and paste the session token. Allow local-network access if your browser asks. Chrome or Edge on desktop is recommended for the local connection. Other browsers may block HTTPS-to-loopback requests; use a supported desktop browser.

Choose a Zcash hook template, set the amount and confirmations, and choose an action: notify you, prepare a ZEC payment, or prepare a SOL transfer. Shielded hooks count Sapling and Orchard amounts only; use the latest companion for pool filters. Low-balance hooks fire when confirmed funds cross below your threshold. Save the hook to start monitoring every 15 seconds while the app is visible. Closing the tab or companion stops monitoring. On reconnect, a new baseline is established; this is not a background alert service and missed intervals are not replayed.

Open Hook matches to review matching hooks and their prepared actions. ZEC actions open a payment request in a compatible wallet. SOL actions load a draft into the Solana transfer form for fee checks, review and wallet approval. They spend from your own Solana wallet; they do not bridge or exchange ZEC. These are local wallet-event hooks, not contracts deployed on Zcash.

Hook definitions and wallet addresses are stored in this browser. Pairing tokens, balances and transactions stay in memory and are cleared on disconnect. Delete saved hooks to remove their wallet references.

Payment requests and Solana signing

Zcash payment requests and native-wallet handoff work without the companion. Open a payment link in a compatible Zcash wallet and review the network, destination and fee there. A payment link is not a transaction confirmation.

For Solana, open ZecHooks inside Phantom, Solflare, Trust Wallet or Coinbase Wallet’s mobile browser, or use their desktop extensions. Choose mainnet or devnet in the Solana screen. A connected Solana wallet does not connect to Zcash or create a ZEC bridge.