Skip to content
Answers

A signed Tickerz number can be checked without asking Tickerz.

Each print is a signed report: canonical JSON, its SHA-256 hash, and an Ed25519 signature by the publisher key in tickerz.com/.well-known/tickerz-signer.json. A public recount counts it again and co-signs the same hash. With a matching recount and no dispute, a print becomes final at the first daily oracle run after its 24 hour window closes.

Five checks.

  1. Read the rule: GET https://tickerz.com/api/v1/indices/{ticker}/rule returns the rule, its version and its hash. The rule names the source, the query, how it is counted and the settlement rights.
  2. Read the report: GET https://tickerz.com/api/v1/indices/{ticker}/report (add ?period= for an older one) returns the report as canonical JSON with its hash and signatures.
  3. Check the hash and signature: sha256 of the canonical JSON equals the hash, and the publisher's Ed25519 signature covers "tickerz-report-v1:" followed by the 32 hash bytes. The publisher key is in https://tickerz.com/.well-known/tickerz-signer.json.
  4. Check the recount: the public recount in github.com/tickerzhq/tickerz-open counts the print again from the source and co-signs "tickerz-cosign-v1:" plus the same hash with its own key, also listed in the signer file.
  5. Check the status: a co-signed print with no dispute becomes final at the first oracle run after its window closes: 24 hours for a daily, weekly or monthly print, 2 hours for an hourly one. A correction is a new signed report that names the one it corrects; a print is never edited.

The browser can do it for you.

https://tickerz.com/signed lists every signed number with its status (signed, recounted, final) and a Verify it yourself button that rebuilds the canonical JSON and checks the hash and every signature in the browser.

The daily Close also carries an OpenTimestamps proof in Bitcoin: GET https://tickerz.com/api/v1/indices/proof?day=YYYY-MM-DD returns canonical_json, digest_sha256 and the proof.

Each number is signed by Tickerz and recounted in public. The feed on Solana comes next.

Asked often

How do I check a Tickerz signature?
Hash the report's canonical JSON with SHA-256 and verify the publisher's Ed25519 signature over "tickerz-report-v1:" followed by the 32 hash bytes, against the key in https://tickerz.com/.well-known/tickerz-signer.json.
When is a Tickerz number final?
When the public recount has co-signed it, no dispute was filed and its window has closed (24 hours for a daily, weekly or monthly print, 2 hours for an hourly one): the next oracle run makes it final.
Is the Tickerz oracle on Solana?
Each number is signed by Tickerz and recounted in public. The feed on Solana comes next.