Build with VerusID

VerusID is a self-sovereign identity system built into the Verus blockchain. Every identity is a full-featured on-chain object with recoverable keys, encrypted storage, and protocol-level authentication — no smart contracts required.

What is VerusID?

A VerusID is a human-readable blockchain identity (like veruscx@) that replaces raw addresses. It's not just a name — it's a programmable container with built-in security, storage, and authentication.

Identity Structure

Every VerusID is an on-chain object returned by getidentity. Here's what it contains:

// getidentity "veruscx@"
{
  "name": "veruscx",
  "identityaddress": "i6QEbNsGThm2JHUwpLwxSu77DwzFWvfHv6",
  "primaryaddresses": ["RAhD9vgrWZ3ALkq541xdqL2oLYEvsLNrzn"],
  "minimumsignatures": 1,
  "revocationauthority": "i6QEb...",  // can revoke access
  "recoveryauthority": "i6QEb...",   // can recover identity
  "flags": 0,                           // 0=unlocked, 2=locked
  "timelock": 0,                        // unlock delay (blocks)
  "contentmultimap": {},               // on-chain data store
  "contentmap": {}
}

Content Multimap

Every VerusID has a built-in on-chain data store called the contentmultimap. It maps VDXF keys to arrays of values — each value up to ~4KB. Think of it as a blockchain-native key-value database attached to your identity.

Writing data

Data is written via updateidentity. Values are typically hex-encoded JSON stored under a VDXF key.

# Store data in your identity
DATA=$(echo -n '{"type":"post","title":"Hello"}' | xxd -p | tr -d '\n')

./verus updateidentity '{
  "name": "yourname",
  "parent": "iParentIdHere",
  "contentmultimap": {
    "iVDXFKeyHere": ["'$DATA'"]
  }
}'

Reading data

Read via getidentity and decode the hex values. From a browser, call the public RPC:

const resp = await fetch('https://api.verus.services', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    jsonrpc: '1.0', id: '1',
    method: 'getidentity',
    params: ['veruscx@']
  })
});
const { result } = await resp.json();
const cmm = result.identity.contentmultimap;
// Decode hex values: hex → bytes → UTF-8 → JSON

Encryption

Data can be encrypted using Verus's built-in Sapling (zk-SNARK) addresses. Encrypt with signdata using an encrypttoaddress parameter, then store the encrypted descriptor in the contentmultimap. Decrypt with decryptdata — only the holder of the z-address private key can read it.

This enables selective disclosure: encrypt each field separately, share viewing keys per-field to reveal only what's needed.

Vault Security

Every VerusID has built-in security features that don't exist in normal crypto wallets.

# Lock an identity
./verus updateidentity '{"name":"veruscx","flags":2}'

# Unlock (starts timelock countdown)
./verus updateidentity '{"name":"veruscx","flags":0}'

Verus Connect

verus-connect is a drop-in package for adding VerusID login and payments to any website. QR codes, deep links, and browser extension support — all handled.

Quick start

# Install
npm install github:Fried333/verus-connect
npm install git+https://github.com/VerusCoin/verusid-ts-client.git

# Configure .env
SIGNING_IADDRESS=iYourVerusIDAddress
PRIVATE_KEY=UxYourWIFPrivateKey
CALLBACK_URL=https://yoursite.com/verusidlogin

# Run (zero code)
npx verus-connect start

Or as Express middleware

const { verusAuth } = require('verus-connect/server');
app.use('/verus', verusAuth({
  iAddress: process.env.SIGNING_IADDRESS,
  privateKey: process.env.PRIVATE_KEY,
  callbackUrl: process.env.CALLBACK_URL,
}));

Endpoints

Key RPC Methods

Libraries