Search results

bot me

Status: Open.

#27 In blast-io/deployment;

· rezamousavand1996-ship-it opened on May 13, 2026

bale

Status: Open.

#26 In blast-io/deployment;

· rezamousavand1996-ship-it opened on May 10, 2026

PM @dirt on telegram ASAP

Status: Open.

#22 In blast-io/deployment;

· ghost opened on Oct 12, 2024

Logg from op-node: Block not found: block not found: no block roots at slot 10074782","code":404

Status: Open.

#21 In blast-io/deployment;

· doviethoang opened on Oct 5, 2024

snap sync

Status: Open.

#20 In blast-io/deployment;

· Rogalek opened on Aug 30, 2024

CRIT [06-25|03:08:08.291] Application failed message="failed to setup: unable to create the rollup node config: failed to read rollup config: open /blast/mainnet/rollup.json: no such file or directory"

Status: Open.

#19 In blast-io/deployment;

· zhaoxiangjunupi opened on Jun 25, 2024

I encountered the problem of Ignoring already known beacon payload and the node got stuck

Status: Open.

#18 In blast-io/deployment;

· bijianing97 opened on Jun 24, 2024

failed to notify engine driver

Status: Open.

#17 In blast-io/deployment;

· sahfd4eiugf opened on Jun 5, 2024

Error:invalid parent beacon block root: fork active, missing expected attribute

Status: Open.

#15 In blast-io/deployment;

· yuanwj210 opened on Jun 3, 2024

OP_NODE_L1_BEACON is defined in the .env but not used in docker compose

Status: Open.

#11 In blast-io/deployment;

· SwatGuard opened on May 24, 2024

Unstable synchronization

Status: Open.

#9 In blast-io/deployment;

· 0xsinhvu opened on Apr 30, 2024

Too much L1 RPC requests during mainnet node syncing

Status: Open.

#8 In blast-io/deployment;

· maxsiz opened on Apr 5, 2024