Tokenized Deposit Quick Start

The tokenized deposit sample represents the life cycle of a fungible token that represents a bank deposit.

All token transfers that are submitted are evaluated against the active approval policy. A transfer settles when approval is not required, otherwise it remains pending and is routed to the configured approver sequence.

The tokenized deposit solution comprises the following downloadable packages.

  • Prebuilt tokenized deposit smart contract
  • Wrapper APIs for tokenized deposit setup and lifecycle operations
  • Sample web application for working with tokenized deposits

To get the tokenized deposit packages, in the Oracle Blockchain Platform Enterprise Edition console select Digital Assets. Select Applications and then select Tokenized Deposit Application.

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

Quick Start

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

  1. Deploy the tokenized deposit 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 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 bank administrator and initialize the token. Register or verify the founder and participant entity organizations. Create the bank accounts and an entity administrator account for each participating entity, 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 entity administrator signs in and creates the remaining manager, officer, user, and auditor accounts for the organization.
  5. After the entity manager accounts are created, as the bank administrator use the Account Actions > Sync Roles command on each manager account to add its Escrow ledger role. The entity 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 bank and entity 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.