Introduce High-Value FT (HVFT) Support — Create, Transfer & Burn Enhancements

[Allen-Cherian]

Summary

This PR introduces High-Value Fungible Tokens (HVFT) functionality across the entire FT lifecycle, including creation, transfer, and burn operations. The changes encompass new API request parameters, updated RBT locking logic, and corresponding database schema modifications to support this new token type.

Key Features Added

1. High-Value FT Creation (/api/create-ft)

Added support for creating High-Value FTs via the following new request parameters:

• is_high_value: A boolean flag to identify the token as a High-Value FT.
• from_rbt: Indicates if RBT is used for the FT creation.
• ft_value: Defines the per-token value for HVFTs.

RBT Lock Calculation Change

The RBT count to be locked is now dynamically calculated for HVFTs using the formula:

RBTs locked = ft_count * ft_value`

New DB Enhancements:

• Added column is_high_value_ft to FTTable to identify high-value token sets.
• Added column rbt_lock_status to FTTokenTable to track the RBT lock state per token.
• Added a new FTIndexTable to maintain the latest index at which a High-Value FT was created.

2. FT Transfer Enhancements (/api/transfer-ft)

The existing transfer API has been extended to support High-Value FTs. The request body has been updated to include:

• is_high_value
• ft_value
• from_rbt (if applicable)

This ensures correct validation and transfer logic for HVFTs, maintaining consistency with the new database schema.

3. FT Burn Implementation (/api/burn-ft)

Introduced new burn functionality for both standard and high-value FTs. The burn logic now correctly identifies and handles high-value tokens with the new high_value_ft flag.

Request Body Example:

{
  "did": "bafybmiguvjk5nqxjmrdhfna42dzpgloy47d7r3vncsax6nxe3irir4vkdy",
  "from_rbt": false,
  "ft_count": 1,
  "ft_name": "HVFT",
  "high_value_ft": true
}