DEVELOPER DOCUMENTATION
Build with VeritasZK.
REST API, TypeScript SDK, MCP server, and CLI. Integrate solvency verification into any application in minutes.
30-Second Quickstart
Verify any organization's solvency tier from your terminal in one command.
npx veritaszk-cli verify --org DemoExchangeExpected output:
VeritasZK CLI v0.2.0 Organization : DemoExchange Tier : T4 Institutional Coverage : ≥ 3.0× (actual: 3.75×) Status : ACTIVE Standard : Basel III Advanced IRB Verified at : Block #15,613,711 Commitment : a1b2c3d4e5f6... ✓ Solvency verified. No financial data disclosed.
Deployed Contracts
All 4 programs are live on Aleo Testnet. Verified on-chain.
Organization identity, credentials, and delegation
Proof generation, multi-wallet support, expiry, selective disclosure
Immutable audit trail and compliance disclosure records
Multi-asset bundle threshold proofs and tier attestation
REST API
Base URL:
https://veritaszk-production.up.railway.app/api/healthIndexer health, last indexed block, uptime, deployed programs
curl https://veritaszk-production.up.railway.app/api/health/api/statsTotal orgs, active/expired/revoked proof counts
curl https://veritaszk-production.up.railway.app/api/stats/api/proofsAll tracked commitments with proof status and tier
curl https://veritaszk-production.up.railway.app/api/proofs/api/proofs/:commitmentSingle org proof details, tier, expiry, verification count
curl https://veritaszk-production.up.railway.app/api/proofs/a1b2c3d4e5f6.../api/tiersTier distribution (T1–T4 counts) across all organizations
curl https://veritaszk-production.up.railway.app/api/tiers/api/proofs/registerRegister a new commitment for the indexer to track
curl https://veritaszk-production.up.railway.app/api/proofs/registerTypeScript SDK
Full-featured SDK for verifying proofs, watching expiry, and batch-verifying organizations.
npm install veritaszk-sdkBATCH VERIFY FROM INDEXER
import { batchVerifyFromIndexer } from 'veritaszk-sdk'
const results = await batchVerifyFromIndexer([
'DemoExchange',
'TestFund',
'SampleDAO',
])
results.forEach(r => {
console.log(`${r.orgName}: Tier ${r.tier} — ${r.tierName}`)
// DemoExchange: Tier 4 — Institutional
// TestFund: Tier 3 — Strong
// SampleDAO: Tier 2 — Verified
})WATCH PROOF EXPIRY
import { watchProof } from 'veritaszk-sdk'
const unsubscribe = watchProof(commitment, (event) => {
if (event.type === 'expiring') {
console.log(`Proof expires in ${event.blocksRemaining} blocks`)
}
if (event.type === 'expired') {
console.log('Proof has expired — renewal required')
}
})
// Stop watching
unsubscribe()CHECK EXPIRY STATUS
import { isProofExpiredFromIndexer } from 'veritaszk-sdk'
const expired = await isProofExpiredFromIndexer(commitment)
if (expired) {
console.log('Proof has expired — request renewal from organization')
}MCP Server
Drop veritaszk-mcp into Claude Desktop to query solvency status from natural language.
npm install veritaszk-mcpCLAUDE DESKTOP CONFIGURATION
// claude_desktop_config.json
{
"mcpServers": {
"veritaszk": {
"command": "npx",
"args": ["veritaszk-mcp"],
"env": {
"VERITASZK_INDEXER": "https://veritaszk-production.up.railway.app"
}
}
}
}AVAILABLE TOOLS
check_org_solvencyCheck the current solvency tier for a named organization or commitment hash.
list_expiring_proofsList all proofs expiring within a specified time window (default 72h).
CLI
Terminal-based verification for CI pipelines and operator workflows.
npm install -g veritaszk-cliVerify solvency tier for a named organization
veritaszk verify --org DemoExchangeVerify by commitment hash
veritaszk verify --commitment a1b2c3...List all active proofs from the indexer
veritaszk list --activeWatch a proof for expiry events (streams updates)
veritaszk watch --org DemoExchangeShow network-wide solvency statistics
veritaszk statsArchitecture
CPI flow between the four deployed Leo programs.
PROGRAM DEPENDENCY GRAPH
veritaszk_registry.aleo
identity & credentials
veritaszk_core.aleo
proof engine · central hub
veritaszk_audit.aleo
compliance trail
veritaszk_threshold.aleo
asset bundles
CPI Note
Registry validation is enforced at the application layer due to a Leo v4.0.0 CPI finalize mapping read compiler limitation. Import statements remain in core for architectural clarity. CPI cross-program invocation is fully planned for the next Leo release.