Manifest digest
ValidThe SHA-256 digest was recalculated from the downloaded manifest bytes.
ContentLedger verification
This page recalculates the stored origin-evidence manifest digest, checks its canonical serialization, and independently reviews its archive, version-chain, timestamp-proof, and digital-signature references.
https://webhombres.com/best-practices-for-backend-database-optimization/
urn:uuid:5b61b0dd-bf70-483a-a243-d024b5b01c5fc3c25d3bd1b3af7e5a5c25c1412ccc2d3594ae7762eb2ee86735c1dac476e237Download canonical manifest Open Wayback snapshot View record JSON-LD
The SHA-256 digest was recalculated from the downloaded manifest bytes.
The manifest matches the deterministic ContentLedger RFC 8785 serialization profile.
The associated Wayback URL passed the plugin’s HTTP availability check.
Any previous-manifest digest resolves to an earlier sealed record in this ledger.
The current WordPress content produces the recorded canonical-content digest.
The protected public key verifies the JWS and its claims bind this exact manifest digest and ledger entry.
The JWS issuedAt value is a signed claim, not an independent timestamp. The verified did:webvh log establishes append order and recorded authorization intervals, but does not by itself provide trusted external time.
Verification methoddid:webvh:QmNg62SQGX2D2ABydNFXauFHMWf2cNXpN2uMKx6bKXvmoV:webhombres.com#d6D_DnQ8-ym-yjTuVUVW3toc7RMcYPRiMBE-nyJLN8E
Cryptographic validity, historical did:webvh authorization, authorization at a claimed signing time, and current assertion authorization are separate results. None independently establishes legal ownership, human identity, original authorship, first publication, or a trusted signing time.
| Artifact | Status | Digest or location |
|---|---|---|
| Content Digest | Recorded |
e60115e0481954530dc3ca6dca9da6bafdc59e293fa4147cdc76e1e8bc561ad2 |
| Manifest | Sealed |
c3c25d3bd1b3af7e5a5c25c1412ccc2d3594ae7762eb2ee86735c1dac476e237 https://webhombres.com/?wal_manifest=5b61b0dd-bf70-483a-a243-d024b5b01c5f
|
| Ed25519 JWS signature | Verified |
c3c25d3bd1b3af7e5a5c25c1412ccc2d3594ae7762eb2ee86735c1dac476e237 Download compact JWS
|
| OpenTimestamps proof | Pending |
3ff325b71aa5ce8d9c6db13258470e66c67b695d0710d3e28a02709230c16913 Download .ots proof
|
| OpenTimestamps proof | Bitcoin attested |
aa9fda47dc967c9ebebad9267413548aaa5c304d32291657a84308114aafc79d Download .ots proof
|
| OpenTimestamps proof | Bitcoin attested |
f3fba936b51da5a1aa79f728b87ff23034eb42fbc4f86a4fec1f1f07497b25cf Download .ots proof
|
| OpenTimestamps proof | Bitcoin attested |
d307cd03d1bc1ba896200d7ed714a86f719b39c07c27c52cbd0e5e6396e8fa15 Download .ots proof
|
| Representation Digest | Recorded |
f27dfda169693715d2a5688e5d8ef4c1d778a1d3711152d5f62fdae0b595cd99 https://webhombres.com/best-practices-for-backend-database-optimization/
|
| Wayback Snapshot | Verified | https://web.archive.org/web/20260919174525/https://webhombres.com/best-practices-for-backend-database-optimization/ |
Download the canonical manifest without modifying it and calculate its SHA-256 digest with a local tool. The result must equal the manifest digest printed above.
sha256sum wp-contentledger-5b61b0dd-bf70-483a-a243-d024b5b01c5f.json
After installing the official OpenTimestamps client, independently verify a downloaded proof against the manifest digest:
ots verify -d c3c25d3bd1b3af7e5a5c25c1412ccc2d3594ae7762eb2ee86735c1dac476e237 wp-contentledger-5b61b0dd-bf70-483a-a243-d024b5b01c5f-PROOF-ID.ots
The signature is an RFC 7515 compact JWS using the fully specified RFC 9864 Ed25519 algorithm and an RFC 8037 public JWK. An independent verifier should validate the JWS, confirm its manifestDigest claim equals the SHA-256 above, and resolve the kid against this website identity's did:webvh JSONL log.