LIVE — SERVING PRODUCTION TRAFFIC TODAY

Flashy ID

Prove who is acting, for whom, and with what authority.

One chain of authority — human, organization, agent — signed at every link, verifiable by anyone, with no Flashy credential required. Live today: the OAuth 2.1 / OIDC issuer, deployed at id.flashyid.com, minting short-lived rewards:issue tokens that Flashy Finance's settlement rail verifies against a public JWKS — plus the site, a verifier whose denial states get the same care as its success state, and spec v0.3 (DRAFT). Still maturing: the consumer login and cross-org verification surface.

Verify an assertion ↗How it fits the network

The chain

Every grant points at its parent, and every chain roots in a named human. Accountability is structural, not procedural.

Attenuation only

A grant can never exceed its parent. An agent cannot widen its own authority — arithmetic, not policy.

Asymmetric by design

Relying parties verify against a published key; nobody holds a shared secret capable of minting a session.

Verify without an account

The keys are public and the whole check runs on the verifier's side. No Flashy credential required.

In the network

Flashy ID is not the same layer as ClaimYour.Gold's identity spine — that's the customer-facing reputation and progression identity built through play. Flashy ID is the machine-to-machine credential layer beneath it, the way an operating system needs an identity and permissions layer under the applications it hosts. FlashyOS is that operating system; Flashy ID is what it runs its identity on.

Status honesty: LIVE means the OAuth 2.1 / OIDC issuer is deployed at id.flashyid.com and answering in production — it mints short-lived rewards:issue tokens (POST /rail/issuer-token) signed with the provider's own key, and Flashy Finance's settlement rail verifies those signatures against the public JWKS. The site, verifier and spec v0.3 (DRAFT) are live alongside it. Precisely scoped: only the issuer-token / rail-verification path is in production; the consumer login and cross-org verification surface is still maturing. The policy engine and cross-org revocation propagation are dated on flashyid.com/spec, not claimed; flashyid.com/trust carries the gap list.

HOW THE LAYERS COMPOUND →ALL TEN PROPERTIES →

FOR ARCHITECTS & COMMITTEES

Read the spec, then verify an assertion — two of the three examples fail on purpose.

Visit flashyid.com ↗Request access