- Compare
- Starknet vs Arbitrum Nova
Starknet vs Arbitrum Nova Scalability
Real-time TPS
Starknet TPS is 1.95 tx/s, while Arbitrum Nova has no data
Max TPS (100 blocks)
Starknet max TPS is 381.6 tx/s, while Arbitrum Nova has no data
Max Theoretical TPS
Starknet max theoretical TPS is 992 tx/s, while Arbitrum Nova has no data
Transaction Volume
Starknet transaction volume is 7,025 txns, while Arbitrum Nova has no data
Block Time
Starknet block time is 8.12s, while Arbitrum Nova has no data
Finality
Starknet finality is 2h, while Arbitrum Nova has no data
Type
Starknet is a layer 2 blockchain, while Arbitrum Nova has no data
Launch Date
Starknet was launched on Nov 16, 2021, while the Arbitrum Nova has no data
Starknet vs Arbitrum Nova Decentralization New
Nakamoto Coefficient
Starknet Nakamoto Coefficient is 1, while Arbitrum Nova has no data
Validators/Miners
Starknet has 1 validators, while Arbitrum Nova has no data
Stake/Hashrate
Starknet and Arbitrum Nova have no data
Consensus Mechanism
Starknet is Rollup (ZK), while Arbitrum Nova has no data
Governance
Starknet governance is on-chain, while Arbitrum Nova has no data
Other Comparisons
Starknet Comparisons
About Blockchains
About Starknet
Starknet stands as a permissionless blockchain solution, functioning as a Validity-Rollup, often referred to as a zero-knowledge rollup (ZK rollup) for Ethereum. It's a Layer 2 (L2) platform that empowers dApps to achieve significant computational scalability while upholding Ethereum's inherent composability and security standards.
About Arbitrum Nova
Arbitrum Nova is a high-performance alternative to Arbitrum One's chain. While Arbitrum One implements the purely trustless Rollup protocol, Arbitrum Nova implements the mostly trustless AnyTrust protocol. The key difference between Rollup and AnyTrust is that the AnyTrust protocol introduces an additional trust assumption in the form of a Data Availability Committee (DAC). This committee (detailed below) is responsible for expediting the process of storing, batching, and posting child chain transaction data to Ethereum's parent chain. This lets you use Arbitrum in scenarios that demand performance and affordability, while Arbitrum One is optimal for scenarios that demand Ethereum's pure trustlessness.