GitHub hosts HunyuanVideo, Tencent's open-source framework for large-scale video generation models, enabling AI-driven video creation.
Human Provenance Standard — HPS
0Popularity
About Human Provenance Standard — HPS
The Human Provenance Standard (HPS) generates cryptographically verifiable provenance records that document human and institutional contributions. Creators sign their own declarations using locally held Ed25519 keys before submission. Authorized institutions can issue records at scale, signing declarations independently. HPS verifies these signatures and countersigns the resulting provenance manifest, ensuring tamper evidence. The system maintains separate records of claimed contributions, supporting evidence, and verified facts. Supporting materials such as drafts, source code, datasets, and version history can be linked via hashed or sealed references. Independent attestations from third parties can be added without altering the original declaration. The trust stack relies on asset integrity (SHA-256), creator or issuer signatures, registry countersignatures, identity assurance, supporting evidence, independent attestations, and status tracking (active, disputed, revoked).
Key features
- Creator-held Ed25519 key signing
- Institutional issuer authorization and bulk issuance
- Registry countersignature for tamper evidence
- Supporting evidence linking (hashed or sealed)
- Independent third-party attestations
- Status tracking (active, disputed, revoked)
- Identity assurance progression (self-declared to institutional)
- Separate record of claims, evidence, and verification
Use cases
- Documenting human and AI contribution provenance
- Institutional issuance of verifiable records at scale
- Verification of integrity and signatures behind HPS records
Pros
- Supports cryptographically verifiable provenance records
- Allows creator and institutional signatures
- Enables third-party attestations without altering original records
- Links supporting evidence via hashed or sealed references
- Maintains separate records for claims, evidence, and verification
Cons
- No free tier or open access mentioned
- Limited to Ed25519 signatures and SHA-256 integrity
- Identity assurance starts as self-declared before institutional verification
Frequently asked questions about Human Provenance Standard — HPS
What is the Human Provenance Standard (HPS) and what does it do?
The Human Provenance Standard (HPS) creates cryptographically verifiable provenance records that document human and institutional contributions to digital assets. It ensures tamper evidence by verifying signatures, countersigning manifests, and maintaining separate records of claims, evidence, and verified facts.
Who is HPS designed for?
HPS is built for creators, institutions, and verifiers. Creators can sign their own declarations, institutions can issue records at scale, and verifiers can check the integrity and signatures of HPS records.
How does HPS ensure the integrity of provenance records?
HPS uses a trust stack that includes asset integrity (SHA-256), Ed25519 signatures from creators or issuers, registry countersignatures, identity assurance, supporting evidence, independent attestations, and status tracking (active, disputed, revoked).
Can third parties add attestations to an existing HPS record?
Yes, independent attestations from third parties can be added to an HPS record without altering the original declaration. These attestations are signed and linked to the provenance manifest.
What types of supporting materials can be linked to an HPS record?
Supporting materials such as drafts, source code, datasets, notes, and version history can be linked to an HPS record via hashed or sealed references, providing additional context and evidence.
How does HPS handle disputes or revocations of provenance records?
HPS tracks the status of records, which can be marked as active, disputed, or revoked. This accountability ensures that changes or disputes are transparently recorded and verifiable.
