We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When we check Uptime in Dungeon Chain it shows 0% for POSTHUMAN validator: https://ping.pub/Dungeonchain/uptime
But POSTHUMAN validator works perfectly, and if we go to blocks, we can see such a picture: https://ping.pub/Dungeonchain/block
Part of blocks a proposed by unnamed validator (this is POSTHUMAN validator)
If we will check block, that is proposed by "unknown validator" we will see next: https://ping.pub/Dungeonchain/block/413809
proposer address: hahfJOmyEvC3y70ffwMrh3W2klg=
this is the address of POSTHUMAN, and as you can see, ping.pub don't recognize POSTHUMAN:
We try to understand how to fix it for 2 days, but still didn't find a solution, maybe problem in the interface? Or maybe you can help us to solve it?
The text was updated successfully, but these errors were encountered:
Is this consumer chain? If yes, you have to config provider rest endpoint
Sorry, something went wrong.
No branches or pull requests
When we check Uptime in Dungeon Chain it shows 0% for POSTHUMAN validator:
https://ping.pub/Dungeonchain/uptime
But POSTHUMAN validator works perfectly, and if we go to blocks, we can see such a picture:
https://ping.pub/Dungeonchain/block
Part of blocks a proposed by unnamed validator (this is POSTHUMAN validator)
If we will check block, that is proposed by "unknown validator" we will see next:
https://ping.pub/Dungeonchain/block/413809
proposer address:
hahfJOmyEvC3y70ffwMrh3W2klg=
this is the address of POSTHUMAN, and as you can see, ping.pub don't recognize POSTHUMAN:
We try to understand how to fix it for 2 days, but still didn't find a solution, maybe problem in the interface?
Or maybe you can help us to solve it?
The text was updated successfully, but these errors were encountered: