Fintech · Crypto payments
Bitilda
A crypto payments and wallet product for simpler digital-asset payments, on/off-ramp access, and multi-chain financial infrastructure. Raised $3k.
- Role
- Co-founder & CTO
- Type
- Co-founded product
- Status
- Funded prototype
- Stack
- Vue · TypeScript · Interledger · Hedera
1 · The problem
Moving value across chains and rails is fragmented: key management, chain differences, fees, failure states, and on/off-ramp access all live in different tools with different trust models.
2 · My responsibility
Wallet and key-management architecture, multi-chain account handling, transaction lifecycle design, and Open Payments / Interledger integration for transfers.
3 · The architecture
Mobile/web clients talk to a TypeScript backend that abstracts chain adapters (Hedera, EVM, Interledger) behind one transfer API. Keys are generated client-side; the backend never holds raw secrets — only encrypted references with strict separation.
4 · Key engineering decisions
Client-side key generation with encrypted backup over custodial storage; one transfer abstraction with per-chain adapters instead of per-chain UIs; Interledger for fiat-adjacent rails rather than building settlement from scratch.
5 · The hardest problem
Chain-specific failure modes (finality, fees, reverted txs) break generic UIs. Solved with per-adapter error normalization into a single transaction state machine the frontend can render honestly.
6 · What I would improve
Production-grade audit of the key lifecycle, formalized on/off-ramp partnerships, and published security boundaries so users know exactly what Bitilda can and cannot touch.