xDispute: International Arbitration Evidence Protection
Double XorIDA protection for international arbitration evidence. Sensitive documents are split across jurisdictions with HMAC-chained chain-of-custody.
Fast Onboarding: 3 Acceleration Levels
Traditional arbitration platform integration requires manual DID generation, arbitrator registry setup, and evidence storage configuration. Xdispute provides three acceleration levels: Zero-Click (15 sec), CLI (90 sec), Deploy Button (10 min).
| Level | Setup Time | Method | What It Does |
|---|---|---|---|
| Zero-Click | 15 seconds | Env var auto-accept | Set XDISPUTE_INVITE_CODE, execute on first use. No manual setup. |
| CLI | 90 seconds | One-line command | npx @private.me/xdispute init generates platform DID, saves to .env, registers first arbitrator panel. |
| Deploy Button | 10 minutes | One-click templates | Vercel/Netlify/Railway buttons provision arbitration platform + evidence storage. |
Example: Zero-Click
Auto-accept invite on first API call. Invite code comes from environment variable. Platform DID generated automatically. Arbitrator panel registered with threshold voting. Evidence storage configured with split custody.
# Step 1: Set invite code (from arbitration platform onboarding email) export XDISPUTE_INVITE_CODE=XD-abc123 # Step 2: Create your first dispute (auto-accepts invite) npx @private.me/xdispute create \ --title "Smart Contract Dispute" \ --claimant did:key:z6Mk...buyer \ --respondent did:key:z6Mk...seller \ --amount 1500000 # What happens automatically: # [0%] Auto-accepting invite... # [20%] Generating platform DID... # [40%] Registering arbitrator panel (2-of-3)... # [60%] Configuring evidence storage (split custody)... # [80%] Provisioning case management dashboard... # [100%] Dispute created # # ✅ Platform DID: did:key:z6Mk...xyz # ✅ Arbitrator panel registered (2-of-3) # ✅ Evidence storage configured # ✅ Case ID: dispute-001 # # Total time: ~15 seconds
Example: CLI
Explicit initialization via CLI. Platform DID saved to .env. Arbitrator panel configuration persisted. Evidence storage endpoints configured. Case management dashboard provisioned.
# Step 1: Install CLI globally npm install -g @private.me/xdispute # Step 2: Initialize platform xdispute init # Platform initialized: # ✅ Platform DID generated # ✅ Saved to .env # Ready to create disputes # Step 3: Create your first dispute xdispute create \ --title "Smart Contract Dispute" \ --claimant did:key:z6Mk...buyer \ --respondent did:key:z6Mk...seller \ --amount 1500000 \ --threshold 2 \ --total-arbitrators 3 # Output: # [0%] Validating configuration... # [20%] Registering arbitrator panel... # [60%] Configuring evidence storage... # [100%] Dispute created # # ✅ Arbitrator panel registered (2-of-3) # ✅ Evidence storage configured (split custody) # ✅ Case management dashboard provisioned # ✅ Ready to file evidence and decisions # # Total time: ~90 seconds
Example: Deploy Button
Click one button to provision arbitration platform server, evidence storage, arbitrator invite dashboard, and case analytics on Vercel/Netlify/Railway.
• Environment variables auto-configured
• Platform DID auto-generated
• Ready to create disputes immediately
• Total setup time: ~10 minutes
The Problem
International arbitration involves sharing sensitive evidence across hostile jurisdictions where local courts may order seizure, and parties may attempt to tamper with or suppress evidence.
Arbitration evidence includes trade secrets, financial records, and strategic documents. When evidence is stored in a single jurisdiction, local authorities can compel disclosure, and opposing parties can seek injunctive access.
Chain-of-custody is critical for admissibility, but traditional custody logs are easily tampered with. Parties routinely challenge evidence integrity in cross-border disputes.
The Old Way
The PRIVATE.ME Solution
xDispute uses Double XorIDA to split arbitration evidence across independent jurisdictions. HMAC-chained custody logs provide tamper-evident evidence handling records.
Evidence is Double XorIDA-split: security threshold (K-of-N) plus erasure coding for survivability. Shares are distributed to custodians in independent legal jurisdictions so no single court order can compel complete disclosure.
Every custody event (upload, access, transfer, exhibit marking) is recorded in an HMAC-SHA256-chained log with DID signatures. The chain of custody is cryptographically verifiable and court-admissible.
The New Way
How It Works
xDispute combines Double XorIDA split custody with HMAC-chained evidence handling and DID-authenticated access across jurisdictions.
Use Cases
Split evidence across jurisdictions to prevent single-court seizure.
ArbitrationHMAC-chained, DID-signed evidence handling for court admissibility.
CustodyDistribute evidence across legal jurisdictions with threshold access.
JurisdictionCryptographic verification that evidence has not been altered or suppressed.
IntegrityIntegration
import { ArbitrationVault } from '@private.me/xdispute'; const vault = await ArbitrationVault.create({ caseDid: caseDid, jurisdictions: ['CH', 'SG', 'UK'], threshold: { k: 2, n: 3 }, doubleXorida: true });
Security Properties
| Property | Mechanism | Guarantee |
|---|---|---|
| Evidence | Double XorIDA | ✓ Security + fault tolerance |
| Custody | HMAC-SHA256 chain | ✓ Tamper-evident log |
| Access | DID + threshold auth | ✓ Multi-party required |
| Jurisdiction | Multi-jurisdiction split | ✓ No single-court seizure |
Verifiable Data Protection
Every operation in this ACI produces a verifiable audit trail via xProve. HMAC-chained integrity proofs let auditors confirm that data was split, stored, and reconstructed correctly — without accessing the data itself.
Read the xProve white paper →
Ready to deploy xDispute?
Talk to Ren, our AI sales engineer, or book a live demo with our team.
Ship Proofs, Not Source
xDispute generates cryptographic proofs of correct execution without exposing proprietary algorithms. Verify integrity using zero-knowledge proofs — no source code required.
- Tier 1 HMAC (~0.7KB)
- Tier 2 Commit-Reveal (~0.5KB)
- Tier 3 IT-MAC (~0.3KB)
- Tier 4 KKW ZK (~0.4KB)
Use Cases
Deployment Options
SaaS Recommended
Fully managed infrastructure. Call our REST API, we handle scaling, updates, and operations.
- Zero infrastructure setup
- Automatic updates
- 99.9% uptime SLA
- Enterprise SLA available
SDK Integration
Embed directly in your application. Runs in your codebase with full programmatic control.
npm install @private.me/xdispute- TypeScript/JavaScript SDK
- Full source access
- Enterprise support available
On-Premise Upon Request
Enterprise CLI for compliance, air-gap, or data residency requirements.
- Complete data sovereignty
- Air-gap capable deployment
- Custom SLA + dedicated support
- Professional services included
Enterprise On-Premise Deployment
While xDispute is primarily delivered as SaaS or SDK, we build dedicated on-premise infrastructure for customers with:
- Regulatory mandates — HIPAA, SOX, FedRAMP, CMMC requiring self-hosted processing
- Air-gapped environments — SCIF, classified networks, offline operations
- Data residency requirements — EU GDPR, China data laws, government mandates
- Custom integration needs — Embed in proprietary platforms, specialized workflows
Includes: Enterprise CLI, Docker/Kubernetes orchestration, RBAC, audit logging, and dedicated support.