Provifier

How it works

Key features

Quick start

npm install @provifier/sdk

const { Provifier } = require('@provifier/sdk');

const p = new Provifier({
  chain: 'sui',          // or 'solana', 'ethereum', 'polygon', 'base'
  network: 'testnet',
  privateKey: process.env.SUI_PRIVATE_KEY,
  packageId: '0x...',   // Sui only — deployed Move contract
});

// Commit a record
const receipt = await p.commit({
  table: 'documents',
  rowId: 'doc-7',
  data: documentContent,
});
console.log(receipt.txDigest);    // Sui transaction digest
console.log(receipt.explorerUrl); // https://suiscan.xyz/testnet/tx/...

// Verify later — trustless
const result = await p.verify({
  table: 'documents',
  rowId: 'doc-7',
  data: documentContent,
  txDigest: receipt.txDigest,
});
console.log(result.valid); // true

Batch commits (Merkle tree)

Commit many records in a single transaction. Each entry gets a Merkle proof for individual verification.

const batch = await p.commitBatch({
  entries: [
    { table: 'users', rowId: '1', data: JSON.stringify(user1) },
    { table: 'users', rowId: '2', data: JSON.stringify(user2) },
    { table: 'users', rowId: '3', data: JSON.stringify(user3) },
  ],
});

// Verify one entry from the batch
const result = await p.verify({
  table: 'users',
  rowId: '2',
  data: JSON.stringify(user2),
  merkleProof: batch.receipts[1].merkleProof,
  merkleRoot: batch.receipts[1].merkleRoot,
  txDigest: batch.txDigest,
});
console.log(result.valid); // true

Client-side wallet signing

For dApps where the user commits from their own wallet — maximum trust, zero server dependency.

const p = new Provifier({
  chain: 'sui',
  network: 'mainnet',
  packageId: '0x...',
  // No privateKey — client-side mode
});

const { transaction, hash } = p.buildCommitTx({
  table: 'documents',
  rowId: 'doc-7',
  data: documentContent,
});

// Pass to user's wallet (Sui Wallet, Suiet, zkLogin)
const result = await wallet.signAndExecuteTransaction({
  transaction,
});

Multi-chain

Use cases

Sui Move contract

Deploy once, use forever. The contract emits events — no stored objects, cheapest possible on-chain operation.

// Two event types:
// HashCommitted  — single record: committer, table, row_id, data_hash, timestamp
// BatchCommitted — Merkle batch: committer, merkle_root, leaf_count, timestamp

cd contracts/sui
sui move build
sui client publish --gas-budget 100000000

API reference

Hosted API

Don't want to manage keys and chain connections? Use the hosted API at provifier.com. Same SDK — just point it at our endpoint instead of running your own.

# Hosted API — no SDK needed, just curl
curl -X POST https://provifier.com/v1/commit \
  -H "X-Provifier-Key: pvf_live_..." \
  -H "Content-Type: application/json" \
  -d '{"table":"docs","rowId":"doc-7","data":"Hello world"}'

# Verify (free, no auth)
curl https://provifier.com/v1/verify/SuiTxDigest...

Decentralization & self-hosting

Hash commitments are on-chain events. Once committed, they exist permanently on the blockchain and can be verified by anyone without provifier.com.

Testing

cd packages/sdk
node --test test/sdk.test.js
# 25 tests — hashing, Merkle trees, commit/verify, tamper detection
# Uses mock chain adapters — no network access needed