A service of idregulators.com · Powered by ELAI
ELAI Signet turns any original work into a cryptographically-signed, biometrically-anchored, hardware-attested attestation of your authorship. Three layers of evidence in one artifact. The artifact carries its proof. The proof outlives the platform.
Sign with your face. Prove with math. Verifiable by anyone, anywhere, forever — using only open cryptographic standards.
The signet for the AI age. Built on the ELAI Ecosystem · US Patent Application 17/085,257 + CIP — both pending.
The problem
Three failures of digital provenance that the AI era has made urgent — and ELAI Signet's structural answer to each:
Anyone can generate a photo, video, or document of anyone saying or doing anything. Without cryptographic provenance bound to a real person at a real moment, denial and impersonation become symmetric — every authentic artifact is suspect; every fake artifact is plausible.
Existing content-credential systems (C2PA, Adobe Content Credentials) bind provenance to camera manufacturers or proprietary platforms. If the vendor sunsets, changes terms, or the metadata gets stripped, the proof vanishes. The credential isn't yours.
"This camera captured this photo at this time" is not the same as "this person made this thing." Existing systems prove device authenticity. They don't prove human authorship. ELAI Signet binds the proof to a live human via biometric authentication — not to a swappable device.
How ELAI Signet works
Every Signet attestation answers three questions independently. Verifiers don't have to trust any one of them — they can validate all three from the artifact itself.
An Ed25519 signature (RFC 8032) is generated over the canonical-JSON serialization of the work's SHA-256 hash, authorship timestamp, and contextual metadata. The signature validates against your published public key.
Your private key is generated, stored, and used inside the Apple Secure Enclave (iOS) or Android StrongBox (Android) — non-extractable hardware. The attestation includes a manufacturer-signed token proving the signing operation happened inside genuine, untampered hardware.
Each signing operation requires a successful FaceID, Touch ID, or BiometricPrompt match. The biometric event is logged with hardware attestation directly inside the signed payload, with timestamp.
How it differs
| Property | ELAI Signet | C2PA / Content Credentials |
|---|---|---|
| Key custody | User-held in Secure Enclave / StrongBox | Device manufacturer or platform |
| Identity binding | Binds to human via biometric | Binds to device only |
| Survives platform sunset | Yes — RFC-standardized primitives | No — vendor-locked verification |
| Verifier requirements | Any RFC 8032 library; no platform | C2PA-compliant viewer |
| Open protocol with FRAND licensing | Yes — ELAI Ecosystem Charter | Industry consortium, vendor-driven |
| Cross-product verifiability | Verified by any ELAI participant | Within C2PA consortium only |
Who needs this
Anywhere AI-generated content makes "real" indistinguishable from "synthetic" — and the cost of being wrong is high.
Reporters sign every photo at capture with FaceID. Wire services display verified-by-photographer badges. Editors verify before publication. Deepfake attacks against named journalists become signature-forgery problems, not narrative problems.
Investigators sign digital evidence at collection. Defense and prosecution verify cryptographic provenance in discovery. Disputes over evidence authenticity become mathematics, not testimony.
Engineers sign code at commit time. Employer audits, IP defenses, and portfolio reviews can verify "this human wrote this code at this moment" — distinguishable from AI-assisted output.
Contributors restore the premium for human-made work. Stock platforms display verified-human badges. Buyers paying for authenticity get cryptographic proof of authenticity.
Students sign essay drafts and code in real time. Institutions verify pre-AI authorship for academic-integrity proceedings. Reversal of the burden of proof — students show their work, not just submit their work.
Government photos, statements, and video are Signet-signed at production. Public can verify authenticity. Deepfake denials of authentic statements become signature checks, not he-said-she-said.
Damage photos signed at time of incident with location attestation. Insurers verify provenance before payout. Anti-fraud built into the workflow rather than litigated after.
Official transcripts signed at production. Verifiable provenance for legal and legislative record. Tampering or substitution becomes cryptographically detectable.
Built on open standards
Every primitive is published, RFC-grade, and independently implementable. No proprietary verification software anywhere in the validation path.
cryptography, noble-ed25519, libsodium, OpenSSL, etc.)Security.framework + CryptoKitandroid.security.keystoreLocalAuthentication with FaceID or Touch IDBiometricPrompt + StrongBox-backed keyEarly access
ELAI Signet is launching in stages. Tier 1 (web-based signing) ships first. Tier 2 (mobile-native with FaceID and StrongBox biometric gating) lands shortly after. Early access participants get pricing-grandfathered pricing and direct engineering access during the beta.
We are prioritizing the following audiences for initial onboarding: photojournalists and wire services, legal/forensic investigators, software engineering teams with IP-audit requirements, stock photography contributors, academic integrity offices, and federal/state agencies with deepfake-defense mandates. If you are in one of these or an adjacent vertical, we are accepting introductions now.
Frequently asked
How does this differ from C2PA?
C2PA binds provenance to the device manufacturer or capture software. ELAI Signet binds provenance to you, via a user-held key inside your device's secure hardware, gated by your biometric. C2PA proves "some camera made this." ELAI Signet proves "I, this specific human, authorized this." Verification requires no proprietary platform — anyone with any RFC 8032 library can validate.
What happens if I lose my phone?
Your private key was non-extractable and lived only on that device — it is permanently lost with the device. You generate a new Signet key on your replacement device and re-publish your public key. Future artifacts sign with the new key. Past artifacts signed with the old key remain verifiable indefinitely under the Charter Survival Guarantee — the only thing that changes is that you cannot sign new artifacts with the old key. This is the same model as physical key loss: your authority moves forward, your past work stays authentic.
Can I sign work I created in the past?
Yes — but the signing timestamp will reflect when you signed it, not when you created the work. This is honest by design. Pre-AI provenance is most powerful when the signing happens at or near the moment of creation. For past work, the Signet attests "I authorize this as mine" with current timestamp — useful for portfolio defense but not equivalent to capture-time provenance.
What about Android?
Full support. The mobile implementation uses Android StrongBox Keymaster for hardware-bound keys and BiometricPrompt for biometric gating. Hardware attestation chains through Google's Key Attestation infrastructure. Signatures produced on Android are byte-for-byte verifiable identically to signatures produced on iOS — same protocol, different hardware platforms.
Is the protocol open?
Yes. The cryptographic primitives are open standards (RFC 8032, RFC 8785, FIPS 180-4). The ELAI Ecosystem Charter governs participation under FRAND licensing. Any third party can implement a Signet-compatible signer or verifier without licensing AmericaFirst4Us proprietary software. The patent portfolio covers the architectural systems and methods — see Charter §8 for licensing posture.
Can I use this without disclosing my identity?
Yes. The public key associated with your Signet does not have to be tied to your legal name. You can publish the key under a pseudonym, a professional persona, or no identity at all. The signature still cryptographically proves "this specific key signed this artifact" — what that key represents in the social world is your choice. For some verticals (journalism source protection, whistleblowing) this is structurally important.
What does enterprise integration look like?
For organizations integrating Signet verification into their workflows (wire services, legal-evidence platforms, stock-photo marketplaces, academic-integrity systems), we provide a verifier API and reference implementations. Enterprise pricing covers integration support, SLA, and dedicated key-publication infrastructure. Contact tpoc@americafirst4us.com for the enterprise track.