Unverified50% confidenceOpinionExact time
Aboard Sign has not disclosed the specific signing mechanism and verification method of its cryptographic signatures, and actual reliability remains for users to verify themselves.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/14/2026
First Seen
Valid until: 2/12/2027
Sources
Related Entities
Related Claims
UnverifiedFor signature-based verifiable claims (such as JWTs signed with a private key), the recipient can verify the signature but cannot confirm the true ownership of the key.76% similarUnverifiedAboard Sign's email-CC model cannot layer on stronger identity verification methods such as SMS verification and ID document checks the way dedicated platforms can.75% similarUnverifiedA signed record has three core properties: integrity (any tampering with an event breaks the hash chain), non-repudiation (the signer cannot deny having generated the record), and verifiability (a third party can verify the signature and the event order using only the public key).74% similarVerifiedSignature verification only guarantees that a certain commit was signed by a certain key; if the private key leaks or the account is compromised, it can still be impersonated, so it is one link in supply chain security rather than the whole.74% similarUnverifiedA common mistake in signature verification is asking only "is the signature valid?" rather than "what does the signature cover?"73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1170213API
curl https://kongchang.com/api/v1/knowledge/claims/1170213MCP
get_claim(id=1170213)