> 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/overview/welcome-to-bluprynt.md).

# Welcome to Bluprynt

Bluprynt is the Compliance OS of digital assets.

## What is Bluprynt?

Bluprynt is the Compliance OS of digital assets.

It gives issuers, regulators, and platforms a machine-readable control layer for identity, disclosures, credentials, and supervision.

### Why It Exists

Tokenized assets now move faster than document-based compliance can handle.

Three gaps define the market:

**No issuer legibility.** Market participants often cannot verify who issued an asset, which entity controls it, or which wallet is authorized to act.

**No machine-readable compliance layer.** Disclosures, approvals, and supervisory actions still live across PDFs, spreadsheets, inboxes, and siloed systems.

**No machine-speed supervision.** Regulators and institutions need real-time visibility into issuer state, not post-facto reconciliation.

### What Bluprynt Does

Bluprynt turns digital assets into machine-legible, governable market objects.

It does this across four core product layers:

#### 1. Identity

Every asset issuer on Bluprynt receives a verifiable onchain identity that's compatible with W3C DID, ONCHAINID (ERC-734/735), and vLEI/LEI standards. This identity is cryptographically linked to:

* The legal entity, via KYB verification
* The issuing wallet, via cryptographic challenge
* The token contract, via onchain attestation

This is what **Know Your Issuer (KYI)** produces — a foundational identity attestation that everything else builds on.

#### 2. Disclosures

**Smart Disclosures** turns regulatory requirements into structured digital workflows instead of static documents. Issuers can:

* Pre-fill jurisdiction-specific disclosure forms using AI extraction
* Complete filings with AI-assisted guidance
* Produce structured outputs in XBRL, PDF, and DOCX
* Publish disclosures as verifiable attestations linked to the issuer

The system is built on a taxonomy of standardized concepts, so the same issuer data can be reused across forms, jurisdictions, and workflows.

#### 3. Supervision

**Compliance Hub** gives regulators and supervisory teams a workspace to:

* Create forms and publish them to issuers
* Review applications and filings
* Issue or revoke credentials
* Directly issue credentials when no form is needed
* Monitor regulated assets and supervisory activity

This replaces fragmented review across email, spreadsheets, and static documents with one auditable operating environment.

#### 4. Credentials

Attestations record facts. **Credentials** authorize actions. Bluprynt issues four types of verification credentials:

| Credential              | Purpose               | Key Question It Answers                            |
| ----------------------- | --------------------- | -------------------------------------------------- |
| **Know Your Issuer**    | Entity authentication | "Is this token issued by a verified legal entity?" |
| **Proof of Collateral** | Backing verification  | "Is this asset properly collateralized?"           |

These credentials are verifiable, portable, and machine-checkable across the asset lifecycle.

### Bluprynt as an Operating System

Bluprynt is a digital asset operating system.

It does not replace blockchains or legal systems. It makes them operable together at scale.

In practice, that means Bluprynt helps market participants:

* Standardize issuer identity and disclosure data
* Connect issuer workflows and regulator workflows
* Turn approvals into verifiable digital credentials
* Make asset status easier to observe across time and jurisdictions

***

### Architecture at a Glance

```
ASSET ISSUER (Organization)
   │
   ├── Identity ──────────── KYI Attestation
   │                         (entity ↔ wallet ↔ token)
   │
   ├── Disclosures ───────── Smart Disclosures
   │   └── Structured filings and disclosures
   │
   ├── Supervision ───────── Compliance Hub
   │   ├── Form creation
   │   ├── Review and approval
   │   ├── Direct issuance
   │   └── Monitoring
   │
   └── Credentials ───────── Verifiable onchain records
       ├── KYI
       └── Proof of Collateral
```

All identities, attestations, and credentials are registered on the **Bluprynt Registry** and are publicly queryable, excluding sensitive issuer data.

***

### Key Concepts

Understanding these terms will help you navigate the rest of the documentation:

* **Compliance OS** — Bluprynt's control layer for digital assets. It unifies identity, disclosures, supervision, and credentials into one operating environment.
* **Onchain legibility** — The condition where an asset's relevant legal and economic attributes are represented in a standardized, machine-readable, and verifiable form.
* **Attestation** — A verifiable record of a fact about an issuer, asset, or submission.
* **Credential** — A verifiable permission or status record issued after a review or filing workflow.
* **CCID (Compliance Chain ID)** — A unique identifier used to track issuers, credentials, and submissions across workflows.
* **Taxonomy Concept** — A standardized compliance data point used to structure forms and reuse data across workflows.
* **Credit** — Bluprynt's billing unit. One credit covers one published Smart Disclosures document or one generated attestation.

***

### Standards Compatibility

Bluprynt's data structures are designed for interoperability with existing identity and attestation standards:

| Standard                               | How Bluprynt Uses It                                   |
| -------------------------------------- | ------------------------------------------------------ |
| **W3C DID**                            | Decentralized identifiers for asset issuers and assets |
| **W3C Verifiable Credentials**         | Schema for attestations and credentials                |
| **ONCHAINID (ERC-734/735)**            | Onchain identity and claim management                  |
| **vLEI / LEI (GLEIF)**                 | Legal entity identification for institutional issuers  |
| **EAS (Ethereum Attestation Service)** | Attestation publishing on EVM chains                   |
| **SAS (Solana Attestation Service)**   | Attestation publishing on Solana                       |
| **IPFS**                               | Content-addressed storage for disclosure documents     |

***

### What's Next

* **Ready to start?** → [Create an account](/bluprynt-docs/getting-started/creating-a-bluprynt-account.md)
* **Want to see the products?** → [Smart Disclosures](/bluprynt-docs/smart-disclosures/what-is-smart-disclosures.md) · [KYI](/bluprynt-docs/kyi-know-your-issuer/what-is-kyi.md) · [MiCA Checker](/bluprynt-docs/mica-checker/mica-checker.md)
* **Building an integration?** → [KYI API](/bluprynt-docs/kyi-know-your-issuer/kyi-api.md) · [Attestation Schemas](/bluprynt-docs/architecture-and-standards/attestation-schemas.md)
* **Exploring credentials?** → [Credentials](/bluprynt-docs/overview/core-products.md#credentials)