$ whoami

handle :: iuanv9
focus :: monero — private, air-gapped, verifiable money
stack :: c++ (wallet2 / lws) · kotlin (android) · rust (monero-oxide)
motto :: no single compromised device should be able to lose funds or leak metadata

I build and break privacy software. Most of my time goes into hardening the full lifecycle of a Monero transaction — scan → construct → cold-sign over QR → broadcast — across a hot Android wallet, a light-wallet server, and an offline pure-Rust signer.

$ cat /proc/self/skills

Skill chart: c++/monero internals 95, native debugging 92, kotlin/android 90, airgap protocols 88, test harnesses 87, rust 85 (self-reported, 0–100)

$ ps aux | grep active_projects

Development orbit: ANONERO wallet and oxide cold signer on the inner orbit, lws/lwsf light wallet and FCMP++ research on the outer orbit

repo	what it is
anonero-fork	hardened Monero Android wallet — LWS mode, QR air-gap cold-signing, duress PIN, Tor-only
lwsf	light-wallet-server framework — wallet2-compatible client for monero-lws backends
monero-lws	light wallet server — scanning, regtest and account-management fixes
monero	monero core — wallet2 patches: fast-refresh, compact unsigned-tx sets, key-image sync
monero_c	C ABI bindings glueing the native wallet cores to the app layer

$ grep -ri interests ~/

Interests: monero, tor/onion services, zero-knowledge & FCMP++, cold-wallet UX, android internals, reproducible builds, threat modeling, regtest automation