EXPLOREINDUSTRIESGUIDESLEARNGLOSSARYBOOKSWHITEPAPERTOOLSRESOURCESPIONEERMARKETSCOUNTRIESFEESMISSION FUNDPASSPORT
SUPPORTLOGINJOIN THE PROTOCOL →
GETREADYANDJUMP.COM · BUILT IN DETROIT

PERSONA
ON GRAJ.

Persona on the GRAJ protocol. One fee. 195 countries. Join the protocol.

JOIN THE PROTOCOL →
Identity

ONE IDENTITY,
MANY ROLES.

Live now

A person is not their role. The same human can be a brand on Monday and a buyer on Thursday, and forcing them into separate accounts fragments a reputation that took years to build. Identity is verified once and attaches to the person, not to the hat they are wearing.

Verify the person, reuse the result

An identity check confirms a human being. Making somebody repeat it for every role they take on is friction with no security benefit, and it is why reputation is not portable on most platforms.

The provider is not the design

Identity verification is deliberately provider-agnostic here: the mapping from a provider's answer to a level on the ladder is one function, so a change of provider does not become a change of security model. Anything a provider returns that is not recognised resolves to pending.

What is stored, and what is not

The level reached, when it was decided, by whom, and the risk signals that supported it. Not the underlying documents beyond what is needed to evidence the decision — the safest data is data nobody is holding.

Standing is derived

A person's current standing is computed from their verification history rather than stored as a flag, and the derived answer is checked against the stored view. A disagreement between them would mean a gate and a screen telling the same person two different things.

Where to go next
/kyc/guides/identity-data-industry/roles
JOIN THE PROTOCOL