Protocol Overview

Veyroq is the chain-agnostic selective disclosure, audit, and tax-compliance infrastructure layer built for institutional digital asset treasuries across EVM and confidential settlement networks.

The Core Breakthrough: Confidential transactions and private payroll allow companies to protect trade secrets and employee privacy. Veyroq provides the cryptographic bridge that allows certified accountants (PwC, EY, Deloitte, internal CFOs) to selectively audit those private records and mathematically prove zero omissions without broadcasting trade secrets to public block explorers.

Why Enterprises Need Veyroq

When an institutional treasury moves funds on a public blockchain, competitors and suppliers can analyze every transfer. However, if they operate inside a completely opaque network, traditional corporate compliance breaks down:

  • IRS & HMRC Mandates: Corporations must submit verified general ledgers backing every expense and payroll deduction under penalty of perjury.
  • Audit Certification: External auditors cannot sign off on balance sheets if transactions could have been selectively deleted from an off-chain spreadsheet.
  • Mixing & Anonymity Red Flags: Pure anonymity pools or mixers trigger severe compliance penalties from banking partners and regulatory bodies.

Chain-Agnostic Multi-Network Design

Veyroq is independent of any single Layer-1 or Layer-2 network. The same VeyroqRegistry.sol settlement contract, Scoped View Key specification, and client-side Merkle reconciliation engine operate identically across EVM networks—including Base, Monad, Arbitrum, Ethereum, and confidential EVM enclaves—allowing corporate treasuries to unify multi-chain audit exports inside a single cockpit.

Architecture & Enclaves

Veyroq operates across two strictly separated execution domains to guarantee both mathematical integrity and absolute confidentiality: the on-chain settlement registry and the local client runtime.

Dual-Domain Execution Model

Confidential payment rails encrypt transaction amounts, counterparties, and business memos before state settlement. Veyroq bridges this encrypted on-chain state with institutional audit requirements across any supported EVM network.

Layer Environment Responsibility Data Exposure
Settlement Registry Multi-Chain EVM / Enclave Maintains VeyroqRegistry.sol across supported chains (Base, Monad, Arbitrum, Arc), validates Merkle root commitments, enforces auditor scopes. Only root hashes & timestamped auditor authorizations. Zero plaintexts.
Local Client Runtime In-browser Web Crypto API / WASM Accepts Scoped View Key, decrypts encrypted RPC transaction logs, builds local Merkle tree, generates GAAP CSVs. 100% ephemeral in local RAM. Zero keys or financial data leave browser.

Execution Boundaries & Information Flow

Corporate treasuries retain complete cryptographic sovereignty. View Keys and decrypted ledgers exist purely within ephemeral browser RAM and are never transmitted across untrusted external networks.

The Zero-Custody Guarantee

Veyroq is engineered on a strict zero-knowledge, zero-custody foundation: no backend databases, no key custody, and zero plaintexts stored off-device.

Zero-Custody Architecture: Veyroq servers never see, handle, or store your private spending keys or Scoped View Keys. All cryptographic operations occur client-side in your local browser sandbox.

Zero Central Database

Traditional SaaS accounting tools store corporate financial statements on centralized cloud databases vulnerable to subpoenas and data breaches. Veyroq operates completely stateless: the application is delivered as a client-side web application that speaks directly to the blockchain RPC node.

Ephemeral In-Memory Execution

Decrypted transaction records exist solely within volatile JavaScript RAM. Closing or refreshing the browser tab immediately purges all plaintext data and cryptographic session keys.

EIP-4361 SIWE Non-Custodial Verification Standard

Veyroq implements strict Sign-In with Ethereum (EIP-4361) structured data challenge/response architecture to verify treasury ownership without exposing assets:

  • Zero Asset Transfer Guarantee: Verification messages contain no token allowances, no Permit/Permit2 functions, and no contract call execution. Wallets (such as Rabby or MetaMask) simulate the signature with "No balance change" and "No token access granted".
  • Replay Attack Immunity: Every verification challenge requires a single-use cryptographically random 32-byte nonce generated by the backend with a strict 15-minute TTL. Upon first verification, the nonce is burned permanently.
  • Domain & Chain ID Binding: The signature is mathematically bound to the application origin and Arc L1 (Chain ID: 5042002), preventing cross-domain relaying or phishing exploitation.
  • Hardware Multisig Verification: Compatible with Gnosis Safe (EIP-1271) and hardware keys (Ledger, Trezor). Ledger screens decode the human-readable text payload directly on the physical secure element.

CFO Quickstart: 4-Step Audit Run

Follow this streamlined 4-step workflow to conduct a certified audit reconciliation session using the Veyroq Auditor Cockpit.

1. Authenticate Institutional Session

Launch the Auditor Cockpit ↗, select your target settlement network (e.g., Base, Monad, Arbitrum, or Arc), and click "Connect Wallet" to authenticate via Privy Email OTP or an EIP-1193 wallet (MetaMask, Ledger, Safe). No seed phrases are transmitted.

2. Enter Scoped View Key

Paste your quarterly Scoped View Key (e.g. vk_live_7a9f...). You can also click "Load Demo Credentials" to populate pre-configured enterprise test accounts.

3. Run Local Decryption & Proof Verification

Click "Decrypt & Verify Ledger". The engine queries encrypted logs from your selected network RPC, decrypts all transactions in local browser memory, computes SHA-256 leaves, and matches the root against VeyroqRegistry.sol.

4. Export 1-Click GAAP Ledger

Download standard double-entry journal CSVs pre-mapped for QuickBooks, Xero, or an immutable cryptographic Audit Certificate JSON signed with Merkle inclusion proofs.

Understanding Scoped View Keys

A Veyroq Scoped View Key is an asymmetric cryptographic credential derived from an institution's master treasury account. It possesses strict read-only decryption capability.

Scoped View Key Structure

View Keys can be restricted to specific settlement networks, calendar quarters, block boundaries, or counterparty classifications:

// Scoped View Key Specification
struct ScopedViewKey {
    uint256 chainId;          // Target EVM network (Base, Monad, Arbitrum, Arc, etc.)
    bytes32 masterKeyId;      // Derived enterprise account identifier
    uint256 validFromBlock;   // Starting block boundary (e.g. Q3 2026)
    uint256 validUntilBlock;  // Ending block boundary
    bytes32 allowedScopeHash; // Restricts decryption to Payroll or Supplier scopes
}

Spending Inability Guarantee

Unlike a private spending key, a Scoped View Key cannot sign transfers, authorize smart contracts, or move funds. Even if an auditor's machine were compromised, zero treasury assets can be moved.

Cryptographic Completeness Proofs

Tax authorities reject arbitrary spreadsheets because rows could be deleted to conceal taxable events. Veyroq mathematically guarantees Merkle Completeness.

The Zero-Omissions Dilemma

In traditional accounting, proving that an enterprise has not omitted transactions is difficult. Veyroq solves this by hashing every transaction leaf and committing the Merkle root on-chain before the audit period closes.

// 1. Each decrypted transaction is hashed as a unique leaf
bytes32 leaf = keccak256(abi.encodePacked(txId, blockNumber, grossAmountUSDC, recipient));

// 2. The Merkle root is verified against on-chain block commitment
bool isVerified = MerkleProof.verify(proof, onChainRoot, leaf);
require(isVerified, "Veyroq: Proof of completeness mismatch");

Mathematical Root Verification

If any party modifies a single cent in the ledger or omits a transaction, the calculated Merkle root fails to match the immutable hash committed to VeyroqRegistry.sol.

On-Chain Proof Verification

Any regulator, lender, or tax auditor can verify an inclusion proof without possessing the organization's private keys or sensitive payroll data.

Verification Flow

External verifiers query the public smart contract method with the cryptographic proof path:

// Call VeyroqRegistry.verifyTransactionInclusion
bool valid = registry.verifyTransactionInclusion(
    0x71C8b46B08639f70efA4C34Db895C989C7Fa22Ec, // Organization
    1,                                          // Proof ID (Q3 FY2026)
    0xa1e4f9b8c2d11099432857492cdaee11b40289..., // Transaction leaf hash
    proofPath                                   // Merkle sibling hashes
);
// Returns true if transaction was part of the certified ledger

VeyroqRegistry.sol Specification

VeyroqRegistry.sol is a standard, chain-agnostic Solidity settlement contract deployable on any EVM-compatible network (Base, Monad, Arbitrum, Ethereum, Arc). It governs auditor authorizations, Merkle root commitments, and public inclusion proofs.

Core Function Interfaces

Function Caller Description
authorizeAuditor(address auditor, uint256 validUntil, bytes32 scopeHash) Organization Authorizes an accounting firm to commit audit proofs for an organization until timestamp expiry.
revokeAuditor(address auditor) Organization Immediately terminates auditor permissions on-chain.
commitAuditProof(address org, bytes32 root, uint256 start, uint256 end, uint256 txCount, bytes32 meta) Authorized Auditor or Org Anchors immutable Merkle root proof, transfers 25 USDC protocol fee to treasury.
verifyTransactionInclusion(...) Public (View) Verifies that an individual transaction leaf hash is included in a committed audit proof.

Supported Networks & Registry Deployments

Adding a new EVM network requires zero changes to the client decryption engine—only deploying VeyroqRegistry.sol and registering the chain RPC and USDC token address:

Network Settlement Rail Registry Status / Address
Base Native USDC (EVM L2) Supported · Deterministic Deployment
Monad Native USDC (Parallel EVM L1) Supported · Deterministic Deployment
Arbitrum & Ethereum Native USDC (EVM) Supported · Deterministic Deployment
Circle Arc (Testnet) Native USDC Gas & Confidential Rail (5042002) 0x56204E81...6fE2 ↗

Foundry Automated Testing Suite

The smart contract suite is thoroughly tested with Foundry, achieving 100% test pass rates across authorization, commitments, and Merkle verification.

Test Suite Execution

$ cd contracts && forge test -vvv
[PASS] test_AuthorizeAuditor() (gas: 111547)
[PASS] test_CommitAuditProof_ByAuthorizedAuditor() (gas: 358579)
[PASS] test_CommitAuditProof_ByOrganization() (gas: 307172)
[PASS] test_MerkleInclusionVerification() (gas: 256818)
[PASS] test_RevertIf_ExpiredAuditor() (gas: 120114)
[PASS] test_RevertIf_UnauthorizedSubmitter() (gas: 47631)
[PASS] test_RevokeAuditor() (gas: 150141)
Suite result: ok. 7 passed; 0 failed; 0 skipped

GAAP / IFRS Worksheets

Veyroq translates on-chain confidential transaction hashes into standard double-entry journal entries recognized by corporate accounting frameworks.

Double-Entry Journal Translation

Transaction Classification GAAP Debit Account GAAP Credit Account Tax Treatment
CONFIDENTIAL_PAYROLL Payroll Expense (W-2 / 1099) Digital Assets (USDC Operating) Ordinary Business Expense
SUPPLIER_SETTLEMENT Accounts Payable / COGS Digital Assets (USDC Operating) Vendor Deductible Expense
TREASURY_REBALANCE Short-Term Investment (BUIDL) Digital Assets (USDC Operating) Balance Sheet Asset Transfer
GAS_AND_NETWORK_FEES Blockchain Transaction Expenses Digital Assets (USDC Gas) Operating Expense

QuickBooks & Xero Sync

The Veyroq Exporter engine dynamically formats verified ledger records into native CSV templates recognized by enterprise ERPs.

Supported Accounting Formats

  • QuickBooks Online: Generates General Journal format with automated Debit/Credit balancing and transaction reference IDs.
  • Xero Accounting: Formatted with Xero Manual Journal headers (*Date, *AccountCode, *TaxType, Reference).
  • Cryptographic Audit Certificate: Exports a self-contained JSON file containing the root hash, block range, and transaction signatures suitable for digital submission to the SEC or IRS.