Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avalanche L1s vs Ethereum L2s #1894

Open
martineckardt opened this issue Sep 19, 2024 · 1 comment
Open

Avalanche L1s vs Ethereum L2s #1894

martineckardt opened this issue Sep 19, 2024 · 1 comment
Assignees

Comments

@martineckardt
Copy link
Collaborator

Performance:

  • L1: 2s block time, 700ms finality
  • Arbitrum Nitro: 100ms block time, X seconds pre-confirmation, week finality
  • OP Stack:

Running Costs

  • L1s: Infrastructure ($50 per Validator/month) & Interoperability Fee ($50 per validator)
  • L2s: Infrastructure ($??? / month) & Settlement (very variable) & Data Availability (very variable) & possibly an interop fee for Superchain & revenue sharing model

Interoperability

  • L1s: Any-to-any, 2 blocks confirmations (max 6s)
  • OP Stack: Through settlement later, challenging because of long finality, many use third-party bridges which doesn't make sense (paying for settlement, but not utilizing the security)
  • Cosmos SDK: IBC point-to-point conncetions and zones

Infrastructure Mangement Complexity

  • L1s: Fault tolerance
  • L2s: Single-point failures
@martineckardt martineckardt self-assigned this Sep 19, 2024
@meaghanfitzgerald
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants