AmericaFirst4Us Inc.
Steward of the ELAI security ecosystem

ELAI Ecosystem · Corporate key publication

The AmericaFirst4Us
Corporate Ed25519 Key.

This page publishes the Ed25519 public key associated with AmericaFirst4Us Inc. in its capacity as Steward of the ELAI Ecosystem. The key is used to sign Steward-issued declarations including the ELAI Ecosystem Charter, the Participant Registry, and any subsequent governance artifacts.

AmericaFirst4Us Inc. — Corporate signer Active

Organization
AmericaFirst4Us Inc.
Role
Steward of the ELAI Ecosystem
Algorithm
Ed25519 (IETF RFC 8032)
Public key
2b2e5044cf52874f38776a8c6053081aea4d8ccc7df247268efb6c1ccb8c5604
Short fingerprint
2b2e5044cf52874f
Established
2026-05-26T15:56:27.527Z  ·  first used to sign the ELAI Ecosystem Charter v1.0
Purpose
Charter signing  ·  Participant Registry signatures  ·  Steward declarations  ·  Charter revisions
Supersedes
— (initial key)

Machine-readable publication

The same data in JSON form, suitable for automated participant tooling. The canonical machine-readable publication is available at /ecosystem/keys.json.

{
  "@type": "ELAI/KeyPublication/v1",
  "organization": "AmericaFirst4Us Inc.",
  "role": "Steward of the ELAI Ecosystem",
  "publishedAt": "2026-05-26T20:00:00.000Z",
  "keys": [
    {
      "publicKey": "2b2e5044cf52874f38776a8c6053081aea4d8ccc7df247268efb6c1ccb8c5604",
      "algorithm": "Ed25519",
      "purpose": "corporate-signer",
      "establishedAt": "2026-05-26T15:56:27.527Z",
      "establishedBy": "Signing of The ELAI Ecosystem Charter v1.0",
      "supersedes": null,
      "status": "active"
    }
  ],
  "previousKeys": [],
  "rotationPolicy": "Keys may be rotated by publication of a successor key signed by the active key."
}

How to verify a Steward-signed artifact

  1. Download the artifact (e.g., the ELAI Ecosystem Charter PDF).
  2. Extract the embedded /ELAIManifest metadata field — it contains the file hash, the signer's public key, and the Ed25519 signature.
  3. Compare the signerPublicKey field in the manifest to the public key published on this page. They must match exactly: 2b2e5044cf52874f38776a8c6053081aea4d8ccc7df247268efb6c1ccb8c5604
  4. Verify the Ed25519 signature against the manifest payload using any RFC 8032-compliant library (Python cryptography, Node noble-ed25519, Rust ed25519-dalek, OpenSSL, etc.). Or upload the PDF to 4pdfs.com/verify for an in-browser verification.
  5. Confirm the file hash recomputed from the PDF bytes matches the fileHash field in the manifest.

If all three checks pass — public key matches this publication, signature validates, file hash matches — the artifact is authenticated as a Steward-issued declaration.

Key rotation policy

Stability: the corporate key is intended for long-term use. Routine rotation is not anticipated. The signing key is held by AmericaFirst4Us Inc. with appropriate custody controls.

Rotation procedure (if required): A successor key is established by publishing, at this URL, a signed declaration from the active (predecessor) key endorsing the successor. The predecessor key remains valid for verification of historical artifacts indefinitely under the Survival Guarantee (Charter §3.7). The successor key takes over signing duties prospectively.

Compromise procedure: If the active key is suspected of compromise, a revocation declaration is published at this URL. Historical artifacts signed prior to the revocation timestamp remain verifiable; participants are notified to require a fresh signature from the successor key for any subsequent declarations.

Note: the Steward holds no ability to retroactively invalidate Attestations issued by individual Participants using their own User-Held Keys (Charter §5.1). Steward key rotation affects only Steward-issued declarations.