-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Various errors with Neutron Network #17
Comments
Hey @qwertzlbert ! Thank you for reporting this. We will look into it. Happy X-mas! |
Thank you very much! Same back to you! I was also taking a look at stride just before Christmas and unfortunately the issue is relatively similar here. The network misses the required API methods via RPC but seems to only support the required requests via gRPC. |
I had some time this week to take a look at consumer chains (mostly stride and neutron) and figured this might get a bit more complicated than I thought. Doing it like it's implemented right now won't work, as first the consumer chain does not implement To actually resolve the monikers and relationship between signer address and security address you have to look up the linked consumer chain on the provider chain. In the case of On cosmos hub you will find the
Looking up the Now we can take the
And now we can finally look up the signer stats we want to export via the
So to summarize what we need to do to get the stats we need here:
Due to this I'm not quite sure how we could implement the support for such networks. I know you started the work already, but I was not able to get it working for now. I'm still playing around trying to find a working solution which makes sense, but again as I said above not as straight forward as I thought. Also it probably makes sense to document this somewhere :) |
Alright I think this was a layer 8 problem on my end and the issue was with the config I created
I did not realize you had already implemented this correctly as I did not understand the |
I created a PR including a readme explaining the consumer chain support in a bit more detail here: #23 |
Problem Description
Using CVMS to monitor Validators on the Neutron network won't work due to various issues.
Steps to Reproduce
add a config to monitor a neutron validator. E.g.
Start CVMS
This will result in the following errors:
Patching the issue related to the de denom lookup will return the following error
Expected Behavior
Missed blocks for the validator and consumer chain metrics are exported via prometheus.
Additional Information
Issue 1 is related to the
staking
API not being supported by Neutron, this means thevalcons
address can't be looked up via/cosmos/staking/v1beta1/validators?status=BOND_STATUS_BONDED&pagination.count_total=true&pagination.limit=500
I tried to fix this, but seems like there's no easy way to actually lookup the
valcons
address on neutron other than using the tendermint CLI query on the validator itself (tendermint show-address
) which is obviously no solution. Alternatively it could either be required for Neutron to use thevalcons
key instead of the normal account address.Issue 2 is caused by Neutron not implementing the
ccv/provider
API query which is used by CVMS to lookup the consumer (cvms/internal/common/types/cosmos.go
Line 210 in f61ea84
ccv/consumer
calls.Until a fix is available I would recommend to either remove support for Neutron entirely or just remove support for the
uptime
moduleThe text was updated successfully, but these errors were encountered: