Failed submitproofscommand error in 6.0.19

[Kitty-Tamatoa]

Issue description

Logs produce warn and error messages concerning submitproofscommand after update to 6.0.19

• Node version: 6.0.19

Error logs

[2023-11-09 14:09:34] DEBUG: sendProof(args=0x5cAC41237127F94c2D21dAe0b14bFeFa9988 0630,870394,0x5cac41237127f94c2d21dae0b14bfefa998806308064ffb5fcea95eabcdc8094430b aabfc07dd4b033618cebe7676939f8e08dea,1,0,,0x0037ba10e23e3e9f83ce174e26b89085931513 a6b9cfaa5ee67e02424fd148b4) call has failed; Error: custom error NodeAlreadyRewar ded(agreementId=0x5df67273b0221309ad49ed6ef001d34a6ec08ae19036223fc3ab2912118f74ac , epoch=0, identityId=75, nodeId=0x516d59326d634c5373776d7263716d6a464353457754595 4654d4838745a56655276437a5a42684155724c723835); RPC: https://astrosat.origintrail. network/.
[2023-11-09 14:09:34] WARN: Error in command: submitProofsCommand, error: Transact ion reverted, reason: missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (transaction={"from":"0xF333b0CD7CdE7CEb034dfEe233D08B73F0D64082","gasLimit":{"ty pe":"BigNumber","hex":"0x0586ce"},"maxPriorityFeePerGas":{"type":"BigNumber","hex" :"0x0a"},"maxFeePerGas":{"type":"BigNumber","hex":"0x0a"},"to":"0xE85c5f8116918B9E AFf4F8d5E74d060b23d65233","value":{"type":"BigNumber","hex":"0x00"},"data":"0x7522 c2b1000000000000000000000000000000000000000000000000000000000000002000000000000000 00000000005cac41237127f94c2d21dae0b14bfefa9988063000000000000000000000000000000000 000000000000000000000000000d47fa00000000000000000000000000000000000000000000000000 000000000000e000000000000000000000000000000000000000000000000000000000000000010000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000001400037ba10e23e3e9f83ce174e26b89085931513a6 b9cfaa5ee67e02424fd148b40000000000000000000000000000000000000000000000000000000000 0000345cac41237127f94c2d21dae0b14bfefa998806308064ffb5fcea95eabcdc8094430baabfc07d d4b033618cebe7676939f8e08dea000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000","type":2,"accessList":[]}, code=CALL_EXCEPTION , version=providers/5.7.2)
[2023-11-09 14:09:34] ERROR: Command error (SubmitProofsError): Transaction revert ed, reason: missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (transact ion={"from":"0xF333b0CD7CdE7CEb034dfEe233D08B73F0D64082","gasLimit":{"type":"BigNu mber","hex":"0x0586ce"},"maxPriorityFeePerGas":{"type":"BigNumber","hex":"0x0a"}," maxFeePerGas":{"type":"BigNumber","hex":"0x0a"},"to":"0xE85c5f8116918B9EAFf4F8d5E7 4d060b23d65233","value":{"type":"BigNumber","hex":"0x00"},"data":"0x7522c2b1000000 0000000000000000000000000000000000000000000000000000000020000000000000000000000000 5cac41237127f94c2d21dae0b14bfefa99880630000000000000000000000000000000000000000000 00000000000000000d47fa000000000000000000000000000000000000000000000000000000000000 00e0000000000000000000000000000000000000000000000000000000000000000100000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000001400037ba10e23e3e9f83ce174e26b89085931513a6b9cfaa5ee6 7e02424fd148b400000000000000000000000000000000000000000000000000000000000000345cac 41237127f94c2d21dae0b14bfefa998806308064ffb5fcea95eabcdc8094430baabfc07dd4b033618c ebe7676939f8e08dea0000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000","type":2,"accessList":[]}, code=CALL_EXCEPTION, version= providers/5.7.2)

[u-hubar]

Hi @Kitty-Tamatoa, you can see the first log that says that Proof was already submitted, so the only consequence is that your node tries to send additional transaction. We're working on the improvement, v6.0.20 should make it more stable

[harveysimpsondata]

Failed to schedule submitProofsCommand repeats for the same serviceId over and over again check timestamps

[SagiShaashua]

I am getting the same WARN and Errors - and while the node is winning some pubs it is winning far less than it used to a few weeks ago (around 5-8 instead of 30-40). could this explain the issue?