[euphrates-0.2.0] Issues regarding PoS integration

[maurolacy]

In the euphrates-0.2.0 context, when running this command: stakercli daemon babylon-finality-providers
The following error is now reported:

[btc-staker] error in json rpc client, with http response metadata: (Status: 200 OK, Protocol HTTP/1.1). RPC error -32603 - Internal error: proto: wrong wireType = 2 for field SlashedBabylonHeight

A way to overcome this issue is querying the FPs (both Babylon and consumer) directly from the Babylon chain.

Also, the following command: stakercli daemon list-outputs
Returns the following error:

[btc-staker] post failed: Post "http://127.0.0.1:15812/": EOF

Also, when running this command: stakercli daemon stake

Error: [btc-staker] error in json rpc client, with http response metadata: (Status: 200 OK, Protocol HTTP/1.1). RPC error -32603 - Internal error: error checking if finality provider exists on babylon chain: proto: wrong wireType = 2 for field SlashedBabylonHeight

The same error when querying the FPs through.

[maurolacy]

On further analysis, this seems to be a regression error as these commands worked when tested initially (around May 17).
The error may be caused by changes in other repos, that were not properly tagged (or whose minor versions were indeed breaking).

My main suspect here is the babylon-contract 0.5.x release series.

[SebastianElvis]

Is this still open?