Skip to content

v1.6.0

Latest
Compare
Choose a tag to compare
@samlaf samlaf released this 26 Nov 11:13
aeeb503

Summary

This release is MANDATORY if upgrading your op-stack to 1.9.4 where op-batcher sends with new /put route) instead of the old /put/ route. This release supports both routes.

Added

  • [New Feature] Failover signaling via 503 status code when EigenDA is down (implementing our proposed spec). This can be used by rollup batchers to temporarily failover to other DA destinations (e.g, 4844).
  • Optional async writes to secondary storage. This allows for minimized latency during dispersals to provide better confirmation throughput to the rollup.

Fixed

  • Support for /put as well as the old /put/.
  • GCP compatibility bug where GCS would unintentionally wrap blob contents with chunk signature encoding metadata.
  • HTTP routes are now strict and only accept for each resource the HTTP method specified in the altda spec.
  • Properly handle http status codes in log/metrics middlewares.

Security

  • All secret values in the config now log as ***** at startup.

What's Changed

  • Allow Google storage endpoints without http/s by @jcortejoso in #179
  • fix: change put route put/ -> put by @samlaf in #168
  • fix(ci): update go1.21->1.22 everywhere by @samlaf in #183
  • Improve local test setup by @samlaf in #177
  • refactor: cleaner routing using gorilla mux regexps by @samlaf in #185
  • fix: fetch quorum parameters from edasm at RBN instead of latest block by @samlaf in #190
  • feat: Optional async decoupling for secondary writes and reworked E2E metric assertions by @epociask in #182
  • refactor: use batch confirmation that was upstreamed to eigenda client by @samlaf in #192
  • fix(e2e tests): missing new eigenda-client required config fields by @samlaf in #196
  • fix(#191): Routing namespace --> Storage by @epociask in #195
  • feat(failover): return 503 to batcher when eigenda is down by @samlaf in #193
  • fix: Hide other sensitive cfg values by @epociask in #194
  • refactor: rename client -> SimpleCommitmentClient and add comments by @samlaf in #201
  • fix(middleware): proper handling of handler status codes in log/metrics middlewares by @samlaf in #200

Full Changelog: v1.5.0...v1.6.0-rc