Dinari earns revenue from transaction fees on dShare issuance and redemption, platform fees charged to partner integrators that consume its tokenization API, and the yield spread on the Treasury reserves backing USD+. Its go-to-market is B2B — third-party wallets, brokerages, and fintechs integrate Dinari as an infrastructure layer rather than end users interacting with Dinari directly.

Dinari issues dShares — ERC-20 tokens backed 1:1 by the underlying equity or ETF, held with licensed custodians. Each share is purchased on traditional markets before the corresponding token is minted, so token prices track real market pricing. The catalog covers 150+ tokenized stocks and ETFs (e.g. AAPL, NVDA, TSLA, SPY). Dinari also issues USD+, a Treasury-backed yield-bearing stablecoin. Products are available on Arbitrum, Base, Blast, Ethereum, Avalanche, and Plume.

Dinari is a US-based fintech that operates as an SEC-registered transfer agent, providing infrastructure for tokenizing publicly traded US equities and ETFs as onchain assets called dShares. Rather than serving end users directly, Dinari positions itself as a B2B infrastructure layer used by partner platforms (e.g. Gemini, Cadana, Fasset) to offer tokenized US securities across 80+ countries.

twitter

website

discord

github

Real-world asset (RWA) issuers

Dinari

# Contract deployers Methodology

## Overview

Contract deployers measures the number of unique addresses that have deployed at least one smart contract. It is a proxy for how many independent developers or entities that actively publish code onchain.

## Data sources

- Blockchain transaction data capturing contract creation operations
- Transaction execution traces for internal contract deployments
- Block metadata for daily time boundary calculation

## Common calculation approaches

### Transaction-based deployment extraction
Contract creation data is extracted from blockchain transaction records where new contract addresses are initialized. For example, unique deployer addresses are identified from transaction metadata on networks such as Ethereum and Polygon.

### Trace-level execution analysis
Internal contract deployments are identified through the analysis of transaction execution traces, which capture creations triggered by other smart contracts. This approach is used to ensure comprehensive developer activity is captured from chains including Arbitrum One and Base.

### Multi-layer infrastructure aggregation
Deployment activity is aggregated across different environments within a single ecosystem to provide a unified view of developer adoption. For instance, unique addresses are consolidated from contract creation records across both the BNB Chain mainnet and opBNB.

**Note:** The calculation approaches and protocol examples above are representative patterns. Individual protocol implementations may vary.

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

Unique addresses that deployed at least one smart contract.

Dinari

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown