About Bitcoin Kali

The project

Bitcoin Kali is a seven-piece generative art series registered as Verus identities on the VRSC mainnet. Each piece carries its own name, devotional verse, generative attributes, image hash, curator signature, rights assertion, and encrypted file delivery — all stored inside the identity's contentmultimap, all verifiable from public RPC.

The series draws on the iconography of Kali — the Hindu goddess of time, destruction, and renewal — reframed through the lens of Bitcoin's challenge to fiat monetary systems. Each piece is named with a Sanskrit epithet and accompanied by a devotional verse.

But the project isn't primarily about the art. It's a demonstration of what Verus can do: typed on-chain data, cryptographic provenance, encrypted file delivery, identity-bound rights, and a zero-trust verification model — all composed from protocol-level primitives.

Why Verus

Most blockchain NFT systems store metadata off-chain (IPFS, Arweave, or a server) and reference it with a URL. If the host disappears, the metadata is gone. The NFT is a token ID and an owner address — everything else is a trust assumption.

Verus enables a different approach. Each NFT is a VerusID — a self-sovereign identity with a human-readable name, an on-chain data store, and transferable control. The metadata isn't pointed-to; it's part of the identity. The curator's signature covers the data directly, not a URL. Verification is a single RPC call, not a chain of trust through intermediaries.

Bitcoin Kali exists to show this in practice, with real mainnet data that anyone can check.

Tech stack

Chain

Verus (VRSC) mainnet — public RPC via api.verus.services

Viewer

SvelteKit + adapter-static, Svelte 5, TypeScript

Images

Decrypted live from chain via decryptdata on rpc.vrsc.syncproof.net

Verification

Client-side SHA-256 + live verifysignature RPC — no backend

Hosting

Static files, no server, no database, no analytics, no tracking

What you can verify

Nothing on this site is trusted. Every claim is independently checkable:

• Identity existence — getidentity on any Verus node
• Curator signature — verifysignature with the mmrroot and signature from the CMM
• Image integrity — decryptdata + SHA-256, compared against the on-chain uint256
• Rights assertion — stored on chain, signed into the MMR, tamper-evident
• Delivery — encrypted bytes on chain, viewing key published, anyone can decrypt

The Learn section walks through each primitive. The verification theatre runs the checks live, streaming each step as it happens.

Links

• verus.io — Verus project home
• docs.verus.io — Verus documentation
• Verus Discord — community
• Gallery — the seven pieces
• Learn — ten guides to the Verus primitives used here

Credits

Built on the Verus protocol. The identity, signing, and encrypted delivery primitives are Verus core features — this project demonstrates them, it didn't invent them. Thanks to the Verus community and core development team for building the infrastructure that makes this possible.

Donate to "Verus Coin Foundation@"