Mainnet preview, sample data 24h vol $48.2M · operators 14 · pairs 26
All-in-one trading and liquidity v1.4.2

Infrastructure for tokenized markets.

Spin up your own market for any tokenized asset. Microsecond matching, real-time settlement, and a journal that auditors and counterparties can verify end to end.

10 ledgers live, including ETH, SOL, BASE, ARB, OP, ZK, BTC L2s operators 14, 24h vol $48.2M (sample) ↓ scroll for the full stack
USDC ↔ USDC 1:1 cross-pair RWA / USDT 1.0024 ETH/SOL 0.0489 ▲ 2.14% BTC/ARB 0.0312 ▲ 0.88% SOL/BASE 0.41 ▼ 0.42% sample / signed journals PEPE / DOGE 0.000002 ▲ 12.4% operators 14 USDC ↔ USDC 1:1 cross-pair RWA / USDT 1.0024 ETH/SOL 0.0489 ▲ 2.14% BTC/ARB 0.0312 ▲ 0.88% SOL/BASE 0.41 ▼ 0.42% sample / signed journals PEPE / DOGE 0.000002 ▲ 12.4% operators 14
01 / Operator setup

Secure composable
crosschain market
infrastructure.

Trading and liquidity infrastructure you actually run. Five steps from clone to first matched fill, operator-controlled, end to end.

01 / I

Infrastructure installation

Provision the Aspens stack on your hardware, cloud, or TEE-backed enclave. Reproducible builds and remote attestation included.

$ just deploy --stack core
02 / II

Smart contract deployment

Deploy the verifying contracts to your chosen origin and destination chains. Foundry scripts, audited templates.

forge script Deploy.s.sol
03 / III

gRPC configuration

Wire signer, arborter, and rebalancer over mTLS-secured gRPC channels. Proto-defined contracts, generated bindings.

arborter.toml, signer.toml
04 / IV

Token registration

Whitelist token contracts, decimals, and bridging policy per pair. Configure rebalancer thresholds and fee tiers.

aspens-cli token add
05 / V

Market creation

Open your first order book across ledgers and route intents through the matching engine. Live in minutes.

POST /v1/markets
02 / Capabilities

Move any tokenized
asset to where it
needs to be.

Four pillars that together produce a self-hosted market for any tokenized asset. Not a hosted product — your stack, your terms.

i / Operate

Run the stack yourself.

Run the entire Aspens stack on your own infrastructure. Reproducible builds, signed releases, and remote attestation — so what you deploy is exactly what you audited.

Components: arborter, signer (TEE), rebalancer, aspens-sdk.

arborterv1.4.2healthy
signer (TEE)v0.9.1attested
rebalancerv0.7.5healthy
aspens-sdkv2.0.0connected
contracts/ethv0.4.0deployed
contracts/solv0.4.0staging
ii / Trade

Trade anything tokenized.

If it's tokenized, it trades here. Pair any asset across any supported ledger. No liquidity middlemen, no custodial bridges, no rehypothecated wrappers.

Native assets, stablecoins, RWAs, memecoins, LSTs, yield tokens. Any pairs, any ledgers.

01StablecoinsUSDC · USDT · DAI · USDe
02Native assetsETH · SOL · BTC · TIA
03Real-world assetstreasuries · credit · CRE
04MemecoinsPEPE · DOGE · BONK · WIF
05Liquid stakingstETH · LST baskets
06Yield tokensPT / YT · vaults
iii / Integrate

Plug into your workflow.

Drop the SDK into your terminal, bot, or treasury workflow in under 50 lines. REST, gRPC, and TypeScript first — compose with whatever already runs your trading.

SDKs: TypeScript, Rust, Python. Transports: gRPC, REST, WebSocket.

// connect to your operator instance
import { AspensClient } from "@aspens/sdk"

const client = new AspensClient({
  endpoint: "https://your-operator.aspens.xyz",
  market:   "ETH-SOL",
  signer:   teeSigner,
})

await client.submitIntent({
  side: "buy",
  size: 1.25,
  price: 0.0489,
})
// matched, attested, settled
iv / Partner

Build it with our team.

We work hand in hand with operators, market makers, and protocols who want infrastructure they actually control. White-glove onboarding, custom market design, direct line to the team.

We onboard credible projects only.

Pilot scope2 to 4 weeks
First marketsingle pair, single op
Mainnet date~ 6 weeks from kickoff
Onboardingwhite-glove
Direct team lineopen
03 / Live activity

Every fill,
fully
accounted for.

A real-time feed of trades settling across operators. Every entry carries a signed receipt and is replayable bit for bit by any party.

SAMPLE / mainnet preview / illustrative feed
24h vol $48.2M fills 12,481 operators 14
0x12bd78a49912
USDC ↔ USDC
actionBRIDGEevents2opaspens-04
125,000.00
Verified
0x88e24a902210
RWA / USDT
actionSETTLEevents3opaspens-07
$48,200.00
Verified
0x9af3e21cfa01
ETH / SOL
actionSWAPevents4opaspens-01
2.481 ETH
Verified
0xff0100330a4d
BTC / ARB
actionSWAPevents5opaspens-02
0.142 BTC
Attesting
0x4d7c91facc02
SOL / BASE
actionSWAPevents4opaspens-01
38.4 SOL
Verified
0xa101bbc171f0
PEPE / DOGE
actionSWAPevents6opaspens-09
412M PEPE
Verified
04 / Process

From intent
to receipt.

Match in microseconds. Settle in real time. Hand over a complete report on demand. Three things every market does — done at speed, with proof.

Match. 01

Match in microseconds.

Operators submit signed intents into a shared mempool. The engine resolves pairs across ledgers in microseconds and emits the optimal fill set without ever touching custody.

Settle. 02

Settle in real time.

Once matched, fills settle directly against the operator's verifying contracts on origin and destination. No waiting on bridges, no batching delays — value moves the moment the match is signed.

Report. 03

Post-trade reporting.

Every fill produces a signed journal entry — engine version, signer attestation, route, latencies. Pull a report for any window and hand it to counterparties, auditors, or regulators.

~/aspens / create-market.sh
zsh● live
$ curl -X POST https://operator.aspens.xyz/v1/markets \
   -H "Authorization: Bearer $OPERATOR_KEY" \
   -H "Content-Type: application/json" \
   -d '{
     "pair":   "ETH-SOL",
     "origin": { "chain": "ethereum", "token": "0xC02a…6cc2" },
     "dest":   { "chain": "solana",   "token": "So111…1112" },
     "lot":    "0.001",
     "tick":   "0.00001",
     "fee_bps": 6
   }'

# 201 Created
{
  "market_id": "mkt_01HZQ8F2XK",
  "status":    "live",
  "attestation": "sgx://0x9a…f21c",
  "opened_at": 1714232041
}

$ aspens-cli market watch mkt_01HZQ8F2XK
# streaming intents
   #0001 buy  1.25 ETH @ 0.0489
        matched 0.8ms · settled 0.6s
   #0002 sell 3.10 SOL @ 0.0488
        matched 0.6ms · settled 0.9s
   #0003 buy  0.50 ETH @ 0.0490
        matched 0.9ms · settled 0.5s
05 / Auditable journal

Every fill carries
its own receipt.

A signed, structured journal entry for every fill. Readable by humans, verifiable by machines, replayable bit for bit.

trade-journal.json
verified● TEE
{
  "trade_id":    "tr_01HZQ8F2XK4N9",
  "market":      "ETH-SOL",
  "timestamp":   1714232133,
  "side":        "buy",
  "size":        1.25,
  "price":       0.0489,
  "execution": {
    "engine":   "arborter@v1.4.2",
    "latency":  "1.18s",
    "hops":     ["eth-mainnet", "solana-mb"]
  },
  "proof": {
    "tee":        "intel-sgx",
    "attestation": "0x9a…f21c",
    "signer_pk":   "0x04…81ef",
    "verified":    true
  }
}
verifiable by anyone

Auditable
by design.

Each trade emits a signed journal entry — engine version, signer attestation, route, latencies. Counterparties replay it locally, auditors get a complete window on demand.

attestationsgx://0x9a…f21c
signer pubkey0x04…81ef
enginearborter@v1.4.2
verifiedtrue
replayabletrue
06 / Why Aspens

Six properties
we won't compromise on.

Each one is load-bearing. Pull on any of them and the rest hold. Together they describe what we mean by infrastructure you can actually run on.

Real-time settlement.

Fills settle the moment they're signed. No waiting on a bridge, no overnight batches — value moves between counterparties at the speed of the match itself.

Microsecond matching.

A real central limit order book under the hood, resolving pairs across ledgers in microseconds. Price discovery happens at engine speed, not block time.

Auditable journal.

Every intent, every match, every settlement leaves a signed receipt. Counterparties, auditors, and regulators all see the same canonical history — replayable bit for bit.

Post-trade reporting.

Pull a complete report for any window — fills, routes, latencies, signer attestations. Hand it to compliance, share it with a counterparty, file it with a regulator.

Operator-controlled infra.

Your hardware, your keys, your policy. We ship the stack. You run it under whatever jurisdiction, uptime regime, and customer agreement makes sense for you.

TEE-attested execution.

Signing keys never leave hardware-attested enclaves. The signer can prove its code, its inputs, and the exact fill it produced — to anyone, on demand.

07 / Questions

Frequently asked
questions.

The short answers. The long ones live in the docs and in conversation. Please reach out.

What exactly is Aspens?
Trading and liquidity infrastructure for tokenized assets. Operators run their own matching engine, signer, and rebalancer; traders submit intents and receive fills that settle in real time and carry a signed, auditable receipt.
Who is this for?
Protocols, market makers, treasuries, and infrastructure teams who want to run their own market and account for every fill themselves — instead of renting trust from a centralized exchange or a black-box bridge.
Which ledgers and assets are supported?
Any EVM-compatible ledger plus Solana out of the box, with active work on additional non-EVM ecosystems. Asset-side we're agnostic — stablecoins, native assets, RWAs, memecoins, LSTs, and yield tokens are all in production today.
How is custody handled?
Operators never take custody of trader assets in the traditional sense. Funds move under signed intents, verified end to end. Compromising any single component is not enough to forge a fill.
How do I get started?
Book a quick call and we'll scope a pilot market with you. We work hand in hand with credible projects from spec through to mainnet.

Connect.
Deploy.
Trade.

We want to work with credible projects. If you have something worth partnering with, reach out. Calendly is open and we read every note.