5 Wholesale Central Bank Digital Currency Application

The wholesale central bank digital currency (CBDC) sample application and related packages support transaction scenarios between a system owner and participating institutions.

The wholesale CBDC sample represents the life cycle of a wholesale CBDC token. The sample specification file uses the extended Token Taxonomy Framework standard that is supported by Blockchain App Builder. The generated smart contract includes methods from initializing a wholesale CBDC token, account operations, and role assignments to minting, transfers, and burning of CBDC tokens. It also provides notary accounts for approving minting, transfers, and burning operations, and it supports compliance through account-level daily limits and auditing procedures.

The wholesale CBDC solution comprises the following packages.

  • Prebuilt wholesale CBDC smart contract
  • Wrapper APIs for CBDC setup and lifecycle operations
  • Database view definitions to support analytics
  • A sample GUI application

To get the wholesale CBDC packages, in the Oracle Blockchain Platform Enterprise Edition console click Digital Assets. Click Applications and then select Wholesale CBDC Application.

To preview sample actions for the application without actually calling a smart contract, click Lifecycle.

Quick Start

Complete the following steps in order, setting up the central bank first and then repeating the required setup for each participating financial institution.

  1. Deploy the wholesale CBDC application from the Oracle Blockchain Platform instance by using one-click deployment. Wait until the smart contract, wrapper API, rich history services, application, and service configuration are ready.
  2. Open the application URL. Enter the wholesale CBDC token ID, review the prefilled values, and optionally update the user-facing customizations. Apply the configuration before creating accounts.
  3. Sign in as the bootstrap central bank administrator and initialize the token. Register or verify the founder and participant institution organizations. Create the central bank accounts and a financial institution administrator account for each participating institution, selecting or creating each user’s wallet and choosing the appropriate application group and limits.
  4. Complete deployment and setup for each participating organization. The financial institution administrator signs in and creates the remaining manager, officer, user, and auditor accounts for the organization.
  5. After the financial institution manager accounts are created, as the central bank administrator use the Account Actions > Sync Roles command on each manager account to add its Escrow ledger role. The financial institution administrator can assign the Manager application group but cannot grant the required Besu Notary role, which is displayed in the UI as Escrow. Verify all accounts, wallets, groups, roles, and limits.
  6. Sign in as each central bank and financial institution persona to verify that the expected workspace opens, the wallet and account context is correct, and that restricted actions are unavailable.
  7. Run operations in the token life cycle: request and approve creation, transfer to the issuer, distribute or return value, approve participant transfers, and retire value.
  8. Use the Transactions page and auditor workspaces to confirm balances, pending requests, operation IDs, and final ledger history.