> For the complete documentation index, see [llms.txt](https://docs.galactica.com/galactica-developer-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.galactica.com/galactica-developer-documentation/galactica-concepts/zero-knowledge-kyc/verification-sbt.md).

# Verification SBT

## What it is

Verification soul-bound tokens (SBTs) are on-chain records. They state successful zkKYC verifications between a wallet addresses and verifier smart contracts corresponding to a DApp. The soul-bound property means that it can not be transferred. Instead it has to be recreated for another wallet with a new ZKP verification.

The on-chain registry is implemented in an EVM smart contract. Galactica provides a standardized system instance defined here: [DevNet: Andromeda](/galactica-developer-documentation/devnet-andromeda.md)\
In general, also custom registries can be deployed and used.

## Purpose

* On-chain record for reference in smart contracts
* Unlocks using DApps requiring compliance without regenerating a ZKP every time
* Carries data about verification

## Contents

The data contained in a Verification SBT is defined in the [smart contract](https://github.com/Galactica-corp/galactica-monorepo/blob/main/packages/zk-certificates/contracts/interfaces/IVerificationSBT.sol).

* Wallet address of the user
* Address of the DApp the verification was for
* Verifier Codehash for tracking what version of the verifier was used. This allows upgrading DApp requirements and migrating previous verifications.
* KYC Guardian public key
* Fraud investigation data, see [Galactica Investigation Module](/galactica-developer-documentation/galactica-concepts/zero-knowledge-kyc/fraud-investigation-process.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.galactica.com/galactica-developer-documentation/galactica-concepts/zero-knowledge-kyc/verification-sbt.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.