Rakshak
Institutional wallet security, without complexity.
Demo
About
The problem it solves Crypto wallets are highly secure, but they are also unforgiving. If a private key is lost, access to the funds can be permanently lost. This creates a serious operational risk for organizations such as DAOs, NGOs, and Web3 startups that manage treasury funds. While solutions like **BitGo** provide strong security through multisig wallets and secure signing, operational recovery is still difficult for non-technical teams. If a key holder becomes unavailable, treasury operations can stop even though the funds remain technically secure. **Rakshak** makes crypto treasury management safer and easier by adding a structured recovery workflow on top of institutional wallets. With Rakshak, teams can: - Configure trusted guardians who can approve recovery actions - Initiate a recovery request if key access is lost - Use team-based approvals to securely authorize recovery - Restore access by transferring funds to a new safe address Instead of relying on complex technical procedures, teams get a simple dashboard and approval flow that ensures treasury continuity. Rakshak ensures that losing a key does not mean losing access to funds, making crypto treasury operations safer, recoverable, and easier for institutional teams to manage.
How it's made
Challenges we ran into A key hurdle was during BitGo integration itself, not just UI work. We had to decide which BitGo wallet flow best matched our recovery model, and initially that was confusing: wallet type selection, key-handling approach, and how to make recovery work reliably for non-technical teams. We also had to align wallet creation, receiver setup, guardian approvals, and recovery execution into one consistent operational flow. How we solved it: - standardized on a single wallet flow for the demo (Arbitrum testnet with BitGo-backed multisig) - built a clear step-based orchestrator flow in our app - added strict ownership mapping and approval checks so only the correct signed-in user can operate a wallet - moved critical mappings from local files to DB-backed storage for consistency and safer multi-user behavior This turned a complex SDK-first integration into a predictable product workflow that PM/ops teams can actually use.