APEX WHITE PAPER

Abstract

This document outlines the underlying architecture, routing protocols, and risk methodologies utilized by the Transcribe Finance trading engine. Our goal is to synthesize disparate liquidity pools, automated market making (AMM) protocols, and centralized order books into a unified, zero-latency execution gateway for retail and institutional capital.

1. Algorithmic Routing Engine (ARE)

The ARE is the core of our Bot Trading methodology. Rather than connecting to a single exchange, the ARE aggregates Level 2 order book data across Binance, OKX, Kraken, and decentralized aggregators. When a user's Grid Bot or Momentum ML Bot triggers a signal, the ARE automatically fractions the order block and executes the trade via the route with the lowest slippage.

2. Copy Trading Synchronization

Latency is the enemy of copy trading. To ensure followers receive identical entry and exit prices as their Master Traders, we employ a Deterministic Execution Ledger. When a Master Trader places an order, the ledger locks the required proportionate leverage sizes for all copiers in memory. The consolidated order is fired collectively to the market.

If the total volume exceeds available tier-1 liquidity, the engine employs a TWAP (Time-Weighted Average Price) algorithmic fill to mitigate price impact, distributing the average execution price proportionally across the Master and Copiers.

3. Collateralized Lending Protocol

Our Capital Loans utilize an over-collateralized lending framework similar to prominent DeFi protocols (e.g., MakerDAO, Aave), but executed internally to avoid smart contract gas fees and external oracle manipulation.

• Oracle Redundancy: Prices are pulled via a medianized feed from 5 independent Tier-1 spot exchanges.
• Liquidation Engine: If a user's LTV approaches the liquidation threshold (75%), an automated margin call is sent. At 80%, the system programmatically unwinds the collateral via our ARE backend, incurring a 2% liquidation penalty.
• Asset Security: Loan collateral is instantly swept to our offline multisig cold vaults.

4. Secure Vault Implementation

Platform security is partitioned into three distinct operational layers:

• Hot Wallet (5% of AUM): Connected to the internet via restricted VPS instances to process real-time withdrawals and bot liquidity demands.
• Warm Protocol (15% of AUM): Multisig wallets requiring 2-of-3 signatures, acting as a buffer reserve for the hot wallets.
• Cold Storage (80% of AUM): Completely air-gapped hardware security modules housed in Swiss ISO-certified data centers. Moving funds requires 4-of-7 manual cryptographic sign-offs from global executives.

5. Data, Privacy & Telemetry

Application logs capture operational events (order lifecycle, risk checks, authentication) with retention scoped by legal and security policy. Personal data processing is described in our Privacy Policy; we minimize collection to what is needed for KYC, fraud prevention, and service delivery.

Wallet connections use standard protocols (e.g. WalletConnect); we do not custody user seed phrases. Telemetry for product improvement is aggregated where possible and configurable per jurisdiction.

6. Monitoring, Incidents & Change Control

Production services are monitored for availability, latency, and error rates. Security-relevant events feed alerting pipelines. Material incidents are triaged under an internal response process; customer-facing communications follow legal and regulatory requirements where applicable.

Changes to trading, lending, or custody paths pass through staged rollout and regression checks. Emergency fixes may bypass full staging only under strict approval and post-incident review.

7. Governance & Document Updates

This white paper is maintained by the product and security teams. Material revisions receive version bumps and a short changelog. Archived PDFs may be available on request for institutional counterparties.

The platform is operated by a UK private limited company (Company No. 16632458). Registration and compliance summaries appear on our Certification page.