verdikta-bounties-onboarding

Verdikta Bounties hot-wallet operator for Base. Can create/import Ethereum keys into an encrypted keystore (its password is never stored; it comes from VERDIKTA_WALLET_PASSWORD via a secret store or a prompt), keep an API key, upload public bounty/work data, call the reviewed Verdikta API and Base RPC, and sign irreversible mainnet/testnet transactions within an owner spend policy. Use fresh low-balance wallets only. Commissions a verdikta-discover work-order draft when the owner approves it in chat with a line such as 'Approve <hash prefix>, payout <X> ETH, window <N>h': it binds that exact draft, writes approved.json and creates the bounty under the spend policy. Places mutual wagers (a bet with another wallet as two directed bounties, on a game or on a YES/NO question about a published value) only with node wager.js propose/answer/check/status/claim/close, posting only after the owner's line 'Approve wager <hash prefix>, stake <X> ETH, vs <opponent>, settle <ISO time>'. Withdraws the wallet's ETH (or leftover LINK) only to the owner address recorded at onboarding, when the owner asks.