Trading Wallet

The trading wallet is implemented using 2-of-2 Timelocked Multisig where

• two signatures are required to authorize a transaction

• one of the signatures expires after a specific period

The trading wallet combines the user wallet’s private key with the radFi backend private key. This ensures that neither party can replace the user's transactions until the transaction has been confirmed on radFi.

Key Components

User Private Key

• The private key controlled by the user.

• Contributes to the multisig authentication required for the trading wallet.

Back-end Private Key

• A private key managed by the radFi backend system.

• Ensures platform-level security and coordination in wallet operations.

Create Trading Wallet API

• This API takes inputs from both the user's private key and the backend private key.

• It processes these keys to generate a radFi multisig trading wallet.

radFi Multisign Trading Wallet

• A multisignature wallet that requires both private keys for transaction execution.

• Enhances security by ensuring that both parties (user and radFi backend) must approve actions.

Flow Overview

• The user private key and backend private key are sent to the Create Trading Wallet API.

• The API processes the request and generates a radFi multisign trading wallet.

• This wallet is then used for secure trading operations within the radFi ecosystem.