Vexalus — Supply Chain Intelligence
Vexalus is a verifiable supply chain platform built on Vexidus L1 primitives. It provides tamper-evident shipment tracking, multi-party custody handoffs, document attestation, invoice tokenization, and a six-layer Accountability Web that makes lying about what shipped economically irrational.
Every Vexalus operation maps directly to a native Vexidus primitive. There is no new trust model to audit — the security guarantees are inherited from the underlying chain.
| Surface | Where |
|---|---|
| Marketing site | vexalus.com |
| REST API | api.vexalus.com |
| ROI simulator | vexalus.com/simulation |
| Contact | vexalus.com/contact |
How Existing Primitives Map to Supply Chain Operations
| Supply Chain Concept | Vexidus Primitive | What It Provides |
|---|---|---|
| Shipment identity | VSC-21 NFT | Unique, non-fungible token representing a physical shipment — ownership = custodianship |
| Checkpoint events | VSC-55 multi-token mint | Scoped tokens (temperature, location, condition, environmental events) minted at each checkpoint — immutable log |
| Custody transfer | VSC-88 multi-sig proposal + execution | M-of-N approval for handoff between carrier, customs, and recipient |
| Document attestation | BLAKE3 hash anchored on-chain | Bill of lading, certificates of origin, inspection reports — hash stored, content off-chain |
| Invoice tokenization | VSC-7 fungible token | Tradeable receivable backed by on-chain shipment proof |
| Independent inspection | VIDA custom:supply_chain_inspector credential | Tier 4 issuer credential — inspectors sign evidence packages, revocation makes collusion irrational |
| Compliance audit | Explorer RPC queries | Full immutable history of every checkpoint, handoff, and attestation |
The Accountability Web
The Accountability Web is six mutually-reinforcing verification layers, plus an independent inspector signature (Layer 7), that combine into a single dispute evidence package. A reviewer with the package can detect any post-hoc tampering with any layer, and the cost of faking all layers exceeds the value of the goods.
| Layer | What it proves | Mechanism |
|---|---|---|
| 1. Unit scanning | Every unit was actually scanned at pack-out | Per-unit barcode / RFID scan logged to the manifest |
| 2. Manifest hash | The unit list hasn't changed since pack-out | BLAKE3 hash of the canonical manifest anchored on-chain |
| 3. Weight continuity | The shipment's weight didn't change between checkpoints | Per-checkpoint weight observations with PASS / minor / major severity bands and a configurable tolerance |
| 4. Seal chain | The container wasn't opened in transit | Sequence of seal attestations from packing through every handoff to unpacking |
| 5. Photo / video evidence | Specific moments (packing, sealing, loading) were captured | Off-chain encrypted media with on-chain BLAKE3 anchor; client-side decrypt by authorized recipients |
| 6. Custody handoffs | Every party that held the shipment is recorded | Custody chain entries with from / to / timestamp / location |
| 7. Independent inspector | A neutral third party verified the package | VIDA-credentialed inspector signs the dispute rollup hash (Ed25519); revocation invalidates past signatures |
A dispute evidence package combines all seven layers into a single rollup BLAKE3 hash anchored on-chain. A verifier:
- Re-computes the per-layer hashes from the bundle's payloads
- Re-computes the rollup hash
- Checks it against the on-chain anchor
- Verifies the inspector's signature against their current VIDA credential
Any mismatch at any step exposes tampering. The bundle becomes legally defensible evidence in a fraction of the 60-120 days a traditional dispute resolution would take.
Environmental Envelope
The environmental envelope aggregates IoT checkpoint events (temperature, humidity, radiation, pressure, vibration, shock, atmospheric pressure, security events, power events) into a per-vertical PASS / FAIL verdict.
Six standard profiles ship with thresholds backed by public standards:
| Profile | Backed by | Highlights |
|---|---|---|
pharma_cold_chain | USP <659>, WHO 2-8°C vaccine cold chain | Tight 2-8°C band, 0.5 °C·h excursion budget, 30-min sustained cap, zero refrigeration outages |
pharma_frozen | Frozen biologics | –25 to –15°C band, any thaw is fail |
electronics | IEC 60068 | Wider band, 30g shock tolerance |
hazmat | DOT 49 CFR class 2/3 | Pressurized container thresholds, zero tamper events |
perishable_food | IATA Perishable Cargo Regulations | 0-7°C with 3 °C·h budget, 85-95% humidity |
general | Wide bands | Tamper + power are the active checks |
The aggregator uses linear-interpolation area-under-curve integration for numeric dimensions -- so a 1°C overshoot for 10 minutes counts as approximately 0.17 °C·h against the budget, not a flat fail. Severity ladder: pass (within band) → minor (excursion under budget) → major (budget exhausted or sustained-time exceeded) → fail (auto-fail subtype fired, e.g. tamper / refrigeration outage / no observations for a required dimension).
Verdicts are anchored on-chain so an auditor can confirm the verdict that was claimed at the time. This eliminates the "we'll get to it later" pattern that turns into "we lost the records" months after the fact.
Store-and-Forward IoT
Real supply chains include ocean cargo, rural distribution, and (eventually) lunar manifests -- environments where the IoT device cannot reach the network reliably. The store-and-forward agent:
- Persists every checkpoint to a local SQLite queue before any network attempt
- Drains the queue when the link returns, with per-event exponential backoff (5s base × 2^retry, capped at 1 hour)
- Detects connectivity via an optional probe so failed batches don't hammer a downed upstream
- Recovers in-flight events on process restart so a crashed gateway doesn't lose telemetry
- Uses UUID-based idempotency so a reconnect-after-blip is safe to retry without double-submitting
The API endpoint accepts a client-supplied UUID per event and dedups against a server-side mapping table. Reconnects are safe by construction.
Three-Tier Privacy
Vexalus operations encrypt shipment data into three tiers:
| Tier | Audience | What they see |
|---|---|---|
public | Anyone | Existence of the shipment, anchor hashes |
counterparty | Direct parties | Routing, status, custody handoffs -- enough to do their job |
owner | Shipping party only | Full manifest (suppliers, unit costs, volumes), commercial terms |
Encryption is AES-256-GCM with per-recipient X25519 key wraps. The recipient's secret key never leaves their device -- decryption is client-side. A Disney can ship a movie tie-in merchandise drop without the carrier seeing what's inside; a Walmart can move private-label inventory without exposing supplier negotiation terms.
SDK Overview
npm install @vexidus/vexalus-sdk
import { Vexalus } from '@vexidus/vexalus-sdk';
const vexalus = new Vexalus({ rpcEndpoint: 'https://api.vexalus.com' });
// Create a new shipment (mints a VSC-21 NFT)
const shipment = await vexalus.shipments.create({
id: 'SHP-2026-00441',
origin: 'Shanghai, CN',
destination: 'Rotterdam, NL',
cargo: 'Electronics — 240 units',
});
// Add a checkpoint (mints VSC-55 tokens for this event)
await vexalus.checkpoints.add({
shipmentId: 'SHP-2026-00441',
type: 'TemperatureReading',
value_celsius: 18,
});
// Aggregate an environmental envelope verdict
const verdict = await vexalus.environmental.aggregate({
shipment,
profileName: 'pharma_cold_chain',
});
// Compile a dispute evidence package (Accountability Web)
const evidence = await vexalus.manifest.compileDisputeEvidence({
shipment,
manifest,
weightObservations,
sealAttestations,
evidenceAttachments,
custodyHandoffs,
});
// → rollupHash binds all six layers; anchor it on-chain for tamper-evident dispute defense
REST API
Base URL: https://api.vexalus.com
| Endpoint | Purpose |
|---|---|
/v1/shipment | Create / retrieve shipments |
/v1/checkpoint | Add / list checkpoints |
/v1/custody | Propose / approve custody handoffs |
/v1/document | Attest / verify document hashes |
/v1/finance | Tokenize / query invoices |
/v1/audit | Full audit trail for a shipment |
/v1/party | Counterparty identity registry |
/v1/dc | Distribution-center entities (Role 4) |
/v1/stores | Retail-store entities (Role 5) |
/v1/inventory | Per-DC inventory snapshots + on-chain attestation |
/v1/network-events | Cross-dock + allocation events |
/v1/shipments/encrypted | Privacy envelope prepare / anchor / verify |
/v1/manifest | Accountability Web — manifest anchor, weight check, seal-chain verify, dispute evidence compile |
/v1/environmental | Environmental envelope aggregate / anchor / verify |
/v1/contact | Public contact form intake |
Swagger UI: https://api.vexalus.com/v1/docs
OpenAPI JSON: https://api.vexalus.com/v1/openapi.json
Five-Role Data Model
| Role | Entity | What they do |
|---|---|---|
| 1. Manufacturer / Producer | Originating party | Mint shipments, attach packing manifests |
| 2. Carrier / Transport | Custodian during transit | Record checkpoints, propose handoffs |
| 3. Buyer / Receiver | Destination party | Approve handoffs, scan-and-verify on receipt |
| 4. Distribution Center | DC NFT entity | Cross-dock events, inventory snapshots, fan-out to children |
| 5. Retail Store | Store NFT entity | Allocation decisions, store-level inventory |
A parent shipment can fan out into typed children allocated to specific stores, with per-SKU quantity validation that the fan-out preserves the total.
ROI Simulation Engine
The simulation engine at vexalus.com/simulation is a white-box ROI calculator. Each savings wedge is a pure function with sanity caps preventing compounding-fractions overestimation. Eight wedges (dispute elimination, compliance automation, working capital acceleration, safety stock reduction, manual reconciliation elimination, insurance premium reduction, distribution routing optimization, counterfeiting / shrinkage reduction) sum to a total annual savings figure traceable line-by-line.
Canonical Disney and Walmart profiles tie out to industry-published baseline numbers (Walmart dispute costs hit the $2-4B published range, sanity-capped). The prospect's analyst can plug their own numbers in and rebuild the calculation from first principles. See the Disney / Walmart enterprise case study via the Vexalus contact form for the full narrative.
IoT Edge Agent
Vexalus includes a lightweight IoT agent for edge device checkpoint submission. The agent runs on any Linux device (including Raspberry Pi) and persists every event to a local SQLite queue before any network attempt -- so a process crash or unexpected reboot does not drop telemetry.
# Install and configure the agent
npm install -g @vexidus/vexalus-iot
vexalus-agent init --device-id IOT-2026-001 --keypair ./device-key.json
# Start streaming checkpoints
vexalus-agent start \
--shipment SHP-2026-00441 \
--interval 60 \
--sensors temperature,humidity,gps
The agent submits signed checkpoint batches at the configured interval. If connectivity is lost, events queue locally and drain on reconnect with exponential backoff. The agent process can pause / resume / flush-soon programmatically, and stuck forwarding events recover on restart.
Cost Model
Vexalus operations use standard Vexidus gas pricing (~10 nanoVXS per unit). A complete shipment lifecycle — creation, four checkpoints, two custody handoffs, two document attestations, an environmental envelope verdict, a manifest anchor, and an invoice tokenization — costs approximately $0.016 at current VXS testnet pricing.
| Operation | Approximate Cost |
|---|---|
| Create shipment (VSC-21 mint) | ~$0.0002 |
| Checkpoint (VSC-55 mint) | ~$0.0002 |
| Custody handoff (VSC-88 multisig) | ~$0.0004 |
| Document attestation (hash anchor) | ~$0.0001 |
| Manifest anchor (Accountability Web Layer 2) | ~$0.0001 |
| Environmental envelope verdict anchor | ~$0.0001 |
| Dispute evidence rollup anchor | ~$0.0001 |
| Invoice tokenization (VSC-7 mint) | ~$0.0002 |
A Disney / Walmart-scale dispute at industry-baseline cost is in the $10K-50K range and takes 60-120 days. The equivalent Vexalus dispute defense produces the evidence package as a byproduct of normal operation at less than 2 cents per shipment.
Multi-Zone Deployment
The Vexalus data model includes a zone field on all entities (default: "earth"). This field is future-proofed for multi-zone deployments — enabling the same shipment tracking infrastructure to operate across logistically distinct domains without changes to the core protocol.
Current Status
| Capability | Status |
|---|---|
| Five-role data model (Manufacturer / Carrier / Buyer / DC / Store) | Live |
| VSC-21 shipment NFTs + VSC-55 checkpoint events | Live |
| VSC-88 multi-sig custody handoffs | Live |
| BLAKE3 document attestation | Live |
| VSC-7 invoice tokenization | Live |
| Privacy envelope (AES-256-GCM + X25519 + three-tier disclosure) | Live |
| Distribution Center + Store + Inventory entities | Live |
| Cross-dock + Allocation events | Live |
| Accountability Web (7 verification layers + dispute compiler) | Live |
| VIDA inspector credential type (Layer 7) | Live |
| Environmental envelope aggregator (6 vertical profiles) | Live |
| Store-and-forward IoT agent with durable queue + retry | Live |
| ROI simulation engine | Live (vexalus.com/simulation) |
| Public marketing site + contact form | Live (vexalus.com) |
| Integrated dashboard UI (shipment map + timeline overlay) | In progress |
| ERP / WMS integration adapter templates | Planned |
| RFID / NFC integration guide | Planned |
Key Links
| Resource | URL |
|---|---|
| Vexalus marketing site | vexalus.com |
| API | api.vexalus.com |
| ROI simulator | vexalus.com/simulation |
| Contact | vexalus.com/contact |
| API documentation | api.vexalus.com/v1/docs |
| VIDA inspector framework | VIDA Identity Protocol |
| Token Standards | VexForge Token Overview |
| Governance / Multi-sig | VSC-88 Multi-Sig Wallets |