v1.2.0-OP_op-node/v1.7.5-CN_v0.13.2

This version contains:

v1.2.0 = @celestiaorg/optimism version
OP_op-node/v1.7.5 = Optimism op-node/v1.7.5
CN_v0.13.2 = celestia-node v0.13.2

What's Changed

• Rebased onto op-node/v1.7.5

Full Changelog: v1.2.0-OP_v1.7.3-CN_v0.13.2...v1.2.0-OP_op-node/v1.7.5-CN_v0.13.2

v1.2.0-OP_v1.7.3-CN_v0.13.2

This version contains:

v1.2.0 = @celestiaorg/optimism version
OP_v1.7.3 = Optimismv1.7.3
CN_v0.13.2 = celestia-node v0.13.2

What's Changed

• Rebased onto v1.7.3

Full Changelog: v1.2.0-OP_v1.7.2-CN_v0.13.2...v1.2.0-OP_v1.7.3-CN_v0.13.2

v1.2.0-OP_v1.7.2-CN_v0.13.2

What's Changed

v1.2.0 = @celestiaorg/optimism version
OP_v1.7.2 = Optimismv1.7.2
CN_v0.13.2 = celestia-node v0.13.2

This release upgrades go-da to v0.5.0 which supports JSONRPC for transport.

It is recommended to switch to the JSONRPC client and connect directly to
celestia-node as starting with v0.13.0 the DA interface is natively supported.

In addition to the dial address of celestia-node, an auth token with blob write
permission and the namespace are required. The auth token can be obtained
by using the celestia rpc client tool:

export CELESTIA_NODE_AUTH_TOKEN=$(celestia light auth write)

The namespace should be the hex encoded v0 blob namespace, including
version byte and must be exactly 29 bytes.

These should be passed to the op-batcher and op-node with the flags:

op-batcher / op-node
--da.rpc http://localhost:26658
--da.auth_token $CELESTIA_NODE_AUTH_TOKEN
--da.namespace 0000000000000000000000000000000000000001020304050607080910

Also see the devnet docker-compose for an example.

If you see an error like:

RPC client error: sendRequest failed: http status 401 Unauthorized unmarshaling response: EOF

Please make sure that the correct auth token is being passed.

gRPC client to celestia-da will be supported, but please note that a url needs to be passed e.g.:

op-batcher / op -node
  --da.rpc grpc://localhost:26650

See the full migration guide.

Full Changelog: v1.2.0-OP_op-node/v1.7.1-CN_v0.12.4...v1.2.0-OP_v1.7.2-CN_v0.13.2

v1.2.0-OP_v1.7.0-CN_v0.12.4

This version contains a modified version of BlobDataSource adopted for Celestia as DA after Ecotone activation:

v1.2.0 = @celestiaorg/optimism version
OP_v1.7.0 = Optimismv1.7.0
CN_v0.12.4 = celestia-da v0.12.9, which corresponds to celestia-node v0.12.4

What's Changed

• Modified BlobDataSource handles L1 input to retrieve frame from celestia and replace it as calldata
• Note: op-node needs to be started with --l1.beacon.ignore following Ecotone activation
• Note: Blob transactions and Plasma mode are NOT supported in this release

Full Changelog: https://github.com/celestiaorg/optimism/compare/[email protected]

v1.2.0-OP_op-node/v1.7.1-CN_v0.12.4

What's Changed

• Rebased v1.2.0 diff onto op-node/v1.7.1

Full Changelog: https://github.com/celestiaorg/optimism/compare/op-node/v1.7.1...release-1.2.0@op-node/v1.7.1

v2.0.0-OP_v1.7.0-CN_v0.12.4

What's Changed

The celestia implementation is now rewritten as a plasma implementation i.e. it uses the DAStorage interface and commitment scheme defined by plasma specs.

This release switches over to the plasma celestia backend on Ecotone mainnet activation following v0.1.7.0 release. For Sepolia testnet it immediately switches over to the plasma celestia backend as Ecotone is already activated.

As this is a major rewrite please note the following changes before upgrading:

• op-node and op-batcher should be started with the config options to switch over to plasma backend on Ecotone activation:
  • --plasma.enabled
  • --plasma.da-server=da:26650
  • --plasma.da-backend=celestia
  • "daChallengeAddress": "0xff00000000000000000000000000000000000905" (in rollup.json unused sample address, must be non-zero)

The new plasma celestia backend has the following major changes:

• Batch submission errors no longer fallback to ethereum. Instead, failed batcher transactions are queued and retried.
• Derivation errors when retrieving data from celestia are now handled by a TemporaryError which does not reset the pipeline.

Full Changelog: https://github.com/celestiaorg/optimism/commits/v2.0.0-OP_v1.7.0-CN_v0.12.4

v1.3.0-OP_v1.6.1-CN_v0.12.4

What's Changed

• Rebased onto v1.6.1 outdated ecotone mainnet release
• Add support for celestia backend to plasma DAStorage interface.
• Note that op-node and op-batcher need to be started with the following flags or corresponding env vars:
  • --plasma.enabled
  • --plasma.da-server=da:26650
  • --plasma.da-backend=celestia
• DA reads now return TemporaryError instead of ResetError so errors don't reset the derivation pipeline for retries.

Full Changelog: v1.6.1...v1.3.0-OP_v1.6.1-CN_v0.12.4

v1.2.0-OP_v1.5.1-CN_v0.12.4

This version contains a hotfix for Ecotone activation on Sepolia:

v1.2.0 = @celestiaorg/optimism version
OP_v1.5.1 = Optimismv1.5.1
CN_v0.12.4 = celestia-da v0.12.9, which corresponds to celestia-node v0.12.4

What's Changed

• Fixed Blob Data Source to retrieve frame from celestia
• Note: op-node needs to be started with --l1.beacon.ignore following Ecotone activation on Sepolia.

Full Changelog: v1.1.1-OP_v1.5.1-CN_v0.12.4...v1.2.0-OP_v1.5.1-CN_v0.12.4

v1.1.1-OP_v1.5.1-CN_v0.12.4

Full Changelog: v1.1.0-OP_v1.5.1-CN_v0.12.4...v1.1.1-OP_v1.5.1-CN_v0.12.4

v1.1.0-OP_v1.5.1-CN_v0.12.4

This version contains:

v1.1.0 = @celestiaorg/optimism version
OP_v1.5.1 = Optimismv1.5.1
CN_v0.12.4 = celestia-da v0.12.9, which corresponds to celestia-node v0.12.4

What's Changed

• Rebased onto v1.5.1

Full Changelog: v1.5.1...celestiaorg:optimism:[email protected]