# Fees & Price Impact

{% hint style="info" %}
Operator and jurisdiction: BASIS is operated by BASIS DIGITAL INFRASTRUCTURE LTD, a Seychelles IBC (LEI: [254900IX2F2KCWNSSS64](https://lei.bloomberg.com/leis/view/254900IX2F2KCWNSSS64)).
{% endhint %}

In structural alpha systems, fees are part of the core cost model. They directly affect realized performance, execution precision, and strategy eligibility.

BASIS presents the fee surface clearly so users can evaluate:

* net yield after costs
* whether a strategy remains valid under current market conditions
* why deterministic risk controls may pause or reject execution

## 1) Platform-level fees

| Action     | Fee   |
| ---------- | ----- |
| Deposit    | 0%    |
| Swap       | 0.01% |
| Withdrawal | 0.05% |

{% hint style="warning" %}
Swaps on BASIS are same-token only and executed 1:1 between native assets and their staking representations:

* BTC ↔ stBTC
* ETH ↔ stETH
* SOL ↔ stSOL
* PAXG ↔ stPAXG

Cross-asset conversion is not supported.
{% endhint %}

## 2) What “price impact” means here

Price impact is the difference between:

* the expected execution level at the time an instruction is evaluated
* the realized average fill level after routing and execution

Price impact depends on:

* available depth and liquidity quality
* market volatility
* routing path quality
* execution latency

BASIS treats price impact as a risk variable within its deterministic execution framework. When projected cost overwhelms expected edge, the system can refuse execution.

This is part of how BASIS maintains execution precision and protects structural alpha capture.

## 3) Network fees are separate

On-chain transfers still require network fees at the protocol level:

* Bitcoin network fees for BTC transfers
* Ethereum gas fees for ETH and PAXG transfers
* Solana network fees for SOL transfers

These fees are paid to the underlying networks, not to BASIS.

## 4) Why fees matter in market-neutral systems

Even when exposure is controlled and directional risk is reduced, cost drag still compounds:

* frequent rebalancing increases cumulative execution cost
* collateral movement can introduce additional transfer overhead
* cross-venue settlement can reduce realized spread capture
* poor routing quality can erode edge through price impact

This is why BASIS emphasizes:

* deterministic execution logic
* strict eligibility thresholds
* state machine risk controls
* proprietary routing infrastructure
* high-throughput market connectivity via BHLE

{% hint style="success" %}
BASIS execution infrastructure is designed around deterministic behavior, mathematical constraints, and infrastructure-level precision, including sub-50μs latency targets and 100K+ OPS routing capacity under BHLE architecture.
{% endhint %}

## 5) User-facing implications

Before initiating activity, users should understand:

* deposits are made in native assets only: BTC, ETH, SOL, or PAXG
* BTC deposits use a BASIS-assigned address unique to the account
* ETH, SOL, and PAXG deposits require a connected Web3 wallet
* rewards accumulate in real time as the same stToken inside the Staking Wallet
* unstaking returns the full claimable stToken amount to the Staking Wallet
* unstake is full-position only and becomes available after any fixed lock-up period ends

## Related references

* Fees & Limits
* Deposits & Withdrawals
* Swaps
* Risk Disclosure
* Arbitrage Economics: Edge vs Cost


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.basis.pro/getting-started/fees.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.