0glabs/0g-storage-node

Reporting problems due to recent updates

Opened this issue · 0 comments

1.validator : v0.2.5
• Validator is accumulating incorrect revert tx from storage nodes.

INF Served eth_call conn=75.119.158.5:36572 duration=1.283066 err="execution reverted" errdata=0x module=geth reqid=519430

2.storage node: 0.3.4 & git(dbd865f) (Both versions of node are being tested)
• revert tx is not created locally normally.

DEBUG miner::submitter: Local construct tx: Legacy(TransactionRequest { from: None, to: Some(Address(0x6176aa095c47a7f79dee2ea473b77
ebf50035421)), gas: None, gas_price: None, value: None, data:Some(Bytes(0xae722e82000000000000000000000000000000000000000000000000000000000000002001136edc732b7a3a2b8400e35e741a75c1c

• Because the tx is not normal, it cannot connect to the mine contract and transmission fails.

WARN miner::submitter: e="Fail to send mine answer
transaction: Revert(Bytes(0x))"

3.da node : git(c99e2b457cd05a6aff2f55b0aa10b105bc6af61e)
• In da node, mine does not work because the storage node has a problem and information cannot be received.

WARN da_miner::watcher: Cannot fetch on chain status error="Failed to query sample range: Revert(Bytes(0x))"
  • This problem occurred when the mine function was added to all nodes, and the problem seems to have started from the storage node. In the latest update, the revert contract is said to be up to date, but it doesn't seem to be working properly.

It looks like we're only a few days away from the mainnet. I commend the team who is developing at an incredibly fast pace. 0g is a fantastic team. I will support you