Layer 1 blockchain
Aptos ticker APT
Summary
Proof-of-stake BFT chain. Validators staking at least 1M APT (stake above 50M APT earns no extra voting power) run AptosBFT, which Aptos says is based on Jolteon, a two-chain variant of HotStuff. A block commits once validators holding more than two-thirds of voting power certify it, assuming fewer than one-third are malicious. Quorum Store spreads transaction batches among validators before a leader proposes, and later changes (optimistic Quorum Store, optimistic proposals, and the Zaptos pipeline enabled by governance in December 2025) aim to cut latency. Block-STM executes each ordered block in parallel with deterministic results. Epochs last two hours; voting power and the validator set change only at epoch boundaries. Aptos's staking docs say slashing is not implemented. 1231416171820
Design
- System
- Layer 1 blockchainProof-of-stake base layer (mainnet chain ID 1) with its own validator set, blocks and BFT commit rule. Joining the validator set is gated by stake (1M APT minimum), not by membership approval, so it is not treated as a permissioned ledger. It settles to no other chain.
- Settlement family
- Its own design
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- One leader per round, chosen pseudo-randomly with weights of stake times a reputation score built from recent proposing and voting history (AIP-1). The mainnet REST API listed 86 active validators on 2026-09-27.
- Fork choice
- No open weight-based fork choice: a block is final once it is committed through two consecutive quorum certificates from more than two-thirds of voting power. Two conflicting commits would require more than one-third of voting power to sign both; with no slashing, that is not automatically penalized in stake.
Qualifications
- Finality · Partial. Aptos defines a transaction as final as soon as it commits under BFT consensus. Because slashing is not implemented, reverting a commit would not automatically cost the signers stake, so it is not classed here as stake-backed economic finality.
- Slashing · Not applicable. Aptos's staking documentation states that slashing is currently not implemented. Rewards depend on successful proposals, so poor performance lowers rewards but does not burn stake.
- Block time · Partial. Blocks are not produced on a fixed slot clock; Aptos says the next block is proposed as soon as network delay allows and mainnet blocks are typically tens of milliseconds apart, so a block count is not a fixed measure of elapsed time.
- Validator concentration · Applies. Computed from the on-chain validator set read through the Aptos Labs mainnet REST API on 2026-09-27: 86 active validators, of which the 14 largest by voting power held more than one-third. This is a point-in-time reading, not a decentralization score.
- Node software license · Applies. The aptos-core repository is published under the Innovation-Enabling Source Code License, which limits use of the code to launch other networks and switches to Apache 2.0 four years after each piece of code is uploaded. What it permits for node operators was not analysed here.
- Settlement family · Partial. Recorded as other: Aptos settles on its own proof-of-stake chain, where aptos-core nodes run AptosBFT consensus and execute Move with Block-STM; nothing settles to another chain. None of the named settlement families describes this.
Tradeoffs
- Emphasizes
- Scalability and Security
- Gives up
- Operational decentralization. Aptos recommends 48-thread server CPUs, 128GB RAM, 3TB of enterprise NVMe and 1Gbps networking for validators and production fullnodes, and a validator needs 1M APT staked. On 2026-09-27, the 14 largest of 86 active validators held more than one-third of voting power; by the two-thirds commit rule, that group going offline together would stop blocks from committing.Security here means committee safety: committed blocks are final while fewer than one-third of voting power is faulty. It is not stake-backed: slashing is not implemented, so signing conflicting blocks would not cost the signers stake. The 14-validator figure is computed from the on-chain validator set at one moment and will drift.
- Full node at home
- Data-center class 9101112Aptos recommends that production public fullnodes meet validator hardware: 48 threads on a 5th-gen AMD EPYC or 6th-gen Intel Xeon, 128GB RAM, 3TB enterprise NVMe with at least 60K IOPS and 600MiB/s, and 1Gbps, with cloud instance examples. The fullnode page says lower specifications can be used for development or testing only and gives no numbers, so no lighter published minimum exists for a personal fullnode that keeps up with mainnet. Ledger pruning is on by default (latest 150 million transactions kept); fast sync fetches current state instead of replaying history.
- Throughput claims
- Lab benchmark: 170,000 tx/s 515Controlled benchmark; not observed network behavior.Block-STM paper (arXiv 2203.06871, first submitted March 2022); Aptos's execution page cites the same work.32 execution threads on a single machine, per the paper abstract.Execution-engine benchmark only; it ignores consensus, transaction propagation, networking and storage commit, so it is not network capacity. Measured on the paper's own 2022 benchmark workloads and code; the same abstract reports roughly half the figure for a contended workload. Ignores state growth and decoy or spam load. Not comparable to any other chain's headline figure or to observed Aptos mainnet usage.
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Built into the protocolLimited scope | Limited to exchanges on Aptos itself. A multi-agent transaction, a built-in transaction type, carries several distinct signers, and a committed transaction either applies all its state changes or aborts with all of them discarded, so two parties can exchange Aptos assets in one transaction that both sign. This is an inference from the documentation; no cross-chain hash- or time-locked swap tooling was reviewed. 67 |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Built into the protocolLimited scope | Consensus produces what a light client checks: validator-signed ledger roots, against which fullnodes verify proofs, and fast sync fetches current state instead of replaying history. Limited because no maintained light client was verified: the only one found is a third-party zero-knowledge implementation (Argument's zk-light-clients) whose development branch shows no commits since November 2024. 8122627 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment, state or application channel network anchored to Aptos was reviewed. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | All transactions run Move code, and accounts support Ed25519, secp256k1, k-of-n multisig and keyless authentication; derivable account abstraction was enabled by governance in November 2025. These are Move module and account authentication rules. 671321 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; no way for a sender to cancel or reclaim a payment was found, and a time delay for multisig accounts (AIP-145) is still a draft. Key rotation without changing address and native k-of-n multisig are rotation by the key holder and a plain threshold, which the current definition does not count as recovery. Keyless accounts are tied to a sign-in account, and Aptos describes recovery flows for users who lose access to it, but the cited page does not say how they work or who runs them. The protocol cannot reverse a confirmed payment. 61319 |
| Rollups | Unknown | No rollup settling to Aptos was found in the reviewed sources; absence was not exhaustively verified. |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | Established in the ecosystemThalaSwap (Thala), Hyperion | Thala documents an AMM with weighted, stable and liquidity-bootstrapping pools; Hyperion documents a concentrated-liquidity market maker with swap aggregation on Aptos. An on-chain order book framework (AIP-120) was deployed by governance in February 2026; venues built on it were not reviewed. Liquidity depth was not measured. 2223282930 |
| Issuer-native stablecoins | Established in the ecosystemUSDC (Circle), USD₮ (Tether) | Circle lists natively issued USDC on Aptos as a fungible asset (0xbae2...6f3b), and Tether lists USD₮ on Aptos as a fungible asset. Native here means issuer-issued on Aptos, not a protocol asset; issuers keep freeze and similar controls. 3133 |
| Algorithmic stablecoins | Unknown | Thala's Move Dollar (MOD) is documented as an over-collateralized debt-position stablecoin, not an algorithmic one. No algorithmic stablecoin with material use on Aptos was verified. 28 |
| Bridges | Established in the ecosystemCircle CCTP (USDC), LayerZero V2 | Circle lists Aptos as CCTP domain 9 for standard (not fast) USDC transfers; LayerZero lists an Aptos mainnet endpoint in its V2 deployments. Aptos has no canonical protocol bridge in the reviewed docs; Wormhole support could not be read. Risk: CCTP depends on Circle's attestation service and USDC issuer controls. LayerZero messages depend on the verifier networks and executors each application configures. A bridged token is only as sound as that path, and none of these contracts were audited here. 3234 |
| Block explorers | Established in the ecosystemAptos Explorer (Aptos Labs), Aptoscan | Aptos Explorer is run by Aptos Labs, describes itself as the official Aptos explorer and is linked from Circle's USDC address page; Aptoscan is an independent Aptos explorer. Explorer views are indexed provider data, not independent validation. 313536 |
| Hardware wallets | Established in the ecosystemLedger | See custody rows: Ledger's Aptos page says an Aptos account can be set up and managed in the Ledger Wallet app, and Petra can connect a Ledger device; Trezor says it does not support Aptos. 373839 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Unknown | Can: Set up an Aptos account and manage APT in the Ledger Wallet app, per Ledger's Aptos page Can: Connect a Ledger device to the Petra wallet, per Petra's siteLower confidence. Ledger Wallet's code has an Aptos feature switch that is off by default, and the only readable sign that Ledger has switched it on for users is its templated Aptos page, which still carries older text about Aptos's 2022 test networks. Whether APT staking or Aptos tokens other than APT are available in Ledger Wallet was not verified. 373940 |
| Trezor | None foundSame as native: No | Cannot: Manage Aptos accounts or APT with a Trezor device, per Trezor's Aptos pageTrezor states that it currently does not support Aptos; third-party signing paths were not checked. 38 |
Public data
iKnow Blockchain has no public-data lookups for Aptos yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Aptos node v1.49.1 released for mainnet, first as a private hotfix
Aptos Labs published a mainnet node release, v1.49.1-hotfix, as binaries and a Docker image only, stating that the source code was not available. Validators were told to upgrade and fullnode operators were advised to. On 23 September the same build was published as open-source v1.49.1, with a change log covering everything since v1.48.6. The log lists a gas schedule version bump to 49, Block-STM v2 turned on by default, and the API returning HTTP 410 for reads of pruned transactions and events.
- Implementation:node software v1.49.1; binaries published 2026-09-17, source and change log 2026-09-23
- Release:released as [Mainnet] node releases on GitHub (v1.49.1-hotfix, then v1.49.1)
- Activation:each operator upgrades separately; no v1.49 framework upgrade proposal was listed on the governance site on 2026-09-27
Sources: Aptos Labs (aptos-core GitHub releases) — [Mainnet] Aptos Node Release v1.49.1-hotfix (external site) · Aptos Labs (aptos-core GitHub releases) — [Mainnet] Aptos Node Release v1.49.1 (external site) · Aptos Labs — aptos-core releases (external site) · Aptos Governance (Aptos Foundation) — Multi-step proposal to upgrade mainnet framework, version v1.48.0 (external site) · Aptos Foundation — Aptos Governance proposals (external site) · Aptos Docs — Governance (external site)
-
Encrypted mempool framework initialised on mainnet in shadow mode
Governance executed a proposal that initialises the encrypted-mempool framework on mainnet and turns on its distributed key generation in shadow mode. Encrypted pending transactions hide a transaction's payload until it is ordered; the docs describe the feature as live on devnet and testnet with mainnet to follow.
- Proposal:AIP-144 marked Accepted
- Implementation:framework initialised; key generation running in shadow mode
- Release:delivered by governance proposal 204
- Activation:not available to users on mainnet as of 2026-09-27
Sources: Aptos Governance (Aptos Foundation) — Initialize Encrypted Mempool Framework and Enable ChunkyDKG Shadow V1 (external site) · Aptos Foundation AIPs — AIP-144: Encrypted Mempool (external site) · Aptos Docs — Encrypted Pending Transactions (external site) · Aptos Labs (public mainnet API) — Mainnet REST API: ledger information (external site)
-
Confidential APT transfers enabled on mainnet
Governance executed a proposal enabling confidential transfers for APT under AIP-143, followed on 30 April 2026 by a proposal enabling the batch Bulletproofs natives that confidential assets depend on. Users who opt in hold encrypted APT balances and send hidden amounts; sender and recipient addresses stay public.
- Proposal:AIP-143 marked Accepted
- Implementation:confidential asset framework with APT allow-listed
- Release:delivered by governance proposals 188 and 189
- Activation:live on mainnet per the Aptos confidential asset docs
Sources: Aptos Governance (Aptos Foundation) — AIP 143: Enable APT for Confidentiality (external site) · Aptos Governance (Aptos Foundation) — Enable Bulletproofs Batch Natives (external site) · Aptos Foundation AIPs — AIP-143: Confidential APT (external site) · Aptos Docs — Confidential Asset (CA) (external site)
-
Tenfold gas schedule increase (AIP-141) executed on mainnet
Governance executed AIP-141, which multiplies every gas cost and storage fee parameter by ten while scaling per-transaction gas limits by the same factor. Fees in APT rose about tenfold for the same work; the amount of computation allowed per transaction did not change.
- Proposal:AIP-141 marked Accepted
- Implementation:new on-chain gas schedule
- Release:delivered by governance proposal 185
- Activation:executed on mainnet 2026-03-19 per the governance page
Sources: Aptos Governance (Aptos Foundation) — AIP 141: Update gas schedule, increase gas fee 10x (external site) · Aptos Foundation AIPs — AIP-141: 10x Gas Fee Increase (external site)
-
Governance enabled Zaptos in the Aptos consensus configuration
An on-chain proposal to enable Zaptos in the consensus configuration, and to skip generating randomness when a block does not need it, was executed on mainnet. Zaptos (AIP-132) runs block execution, state certification and storage alongside ordering so that less work remains after a block is ordered, with the aim of lowering end-to-end latency.
- Proposal:AIP-132 marked Draft
- Implementation:enabled through an on-chain consensus configuration change
- Release:delivered by governance proposal 163
- Activation:executed on mainnet 2025-12-08 per the governance page
Sources: Aptos Governance (Aptos Foundation) — Proposal to enable zaptos in consensus config, enable skipping generating randomness if not needed (external site) · Aptos Foundation AIPs — AIP-132: Zaptos - the latency optimal blockchain architecture (external site)
Topics your AI can explain
Your AI can explain these topics for Aptos through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Past mainnet outages or halts were not reviewed; web search was unavailable and the Aptos Foundation and Medium news pages blocked automated reading.
- No lighter published minimum for a personal, non-production fullnode was found; the home-node rating rests on the recommended production hardware.
- Validator operator identities, hosting and geographic spread were not reviewed; only the on-chain voting-power split was computed.
- How transaction fees are split between burning and block proposers today is unclear: the fee page says execution fees are burned, a January 2026 governance proposal enabled distributing fees to validators, the priority-fee proposal (AIP-126) is still marked Draft, and the Foundation's February 2026 tokenomics proposal (AIP-140) still says all gas fees are burned.
- The mainnet status of validator fullnode removal (AIP-139, Accepted) was not confirmed.
- Wormhole and other bridges beyond Circle CCTP and LayerZero could not be verified; Wormhole's supported-networks page did not render.
- Whether Ledger Wallet supports APT staking or Aptos tokens other than APT was not verified.
- No maintained official light client was found; only a third-party zero-knowledge client with no commits on its development branch since November 2024.
- Ledger support rests on Ledger's templated Aptos coin page, which still carries older 2022 text; Ledger Wallet's code keeps Aptos behind a feature switch that is off by default, and Ledger's remote switch settings and supported-assets list could not be read.
- Rollups, channels and cross-chain trust-minimized swap tooling anchored to Aptos were not found; absence was not exhaustively verified. Same-chain swaps rest on the documented multi-agent transaction format and were not tested.
- What the aptos-core source licence permits for node operators and forks was not analysed.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Glossary (external site)
- Validator Nodes Overview (external site)
- Staking (external site)
- Blocks (external site)
- Execution (external site)
- Accounts (external site)
- Move - A Web3 Language and Runtime (external site)
- Fullnodes Overview (external site)
- Node Requirements (external site)
- PFN Requirements (external site)
- Data Pruning (external site)
- State Sync (external site)
- Aptos Keyless Introduction (external site)
- Jolteon and Ditto: Network-Adaptive Efficient Consensus with Asynchronous Fallback (external site)
- Block-STM: Scaling Blockchain Execution by Turning Ordering Curse to a Performance Blessing (external site)
- AIP-1: Proposer selection improvements (external site)
- AIP-106: Baby Raptr (Optimistic Quorum Store) (external site)
- AIP-131: Single-Hop Block Time (external site)
- AIP-145: Multisig Account Timelock (external site)
- Proposal to enable zaptos in consensus config (external site)
- Enable Derivable Account Abstraction (external site)
- Deploy aptos-trading (AIP 120) to mainnet (external site)
- AIP-120: Trading Engine on Aptos (external site)
- Mainnet REST API: 0x1::stake::ValidatorSet resource (external site)
- aptos-core LICENSE (Innovation-Enabling Source Code License) (external site)
- zk-light-clients: Aptos light client (external site)
- zk-light-clients commit history (dev branch) (external site)
- Thala overview (external site)
- Pool Types (external site)
- Introduction (external site)
- USDC Contract Addresses (external site)
- CCTP supported chains and domains (external site)
- Supported Protocols (external site)
- Aptos (LayerZero V2 mainnet endpoint) (external site)
- Aptos Explorer (external site)
- Aptoscan (external site)
- Aptos Wallet (external site)
- Aptos wallet (external site)
- Petra Wallet (external site)
- currencyAptos feature switch in Ledger Wallet code (declared without a value, so off by default) (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding