Tokenization

OpenGDP treats tokenization as a first-class primitive. You define the asset. You set the transfer and compliance rules. The network provides issuance, settlement, and observability. Assets integrate directly with exchange and coordination, so value can move and operate without extra glue code.

​

Asset model

An asset is a contract with rules. It has a type, metadata, supply constraints, transfer policy, and lifecycle events. The model supports fungible, non-fungible, and structured instruments.

​

Types

• Fungible: Currency-like units or shares of a common pool.
• Non-fungible: Unique items with their own metadata.
• Semi-fungible: Batches or classes that behave like fungible units within the class.
• Structured instruments: Fund shares, treasuries, credit, invoices, usage credits, and permits.

​

Core fields

• Metadata: Name, symbol, description, decimals, display preferences.
• Supply rules: Fixed supply, capped supply, or issuer-governed supply with controls.
• Transfer policy: Unrestricted, allow list, block list, geography or role restrictions, or time-based restrictions.
• Compliance policy: Required checks before transfer, such as identity or accreditation.
• Lifecycle hooks: Events that update the state, such as coupon, redemption, distribution, freeze, or clawback, if configured.
• Accounting tags: Labels for reporting and subledger views.

​

Templates

OpenGDP ships turnkey asset templates that can also be extended. Some examples are:

• Currency or stable value: Simple transfers with optional transfer controls.
• Stocks or equity: Primary issuance, transfer restrictions, cap table registry, dividends, splits, buybacks, and optional voting workflows.
• Compute credit: Metered usage for AI training and inference or data access.
• Insurance: Parametric or indemnity policies with premiums, coverage limits, claims, reserves, oracle triggers, and capital pool or reinsurance hooks.

Each template exposes a clean interface, events, and a default policy set. You can extend a template through modules or deploy a custom contract that implements the same interfaces.

​

Lifecycle

Lifecycle events are standardized so assets behave predictably across the network.

• Issuance: Mint or allocate supply according to policy. Primary issuance can require approvals or multi-signer flows.
• Transfer: Verify policy checks. Move balances and emit events. Optional settlement windows for complex flows.
• Cashflows: Coupon, dividend, distribution, premium collection, claim payout, staking reward, or streaming payment.
• Corporate actions: Split, merge, reclassify, or migrate with holder-friendly paths.
• Controls: Freeze or unfreeze by role. Clawback if the asset was configured with this power.
• End of life: Redemption or burn with final reporting.

All lifecycle events emit consistent logs for indexing and audit.