# Fees
Divergence v1 introduces highly customizable options pools. Each has its own underlying, collateral, expiry, and strike price. Once options expire, a pool's address cannot be reused to deploy a new pool. It is impractical to enable different fees for each pool, due to the issue of liquidity fragmentation. Therefore, fees are configured based on the underlying asset.
It is expected that traders and liquidity providers favor certain fee levels for options with common underlying assets. Option pools with rarer underlying will naturally prefer a higher fee, to counterbalance market-making risks.
### Transaction Fee
Transaction fees are proportionally divided among active liquidity at the time of a trade. If the option price leaves a position's range, that liquidity no longer earns fees. If the options price reenters the range, the liquidity starts earning fees again. Liquidity providers collect fees separately from the pool.
Pools have a default transaction fee of 0.3% per notional. That means, for each option token sold, a transaction fee of 0.003 collateral units applies. More fee rates of up to 1% may be added in the future per on-chain governance.
### Exercise Fee
After settlement, those options that expire profitably can be exercised for 1 collateral each. An exercise fee of 0.15% applies when option holders claim payoffs. This fee rate does not apply to liquidity providers, who can keep their received premiums from out-of-money options.
### Protocol Fee
The protocol collects 30% of the transaction fee, as well as the exercise fee. The protocol governance has flexibility in changing the fraction of fees that go to the protocol.
---
# 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.divergence-protocol.com/overview/protocol-basics/fees.md?ask=
```
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.