Strange error: Staking credential registered in rewards map

Staking & Delegation Operate a Stake Pool
1

Hey guys,

Seeing this errors in the log… Anyone know what it means?

{“at”:“2020-08-23T06:22:09.54Z”,“env”:“1.19.0:48140”,“ns”:[“cardano.node.Mempool”],“data”:{“tx”:{“txid”:“txid: TxId {_unTxId = “baa0fc5fc337e37ddddf75db2298b2c95c423ef9300005c4aa7cc31a4a4f56fb”}”},“kind”:“TraceMempoolRejectedTx”,“mempoolSize”:{“numTxs”:2,“bytes”:842},“err”:{“kind”:“StakeKeyInRewardsDELEG”,“error”:“Staking credential registered in rewards map”,“consumed”:0,“credential”:“KeyHashObj (KeyHash “c90c06151cd0179af9517684aae6cd86e5e4bd327e7107421ff519dd”)”,“badInputs”:[[“949bbe62148ad7a69ee60d319e906ea261feede2667fc8b272d2d98baa4a21e5”,0]],“produced”:1839998945951}},“app”:,“msg”:"",“pid”:“80340”,“loc”:null,“host”:“ip-172-3”,“sev”:“Info”,“thread”:“1163”}
{“at”:“2020-08-23T06:22:09.57Z”,“env”:“1.19.0:48140”,“ns”:[“cardano.node.Mempool”],“data”:{“tx”:{“txid”:“txid: TxId {_unTxId = “baa0fc5fc337e37ddddf75db2298b2c95c423ef9300005c4aa7cc31a4a4f56fb”}”},“kind”:“TraceMempoolRejectedTx”,“mempoolSize”:{“numTxs”:2,“bytes”:842},“err”:{“kind”:“StakeKeyInRewardsDELEG”,“error”:“Staking credential registered in rewards map”,“consumed”:0,“credential”:“KeyHashObj (KeyHash “c90c06151cd0179af9517684aae6cd86e5e4bd327e7107421ff519dd”)”,“badInputs”:[[“949bbe62148ad7a69ee60d319e906ea261feede2667fc8b272d2d98baa4a21e5”,0]],“produced”:1839998945951}},“app”:,“msg”:"",“pid”:“80340”,“loc”:null,“host”:“ip-172-3”,“sev”:“Info”,“thread”:“11653”}
{“at”:“2020-08-23T06:22:09.58Z”,“env”:“1.19.0:48140”,“ns”:[“cardano.node.Mempool”],“data”:{“tx”:{“txid”:“txid: TxId {_unTxId = “baa0fc5fc337e37ddddf75db2298b2c95c423ef9300005c4aa7cc31a4a4f56fb”}”},“kind”:“TraceMempoolRejectedTx”,“mempoolSize”:{“numTxs”:2,“bytes”:842},“err”:{“kind”:“StakeKeyInRewardsDELEG”,“error”:“Staking credential registered in rewards map”,“consumed”:0,“credential”:“KeyHashObj (KeyHash “c90c06151cd0179af9517684aae6cd86e5e4bd327e7107421ff519dd”)”,“badInputs”:[[“949bbe62148ad7a69ee60d319e906ea261feede2667fc8b272d2d98baa4a21e5”,0]],“produced”:1839998945951}},“app”:,“msg”:"",“pid”:“80340”,“loc”:null,“host”:“ip-172-3”,“sev”:“Info”,“thread”:“11686”}
{“at”:“2020-08-23T06:22:09.65Z”,“env”:“1.19.0:48140”,“ns”:[“cardano.node.Mempool”],“data”:{“tx”:{“txid”:“txid: TxId {_unTxId = “baa0fc5fc337e37ddddf75db2298b2c95c423ef9300005c4aa7cc31a4a4f56fb”}”},“kind”:“TraceMempoolRejectedTx”,“mempoolSize”:{“numTxs”:2,“bytes”:842},“err”:{“kind”:“StakeKeyInRewardsDELEG”,“error”:“Staking credential registered in rewards map”,“consumed”:0,“credential”:“KeyHashObj (KeyHash “c90c06151cd0179af9517684aae6cd86e5e4bd327e7107421ff519dd”)”,“badInputs”:[[“949bbe62148ad7a69ee60d319e906ea261feede2667fc8b272d2d98baa4a21e5”,0]],“produced”:1839998945951}},“app”:,“msg”:"",“pid”:“80340”,“loc”:null,“host”:“ip-172-3”,“sev”:“Info”,“thread”:“1126”}
{“at”:“2020-08-23T06:22:09.66Z”,“env”:“1.19.0:48140”,“ns”:[“cardano.node.Mempool”],“data”:{“tx”:{“txid”:“txid: TxId {_unTxId = “baa0fc5fc337e37ddddf75db2298b2c95c423ef9300005c4aa7cc31a4a4f56fb”}”},“kind”:“TraceMempoolRejectedTx”,“mempoolSize”:{“numTxs”:2,“bytes”:842},“err”:{“kind”:“StakeKeyInRewardsDELEG”,“error”:“Staking credential registered in rewards map”,“consumed”:0,“credential”:“KeyHashObj (KeyHash “c90c06151cd0179af9517684aae6cd86e5e4bd327e7107421ff519dd”)”,“badInputs”:[[“949bbe62148ad7a69ee60d319e906ea261feede2667fc8b272d2d98baa4a21e5”,0]],“produced”:1839998945951}},“app”:,“msg”:"",“pid”:“80340”,“loc”:null,“host”:“ip-172-3”,“sev”:“Info”,“thread”:“1131”}

Relay node - Info log with error
4

dear @theh1982 although these log messages are using the “error” logging facility they’re only being submitted with the “Info” severity which is the lowest severity of all, except Debug which is below the default setting of cardano-node.

When I was looking to trim the logfiles, or at least my attention to them, I found this which explains that the difference is between a rejected & a removed transaction:

The discussion around this issue suggests the rejected & removed transactions are mainly there to prevent spoofing, which generally the SPO will be leaving to the node itself. If there’s a way we can use this information, other than checking periodically for floods of rejected transactions, I’d like to hear it.

For evidence that our relays are working properly, we consider it enough that we get the messages about the added transactions (TraceMempoolAddedTx) and trim our logfiles like this:

tail -fn20 ~/node.log | \
  grep --line-buffered -v ',String..The transaction contains inputs that do not exist in the UTxO set.' |\
  grep --line-buffered -v ',String..TraceMempoolRemoveTx' |\
  grep --line-buffered -v ',String..TraceMempoolRejectedTx'
1 Like
5

Yep - these errors look ok - the appear to be individuals somewhere in cardano land submitting invalid transactions.