How we know what we publish

tempowiki is only as good as its sourcing. The goal is simple: every meaningful claim should be traceable to a primary source, dated, and honest about how confident we are. Here is how that works.

Primary sources first

We prioritise primary sources — Tempo's official site and docs, the protocol's GitHub and TIPs, issuer attestations, company announcements, and on-chain explorers — over secondary coverage. Each key fact stores the source URL and the date it was retrieved, rendered as a citation on the page.

Multi-model cross-checking

Research is cross-checked across multiple independent models and web search, run offline rather than at page load. When the models and sources agree, confidence is high. When they disagree, the disagreement itself becomes the signal: the claim is downgraded or held back. No fact is published just because one model asserted it.

Confidence, not false precision

• High — multiple independent primary sources agree.
• Medium — a single credible source, or partial corroboration.
• Low — reported but unconfirmed; shown with a caveat.

Named gaps over guesses

Tempo is new and some disclosures are thin — funding details, full team rosters, audit status. Where we can't verify, we do not guess. We list a named gap so you can see exactly what is unconfirmed. We never assert a native token or airdrop, because none exists.

Live data, cached locally

Quantitative figures — supply, TVL, throughput, validator counts — come from provider feeds that sync into our data layer with an as-of timestamp. Pages read the local copy, so a slow or rate-limited upstream shows the last known value rather than breaking. Curated baselines mean nothing renders empty while sources warm up.

Corrections

Found an error? Tell us with a source. Verified corrections are applied and recorded in the Pulse change feed. Neutrality and accuracy beat speed every time.