AmericaFirst4Us Inc.
Steward of the ELAI security ecosystem

The ELAI Ecosystem Charter · v1.0

An open security ecosystem.
Not a platform.

The ELAI Ecosystem is an open network of independent product surfaces sharing one cryptographic trust primitive. Any organization implementing the protocol obligations of the Charter may participate. Cross-surface verification. Local-first key custody. No centralized aggregation point. Stewarded — not owned — by AmericaFirst4Us Inc.

Ed25519 · RFC 8032 Canonical JSON · RFC 8785 SHA-256 · FIPS 180-4 User-held keys FRAND licensing

The problem the ecosystem solves

Identity infrastructure has been failing users in three predictable ways.

1. Credential surveillance

Vertically-integrated identity platforms aggregate every credential at a single network endpoint. Every verification produces a data point at that endpoint. The user becomes legible to the platform; the platform becomes a surveillance target.

2. Credential revocation by single authority

A single platform can unilaterally invalidate any credential it issued. Users have no recourse. The credential's continued usefulness depends on a relationship — not on cryptography.

3. Credential loss through platform sunset

When a platform shuts down, deprecates a product, or changes its terms, every credential it ever issued becomes worthless. There is no migration path because the verification depended on proprietary software.

The ecosystem alternative

An open network of independent participants implementing public cryptographic standards. No centralized aggregation. No single authority. Cryptographic verifiability that survives the sunset of any participant — because the primitive is open, not proprietary.

Charter at a glance

What every participant implements.

The full Charter is the canonical document. This is the summary every prospective participant should read first.

Protocol obligations

  • Sign attestations using Ed25519 over canonical JSON.
  • Hash payloads using SHA-256.
  • Use user-held keys. Never possess, transmit, or persist a user's private key.
  • Deliver every signed attestation back to the user's device. Never aggregate cross-user.
  • Verify attestations from every compliant participant — not just your own.

Honesty obligations

  • Label every attestation with an explicit event class — cryptographically_anchored, presence_only, or absent.
  • Never mislabel a magstripe or biometric presence event as chip-level cryptographic authentication.
  • Survive your own sunset — design so that artifacts signed today remain verifiable after your surface shuts down.
  • Use only open cryptographic standards in the verification path. No proprietary verifier software.

Read the full Charter →

Current participants — v1.0

The founding five.

Five reference implementations operated by the Steward. All compliant with Charter v1.0. All cross-verify each other's artifacts in production.

Reduction-to-practice anchor: on May 23, 2026, a multi-card hardware attestation generated by verifythecard.com was independently and concurrently verified by 4pdfs.com, by verifythecard.com's own verifier, and by an offline Python implementation of RFC 8032 — three witnesses, two participants, one library. The interoperability property is real.

How to become a participant

Four steps. Thirty days.

The ecosystem is open. The Charter defines compliance. The Steward conducts the interoperability test. The Participant Registry publishes the result.

Describe your proposed surface

Send a description of the surface, the credential class or classes it will attest, and a statement of intent to comply with Charter Sections 3 and 4.

Demonstrate an attestation

Produce a sample signed attestation or bundle from your prototype surface. Include payload, signature, public key, and event class.

Interoperability test with the reference implementations

The Steward verifies your sample against the existing reference implementations. The reverse test — your surface verifying their artifacts — completes the loop.

Join the Registry and display the mark

Successful participants are added to the public Participant Registry, granted the right to display the ELAI ecosystem mark on compliant surfaces, and invited to the coordination forum.

Patent stewardship

The Steward intends to license on FRAND terms.

US Patent Application 17/085,257 + Continuation-in-Part

The ecosystem's architectural systems and methods — multi-surface cross-verification, multi-credential bundling, pair-reference absence attestation, the honest-decline framework — are the subject of pending US patent claims assigned to AmericaFirst4Us Inc.

The cryptographic primitives themselves (Ed25519, SHA-256, canonical JSON) are open standards and remain open.

The Steward's stated intent is to license the patent portfolio to ecosystem participants on fair, reasonable, and non-discriminatory (FRAND) terms. Zero-cost licenses are contemplated for small participants, defense and government use, and educational use. Specific licensing terms will be published as a supplement to the Charter.