Skip to main content
When an end user connects their wallet, you, the developer, get a JSON Web Token (JWT) that can be used to verify some claims about the end user, notably a proof of ownership over a wallet public address. After authenticating the JWT token, see Server-side verification, you may want to leverage user and wallet information provided in the JWT. Below we have the content defined with the aim of following the JWT standards.
Standard JWT claims:
See: https://www.rfc-editor.org/rfc/rfc7519#section-4.1
Dynamic-specific claims:
These fields are optional and you depends on whether you want to collect this information during onboarding. For more information about collecting this information, see here.

Example