Unverified50% confidenceFactExact time
Timestamps are usually based on the RFC 3161 protocol: the application first computes a cryptographic hash (such as SHA-256) of the file, then sends the hash value to the timestamp authority, which binds the hash to an authoritative time source, signs it and returns it.
1
Sources
50%
Confidence
Long-term
Relevance
11/2/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe core technical principle of a cryptographic receipt is to hash the output content, attach a timestamp, then sign it with a private key and encapsulate it as a receipt; anyone can verify the signature with the public key and compare the hash value to determine whether the content has been tampered with.72% similarUnverified数字签名工程实现中通常先计算消息的密码学哈希（如 SHA-256）再对哈希值签名，因为非对称加密运算开销远大于哈希运算71% similarUnverifiedHash sealing refers to the server computing a cryptographic hash (such as SHA-256) over the byte content of a CSV after building it and persisting the hash together with the export task, so that any change to the batch content produces a different hash value and is thereby detected.69% similarUnverifiedThe gate generates a change fingerprint by SHA-256 hashing the diff of protected files together with the affected stages and rules; any change to a single line of protected code changes the fingerprint, making evidence binding to exact code a machine-enforceable property.67% similarUnverifiedThe receipt mechanism generates a cryptographic receipt for each action of each Agent, binding the Agent's identity, the tool called, the exact input, the exact output, a timestamp, and a SHA-256 hash chain.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1126668API
curl https://kongchang.com/api/v1/knowledge/claims/1126668MCP
get_claim(id=1126668)