Title Agenda Tplus Overview Key Challenges Solutions Next Steps
Discovery Call
Tplus × Alchemy

Infrastructure & Data Layer for a Latency-Sensitive, Multi-Chain CLOB Exchange

Call Objective: Understand Tplus's current infrastructure bottlenecks, scalability requirements, and multi-chain architecture to explore how Alchemy can support their growth as a long-term infrastructure partner.

Key People

WhoRoleWhat They Care About
Markus Founder End-to-end product velocity, exchange-grade performance, technical architecture
Charco Head of Growth GTM strategy, partner pipeline, ecosystem distribution, narrative
Lazer Head of Liquidity Market maker relationships, liquidity sourcing, capital onboarding

Agenda

01
Tplus Overview

An overview of Tplus's core business
03
Alchemy Solutions

How can Alchemy help scale Tplus and solve their bottlenecks?
02
Key Challenges

Key challenges we noticed on the surface
04
Next Steps

Establish next steps/follow-ups

01

Tplus Overview

Here's what we've learned about your architecture, your differentiators, and what you're solving for.

Core Architecture

  • DEX built on an offchain CLOB running inside a TEE
  • Trade execution & confirmation targeted at <1ms
  • Decouple trade confirmation from settlement

What Makes Tplus Different

  • Unified Liquidity
  • Composability w/ external protocols, exchanges, and custodians
  • Support every asset and product, including non-crypto categories

Capital Efficiency Focus

  • Margin checked at match time
  • Quote and cancel prioritized for market makers
  • Solvency is the #1 design constraint

Problem Tplus is Solving

  • Liquidity and product fragmentation across chains & venues creates verification and latency overhead
  • Tplus solves orderflow execution in a trustless & multi-chain setting

02

Key Challenges

A few challenges Tplus may face while building

1

Node Latency & Data Gaps

  • Sub-millisecond matching engines require deterministic, low-latency blockchain reads across multiple chains
  • Public RPC infrastructure often produces latency spikes and inconsistent responses
  • Inconsistent chain data can cause incorrect margin checks, stale balances, or risk engine errors
2

Multi-Chain Polling Bottlenecks

  • Exchanges must monitor deposits, settlements, and liquidation triggers across many chains in real time
  • Polling infrastructure introduces detection lag and missed-event risk
  • As chain coverage expands, polling becomes expensive and difficult to scale reliably
3

Token Data

  • Supporting many assets requires token metadata, balances, transfer history, and pricing data
  • Long-tail token support creates manual onboarding and maintenance overhead
  • Without a unified data layer, teams must build and maintain complex indexing infrastructure

03

Alchemy Solutions

How can Alchemy help scale Tplus and solve their bottlenecks?

Node Latency & Data Gaps → Alchemy RPC (Cortex)

Their Problem

Need fast, deterministic chain reads for a sub-ms matching engine and risk system.

What Alchemy Provides

  • Contextual smart routing — up to 2.5x faster queries globally
  • Elastic throughput — scales automatically, launch-day safe
  • Multi-region infrastructure with autonomous failovers
  • Unlimited-range getLogs — scan entire chain event history 265x faster
  • Block-perfect data consistency — no stale reads
  • Shuffle-sharded tenant isolation — no noisy-neighbor spikes
Your risk engine and matching layer get deterministic, low-latency data without managing node infrastructure. You focus on trading logic; the chain access layer just works.
Polling Bottlenecks → Webhooks + Smart Websockets

Their Problem

Polling multiple chains for deposits, settlements, and liquidation triggers is expensive, unreliable, and introduces dangerous detection lag.

What Alchemy Provides

  • Webhooks: Mined/dropped transaction alerts, address activity monitoring, custom event hooks — at-least-once delivery guarantee
  • Smart Websockets: Filtered subscriptions for new events/logs, pending transactions (mempool), mined transactions, and new block heads
Replace polling with push. Deposits credited instantly, settlement confirmations in real time, liquidation triggers without gaps. Lower cost, higher reliability.
Token Data → Token API + Transfers API

Their Problem

Supporting "every asset" means managing metadata, pricing, and transfer history for a growing universe of tokens across chains.

What Alchemy Provides

  • Token API: No token list required — balances, allowances, metadata, and real-time/historical pricing across all supported EVM chains
  • Transfers API: Full historical activity (including internal transfers) in one request — 100x faster than alternatives
Onboard new assets without building your own indexing pipeline. Your "every asset" roadmap stays on track without engineering drowning in token data infrastructure.

04

Next Steps

Start with the 2-3 chains that matter most, prove the fit, and expand from there.

1
Validate
This Week
2
Deep-Dive
Week 2
3
Pilot Scope
Week 3
4
Production
Week 4+

Step 1: Validate Technical Fit

  • Tplus shares: Top 2-3 priority chains, critical RPC methods, peak throughput estimates, real-time event requirements
  • Alchemy shares: Benchmark data and latency profiles for those specific chains
  • Architecture recommendations based on Tplus's throughput and latency requirements

Step 2: Technical Deep-Dive

  • Joint session: Tplus engineering + Alchemy Solutions Engineering
  • Walk through RPC performance, Webhook/Websocket architecture, Token API coverage
  • Identify gaps or custom requirements

Step 3: Define Pilot Scope

  • Focused pilot: RPC + Webhooks on 2 chains in testnet environment
  • Success criteria: latency targets met (p50/p95/p99)
  • Zero missed events over defined test period
  • Token data coverage confirmed for target asset list

Step 4: Pilot Execution → Production

  • Run pilot, measure against agreed SLOs, iterate
  • Gate mainnet infrastructure decision on pilot results
  • Expand to additional chains and products based on what works