The network uses pessimistic proofs via the AgglayerGateway for settlement on Ethereum, with vault bridges for cross-chain asset transfers.

Katana Network provides a scalable execution environment connected to Ethereum through the Agglayer interoperability layer.

Katana Network is a Layer 2 blockchain built on the Agglayer ecosystem.

twitter

website

github

Blockchains (L2)

Katana

# Katana Network Trade count Methodology

## 1. Overview

Trade count measures the number of trades executed on a decentralized exchange. It shows how frequently users are buying or selling assets through the project. For Katana Network, the total number of trades executed on Katana Perps is captured across both V1 and V2 exchange deployments. Trading activity is monitored to provide insights into user engagement, platform liquidity, and overall transaction frequency.

## 2. Data sources

- **Blockchain events**: `TradeExecuted` events from `Exchange` contracts, covering Katana Chain

## 3. Step-by-step calculation

### Component A: Katana Perps trade extraction

- **Purpose**: Individual trade records are extracted from Katana Perps contracts.
- **Logic**: `TradeExecuted` events are parsed from `Exchange` contracts across both V1 and V2 deployments on Katana Chain. For each event, transaction details including the block timestamp, exchange version, buyer address, and seller address are extracted to identify unique trade occurrences.
- **Key fields**: `block_timestamp`, `buyer_address`, `seller_address`

### Component B: Daily aggregation

- **Purpose**: Trade records are aggregated into daily counts.
- **Logic**: Trade records are grouped by day using the block timestamp truncated to daily granularity. The total number of trades is calculated by counting the total records for each day, categorized by the chain and the Katana Perps product.
- **Key fields**: `block_timestamp`, `trade_count`

### Component C: Finalization and zero-filling

- **Purpose**: Data continuity is ensured and chain availability filters are applied.
- **Logic**: Daily trade counts are processed to ensure correct data types and valid chain and project identifiers. Missing days in the time series are filled with zeros to maintain a continuous daily record. Chain availability filters are applied to align the data with active chain periods.
- **Key fields**: `timestamp`, `trade_count`

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Number of trades executed on a decentralized exchange.

KatanaKAT

Trade count

Trade count

Competitive landscape

Chain breakdown