SSI & Claims

Who it's for: Service developers building any Shika product that needs to confirm a user is verified before allowing them to borrow, trade, or hold assets. Why it matters: A single on-chain credential check replaces every per-product identity gate — compliance is automatic and consistent across the entire protocol.

Reading Identity On-Chain

Any service can verify a user's KYC status directly from SSIComposable:

// Get a user's on-chain identity contract address
address identity = ssi.userToIdentity(userAddress);
 
// Check if the identity holds a valid KYC claim (topic 666)
bool verified = ssi.isVerified(identity);

SSI ABI Fragments Used Across Services

// Shared across core-jit, core-lending, core-rwa
const SSI_ABI = [
  {
    name: 'userToIdentity',
    type: 'function',
    inputs: [{ name: 'user', type: 'address' }],
    outputs: [{ type: 'address' }],
    stateMutability: 'view',
  },
  {
    name: 'isVerified',
    type: 'function',
    inputs: [{ name: 'identity', type: 'address' }],
    outputs: [{ type: 'bool' }],
    stateMutability: 'view',
  },
]

Where SSI Is Enforced

Protocol Contract Identities

Smart contracts themselves also have SSI identities — this allows them to hold compliant RWA tokens and be whitelisted as agents.