Skip to content

1.0Platform

How Kibora works

Four places do work in Kibora: your browser, public chain nodes, a small server, and two contracts. Here is who sees what.

Your browser

All cryptography runs here, in a Web Worker, with @noble/post-quantum 0.7.1 and the browser's own Web Crypto (AES-GCM, HKDF, PBKDF2). Secrets and readable content stay in the page's memory; the Watch list, the theme and practice records live in local storage. Nothing secret is uploaded.

Public nodes

Exposure Scan and Watch read Ethereum, Base, Bitcoin and Solana straight from public endpoints. Robinhood Chain reads go through the site's relay first, because some networks intercept the public RPC host; the relay only allows read methods, applies a budget per network and keeps no log of addresses.

The server

  • /api/rpc: read-only relay for Robinhood Chain (allowlisted methods and contracts, rate-limited).
  • /api/chain: block, gas, ETH/USD and contract counters for the live strip.
  • /api/access: one-time nonces, sign-in signature checks, $KIBORA balance reads and beta codes (one per wallet).
  • /api/stats: two numbers per day, finished scans and how many found an exposed key. No addresses.

The contracts

KiboraLatticeBook stores public post-quantum keys by account. KiboraWardForge opens KiboraWard safes. Neither has an owner, a fee or an upgrade path. Details are on the contracts page.