> For the complete documentation index, see [llms.txt](https://bluprynt.gitbook.io/bluprynt-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluprynt.gitbook.io/bluprynt-docs/credentials/kyi.md). # KYI Overview of the Know Your Issuer credential. ## Know Your Issuer (KYI) Know Your Issuer is Bluprynt's foundational credential. It cryptographically proves that a token was issued by a verified legal entity and that the controlling wallet holds legitimate minting authority. KYI is **free for all qualifying assets**. {% hint style="info" %} KYI eliminates one of the most common fraud vectors in crypto: the ease with which bad actors can deploy copycat tokens that mimic legitimate projects. It also reduces listing and compliance risk for exchanges, dApps, and DeFi protocols by linking each token to a verified, onchain identity. {% endhint %} ### What KYI Produces When an asset issuer completes KYI, three things happen: 1. **Onchain identity created** — The asset receives a W3C DID and ONCHAINID-compatible identity, linked to the issuer's verified legal entity. 2. **KYI attestation published** — An attestation linking the issuer's onchain identity, the asset's onchain identity, and the verified wallet is published to the asset's blockchain network. 3. **Registry listing** — The asset appears on the Bluprynt Registry with an "Authenticated" status, queryable via the KYI API. ### What Gets Verified | Verification | How | | --------------------- | ---------------------------------------------------------------------------------------- | | **Legal entity** | KYB check against company registries and sanctions lists | | **Wallet ownership** | Cryptographic challenge — issuer signs a Bluprynt-generated message to prove control | | **Mint authority** | On-chain verification that the signed wallet holds mint authority for the token contract | | **Business identity** | Company documents (certificate of incorporation, registration excerpts) | ### The KYI Process #### Step 1: Open the KYI Application From the Bluprynt dashboard home page, click "Authenticate Asset" on the Know Your Issuer card. You'll need an organization set up first — KYI is an organization-level attestation. #### Step 2: Fill Out Token Details Provide the basic information about your asset: * **Token address** — the contract address or on-chain identifier * **Token name** and **ticker symbol** * **White paper URL** — optional, but links to your Smart Disclosures document if you have one * **Website URL** These details will be publicly visible on the Bluprynt authenticated asset dashboard. #### Step 3: Verify the Issuing Wallet Prove control over the wallet(s) with mint authority. Bluprynt supports three verification methods: * **Wallet extension** — Sign via MetaMask, Phantom, or other browser wallets. This is a non-transactional signature — no assets are moved or at risk. * **Command line** — Sign with CLI from a wallet that holds mint authority. Also non-transactional. * **HSM** — Send a no-op transaction using a hardware security module with a Bluprynt ID-linked signature. Designed for institutional issuers with HSM-based key management. The system verifies both mint authority and freeze authority, where applicable, for the connected wallets. #### Step 4: Complete Business Verification If your organization hasn't already completed KYB when creating your Bluprynt account, you'll do it here. Required information: **Company data:** company name, country, registration number, location of registration, website, legal address. Optionally, a Legal Entity Identifier (LEI). **Company documents** (any one of the following): certificate of incorporation or registration, memorandum or articles of incorporation, association, or registration, or a recent excerpt from a state company registry. **Email verification:** Bluprynt sends a confirmation email with a code to verify your contact on the platform. Once submitted, the information is reviewed against company registries and internationally accredited sanctions lists before the business entity status is marked as "Verified." #### Step 5: Submit the Asset With all sections complete, click "Submit" to finalize the KYI process. The asset goes into "Pending" status and is typically approved within one business day. Bluprynt will reach out if additional information is needed. You'll need to accept that your data will be published to the relevant blockchain attestation service and will be publicly visible. #### Step 6: Attestation Generated Once approved: * The asset receives its own W3C DID and ONCHAINID-compatible identity * A KYI attestation linking the issuer's identity to the asset's identity is created and published onchain * The asset appears on the Bluprynt Registry with a dedicated profile page * The KYI attestation and asset identity are accessible via the KYI API ### What a KYI Attestation Contains The KYI attestation creates the foundational link between three entities: 1. **The off-chain entity** — the asset issuer and its legal status 2. **The on-chain asset** — the token contract and issuing wallet 3. **The asset's disclosures and licenses** — connected via Smart Disclosures attestations This three-way link is what makes all other Bluprynt credentials possible. Proof of Collateral, Proof of Insurance, and Proof of Integrity all build on the identity foundation that KYI establishes. ### Supported Chains KYI attestations can be published on: * **Solana** — via the Solana Attestation Service (SAS) * **Ethereum and EVM-compatible chains** — via the Ethereum Attestation Service (EAS) * **Stellar** * **Avalanche** * **Aptos** Additional chain support is added based on demand and attestation service availability. ### KYI API The KYI API enables partners to programmatically verify whether assets are KYI-authenticated. See the full [API Reference](/bluprynt-docs/kyi-know-your-issuer/kyi-api.md) for endpoints, authentication, and response schemas. ### Integration Options KYI attestations are designed to be integrated by platforms that need to verify token legitimacy and issuer identity: * **Block explorers** — display which tokens are KYI-verified * **Token listing services** — prevent copycat or fraudulent submissions * **Wallets and dApps** — warn users or restrict interaction with unauthenticated tokens * **DeFi protocols** — require KYI as a prerequisite for protocol participation Attestations can be queried via the API or linked to token metadata, and are compatible with EVM, Solana, and ACE-enabled environments. ### Partner With Us If you operate a block explorer, listing platform, or wallet and are interested in surfacing KYI verifications for your users, reach out to our integrations team at ****. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://bluprynt.gitbook.io/bluprynt-docs/credentials/kyi.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.