Give this to your AI agent to get started

Copy this into ChatGPT, Claude, Meta Muse, Gemini or any AI agent. It connects to our AI agent, Nexus to get you started.

What can I do with Provenance Rails at cymetica.com/provenance?
EventTrader
Financial AI Models
PAPER
Menu
Dark Mode
Plain English Mode
PAPER TRADING MODE — Enable real trading on your Account page
Back

Provenance Rails

Prove who registered a research artifact, when, and under which licence. Hash your file, get an attestation signed by the platform's attestor wallet, and let anyone verify a copy by its hash. The content itself never leaves your machine.

Stage 1 of the VSB Layer 1 proposal · live

Attest an artifact

Requires a signed-in account. Attestations are currently free.

Computed hash: —

Verify a copy

Looks up every attestation on that hash and re-checks each signature on the server. You can also verify independently: recover the signer of the canonical JSON with any Ethereum wallet tool.

My attestations

Sign in to see the attestations you issued.

Attestation

How it works

  • Hash, don't upload. Your browser computes the SHA-256 of the file or text; only the hash, a title and a licence reference are sent.
  • Signed by a platform wallet. The canonical payload (hash, title, author, licence, lineage, timestamp) is signed EIP-191 by the attestor address shown below. Signing a message costs nothing and moves nothing.
  • Verify anywhere. Recompute the hash of your copy, look it up here or at GET /api/v1/provenance/verify?sha256=…, and recover the signer from the signature yourself if you prefer not to trust this page.
  • Lineage. A derivative points at the attestation it came from, so a chain of research outputs reads as one record.
  • Licence references. SPDX ids or your own terms URL are recorded in the signed payload. The attestation records the reference; it does not grant or price a licence.
  • Anchoring. off-chain signed; on-chain anchoring not yet enabled. When enabled, a daily Merkle root of all attestations is written to Ethereum and each attestation gets a proof.
Attestor address
…
Signature scheme
EIP-191 personal_sign over canonical JSON
API
POST /api/v1/provenance/attest · GET /api/v1/provenance/verify?sha256= · GET /api/v1/provenance/{id}

Where this is going

This is Stage 1 of feature request #792: provenance rails that a future Layer 1 for the VSB ecosystem would host natively. The chain itself (post-quantum signatures, ET10 settlement, open to builders) is roadmap work and goes through its own engineering and compliance gates before anything else is said about it. Stage 1 stands on its own: it works today, on Ethereum-compatible signatures, with nothing to buy.