Skip to main content

What it does

This helper returns two instructions: an Ed25519 verification instruction for the platform signature and a TIN registry instruction that stores the encrypted identity link.

How the flow works

1

Caller invokes the function

The caller supplies the owner, registry, platform public key and signature, proof message, encrypted payload, and metadata.
2

Validation

The platform proof is placed first so the registry program can inspect the instruction sysvar and verify it.
3

Main work

The SDK encodes the identity fields and creates the platform proof plus registry instruction.
4

Result

The caller adds both returned instructions to one transaction and has the owner sign it.

Signature

PublicKey
required
Owner signer and writable identity authority.
PublicKey
required
TIN identity registry PDA.
Uint8Array
required
Ed25519 signature over proofMessage.
Uint8Array
required
Canonical platform proof message.
string
required
Social identity provider type.
string
Optional public label; defaults to an empty string.
Uint8Array
required
Encryption nonce.
Uint8Array
required
Encrypted identity value.
string
Metadata JSON; defaults to {}.

Result and errors

The result is two Solana instructions. The function itself has no named error branch; invalid instruction data or an invalid platform proof is rejected during transaction execution.
Source: tins.ts:982-1023