Start free
AboutMarketplacePricingContactSearch apps
Products
VantageStrataFolioGroundProof
Use cases
Treasury and financePayments and fintechTrading and market makingFunds and researchIssuers and protocolsCompliance and riskResearch and media
Sign inStart free
Report · FolioPlanned

Sui vs Aptos: Activity, Fees and Staking Compared

How do Sui and Aptos compare on activity, fees and staking this month?

Sui and Aptos compared each month on one set of definitions: user transactions, senders, fees on each chain's model, stake and stablecoins.

Build it in Studio →Ask for this data
ShareEmail itvoltfincrypto.com/apps/sui-vs-aptos
Blueprint

What the report will cover.

The report as it will open in Folio. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.

A monthly edition, dated and cited

Sui vs Aptos: Activity, Fees and Staking Compared

  1. The month in one table

    Sui and Aptos on one line each: transactions, senders, fees, stake and stablecoin supply, with the change from last month.

    • User transactions per chain
    • Distinct senders per chain
    • Fees paid per chain
    • Staked share of supply per chain

  2. How much each chain was used

    User transactions and distinct senders on matched rules, with Aptos system transactions left out, Sui transactions counted from checkpoints and the largest senders named.

    • User transactions
    • Distinct senders
    • First-time senders
    • Share of transactions from the largest senders

  3. What users paid

    Fees on each chain's own model: Sui computation and storage net of rebates, Aptos gas burned with storage deposits and refunds apart, in native tokens and USD.

    • Net gas fees in SUI
    • Gas burned in APT
    • Fees in USD per chain
    • Median fee per transaction

  4. Staking and validators

    Total stake, active validators, the share of supply staked and the rewards paid in the month's epochs on each chain.

    • Total stake
    • Active validators
    • Rewards paid in the month
    • Staked share of supply

  5. Stablecoins on each chain

    Month-end supply of USDC and USDT on each chain, counting native issuance only, with its change over the month.

    • USDC supply per chain
    • USDT supply per chain
    • Monthly change in stablecoin supply

  6. Definitions and receipts

    How each measure is defined on each chain, the checkpoints and blocks that close the month and the price sources used, so any figure can be checked.

About

What it answers, and for whom.

Sui and Aptos are layer 1s built on the Move language by teams that came from the same earlier project, yet they record activity differently: Sui counts transactions in checkpoints and charges storage separately, while Aptos writes protocol transactions into every block and burns its gas. This report sets them side by side each month, with one written definition per measure and the same month boundaries on both chains.

Each edition covers user transactions and distinct senders and the fees users paid under each chain's own model. It also compares stake, validators, rewards and month-end stablecoin supply. Every figure is pinned to the last checkpoint or block of the month on its chain and opens a receipt.

Method

How it will be measured.

Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.

How receipts work →
  1. The month closes at the last Sui checkpoint and the last Aptos block before midnight UTC, and every figure is read up to those points on both chains.
  2. Activity uses one rule on both chains: transactions users signed and their distinct senders, leaving out the protocol transactions Aptos writes into every block and crediting sponsored transactions to their senders.
  3. Fees follow each chain's own model and are shown in native tokens and in USD: on Sui, computation plus storage minus rebates; on Aptos, gas burned, with storage deposits and refunds apart.
  4. Stake and rewards are read from each chain's system state at its epoch boundaries, and stablecoin supply from the token contracts at month end; every figure links to a receipt.

The data it needs

Read from chain state and history

  • chain_activity_dailyTo buildChain activity by dayTransactions, active sending addresses, new addresses, contracts created and gas used on each chain per day, counted from blocks and transactions.
  • chain_fees_dailyTo buildFees and gas by chainFees paid per chain per day in the native token: base fee and priority fee percentiles, total fees, and the share burned where the chain burns fees.
  • staking_networks_dailyTo buildProof-of-stake networksStaked supply, staking ratio, validators and nominal rewards per proof-of-stake network per day.
  • stablecoin_supply_dailyPublishedStablecoin supply by token and chainNative supply of each USD and EUR stablecoin on each covered chain at the chain's last block of each day, from totalSupply() reads, with bridged copies kept apart.
  • native_prices_dailyTo buildOracle prices by dayReference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
  • Sui checkpoints and transaction effects: senders, computation cost, storage cost and storage rebate
  • Aptos user transactions: sender, gas used, gas unit price and the FeeStatement event
  • Sui system state and the Aptos validator set at each epoch boundary: stake, validators and rewards
  • Native USDC and USDT supply on each chain at month-end: Sui coin total supply and Aptos fungible asset supply
  • SUI and APT prices from DEX pools against native USDC on each chain at the month's last block
Questions

Questions people ask.

What is the difference between Sui and Aptos?

Both are layer 1s on the Move language whose founding teams came from Diem, but their designs diverged. Sui stores everything as objects and finalizes transactions on owned objects without full consensus ordering; Aptos keeps resources under accounts and runs every block through consensus and parallel execution.

Which is cheaper, Sui or Aptos?

Both charge small fees for a simple transfer, and the comparison depends on what a transaction does. Sui adds storage costs that can be refunded, and Aptos charges a refundable deposit for new state. The report compares the median fee per transaction and the total fees each month on the same definitions.

Which has more users?

The report compares distinct senders on both chains under one rule. Addresses are not people: both counts include bots and apps that send on users' behalf, and a single campaign can move a month's figure, so the report names the largest senders when they drive a change.

How does staking compare?

Both chains use delegated proof of stake with rewards paid at epoch boundaries. Sui's epochs last about a day and pay rewards from fees and a stake subsidy, while Aptos's epochs are shorter and pay rewards from new issuance. The report compares stake, validators, rewards and the share of supply staked.

Why compare them every month?

They compete for the same developers and users, and their figures are often quoted under different definitions. A dated monthly edition on shared rules shows how the comparison moves over time instead of fixing it at one moment.

Move
A programming language for smart contracts built around resources that cannot be copied or lost, used by Sui and Aptos in different dialects.
Owned object
On Sui, an object controlled by one address; transactions that touch only owned objects skip consensus ordering.
Epoch
The period after which each chain updates its validator set and pays staking rewards; Sui's and Aptos's epochs differ in length.
Related
All Layer 1 chains apps →

Build Sui vs Aptos: Activity, Fees and Staking Compared on verified data.

Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.

Start free →Open live apps