Execution Precision & On-chain Routing

Operator & jurisdiction: BASIS is operated by BASIS DIGITAL INFRASTRUCTURE LTD, a Seychelles IBC (LEI: 254900IX2F2KCWNSSS64).

Accounting convention: USDT is used as an internal accounting and display unit only. It is not a deposit or withdrawal asset. Funding uses native assets only. BTC deposits use a BASIS-assigned address. ETH, SOL, and PAXG deposits use a connected Web3 wallet.

Public-chain execution is not a substitute for centralized execution. It is a distinct market structure with visible state, observable intent, and transaction ordering risk.

This page explains why execution precision matters for BASIS modules, especially structural alpha capture strategies that interact with public-chain liquidity.

1) The core execution problem

When a transaction is broadcast publicly, other market participants can observe intent before finalization.

This creates risks such as:

• order anticipation

• adverse reordering

• slippage amplification

• fee bidding pressure

For strategies that depend on small spreads, these effects can eliminate expected edge before settlement.

2) Why public-chain routing affects structural alpha capture

Opportunities on decentralized venues are visible through:

• pending transaction flow

• public state transitions

• quoted liquidity and reserve movement

If a profitable route is exposed too early, competing participants can:

• replicate the trade path

• move execution priority

• consume available spread

• force execution outside acceptable price bounds

This is why BASIS treats public-chain execution as a constrained routing problem, not as a guaranteed alpha source.

3) BASIS execution framework 🛡️

Market reality

Public-chain venues expose timing, state, and route intent.

Profitability depends on execution quality, not only signal quality.

BASIS control model

Key controls include:

• private and selective routing where supported

• bounded slippage with revert conditions

• route sizing based on real-time liquidity depth

• latency-aware venue selection

• failure-rate and fee-regime monitoring

• hard disable conditions when execution precision deteriorates

No routing method is perfect.

BASIS does not force execution when deterministic bounds fail. If the required execution precision cannot be maintained, the module is paused.

4) Decision policy

1

Measure spread, depth, and fee burden.

2

Estimate execution quality under current ordering conditions.

3

Apply state-machine limits and route constraints.

4

Execute only if expected structural alpha remains positive after all costs.

5

Disable or defer if the route fails deterministic checks.

5) When BASIS disables public-chain modules

BASIS will disable or restrict a module when one or more of the following conditions is present:

Condition	Why it matters	BASIS response
Fee regime spike	Net edge compresses below threshold	Pause or reduce route size
Unstable block conditions	Settlement predictability declines	Restrict execution
Elevated ordering competition	Public intent becomes easier to exploit	Shift routing or disable
Slippage bound breach	Execution no longer matches modeled price	Revert or pause
Abnormal failure rate	Signals degradation in route quality	Enter protective mode

6) Why this belongs in a trust document 🔍

A credible platform should define:

• the adversarial market structure

• the exact stop conditions

• the control logic that prevents forced execution

BASIS trust is grounded in deterministic execution, mathematical constraints, and auditable risk transitions.

Research support is provided by Base58 Labs as Research Partner, with ongoing work in market microstructure, structural alpha capture, and routing design.

Execution principle

Run only when:
expected edge > fees + slippage + ordering risk

Otherwise:
do not execute

Next: Risk Quantification & Stress Testing.