Transferring Assets - IBM Digital Asset Haven integrated with OSO

Edit online

This section explains how to transfer assets using IBM Digital Asset Haven integrated with IBM Hyper Protect Offline Signing Orchestrator. It covers prerequisites, step-by-step instructions for initiating transfers, and policy approval workflows. The guide also highlights transaction monitoring and security considerations for irreversible blockchain operations.

Before you begin

  • Log in to your IBM Digital Asset Haven.
  • Ensure you have a wallet with a sufficient balance of the asset you want to transfer.
  • Confirm the recipient’s wallet address.
  • Verify that IBM Hyper Protect Offline Signing Orchestrator (OSO) is integrated with IBM Digital Asset Haven.
Note: Use the SDKs to perform transactions with a Solana wallet. For assistance, contact IBM Support.

Procedure

  1. Navigate to Operations > Wallet
    Locate and click the wallet you want to use for the transfer. The wallet details page opens, displaying balances and transaction history.
  2. Initiate the Transfer
    In the assets list, find the asset you want to transfer and click Send. The transfer modal opens. Complete the following fields:
    • To: Paste the destination wallet address. Double-check that the address is correct and matches the intended blockchain network.
    • Amount: Enter the amount of the asset you wish to transfer.
    • Pay Fees with Another Wallet: Optionally, use the Fee Sponsor feature to pay transaction fees from a different wallet.

    Review all details carefully, asset type, amount, and recipient address before clicking Transfer.

    Important: Blockchain transactions are irreversible. Once confirmed, they cannot be canceled or reversed.
  3. Await Policy Approval (If Applicable)
    If your organization enforces security policies (for example, requiring manager approval for transactions above a certain amount), the transfer will remain in Pending status until approved.
  4. Monitor Your Transaction
    Track the transaction status in real time. It will progress through the following stages: Pending Approval → Executing → Broadcasted → Confirmed.
    Note: The status changes to Confirmed after the trasactions are approved in IBM Hyper Protect Offline Signing Orchestrator.
  5. Approval in IBM Hyper Protect Offline Signing Orchestrator
    Auditors must approve the transaction in both Preconfirmation and Postconfirmation queues within IBM Hyper Protect Offline Signing Orchestrator. The status changes to Confirmed only after these approvals are completed.
    Restriction: Do not initiate multiple transactions at the same time. Always wait for the previous transaction to complete before starting a new one. Starting concurrent transactions can cause failures.