Fraxtal batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

Fraxtal is an Ethereum Layer 2 (L2) blockchain built on the OP Stack by Frax Finance. It uses frxETH as the gas token and features a blockspace incentive system called Flox. Fraxtal launched in February 2024.

Frax Finance team owns and governs the protocol. Frax Finance's investors include Dragonfly Capital, Mechanism Capital, Galaxy Digital, etc.

twitter

discord

etherscan

website

Blockchains (L2)

Fraxtal

# Fraxtal Contract deployers Methodology

## 1. Overview

Contract deployers is measured by the number of unique addresses that have successfully deployed at least one smart contract on Fraxtal. This metric is utilized as a proxy for the number of independent developers or entities actively publishing code onchain. It provides a foundational view of developer engagement and the expansion of the network's application layer.

## 2. Data sources

- **Blockchain events**: Contract creation records from the `contracts` table, covering Fraxtal

## 3. Step-by-step calculation

### Component A: Identification of contract deployments

- **Purpose**: Extract all recorded smart contract creation instances on the network.
- **Logic**: Contract creation records are retrieved from the underlying network data. For each deployment, the address of the account initiating the contract creation and the timestamp of the block are captured to identify the responsible entity.
- **Key fields**: `deployer_address` (identification of the creator) and `block_timestamp` (timing of deployment).

### Component B: Distinct deployer aggregation

- **Purpose**: Determine the daily count of unique entities publishing code.
- **Logic**: A distinct count is performed on the `deployer_address` field to isolate unique participants. The data is truncated to daily granularity using UTC timestamps. Each address is represented once per day regardless of the total volume of contracts deployed by that address within the period.

### Component C: Data finalization and normalization

- **Purpose**: Standardize the metric for reporting and ensure time-series continuity.
- **Logic**: Metric values are cast to bignumeric types to ensure numerical precision. A zero-filling strategy is applied to account for days where no contract deployments are recorded, maintaining a continuous historical record. Data is also filtered according to chain availability and data freshness parameters.

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

Unique addresses that deployed at least one smart contract.

FraxtalFXTL

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown