Explorer details
Open validator details to confirm the master key, network, ledger index, version, domain verification, and agreement metrics from the Post Fiat explorer.
Core identity
Validator Facts
The bounded facts below are the quickest way to confirm whose validator this is, which key it uses, which network it serves, and where proof and updates live.
- Operator
- @wizbubba
- Network
- Post Fiat testnet
- Validator public key
- nHUzc5XzsmweRV6aNyUQJD5eRUM4TT4tVCBv5DKx6T7Buq4gn9Lr
- Domain proof
- /.well-known/pft-ledger.toml
- Status
- Awaiting explorer data
- Version
- Awaiting explorer data
- Location
- North America
- Last updated
- Live status fields update from the explorer source at page load when available.
Proof packaging
Verification & External Proof
Each proof surface has a job. This page links them directly and states what each one confirms, instead of leaving visitors or models to infer that on their own.
Validator board
Open the validator board to inspect the broader validator set and compare this validator against the rest of the testnet roster.
Network overview
Open the Post Fiat explorer to review the broader network surface, navigate validator data, and inspect the current explorer homepage.
Domain attestation
Open the TOML proof file to confirm the domain-controlled validator attestation published at this site's .well-known path.
Machine-readable identity
Open validator.json to retrieve the site's stable identity, source links, and operator metadata in JSON form.
Machine-readable status
Open status.json to inspect the latest published snapshot fields and the source URL used to refresh them.
Explorer-backed metrics
Live Status
This section only renders approved explorer-backed fields. If the source cannot be fetched, values stay explicitly marked as unavailable rather than guessed.
Master Key
Unavailable
Uptime
Unavailable
Server State (Full)
Unavailable
Inferred conservatively from the explorer payload when current ledger data is available.
Ledger
Unavailable
Version
Unavailable
Domain Verified
Unavailable
Agreement (1H)
Unavailable
Agreement (24H)
Unavailable
Agreement (30D)
Unavailable
Last status refresh
Unavailable
Source: approved explorer details page.
Ongoing updates
Change Log
The change log is the running public record for validator site updates, proof changes, and release notes. It has its own crawlable page and now auto-loads recent repository commits.
The homepage is the verification layer. The change log page is the chronological layer. Use it when you want to see what changed, when it changed, and which repo update introduced it.
Current change log coverage:
- validator site revisions
- proof and status source notes
- repository-backed release entries
Trust questions
FAQ
This section answers the obvious first-pass questions a person or model will ask when evaluating the validator surface.
What does this validator do?
It is a Post Fiat testnet validator operated by @wizbubba. This site exists to package the validator's identity, proof links, and status context in one place.
How do I verify this public key?
Compare the public key shown here against the explorer details page, the machine-readable JSON endpoints on this site, and the domain attestation file in /.well-known/.
What is the change log?
It is the running public log for validator-related updates on this domain. It complements the homepage by giving chronological context instead of only a static summary.
Where do the status metrics come from?
The live status section is backed by the Post Fiat explorer source for this validator. If the explorer is unavailable, the site shows Unavailable instead of filling values from guesses.
How often is this page updated?
Static site content updates when the repo changes. The live status section refreshes from the approved explorer source on page load whenever the source is reachable.
What is this page not?
This is a validator trust surface, not a full explorer and not a general Post Fiat network explainer. It is intentionally narrow: identity, proof, status, and updates.
Endpoints
Machine-readable endpoints
These files are intended for scripts, crawlers, and downstream trust tooling that needs a stable JSON surface instead of scraping HTML.
/validator.jsonStable identity, operator, public key, verification links, and site purpose.
/status.jsonLatest published snapshot fields, source URL, and snapshot refresh timestamp.