Closed timbrinded closed 2 years ago
The vault logs uses prefix 42 instead of whichever chain it is connected to e.g. 2092 for kintsugi.
42
2092
Tested against: kintsugi main net, vault is successfully integrated to the network though, so this is logging defect only.
kintsugi main net
⚠️ Account format used is not for kintsugi Apr 27 18:29:10 timbo-ubun2 systemd[1]: Started Vault servicing issue and redeem requests for Kintsugi. Apr 27 18:29:10 timbo-ubun2 vault[7384]: Apr 27 18:29:10.824 INFO vault: Starting Prometheus exporter at http://127.0.0.1:9615 Apr 27 18:29:10 timbo-ubun2 vault[7384]: Apr 27 18:29:10.824 INFO service: Version: 1.9.6 Apr 27 18:29:10 timbo-ubun2 vault[7384]: Apr 27 18:29:10.824 INFO service: AccountId: 5CFUfGrWKPdTJQ5bM4co11cYijfHXnp96PBtYj3K2dk2KSpd
⚠️ Account format used is not for kintsugi
Apr 27 18:29:10 timbo-ubun2 systemd[1]: Started Vault servicing issue and redeem requests for Kintsugi. Apr 27 18:29:10 timbo-ubun2 vault[7384]: Apr 27 18:29:10.824 INFO vault: Starting Prometheus exporter at http://127.0.0.1:9615 Apr 27 18:29:10 timbo-ubun2 vault[7384]: Apr 27 18:29:10.824 INFO service: Version: 1.9.6 Apr 27 18:29:10 timbo-ubun2 vault[7384]: Apr 27 18:29:10.824 INFO service: AccountId: 5CFUfGrWKPdTJQ5bM4co11cYijfHXnp96PBtYj3K2dk2KSpd
Raised in wrong repo. Re-raised at: https://github.com/interlay/interbtc-clients/issues/284
Description
The vault logs uses prefix
42
instead of whichever chain it is connected to e.g.2092
for kintsugi.Tested against:
kintsugi main net
, vault is successfully integrated to the network though, so this is logging defect only.Steps to recreate