OriginTrail
Proofing fails on Gnosis due to gas price
Despite having 0.5 XDAI for gas fees on Gnosis, I get errors on proofing mechanisms on version 8.1 on OTHub node as follows:
[2025-06-25 17:26:42] ERROR: [PROOFING] Error in proofing mechanism for gnosis:100: Error: processing response error (body="{"jsonrpc":"2.0","error":{"code":-32010,"message":"FeeTooLow, EffectivePriorityFeePerGas too low 719999980 < 1000000000, BaseFee: 20"},"id":15182}", error={"code":-32010}, requestBody="{"method":"eth_sendRawTransaction","params":["0x02f86f6402842aea5400842aea540083023ce89404498d3e5de9689c519a6904e9c91223531be6f280841cd821ebc001a0f320f146d9bd6b0b993a4adab436f14b93423854f300b1ecec2bbe89e3d835a2a0324c4506f6d7667ed78de5759722273d30eb0fae1597929f5a10f493858fe920"],"id":15182,"jsonrpc":"2.0"}", requestMethod="POST", url="https://api-gnosis-archive.dwellir.com/xxxxx", code=SERVER_ERROR, version=web/5.8.0), stack: Error: Error: processing response error (body="{"jsonrpc":"2.0","error":{"code":-32010,"message":"FeeTooLow, EffectivePriorityFeePerGas too low 719999980 < 1000000000, BaseFee: 20"},"id":15182}", error={"code":-32010}, requestBody="{"method":"eth_sendRawTransaction","params":["0x02f86f6402842aea5400842aea540083023ce89404498d3e5de9689c519a6904e9c91223531be6f280841cd821ebc001a0f320f146d9bd6b0b993a4adab436f14b93423854f300b1ecec2bbe89e3d835a2a0324c4506f6d7667ed78de5759722273d30eb0fae1597929f5a10f493858fe920"],"id":15182,"jsonrpc":"2.0"}", requestMethod="POST", url="https://api-gnosis-archive.dwellir.com/xxxx", code=SERVER_ERROR, version=web/5.8.0) at ProofingService.getAndPersistNewChallenge (file:///root/ot-node/8.1.0/src/service/proofing-service.js:284:19) at async ProofingService.prepareAndSendProof (file:///root/ot-node/8.1.0/src/service/proofing-service.js:231:34) at async ProofingService.runProofing (file:///root/ot-node/8.1.0/src/service/proofing-service.js:221:13) at async Timeout._onTimeout (file:///root/ot-node/8.1.0/src/service/proofing-service.js:60:17)
Looks like the Gnosis gas oracle is giving nodes trouble again. We'll take it on as a bug
Hey @Valcyclovir, thanks for reporting
We are working on the issue.
