Skip to main content

Manual Tasks Documentation

This document describes manual tasks that can be performed to manage supported assets in the Asset Reality platform.

Overview​

The platform integrates with external custodian providers (primarily Fireblocks) to manage supported cryptocurrency assets. These manual tasks allow administrators to refresh and retrieve the list of supported assets.

Authentication​

All API endpoints require authentication using an AR-Token header:

ar-token: <your-token-here>

You can fetch this by logging into production and checking the API calls made to the backend (e.g the /me endpoint) and using the AR token in the header to set this.

Tasks​

1. Refresh Supported Assets​

Purpose: Updates the list of supported assets from external custodian providers (e.g., Fireblocks).

Endpoint: POST /api/v1/custodian/supported-assets/refresh

Description: This endpoint triggers a refresh of the supported assets list from the configured custodian providers. Currently supports Fireblocks as the primary custodian provider.

Request Body:

{
  "fireblocks": true
}

Response (Success - 200):

{
  "error": false,
  "message": "Successfully refreshed supported assets",
  "data": true
}

2. Fetch All Supported Assets​

Purpose: Retrieves the current list of all supported assets from the local cache.

Endpoint: GET /api/v2/custodian/supported-assets

Description: Returns the complete list of assets currently supported by the configured custodian providers. This data is cached locally and can be refreshed using the refresh endpoint above.

Environment-Specific Endpoints​

  • Production: https://broker.assetreality.com
  • Demo: https://broker.assetreality-demo.com
  • Staging: https://broker.assetreality-staging.com
  • Local Development: http://localhost:8080 (if running via Tilt)

3. Fixing Tokens Sent to Wrong Address/Chain​

Purpose: Create assets for tokens that were sent to a deposit address on the wrong blockchain network.

Scenario: A token is sent to the wrong chain (e.g., PENDLE token sent to Arbitrum address instead of the intended Ethereum mainnet address).

Steps for Token Recovery​

Case 1: Token exists in Fireblocks but not configured in the Platform

  1. List the token on the correct chain in the Platform

    • Navigate to the currency/asset management interface on Fireblocks
    • Add the token with the correct blockchain network specification
    • Example: List PENDLE on Arbitrum network on Fireblocks

  2. Trigger supported assets refresh

    • Use the endpoint: POST /api/v1/custodian/supported-assets/refresh
    • This ensures the Platform recognizes the newly added asset from Fireblocks

  3. Generate new deposit address

    • In the Platform workspace generate a new deposit address for the token on the correct chain using the same subject and case
    • Example: Generate PENDLE (Arbitrum) deposit address

  4. Request Fireblocks transaction rescan

    • Contact Fireblocks support to rescan transactions for the affected vault/wallet
    • This ensures the incoming PENDLE (Arbitrum) deposit is detected and reflected in Fireblocks

  5. Refresh balance in Platform

    • Use the balance refresh functionality to sync the updated balance from Fireblocks
    • The recovered tokens should now be visible

Case 2: Asset already exists in Fireblocks and Platform

If the asset is already registered in both Fireblocks and the Platform:

  • Only Step 3 is required (generate the new asset/deposit address)
  • The Platform should automatically detect the balance once the deposit address is created

Testing​

Use the provided supported-assets.http file with REST Client extensions (VS Code REST Client, IntelliJ HTTP Client) to test these endpoints interactively.