FAQ

Clear answers about DKAM, Blucks and consent-controlled capability data

DKAM is built for trust decisions where a simple profile is not enough. These answers explain what the product is, what it is not, and how verified evidence stays under individual control.

Verified evidence

Claims should show where they came from and how strongly they are validated.

Consent first

Individuals decide what to reveal, to whom, and for how long.

Interoperable trust

Employers, universities, recruiters, investors and professionals work from the same evidence structure.

Aura scale

Higher Aura, stronger signal

Every Aura is the same crystal core. What changes is the light it gives off. The brighter the glow, the deeper the verified evidence behind the node.

Aura 1
Self-asserted
0x1A2B5566
Aura 2
ID + liveness passed
0x2b8f6677
Aura 3
Source verified
0x3C7D3344
Aura 4
Multi-source verified
0x4d9edef1
Aura 5
Elite, source verified
0x5eF13344
Detailed answers

Twenty questions stakeholders usually ask

DKAM stands for Decentralised Knowledge and Capability Management. It is a trust layer for professional identity and capability evidence. Individuals own a verifiable record of who they are and what they can do. Organisations, universities and recruiters interact with that record through consent, not by holding copies of it.

Maintained by the DKAM team. Compliance certifications, audits and infrastructure components are labelled by status across the platform and the white paper. See the Security and Verification Policy pages for detail.