SWSS Identity X is the product through which individuals and institutions interact with the SWSS Identity Verification Layer. IVL is the protocol layer; Identity X is the interface to it.
Why an Asset Record Needs an Identity
An asset record without an identity behind it is a number in a database. Identity X anchors every real-world asset record to a verified human or institutional identity issued by IVL and enforced at consensus rather than checked by an application, which is the property that makes a chain record legible to a registry or a court.
The credential is non-transferable by design. An asset can change hands; the identity that held it cannot be handed to someone else. Every ownership event is attested under that identity and remains permanently associated with it.
What a Developer Integrates Against
| Capability | Where it lives |
| Credential validity check | swss_credentialValid: returns a boolean with optional scope and jurisdiction. No credential data is transmitted |
| Credential retrieval | swss_getCredential |
| Credential behind a deed | swss_getCredentialByDeedId |
| Access tier evaluation | Applied at query time against the caller's credential: see Three-Tier Deed Access |
See Custom swss_* RPC Methods for the full method set. The endpoint is issued with your SWSS DevHub credentials.
Inheritance
A non-transferable credential raises a question a general-purpose chain never has to answer: what happens to an asset when the identity holding it ends. Identity X carries an inheritance registry so succession is a recorded, verifiable event under the same credential framework rather than a private arrangement that a registry would have no way to check. The mechanism is specified with the product; this page documents that the capability is part of it, not how a specific succession is executed.
Status
Identity X is in development. IVL itself is live and its credentials are already enforced at the consensus layer, the product interface is what is being built, not the identity layer beneath it. Launch timing is published on the Master Timeline, which reads the ecosystem roadmap rather than storing a date here.
Next Steps