Industry Solutions

The Relative Sun protocol provides dedicated infrastructure for enterprise logistics and compliance, ensuring critical state transitions achieve Absolute Thermodynamic Finality. This prevents double-spending of titles and systemic drift across global supply chains.

1. The Standard Payload

Your internal systems must format the metadata according to the official JSON schema before hashing.

Standard eBL Schema:

{
  "schema": "DCSA_eBL_v2",
  "documentStatus": "ISSUED",
  "transportDocumentReference": "REL-SUN-99821A",
  "carrierCode": "MSCU",
  "vesselName": "EVER GIVEN"
}

2. Zero-Knowledge Proof Generation

To maintain enterprise privacy, you never upload the raw JSON to our servers. Your local client must serialize the JSON and compute a local SHA-256 hash (The Zero-Knowledge Hash).

Local WebCrypto Implementation:

const payloadString = JSON.stringify(payloadData);
const encoder = new TextEncoder();
const data = encoder.encode(payloadString);
const hashBuffer = await crypto.subtle.digest("SHA-256", data);

POST

/v1/enterprise/dcsa/stamp

3. The Epoch Injection

Submit the resulting hash to your dedicated industry routing lane. Our VDF engine will immediately upgrade it to a Temporal Anchor (T-Index) and queue it for batching. This ensures your supply chain events cannot be reordered.

Headers:

Authorization: Bearer [Your_Enterprise_API_Key]

Payload:

{
  "client_hash": "a1b2c3d4e5f6g7h8i9j0...",
  "schema_type": "DCSA_eBL_v2"
}

Once settled, your system can download the portable HTML visual certificate to pass along to external auditors, regulatory agencies, or downstream partners.