The content travels. Its context often stays elsewhere.
Evidence, status or policies may depend on a separate service.
DIGITAL ORIGINAL FORMAT · ACTIVE VERSION 4.0.0
Discover the .gkp format
A container designed to carry a document with the metadata, fingerprints and signatures needed for its checks — without claiming that a format alone establishes authenticity.
GKP2 · v4.gkp64 BCBORPAYLOADBLAKE3SIGNATURE
01
A file, not a permanent dependency on a platform.
The document and its control elements travel together.
The holder keeps the file and can run supported checks locally.
02
The actual v4 container structure.
Educational diagram faithful to the current binary order. Co-signature records are optional and follow the primary block.
What the format does not guarantee by itself
A mathematically valid signature does not automatically establish identity, authority, revocation, temporal validity or legal effect. Those conclusions depend on available evidence and a trust policy.
03
Creation. Signature. Storage. Transmission. Verification.
- SuitePrepares the document and journey.
- WalletCarries consent and operations according to the journey.
- .gkpKeeps the blocks and evidence defined by its version.
- .gksendMay transport a request through the chosen channel.
- Docs / VerifyRead and check within their qualified capabilities.
TWO LEVELS THAT MUST NOT BE CONFUSED
Checking bytes is not the same as deciding all trust.
Local cryptographic check
Structure, header checksum, signature, fingerprint and payload integrity can be checked from available elements.
Complete trust assessment
Certificate chain, revocation freshness, timestamp, policy and authority may require current anchors or external services.