Nchedo

Nchedo (Igbo: Nchèdọ, pronounced roughly "N-cheh-doh") means protection, is a deployment vault for developers who have to keep a hot wallet in a .env file. I built it after exposing private keys while building Web3 projects, including one incident that resulted in a wallet being drained. It made me realize that deployment wallets are often protected only by secrecy—once the key leaks, the funds can disappear before the owner even notices. Instead of trying to prevent every leak, Nchedo assumes the leak has already happened. What problem does it solve? It solves the vulnerability of hot wallets used in automated scripts and AI coding agents. Automation requires key availability, but storing private keys in local files like .env leads to inevitable leaks (accidental Git commits, terminal history exposure, copy-paste errors). Traditional security focuses on off-chain scanning and post-facto alerts, which are always outrun by automated drainer bots. Nchedo shifts the security model by using on-chain timelocks to delay withdrawals, coupled with a canary tripwire that locks the vault atomically when touched. What did you learn? I learned how to turn an attacker’s speed and automated scripting into a defense mechanism. By structuring the bait contract so that claim() invokes vault.lock() before emitting value, we proved that we can enforce security deterministically via EVM consensus inside the thief's own transaction. We also learned how to leverage Monad's high speed and low gas costs to make frequent on-chain deployment containment and canary gas-dusting practical and inexpensive. And of course, nevre to make the mistake I made ever again. The project is deployed on Monad Testnet. Every balance, event and timeline shown in the UI comes directly from on-chain reads rather than mocked data. Nchedo doesn't promise a leaked key is harmless—it guarantees that a leaked deployment key can no longer drain the protected reserve instantly.