- Setup
- Overview
- Tutorials
- How Tos
- Reference
- DAR Versions
- API Reference
- Commercials API
- Credential API
- Registry API
- Utility.Registry
- Utility.Registry.V0.Configuration.Instrument
- Utility.Registry.V0.Holding.Allocation
- Utility.Registry.V0.Holding.Burn
- Utility.Registry.V0.Holding.Lock
- Utility.Registry.V0.Holding.Mint
- Utility.Registry.V0.Holding.TokenApiUtils
- Utility.Registry.V0.Holding.Transfer
- Utility.Registry.V0.Holding.Unlock
- Utility.Registry.V0.Types
- Utility.Registry.V0.Util
- Utility.Registry.App
- Utility.Holding
- Utility.Registry
- Operator Backend API
- Releases
Introduction¶
This tutorial details the steps to force transfer
a tokenized instrument from Investor1
to Issuer
using the Credential and Registry utilities.
Contrary to a regular transfer
where both Investor1
and Investor2
have to approve, in a force transfer
, provided Investor1
granted an enforcement service
to the Registrar
, the Issuer
can initiate a force transfer
from Investor1
. And if the Registrar
approves the request, then the instrument is transfered to Issuer
without requiring the approval from Investor1
.
Instrument¶
The tokenized instrument transfered is called BOND.
Roles¶
Assumptions:
All entities are already onboarded for the roles below. See Issuing Tokenized Instruments if this is not the case.
Roles in Tokenization Utility |
Entity |
Roles in Asset BOND |
---|---|---|
Registrar (onboarded by Provider) |
Registrar |
|
Issuer (onboarded by Provider) |
Issuer |
Issuer of BOND, Holder of BOND |
Investor1 (onboarded by Provider) |
Investor1 |
Holder of BOND |
Credential Design¶
Assumptions:
All entities already have the credentials defined in Issuing Tokenized Instruments.