VERIFY · LIVE

Trace an entry

Five steps, using only public surfaces, ending in a sentence you can state accurately about how much of the trail is verified. If you read one page on this site, read this one.

STEP 1

Find a funded source

/issuance-rules/

Pick any issuance source and read what funds it and whether it is capped.

WHAT IT PROVES · That Gold is never created without something behind it.

STEP 2

Open one entry

/explorer/

Take an entry permalink. It carries its amount, type, source and recorded time.

WHAT IT PROVES · That the movement exists as a discrete, citable record.

STEP 3

Check it is included

/api/v1/public/ledger/circulation

Confirm the entry falls inside the period the published total covers.

WHAT IT PROVES · That the total is a sum of entries like this one, under a stated definition.

STEP 4

Read the definition

/methodology/

Read what that total includes and — more importantly — what it excludes.

WHAT IT PROVES · That the figure has a method, so it is a figure rather than a number.

STEP 5

Ask whether it ties out

/proof/

Read the invariant state, and the drift beside it. Every run is published, passing or not.

WHAT IT PROVES · Exactly how much of the trail is verified — and, when a run fails, that we say so in the same place we would have said it passed.

The accurate sentence, today

“I traced one Flashy Gold entry from its funded source to its effect on a balance, and confirmed it is included in a published total under a stated definition. A nightly ledger-wide invariant runs and publishes its result, passing or failing; it is an internal control rather than a third-party audit, and balances are still stored as floating-point values.”

That sentence is the deliverable. It will get shorter as the exit criteria on the proof page go green, and this page will be updated to match the code rather than the other way around.