EVIDENCE, NOT A BADGE

Follow the evidence.

Check the asset, the right, the record, and the exit separately. One report should never be treated as a guarantee of everything a project claims.

01

Identify the assertion

Make the statement specific enough to test: the party, quantity, unit, obligation, and effective date.

02

Respect the scope

Distinguish an operating report, an independent review, a legal document, and a software assessment. Each addresses a different question.

03

Keep gaps visible

Record missing evidence, timing differences, and unresolved discrepancies. An organized file is useful, but organization alone is not proof.

Capacity is not inventory

EIA distinguishes storage capacity, actual gas in storage, base gas, working gas, and deliverability. A facility’s maximum capacity should not be presented as an available quantity allocated to digital claims. The relevant amount and date need their own evidence. [Source]

An evidence register with purpose

For each important assertion, record the document, origin, effective period, version, scope, reviewer, and limitations. Compare like-for-like quantities and dates. A mismatch should trigger a documented question, not an automatic accusation or an assumption that the records agree.

What this website does not verify

GasTokenization.com does not inspect facilities, certify reserves, audit token contracts, verify ownership, or endorse an issuer. The framework below is educational. Real conclusions about title, backing, enforceability, or suitability require current project-specific evidence and qualified review.

GO A LEVEL DEEPER

Field notes worth exploring.

All field notes

Good questions are a powerful starting point.

Build your understanding, one clearly explained concept at a time.

Explore the field notes
↑