Capsule config of the vega key producing “invalid signature” err events

[vega-paul]

Capsule network running

vegatools TXErrEvent event types produced

 {“id”:“24546-124”,“block”:“1BC6232BFB761B1924EC6297A35AE2D5ADDAA140B1C87C4517077AFE33E638B9”,“type”:“BUS_EVENT_TYPE_TX_ERROR”,“txErrEvent”:{“partyId”:“334d6a39cf1da71451b6d0266b892bed07df2b811d7f9852643e8e7b61e5319d”,“errMsg”:“invalid signature”},“version”:1,“chainId”:“test-chain-zGCdGM”,“txHash”:“25A1DA446BA8416F74AA480AF320D2790166A79F5EDBD695CF615ED8908D1532”

Core logs for same party

2022-04-25T20:09:20.965+0100    DEBUG   validators      validators/topology.go:358      requested existing validator    {“validators”: [“334d6a39cf1da71451b6d0266b892bed07df2b811d7f9852643e8e7b61e5319d”, “fa12817eed61bf32e25a1e33fb0a97792276d6d5230225355e9ee87f612204a8”], “pubkey”: “334d6a39cf1da71451b6d0266b892bed07df2b811d7f9852643e8e7b61e5319d”}

Check capsule config of the ethereum key

[ze97286]

not very important but the log message in the core is not very relevant or related to this. It does help in that it tells us that the party is a validator though.

[gordsport]

This issue is no longer seen in the logs

[jgsbennett]

I still see these on current builds, as I believe, do @vega-paul and @wwestgarth , like this:

{"id":"9131-10","block":"47D1DAA3BA336F3289E7A4E8522017157C0D4FFBCCEEE53FA899076171225E59","type":"BUS_EVENT_TYPE_TX_ERROR","txErrEvent":{"partyId":"3c2d72d3b1defe2863c45e28836b87fd05166a99cfa07b497a2e78302443e319","errMsg":"Validator Heartbeat - invalid signature"},"version":1,"chainId":"test-chain-ezdi1g","txHash":"A57B1635207C9B48642E68557A083BED4C30A0156CF82CEA886CD7CB45E4BEE4"}

[gordsport]

@daniel1302 - please can you see if this issue is still present and indicat the priority?