Bits and pieces a Verus developer tends to need. All open source, all in one org.
TypeScript client for the Verus (verusd) JSON-RPC interface. Every daemon method is reachable via call(); the common ones have proper types.
Typed TypeScript SDK for Verus transaction signing, offline.
Offline signing of Verus shielded (Sapling) transactions — t→z, z→z, z→t, with memo. WASM prover, so no full node on the signing host.
Offline Verus transaction SDK in Rust — transparent and shielded. Builds and signs the bytes; your application broadcasts.
Non-custodial Verus wallet as a Chrome extension. Keys stay encrypted in the browser, transactions are built and signed in WebAssembly and shown — txid, fee — before broadcast.
Pecu — desktop wallet for Verus (Windows, macOS, Linux).
Docker and Kubernetes images for Verus — mainnet, testnet and PBaaS chains.
An HTTP-402 payment protocol for AI-agent APIs, Verus-native — spec plus a reference implementation.
Peculium — a Verus wallet for AI agents (MCP server + CLI, lite: local signing against public nodes).
TypeScript SDK for server-side VerusID OAuth/OIDC login.
A look at the Verus mempool — transactions orbit the next block and drift inward while they wait, blocks pulse in, conversions and VerusID registrations get their own colors.
HTTP gateway for accessing files stored on the Verus blockchain, written in Go.
Small CLI to compress images to AVIF without thinking about flags.
I mostly enjoy building the unglamorous parts — a wallet that just works, a client library that does what the docs say, tools you install once and then forget about.
Crypto has been my playground for a while: Bitcoin first, then Ethereum, Solana and IOTA. These days it's mostly Verus, plus a general interest in web3 and fintech.
Working on something in this space? Always happy to chat — just say hi.