ACN is AITECH’s cloud network for AI. It is the broader product surface: staking with $ACN, subscriptions, agent discovery, on-chain registry (ERC-8004), and a marketplace for agents that others can use. When someone finds an agent on ACN, they need it to be useful and published by someone accountable.

Forge (Agent Forge) is the builder inside that network. Creators assemble workflows from blocks, connect tools, deploy APIs and chat surfaces, and register agents so they appear in discovery. Forge already records which login published an agent. A login is not the same as a person. Email and OAuth accounts are inexpensive to create; they do not answer whether there is a verified human behind the agent.

Concordium is an AI infrastructure for the agentic economy. Every Concordium account is backed by a credential issued by a regulated identity provider. The chain never stores the holder’s name, date of birth, or identity document. Instead, a holder can produce a zero-knowledge proof that a valid credential exists, and reveal nothing else. Concordium also runs a native agent registry (CIS-8004), aligned with Ethereum’s ERC-8004, and an external-key registry (CIS-8) that can bind a Concordium account to a public key on another chain.

Forge already mints agents as ERC-8004 NFTs on Ethereum. Concordium is the identity layer: cryptographic evidence that the publisher is a person, not an unbounded set of disposable accounts.

Discovery on Forge lists agents that other users can call, pay, and rely on. The existing Verified chip on those listings comes from 8004scan’s view of the on-chain agent record. It says nothing about the creator.

That gap appears as soon as agents leave a private workspace:

• Forge accounts are easy to create. Without a sybil-resistant identity, “verified” on an agent is easy to game.
• Running KYC inside Forge would put sensitive documents on a builder platform that should not hold them, and would discourage creators from publishing.
• Identity belongs to the person, not to each agent. Requesting a proof in the middle of the registry deploy wizard would slow every publish and repeat a wallet flow that only needs to happen once.

Concordium’s model is “verify once, prove everywhere.” A creator completes identity with a Concordium identity provider once, in their wallet. Forge requests a proof that the credential exists. The platform stores the Concordium account address and a timestamp. Underlying attributes are never disclosed to Forge.

The requested proof is minimal: the holder shows that date of birth falls in the widest range the protocol allows. That statement is unprovable without a real identity credential, and it discloses nothing about the holder. One Concordium account can back at most one Forge user, which gives the badge sybil resistance.

This step has no on-chain cost. No CCD, no gas, and no contract call. The wallet signs a presentation; Forge verifies it against Concordium’s public parameters and consumes the challenge so the same presentation cannot be replayed.

For ACN, that is the trust signal discovery was missing: the agent was published by a verified human, without turning Forge into an identity-document processor.

Creators opt in from Settings → Identity. They connect a Concordium browser extension or a mobile wallet (via WalletConnect), approve a proof request, and receive a persistent Verified Creator status.

That status is stored on the Forge user and shown on Agent Forge discovery cards as a separate badge from 8004scan’s agent-level Verified. The Ethereum staking wallet in the header is unrelated; Concordium identity does not appear there.

Unlinking is supported. Re-verifying later requires a fresh proof. Linking the same Concordium account to a second Forge user is rejected.

Discovery of Concordium-native agents. The Concordium Agent Registry is live on mainnet (CIS-8004). A later release will treat it as a third source in Discover Agents, alongside Forge and the global ERC-8004 scan, with card-hash and owner-badge checks so trust is read from chain rather than assumed.

Agents that can verify other agents. The registry will be exposed as a Forge workflow block so an agent can ask, at runtime, whether another address is backed by a verified human.

On-chain registration. An optional path will bind the creator’s Ethereum key to their Concordium account (CIS-8), then register the agent on CIS-8004. That work depends on a fee model for Concordium transactions and on published testnet contract addresses. Until those are in place, Forge does not mint Concordium agents on the creator’s behalf, and a platform-owned on-chain account is not labelled “verified creator.”

Account-level identity is the prerequisite for all of the above: a Concordium account with a real credential, linked once to the Forge user, with a badge that means the same thing on every agent that user publishes.