Whytegod Protocol

Protocol Records

A record is the fundamental object of the Whytegod Protocol. Records allow any data to be proven as existing at a specific point in time without revealing the data itself.

What a Record Is

• A cryptographic hash (SHA-256)
• A timestamp
• An immutable anchor reference
• Optional human-readable metadata

The protocol never stores raw files, messages, or documents. Only hashes are used.

What a Record Is Not

• Not stored user data
• Not encrypted content
• Not reversible
• Not editable once anchored

Record Lifecycle

1. User generates a hash from their data
2. The hash is submitted for anchoring
3. An anchor event finalizes the record
4. The record becomes permanently verifiable

Anchoring

Anchoring is the act of committing a hash into a public, time-ordered reference.

Anchoring requires WGD to prevent spam and abuse. Verification does not require WGD.

Verification

Any person can verify a record by:

1. Hashing the original data again
2. Comparing it with the anchored hash
3. Confirming the timestamp and anchor reference

Verification is free, permissionless, and permanent.

Immutability Guarantee

Once a record is anchored:

• It cannot be changed
• It cannot be deleted
• It cannot be revoked

Any correction requires a new record.

Privacy Model

Whytegod is privacy-preserving by design.

• No personal data stored
• No identity requirements
• No content inspection

Legal and Interpretive Responsibility

The protocol provides cryptographic proof only. Legal meaning, enforcement, and interpretation are entirely the responsibility of users.