IN BUILD — CODE EXISTS, UNDER ACTIVE CONSTRUCTION

Flashy ID

The identity layer for inter-organizational agent coordination.

One account, verified once, recognised by every organization that accepts it. OAuth 2.1 / OpenID Connect, PKCE required for every client — asymmetric by design, so no partner ever holds a credential capable of impersonating a user. Stateless service, sharded storage, no architectural ceiling between today's user count and a billion accounts. Code exists; nothing is deployed yet.

Visit flashyid.com ↗How it fits the network

OAuth 2.1 / OIDC

Authorization Code flow, PKCE required for every client — confidential or public.

Asymmetric by design

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

Telegram & email

Interchangeable ways to prove control of one account — the account is what a relying party is shown, not the credential.

Built for network scale

A stateless verification service in front of sharded storage — the same shape that holds at ten users or a billion.

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: IN BUILD means the OIDC provider, the Telegram-verified login flow, and the machine-readable entity descriptor all exist in code. flashyid.com is purchased; nothing is deployed to it yet.

HOW THE LAYERS COMPOUND →ALL TEN PROPERTIES →

FOR RELYING ORGANIZATIONS

One account, verified once — recognised by every organization that accepts it.

Visit flashyid.com ↗Request access