I connected the btc-validator to a remote EOTS manager address that didn't exist. The daemon didn't report any error. Afterwards when I tried to create a BTC Validator on it, it crushed silently with no indication why.
+ vald start
service injective.evm.v1beta1.Msg does not have cosmos.msg.v1.service proto annotation
2023-12-06T14:57:08.411899Z info successfully connected to a remote EOTS manager {"address": "NON_EXISTENT_FQDN"}
2023-12-06T14:57:08.416385Z info Starting ValidatorApp
2023-12-06T14:57:08.416956Z info RPC server listening {"address": "[::]:15812"}
2023-12-06T14:57:08.417006Z info BTC Validator Daemon is fully active!
gitferry
commented
10 months ago
I connected the btc-validator to a remote EOTS manager address that didn't exist. The daemon didn't report any error. Afterwards when I tried to create a BTC Validator on it, it crushed silently with no indication why.