Bobimala

Most financial institutions don't touch crypto because they can't. Banks need private flows and verified accounts with full transaction attribution, which is opposite to what public blockchains offer. @KeetaNetwork is building for this gap. Their approach uses onchain identity certificates via the X.509 standard, the same cryptographic framework used across internet protocols). Wallets get tied to verifiable identity attestations without exposing the underlying personal data. With selective disclosure, users can prove specific attributes (KYC status, jurisdictional permissions, business licenses) to counterparties without revealing everything else. Compliance is enforced at the protocol level while pseudonymity is preserved on the public ledger. Keeta has also built a permission system around asset issuance that includes jurisdictional restrictions, KYC-gated transfers, and role-based permissions for custodians. These features are standard in traditional finance but still missing from most crypto infrastructure. Keeta is building the compliant rails institutions need before they can move onchain.

Quick update on the private subnets: Accepting USDC as payment turned out to be far more painful than expected. Almost every major centralized API provider (*retracted*, *retracted*, etc.) requires a US entity, which we don’t have. We were told last minute that there is a compliance bottleneck, even if we wanted to accept USDC without an onramp.... In the short term, we’re integrating NOWPayments now so we can move forward without blocking users. In the medium term, we’ll use @KeetaNetwork to build our own payment stack, removing reliance on centralized gateways altogether. Why Keeta? 1. Non-custodial 2. No US-entity gatekeeping 3. Protocol-level settlement 4. Fewer compliance chokepoints Not ideal, but this gets us shipping — and long-term, it’s the stronger architecture. Also if someone has a intro to Keeta team, slide in our DMs. Appreciate everyone’s patience. 🚀