Connect physical data
to TWIX proof.

No API secret has to live on our server.

The device identity is its Ed25519 public key. The meter or gateway keeps the private key, builds the canonical record, hashes it and signs the raw 32-byte hash. The collector verifies the registered public key, sequence and previous-hash chain before accepting anything.

Register only the public identity.

In Admin → Devices, create a stable device ID and paste its 32-byte Ed25519 public key as base64url. Choose a visibility policy: public, hash_only (recommended default), or private. Batches are built from one visibility class at a time so a public proof cannot accidentally expose commitments from a restricted batch.

Device ID:  meter:facility-a:main-001
Public key: n2E...base64url...
Adapter:    modbus
Visibility: hash_only

Build the exact signed object.

{
  "protocol": "twix-dap/0.1",
  "device_id": "meter:facility-a:main-001",
  "sequence": 1843,
  "schema": "energy.meter.reading/1",
  "measured_at": "2026-08-26T19:30:00Z",
  "previous_hash": "d7ac...",
  "payload": {
    "value": "14832.771",
    "unit": "kWh"
  }
}

Objects are key-sorted recursively, arrays retain order, whitespace is removed, and precision-sensitive decimal measurements are strings. JSON floating-point numbers are rejected by the reference collector.

Domain-separated commitment.

record_hash = SHA-256(
  UTF8("TWIX-DAP-RECORD-v0.1") ||
  0x00 ||
  UTF8(canonical_record_json)
)

signature = Ed25519.sign(device_private_key, raw_32_byte_record_hash)

The private key never appears in the API request.

POST the signed envelope.

curl -X POST https://validator.twixchain.com/api/ingest.php \
  -H 'Content-Type: application/json' \
  --data @signed-reading.json

{
  "record": { "...": "canonical TDAP record" },
  "record_hash": "64 lowercase hex characters",
  "signature": "base64url Ed25519 signature"
}

Success returns HTTP 201 with the accepted hash, collector receive time, sequence and visibility. Requests over 64 KiB are rejected. Replay/out-of-order sequence, bad previous hash, bad signature and unknown/expired devices are rejected.

Store the complete envelope anywhere you can afford to keep bytes.

The collector keeps a protected local copy for the reference implementation, but TDAP integrity does not depend on that specific disk. The exact signed envelope can be mirrored to ordinary shared hosting, S3-compatible object storage, Backblaze, a NAS, IPFS or archival media. When the bytes are retrieved later, the record hash, device signature and Merkle proof detect alteration.

Cross-language implementations can test themselves.

Canonical JSON:
{"device_id":"meter:test:001","measured_at":"2026-08-26T20:00:00Z","payload":{"unit":"kWh","value":"14832.771"},"previous_hash":null,"protocol":"twix-dap/0.1","schema":"energy.meter.reading/1","sequence":1}

TDAP record hash:
3770ad8a5ff06fb05403926524dae336e3d1bf122ecdb145502822ab8ce03798

Public endpoints

The meter does not need to know TWIX exists.

Reference SDKs and integration examples