Blog

Polaris Chain team

How the Polaris Trust Registry works


Real-world asset transfers on Polaris need to know something about the people on both ends of a trade, such as whether they passed KYC checks or which jurisdiction they belong to, without putting that information itself on a public, permanent ledger. The Polaris Trust Registry is the layer that makes this possible: a system of signed, verifiable claims that identities can present, and that anyone can check, without exposing the underlying personal data.

The core idea: signed claims, not stored documents

An identity on Polaris is not a name and a document sitting in a database. It is an address bound to an identity record, and a set of claims attached to that record. A claim is a small, signed statement: this address passed KYC, this address is an accredited investor, this address belongs to jurisdiction X. It is signed by a trusted issuer, an institution registered on-chain and authorized to make that kind of statement.

The signature is what carries the trust. Because the issuer signed the claim off-chain, before it was ever submitted to the chain, no on-chain computation is needed to verify who made the claim, only that the signature is valid and the issuer is still on the trusted list. Personal information itself, names, documents, and identifying detail, never lands on-chain. Only a commitment, such as a hash, does. That split is what lets the system satisfy data-protection rules like the right to erasure: deleting the off-chain record removes the personal data, while the on-chain commitment remains an unreadable hash.

Revocation

A claim is not permanent by default. An issuer can revoke a claim it made, for example if a KYC status changes or an accreditation expires. Once revoked, that claim can no longer be used to satisfy a compliance check. This matters because a real-world identity's status changes over time, and a compliance system that could not reflect that would quickly become inaccurate.

Selective disclosure

Selective disclosure means proving a specific fact, such as "this address holds a valid KYC claim from an approved issuer," without revealing anything else about the underlying identity. Polaris verifies membership on an approved list without publishing the entire list or the entry's surrounding details, keeping the technique consistent with a chain built around post-quantum-safe cryptography. See the milestones page for the privacy and credential work each stage carries.

Why this belongs on-chain at all

An alternative design would keep all of this off-chain and simply trust an API to tell the chain whether a transfer is allowed. Polaris does not do that, because the whole point of the compliance layer is that its rules are enforceable and checkable by anyone, not just by whichever service happens to be running an off-chain check at the moment. Putting the claims, the trusted issuer registry, and the transfer rules on the ledger means a regulator, an auditor, or any outside party can verify exactly which rules applied to a transfer and why it succeeded or failed, without needing to trust a private system in the middle.

What this is not

The Trust Registry is not a general identity system for the internet, and it is not a place to look someone up by name. It is narrowly built for one job: letting a regulated asset's transfer rules be checked against signed, revocable claims, while keeping the underlying personal data off-chain.