Optimism is a low-cost and lightning-fast Ethereum L2 blockchain, built with the OP Stack.

+

NEAR is a low-cost, usable, and scalable layer-one blockchain that offers cheap data availability layer.

NEAR DA + OP Stack tutorial

If you're looking to run the OP Stack + NEAR DA setup for this repository, please visit the NEAR DA guides to get started.

What are Optimism and the OP Stack?

Optimism is a low-cost and lightning-fast Ethereum L2 blockchain, but it's also so much more than that.

The OP Stack powers Optimism, an Ethereum L2 blockchain, and forms the technical foundation for the the Optimism Collective—a group committed to the impact=profit principle. This principle rewards individuals for their positive contributions to the collective.

Optimism addresses critical coordination failures in the crypto ecosystem, such as funding public goods and infrastructure. The OP Stack focuses on creating a shared, open-source system for developing new L2 blockchains within the proposed Superchain ecosystem, promoting collaboration and preventing redundant efforts.

As Optimism evolves, the OP Stack will adapt, encompassing components ranging from blockchain infrastructure to governance systems. This software suite aims to simplify L2 blockchain creation while supporting the growth and development of the Optimism ecosystem.

What is NEAR?

NEAR is a decentralized application platform designed to improve scalability and user experience in blockchain technology.

Utilizing a proof-of-stake consensus mechanism, it focuses on energy efficiency and high transaction throughput. NEAR’s standout feature is sharding, which breaks the network into smaller segments for parallel processing, greatly enhancing speed and capacity.

This approach makes NEAR particularly appealing for developers building decentralized applications and for users seeking fast, low-cost transactions, and also for data availability for Ethereum rollups.

Documentation

If you want to learn more about the OP Stack, check out the documentation at stack.optimism.io.

If you want to learn more about the NEAR Data Availability and also NEAR, check out the documentation at near.org

Community

Optimism

General discussion happens most frequently on the Optimism Discord. Governance discussion can also be found on the Optimism Governance Forum.

NEAR

General discussion happens most frequently on the NEAR discord. Other discussions can be found on the NEAR Governance Forum.

e2e testing

This repository has updated end-to-end tests in the op-e2e package to work with NEAR DA as the data availability (DA) layer.

Currently, the tests assume a working Celestia devnet running locally:

docker run --platform linux/amd64 -p 26658:26658 ghcr.io/rollkit/local-celestia-devnet:v0.11.0-rc8

The e2e tests can be triggered with:

cd $HOME/optimism
cd op-e2e
make test

Bridging

If you have the OP Stack + NEAR DA setup running, you can test out bridging from the L1 to the L2.

To do this, first navigate to the packages/contracts-bedrock directory and create a .env file with the following contents:

L1_PROVIDER_URL=http://localhost:8545
L2_PROVIDER_URL=http://localhost:9545
PRIVATE_KEY=bf7604d9d3a1c7748642b1b7b05c2bd219c9faa91458b370f85e5a40f3b03af7

Then, run the following from the same directory:

npx hardhat deposit --network devnetL1 --l1-provider-url http://localhost:8545 --l2-provider-url http://localhost:9545 --amount-eth <AMOUNT> --to <ADDRESS>

Directory Structure

~~ Production ~~
├── packages
│   ├── common-ts: Common tools for building apps in TypeScript
│   ├── contracts: L1 and L2 smart contracts for Optimism
│   ├── contracts-periphery: Peripheral contracts for Optimism
│   ├── core-utils: Low-level utilities that make building Optimism easier
│   ├── data-transport-layer: Service for indexing Optimism-related L1 data
│   ├── chain-mon: Chain monitoring services
│   ├── fault-detector: Service for detecting Sequencer faults
│   ├── message-relayer: Tool for automatically relaying L1<>L2 messages in development
│   ├── replica-healthcheck: Service for monitoring the health of a replica node
│   └── sdk: provides a set of tools for interacting with Optimism
├── batch-submitter: Service for submitting batches of transactions and results to L1
├── bss-core: Core batch-submitter logic and utilities
├── gas-oracle: Service for updating L1 gas prices on L2
├── indexer: indexes and syncs transactions
├── infra/op-replica: Deployment examples and resources for running an Optimism replica
├── integration-tests: Various integration tests for the Optimism network
├── l2geth: Optimism client software, a fork of geth v1.9.10  (deprecated for BEDROCK upgrade)
├── l2geth-exporter: A prometheus exporter to collect/serve metrics from an L2 geth node
├── op-exporter: A prometheus exporter to collect/serve metrics from an Optimism node
├── proxyd: Configurable RPC request router and proxy
├── technical-documents: audits and post-mortem documents

~~ BEDROCK upgrade - Not production-ready yet, part of next major upgrade ~~
├── packages
│   └── contracts-bedrock: Bedrock smart contracts. To be merged with ./packages/contracts.
├── op-bindings: Go bindings for Bedrock smart contracts.
├── op-batcher: L2-Batch Submitter, submits bundles of batches to L1
├── op-e2e: End-to-End testing of all bedrock components in Go
├── op-node: rollup consensus-layer client.
├── op-proposer: L2-Output Submitter, submits proposals to L1
├── ops-bedrock: Bedrock devnet work
└── specs: Specs of the rollup starting at the Bedrock upgrade