> For the complete documentation index, see [llms.txt](https://pleasing.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pleasing.gitbook.io/docs/solutions/tokenization-as-a-service-taas.md).

# Tokenization-as-a-Service (TaaS)

Turn certified physical metals into programmable, on-chain assets—fractional, instantly transferable, and distribution-ready across exchanges, DeFi partners, and our community.

### 1. What You Can Achieve

* Financing: Unlock working capital against allocated/segregated inventory.
* Fundraising: Programmatic issuance with transparent reserve attestations.
* Sales Channel: 24/7 global retail/institutional distribution.
* Transfer & Settlement: Fast, auditable title transfer; metal moves only on redemption.

### 2. Denomination Standard (Important)

* Fixed unit: Every token = 1 troy ounce of gold.
* No custom SKUs: We do not issue gram/kilo/serial-bar denominations.
* Benefits of standardization: Uniform pricing, simpler accounting, cleaner integrations, and deeper shared liquidity.

*(Today: PGOLD for gold. Silver/platinum families may be introduced later, each may have different SKU per token.)*

### 3. Benefits of Turning Your Gold into PGOLD

* Expanded market access: Reach buyers and lenders across geographies and platforms.
* Fractional investment (by token count): Offer single-ounce units suited to both retail and institutions.
* Trade settlement & clearing: Transfer digital title in seconds—no metal movement required.
* Cost & operational efficiency: Tamper-evident ledgers replace manual reconciliation; reduce paperwork and logistics overhead.
* Composability: Use PGOLD across DeFi—lending, LP, hedging, and structured products.

### 4. Who It’s For

Vaults • Refiners • Dealers • Aggregators • Treasuries • Family Offices • Brands • Market Makers

### 5. How It Works (End-to-End)

{% stepper %}
{% step %}
Warehouse Reserves Due Diligence

We review your business, inventory, and objectives. We conduct KYC/KYB, verify custody setup, certifications, insurance, and logistics, and align on program terms—so you don’t need to handle blockchain complexity.
{% endstep %}

{% step %}
Physical Assets → Digital Tokens (PGOLD)

Once approved, we mint PGOLD 1:1 against certified reserves and record the linkage to your physical asset (bar list/serials, fineness, vault). Each PGOLD = 1 troy oz.
{% endstep %}

{% step %}
Tradable & Collateral-Ready

Your tokens behave like any digital asset: transfer, list for sale, collateralize, or integrate with DeFi (trading, lending, LP, structured notes). Redemptions burn tokens and release bars per program SLA.
{% endstep %}
{% endstepper %}

### 6. Partner Requirements (Checklist)

* Corporate registration & UBO documentation
* Vault operator details, certifications (e.g., LBMA where relevant), insurance
* Inventory evidence (bar lists, serials, weights, fineness, custody model)
* Jurisdictional disclosures & redemption logistics
* Program selections (fee model, reporting/attestation cadence, redemption locations)
* Technical contact for API/reporting integration

### 7. Technical & Operational Architecture

* Token standard: ERC-20 on primary chain; omnichain expansion via messaging where enabled
* Lifecycle controls: Role-gated mint/burn; attestations anchor issuance/redemption
* Telemetry: Supply, mints/burns, holder distribution, and reserve snapshots via dashboard & APIs
* Oracles & pricing: Market data for NAV/marking (integration-dependent)
* Monitoring: Status page, incident handling, reconciliation workflows

### 8. Data, Attestations & Transparency

* Dashboards: Total/circulating supply, mints/burns, holder distribution
* Attestations: Reserve proofs (monthly standard; higher cadence optional)
* APIs:
  * `GET /supply` — total & circulating
  * `GET /events` — mint/burn/bridge feed
  * `GET /reserves` — latest attestation snapshot/metadata
* Audit access: Read-only data rooms and exportable reports

### 9. Economics (High-Level)

* Setup: Legal, technical, and vault onboarding
* Flow fees: Mint/burn, settlement, optional DeFi integration
* Distribution: Listings, liquidity seeding (if applicable), co-marketing
* Revenue sharing: Optional splits for channel partners/OEMs. *Full schedule provided in the Partner Agreement.*

### 10. Service Level Agreements (Indicative)

* Mint window: T+0 once custody is confirmed (business hours)
* Attestations: Monthly (standard) • Weekly (premium)
* Redemption: T+1 bar release (standard) • Same-day (priority, location-dependent)
* Support: 24/5 operations; incident updates ≤ 2 hours; post-mortems ≤ 5 business days

### 11. Compliance & Risk Controls

* Licensed settlement: Precious metals & stablecoin rails where applicable
* KYC/KYB & sanctions: Required for program onboarding; mandatory for physical redemption
* Address-level controls: Rare, policy-bound (e.g., legal requests, exploit response)
* Change management: Mint/burn role rotation, key management, upgrade policy
* Risk disclosures: Market, custody, counterparty, bridging, smart-contract, and liquidity risks

### 12. Integrations & Distribution

* Venues: DEX/CEX/OTC partners, market-maker programs
* DeFi rails: Lending markets, LP vaults, hedged strategies, structured notes
* Bridging: Omnichain movement as enabled; settle where liquidity is deepest
* Oracles: Price feeds for NAV/marking (per integration)

### 13. Example Term Sheet (Template)

> Issuer: \<Partner Legal Name>\
> Asset: Gold (LBMA 99.99%), allocated/segregated\
> Unit: 1 troy ounce per token (fixed)\
> Chain: Primary \<chain>; bridging per schedule\
> Initial mint cap: \<X,000> oz (expandable via attestation)\
> Fees: Setup \<x>; Mint \<x bps>; Burn \<x bps>; Settlement \<x>; DeFi \<x>\
> Attestations: Monthly (independent audit optional/quarterly)\
> Redemption: T+1 at \<Vault Location>; shipping at cost\
> Reporting: API + monthly PDF\
> Co-marketing: Joint PR + listing support (optional)

### 14. Example Use Cases

* Refiner working capital: Tokenize 5,000 oz; sell 1,000 oz on-chain; use remaining as collateral for a revolving line.
* Dealer omni-retail: Offer 1-oz PGOLD units to global buyers; ship bars only on redemption.
* Treasury optimization: Park idle bars as tokens for short-term liquidity and hedged LP strategies.

### 15. FAQs

<details>

<summary><strong>Do you support gram/kilo denominations or serial-bar tokens?</strong></summary>

**No.** All issuance is standardized: **1 troy oz per token**.

</details>

<details>

<summary><strong>Who can mint/burn?</strong></summary>

Only role-gated program addresses controlled by the TaaS agreement.

</details>

<details>

<summary><strong>Is KYC/KYB required?</strong></summary>

For program onboarding and **physical redemption**. Secondary on-chain transfers remain permissionless unless policy requires controls.

</details>

<details>

<summary><strong>How is supply matched to reserves?</strong></summary>

1:1 mapping with attestation references; burns on redemption reconcile supply.

</details>

### 16. Getting Started

<details>

<summary>Contact Us</summary>

<support@pleasing-international.com>

</details>

<details>

<summary>Schedule a Call</summary>

<https://calendly.com/pleasing_golden/30min>

</details>


---

# 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:

```
GET https://pleasing.gitbook.io/docs/solutions/tokenization-as-a-service-taas.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
