> For the complete documentation index, see [llms.txt](https://golden-shield-digital-treasury-b.gitbook.io/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://golden-shield-digital-treasury-b.gitbook.io/product-docs/bondtrust-protocol/editor.md).

# Overview of the BondTrust Protocol

Unlike ordinary crypto tokens, **tokenized sovereign bonds** require multiple mechanisms for **compliance, custody, and transparency**. For example, the issuance and transfer of GDB sovereign bond tokens are only permitted for verified investors who have completed **KYC/AML checks** and meet jurisdictional requirements. Therefore, tokenized government securities cannot be issued or transferred freely like standard ERC-20 tokens. It is crucial to ensure that issuers, custodians, and investors can issue, invest, and trade in a **fully regulated and transparent manner**. This is the role of GDB’s **BondTrust Protocol**.

The BondTrust Protocol provides issuers with tools to manage the **entire lifecycle of digital sovereign bonds** and offers smart contract infrastructure for issuance, settlement, interest payments, and redemption. It also ensures that all operations remain compliant with regulatory frameworks while maintaining **on-chain transparency and 1:1 reserves**.

### Structure of the BondTrust Protocol

The main components of the BondTrust Protocol are as follows:

* **GDB Tokenized Bond (G-Bond):**\
  An ERC-20 compatible token representing a unit of sovereign debt, extended with compliance and settlement features. Each G-Bond is **1:1 backed by real U.S. Treasuries or other sovereign bonds** held by licensed custodians.
* **Bond Apps:**\
  Smart contract applications that manage key events in the lifecycle of digital sovereign bonds — including **issuance, trading support, coupon distribution, and redemption at maturity**.
* **BondTrust Services:**\
  The infrastructure layer enabling G-Bonds and Bond Apps to function. It consists of:
  * **Compliance Service:** Ensures transfers and holdings comply with jurisdictional rules (e.g. investor eligibility, transaction limits).
  * **Custody & Reserve Service:** Verifies that every token is 1:1 backed by real sovereign bonds in licensed custody.
  * **Registry Service:** Maintains verified investor data (wallet address, KYC/AML status, jurisdiction) to ensure only eligible users can hold G-Bonds.

***

### Overview of How It Works

The BondTrust Protocol allows issuers, custodians, and investors to handle **tokenized sovereign bonds** in a compliant and secure manner through G-Bonds and BondTrust Services.

A G-Bond can be understood as an **extended version of a standard ERC-20 token**. Unlike ordinary tokens, G-Bonds cannot be freely transferred. Instead, the **Compliance Service** intervenes at each transaction:

* Is the transaction compliant with securities and financial regulations?
* Is the recipient an eligible, KYC-verified investor?
* Does the transfer remain within predefined limits or holding rules?

When new G-Bonds are issued, the **Custody & Reserve Service** verifies that an equal amount of sovereign bonds are held in reserve, ensuring 100% backing and preventing over-issuance. Advanced features include **automatic coupon payments via smart contracts**, redemption at maturity, and the ability to apply **vesting or lock-up conditions** if required by regulation.

Wallet roles (issuer, investor, custodian, or exchange) are managed by the **Registry Service**, which links each address to its verified attributes (e.g. jurisdiction, accreditation status, investor ID). This ensures only authorized participants can access or transfer sovereign bond tokens.

Through this design, the BondTrust Protocol ensures that **GDB’s digital sovereign bonds operate with the same trust and compliance as traditional markets**, while adding the efficiency, transparency, and programmability of blockchain technology.