πŸ“–Key Concepts & Glossary

Definitions for the core terms used across Bluprynt's documentation.

Key Concepts & Glossary

This page defines the core terms used throughout Bluprynt's documentation. If you encounter an unfamiliar term elsewhere in the docs, it should be defined here.


Core Entities

  • Asset Issuer β€” An organization that creates and registers digital or tokenized assets onchain. Asset issuers are the primary users of Bluprynt's compliance tools. Every asset issuer on the platform has a verified identity linked to their legal entity, issuing wallets, and token contracts.

  • Asset β€” A tokenized representation of value or rights, issued by a verified asset issuer. In Bluprynt's system, each asset has its own identity, linked attestations, and credential status.

  • Compliance OS β€” Bluprynt's operating layer for digital assets. It brings identity, disclosures, supervision, and credentials into one machine-readable system.

  • Digital Asset Operating System (daOS) β€” A control layer that makes digital assets operable at scale by coordinating issuance, disclosures, supervision, and verifiable status across participants and systems.

  • Onchain Legibility β€” The condition where an asset's relevant legal and economic attributes are represented in a standardized, machine-readable, and verifiable form.


Identity

  • KYI (Know Your Issuer) β€” Bluprynt's token authentication system. KYI creates a cryptographic link between a legal entity, its issuing wallet, and its token contract β€” producing an onchain attestation that anyone can verify. KYI is free for all qualifying assets.

  • KYB (Know Your Business) β€” The business verification step within KYI. The asset issuer provides incorporation documents, registration details, and legal entity information, which is checked against company registries and sanctions lists.

  • DID (Decentralized Identifier) β€” A W3C standard for self-sovereign digital identity. Bluprynt assigns each asset issuer and asset a DID that can be resolved to their verification status and linked attestations.

  • ONCHAINID β€” An identity standard based on ERC-734 (key management) and ERC-735 (claim management) that enables onchain identity verification. Bluprynt creates ONCHAINID-compatible identities alongside W3C DIDs.

  • CCID (Compliance Chain ID) β€” Bluprynt's internal unique identifier for each entity in the system. The CCID is used to track and link all attestations, credentials, and form submissions across products and jurisdictions for a given issuer or asset.


Attestations & Credentials

Attestation β€” An onchain record that a verified fact is true. Attestations are published to IPFS (for the document content) and to the asset's blockchain network (for the onchain reference). There are three types:

  • Informational Attestation β€” A disclosure voluntarily submitted by the issuer to inform users (e.g., white papers, audit reports). Does not require regulatory approval.

  • Regulatory Attestation β€” A verified proof of compliance with specific legal or jurisdictional requirements (e.g., an approved MiCA white paper, a granted license). Requires regulatory review.

  • Operational Attestation β€” A dynamic assertion about the issuer's technical or business activity (e.g., reserve audit results, oracle verification). Can be updated programmatically.

Credential β€” A verifiable onchain claim that authorizes specific token actions. Unlike attestations (which record facts), credentials grant permissions. When a credential expires or is revoked, the associated permissions are automatically gated by the Compliance Hub. Bluprynt issues four credential types:

  • Know Your Issuer (KYI) β€” Verifies the entity behind a token

  • Proof of Collateral β€” Verifies asset backing

  • Proof of Insurance β€” Verifies coverage

  • Proof of Integrity β€” Verifies security posture (via the four-partner ecosystem: Bluprynt, Dowsers Finance, Circuit Security, Howden Group)


Taxonomy

  • Taxonomy β€” Bluprynt's structured system for organizing compliance data. Every question on every form maps to one or more taxonomy concepts, enabling cross-form data reuse, AI-assisted authoring, and structured analysis.

  • Taxonomy Concept β€” A single, standardized data point in the taxonomy. Each concept has a canonical ID, a human-readable label, and belongs to a scope and category. Example: BPT-CUS-0001 represents custodian_name in the custody scope.

  • Concept ID β€” The canonical identifier for a taxonomy concept, following the format BPT-{SCOPE}-{NNNN}. IDs are sequential within each scope, append-only, and never reused.

  • Scope β€” The top-level subject matter category in the taxonomy. There are seven scopes:

Prefix
Scope
Covers

UNI

Universal

Cross-form entity facts (legal name, jurisdiction, entity type)

ID

Issuer Diligence

Governance, financials, operations, leadership

AD

Asset Diligence

Structure, valuation, NAV, token mechanics

SEC

Security

Audits, penetration testing, key management

REG

Regulatory

Licensing, filings, regulatory approvals

INS

Insurance

Coverage, underwriter, exclusions, claims

CUS

Custody

Custodian identity, segregation model, key ceremony

Cross-Reference β€” A link between taxonomy concepts across different scopes. When a concept in one scope references a concept in another (e.g., BPT-COL-0012 collateral_custodian cross-references BPT-CUS-0001 custodian_name), the auto-fill system uses this link to pre-populate data from prior submissions.


Products

  • KYI (Know Your Issuer) β€” Bluprynt's issuer identity product. It links a verified legal entity, its controlling wallet, and its asset onchain, creating the identity foundation for disclosures, credentials, and supervisory workflows.

  • Smart Disclosures β€” Bluprynt's AI-assisted disclosure creation and validation engine. Transforms complex legal documents into structured, jurisdiction-compliant disclosures. Previously referred to as "SmartDocs" in some contexts β€” Smart Disclosures is the current name.

  • Compliance Hub β€” Bluprynt's regulator-facing supervisory workspace. It gives regulators and supervisory teams a place to create forms, review submissions, issue credentials, and monitor digital asset issuers.

  • MiCA Checker β€” A free diagnostic tool that evaluates whether a white paper meets MiCA Article 4 and 5 disclosure requirements. Open to anyone, no account required.


Technical

  • EAS (Ethereum Attestation Service) β€” An open-source attestation protocol on Ethereum and EVM-compatible chains. Bluprynt publishes attestations using EAS on supported EVM networks.

  • SAS (Solana Attestation Service) β€” The equivalent attestation protocol on Solana. Bluprynt publishes attestations using SAS on Solana.

  • IPFS (InterPlanetary File System) β€” A decentralized, content-addressed storage network. Bluprynt stores disclosure document content on IPFS, with the content hash referenced in the onchain attestation.

  • vLEI / LEI β€” The Legal Entity Identifier system managed by GLEIF. Bluprynt supports LEI codes as part of the asset issuer identity schema for institutional issuers.

  • Bluprynt Registry β€” The public registry where all verified identities, assets, attestations, and credentials are queryable. Sensitive issuer data is excluded. Accessible via the Bluprynt API.


Billing

  • Credit β€” Bluprynt's billing unit. One credit = one published Smart Disclosures document or one generated onchain attestation. KYI is free and does not consume credits.

  • Account Tier β€” Bluprynt offers Free (KYI only), Starter, Pro, and Enterprise tiers. Each paid tier includes a number of credits, with additional credits available for purchase. See Pricing for current rates.

Last updated