Layer 2 blockchain · settles to Ethereum
Abstract ticker ETH
Summary
Zero-knowledge rollup on Ethereum built with ZKsync's ZK Stack. One operator-run sequencer orders transactions into L2 blocks and groups them into batches, and the operator commits each batch to Ethereum as compressed state differences in blobs. A prover built on Boojum produces a STARK proof, compresses it into a SNARK, and a verifier contract on Ethereum checks it; after a 3-hour execution delay the batch is executed on Ethereum and becomes final. Contracts run on the ZKsync VM (an EVM interpreter exists at higher gas cost), and every account is a smart contract account. Block production uses no stake or work of its own. 23459121329
Design
- System
- Layer 2 blockchainAbstract Mainnet (chain ID 2741) is a zero-knowledge (validity-proof) rollup on Ethereum built with ZKsync's ZK Stack, not an optimistic rollup. ETH is the gas asset; Abstract's docs name no separate gas or governance token. At review time it was still producing blocks and committing its batches directly to Ethereum, not through ZKsync's Gateway settlement layer.
- Settles to
- EthereumBatches are committed to Ethereum as state differences in blobs, proven by a SNARK checked on Ethereum, and executed after a 3-hour timelock; only then can withdrawals be claimed on Ethereum. ZKsync's docs put full finality at around 3 hours but say proving and batching can add time, while Abstract's bridge page says withdrawals take up to 24 hours. Users can queue transactions through Ethereum, but L2BEAT says the operator can stop processing that queue.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Other
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- One centralized operator. Abstract's node docs say running a sequencer is not possible and public nodes are read-only replicas of the main node. L2BEAT says only whitelisted proposers can post state roots, batch execution needs approval from a 1-of-3 validator multisig, and Abstract's 4-of-8 multisig holds the chain admin role.
- Fork choice
- No open L2 fork choice: the operator's blocks are canonical. Before a batch is executed on Ethereum the operator can revert it (Abstract's docs call this rare, for example after a sequencer bug); batches already executed on Ethereum cannot be reverted.
Qualifications
- Scarce resource · Not applicable. Abstract block production uses no stake or work of its own; the sequencer is operator-assigned and security comes from Ethereum plus validity proofs.
- Finality · Partial. Abstract's explorer shows four stages: processed on Abstract (a soft confirmation from the sequencer), committed to Ethereum, proof validated on Ethereum, and executed on Ethereum. Only execution is final; before it the operator can revert batches.
- Withdrawal window · Contested. Abstract's bridge page says withdrawals take up to 24 hours because of a built-in delay, while ZKsync's withdrawal-delay page says the delay was cut from 21 hours to a 3-hour minimum and L2BEAT shows a 3-hour execution timelock on Abstract.
- Evm equivalence · Partial. Abstract is EVM-compatible but runs the ZKsync VM: contracts are normally compiled with ZKsync compilers, CREATE and CREATE2 addresses differ from Ethereum, accounts keep separate transaction and deployment nonces, and unmodified EVM bytecode runs through an interpreter at 150 to 400 percent higher gas.
- Upgrade exit window · Partial. L2BEAT reports about four days (about eight if ZKsync's Guardians extend their review) before a regular upgrade of the shared ZK Stack contracts takes effect, but none on the emergency path, so it concludes users have no exit window against an unwanted instant upgrade. It also says the operator can install a filter that censors transactions queued through Ethereum, the route users would use to force a withdrawal, without delay.
Tradeoffs
- Emphasizes
- Scalability and Security
- Gives up
- Decentralized operation and upgrade safety: one operator sequences, proposes and executes every batch, can add a filter on transactions queued from Ethereum without delay, and if it stops proposing, withdrawals freeze. L2BEAT rates Abstract Stage 0: the shared ZK Stack contracts can be upgraded instantly through an emergency path, and regular upgrades leave only about four days to exit.The security emphasis refers to validity proofs checked on Ethereum and full state-difference data posted there. It depends on sound circuits and verifiers and on ZKsync governance and Abstract's multisig: per L2BEAT, an unprovable batch stopped finalization for about two days in May 2025 until an emergency upgrade replaced the verifier, and the verifiers were upgraded again in August 2026.
- Full node at home
- Demanding 12131429Abstract lists minimums of 32 GB RAM, a modern CPU, a 100 Mbps link and 300 GB of mainnet storage, yet also says state grows about 1 TB per month. It describes the node as an archive node, and a default first run syncs from genesis until a snapshot is offered, so real storage and sync time may exceed the minimum. The node is a beta, read-only replica that re-executes the main node's blocks and checks batch commitments against Ethereum; it cannot produce blocks or proofs. L2BEAT says the node software does not rebuild state from Ethereum data, though a separate tool can.
- Throughput claims
- No classified figure recorded
Scaling layers
- MPP session channels (Abstract Foundation package for paid APIs) · Payment channels, mainnet 202425
Client-to-server channels for machine payments: after one on-chain opening, a client deposits tokens (the docs list USDC.e) in an escrow contract on Abstract, pays repeatedly with cumulative signed vouchers sent off-chain, and the server settles on Abstract when it chooses. Abstract's agent reference lists one escrow contract address beside the mainnet and testnet token addresses; dispute rules, timeouts, audits and real usage were not reviewed. It is a client-to-server payment tool, not a general payment network.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | A protocol-level trust-minimized swap mechanism on Abstract was not reviewed; contracts could implement hash-locked swaps, but none was verified. |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Built into the protocolLimited scope | Abstract's rollup protocol produces what a light verifier checks: executed batches leave validity-proven state commitments on Ethereum, the zks_getProof RPC method returns Merkle proofs of storage values, and the read-only node checks each batch commitment against Ethereum. Limited: only state in batches executed on Ethereum can be checked this way, and no dedicated Abstract light client was found. 51326 |
| 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 | Ecosystem software (publisher not distinguished) Earlier definition | Abstract's MPP package documents escrow-backed one-way payment channels for paying HTTP APIs, settled on Abstract. It is an application-level tool for machine payments, not a general channel network, and its dispute rules and audits were not reviewed. 2425 |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Every Abstract account is a smart contract account: the protocol calls each account's own validation code, paymasters can sponsor fees or accept ERC-20 tokens, and contract wallets add session keys and passkey signers. This is native account abstraction on the ZKsync VM. 782223 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Core-team softwareLimited scope | No protocol feature cancels or delays a sent payment. Abstract Global Wallet, the smart contract wallet that Abstract's docs present as the wallet powering its ecosystem, documents email or guardian recovery for regaining access to an account. It is software of the chain's steward (Abstract's docs are published by the Abstract Foundation); its default signing key is created through Privy's embedded wallet. Limited: this recovers control of an account (part b) and does not reverse payments. 722 |
| Rollups | Unknown | Rollups anchored to Abstract were not reviewed. Abstract itself is a rollup on Ethereum; its settlement is described in the mechanism and Ethereum dependency notes. |
| 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 | ThinKona (Kona Swap), Uniswap V2 and V3 contract sets listed by Abstract | Abstract's deployed-contracts page lists Uniswap V2 and V3 contract sets, but Uniswap's v3 deployment index has no Abstract page, so who deployed and runs them was not verified. Kona describes itself as a place to trade on Abstract, and its docs describe v2-style and stableswap pools. Liquidity was not measured; the thin rating reflects the modest value L2BEAT reports as secured on the whole chain, not a per-venue measure. 1929353637 |
| Issuer-native stablecoins | None found | No issuer-native stablecoin was found: Circle's USDC address list and the USDT0 deployment list do not name Abstract. The USDC and USDT contracts in Abstract's docs are bridged tokens: Abstract's own agent docs label the USDC contract USDC.e, Stargate's docs list USDC and USDT contracts for Abstract and say it uses Stargate's Hydra model for stablecoins, and a read-only check of Abstract's public RPC at review time found those Stargate contracts pointing to the same two token addresses Abstract lists. 1920323334 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on Abstract were not reviewed. |
| Bridges | Native to the protocolAbstract native bridge (ZK Stack shared bridge contracts), Stargate, Relay, Jumper, Symbiosis, deBridge, thirdweb | Abstract's native bridge moves ETH and ERC-20 tokens between Ethereum and Abstract through the ZK Stack shared bridge contracts; deposits take about 15 minutes. Abstract's docs list third-party routes (Stargate, Relay, Jumper, Symbiosis, thirdweb, deBridge) and LayerZero and Hyperlane for messaging; only Stargate's own docs were checked, and they list Abstract. Risk: Canonical withdrawals depend on the operator proposing and executing batches (L2BEAT says withdrawals freeze if it stops), on a sound ZKsync proof system, and on shared contracts that ZKsync governance can upgrade after about four days or instantly on its emergency path. Bridged stablecoins such as USDC.e add Stargate and LayerZero trust, and L2BEAT counts more than half of Abstract's secured value as carrying extra trust assumptions. 6161718282932 |
| Block explorers | Established in the ecosystemAbscan (abscan.org), Abstract Block Explorer (explorer.mainnet.abs.xyz) | Abstract's docs name Abscan for mainnet and say its explorer shows batch and finality status; Abscan's own footer says it is built by the Etherscan team. A site titled Abstract Block Explorer also responds at an Abstract-run mainnet address, but the current docs do not link it and its operator and scope were not confirmed. Explorer indexes are not canonical consensus. 1153031 |
| Hardware wallets | ThinTrezor Safe 3, 5 and 7 (through MetaMask or Rabby) | See custody rows. Trezor lists Abstract among its supported Ethereum networks, but Trezor Suite does not include it, so Trezor use goes through third-party wallet apps; Ledger support was not found. Abstract Global Wallet, which Abstract's docs call the wallet powering its ecosystem, signs by default with a key created through Privy's embedded wallet rather than a hardware device. 2122383940 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | UnknownSame as native: Unknown | Ledger's coin page for Abstract returned 404 and its supported crypto assets page did not name Abstract; support was not verified either way. 39 |
| Trezor | Through an intermediaryMetaMask or Rabby (third-party wallet apps named on Trezor's Ethereum page)Same as native: Unknown | Can: Use a Trezor Safe 3, 5 or 7 on the Abstract network through MetaMask or Rabby, confirming transactions on the device; Trezor's Ethereum page lists Abstract among its supported Ethereum networks Cannot: Add an Abstract account in Trezor Suite: Suite's network configuration does not include Abstract, although Trezor's Ethereum page names Suite among its apps Cannot: Rely on an Abstract-specific Trezor page: Trezor's Abstract wallet address returned 404On Abstract a key-held address acts through the protocol's built-in default account contract. Adding a Trezor as a signer on an Abstract Global Wallet was not documented in the pages reviewed, and older Trezor models and contract-interaction coverage were not checked. 83840 |
Public data
iKnow Blockchain has no public-data lookups for Abstract 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
-
Abstract's Ethereum contracts moved to ZK Stack protocol version 0.30.1 with new proof verifiers
L2BEAT recorded three upgrades of Abstract's main contract on Ethereum in August 2026, moving it to protocol version 0.29.5 (4 August), 0.30.0 (8 August) and 0.30.1 (16 August), each with new Boojum proof verifiers. L2BEAT names Abstract's multisig as applying the last two, describes the first two verifier sets as the same as ZKsync Era's, and says the 0.30.1 verifiers had been registered in the shared ZK Stack contracts beforehand. For each upgrade L2BEAT noted that the new verifiers had not yet been reproduced.
- Implementation:applied to Abstract's contracts on Ethereum mainnet
- Release:protocol version 0.30.1 recorded by L2BEAT
- Activation:active since 2026-08-16 per L2BEAT's contract record
Sources: L2BEAT — Abstract (external site) · Abstract Foundation (GitHub) — abstract-node releases (external site)
Topics your AI can explain
Your AI can explain these topics for Abstract through the connection, with sources.
Known gaps
What this profile's review did not establish:
- The legal entity that runs Abstract's sequencer, prover and operator keys was not sourced; the docs are published by the Abstract Foundation, and L2BEAT describes only a centralized operator.
- The signers behind Abstract's 4-of-8 multisig and the 1-of-3 validator multisig were not identified; the governance picture relies on L2BEAT because Abstract's docs do not describe upgrades.
- Abstract's node page gives 300 GB of mainnet storage but also says state grows about 1 TB per month; current chain size, and whether the growth figure means the node now needs far more than the minimum, were not verified, and the page says a default first sync starts from genesis until a snapshot is set up.
- Abstract's bridge page (withdrawals up to 24 hours) conflicts with ZKsync's 3-hour minimum delay; no typical end-to-end withdrawal time for Abstract was published in the reviewed docs.
- Whether Abstract plans to move settlement to ZKsync's Gateway was not reviewed; it was committing directly to Ethereum at review time, and L2BEAT says Abstract's multisig can move the chain to another approved settlement layer.
- No dated release notes or changelog for the chain were found in Abstract's docs, and its blog shows no posts after September 2024, so most announcements appear to go out on X, which this product treats as link-only.
- Ledger support for Abstract was not found (coin page 404; not named on the supported-assets page).
- Trezor use of Abstract through MetaMask or Rabby follows from Trezor's Ethereum page and Suite's network list, not from an Abstract-specific Trezor page; whether a hardware signer can be added to an Abstract Global Wallet was not verified.
- Who deployed and maintains the Uniswap V2 and V3 contract sets listed in Abstract's docs, and DEX liquidity depth, were not verified; other venues seen in an aggregator (Aborean, SakuraSwap) were not checked at their own documentation.
- Relay, Jumper, Symbiosis, thirdweb and deBridge were not individually checked for current Abstract support; only Stargate's docs were.
- The MPP escrow contract's dispute rules, timeouts, audits and usage were not reviewed.
- Abstract Global Wallet's key custody relies on Privy's key-sharding service, whose security was not independently reviewed.
- Atomic swaps, algorithmic stablecoins and rollups or app chains anchored to Abstract were not reviewed.
- No Abstract gas or governance token was found in Abstract's docs; absence elsewhere was not exhaustively verified.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Connect to Abstract (external site)
- Layer 2s (external site)
- Transaction Lifecycle (external site)
- Sequencer (external site)
- Prover & Verifier (external site)
- L1 Rollup Contracts (external site)
- Native Account Abstraction (external site)
- Transaction Flow (external site)
- EVM Interpreter (external site)
- Nonces (external site)
- Contract Deployment (external site)
- Nodes: Introduction (external site)
- Nodes: Components (external site)
- Running a node (external site)
- Block Explorers (external site)
- Bridges (native bridge) (external site)
- Bridges (third-party) (external site)
- Interoperability (external site)
- Deployed Contracts (external site)
- Contracts and Endpoints (external site)
- Abstract Global Wallet (external site)
- Abstract Global Wallet: How It Works (external site)
- Session keys (external site)
- MPP (external site)
- MPP Session Payments (external site)
- zks_getProof (external site)
- Finality (external site)
- Withdrawal delay (external site)
- Abstract (external site)
- Abstract (ETH) Blockchain Explorer (external site)
- Abstract Block Explorer (external site)
- Mainnet Contracts (external site)
- USDC Contract Addresses (external site)
- Deployments (external site)
- v3 Deployments (external site)
- Kona (external site)
- Kona Swap (external site)
- Ethereum wallet (external site)
- Supported crypto assets (external site)
- Trezor Suite Ethereum network configuration (networkConfig.ts, develop branch) (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