When I was looking at the code this morning, I incorrectly interpreted it's purpose.
I see my issue that I had reading it this morning. Reverted back to the original.
CORS has been fixed and is ready to go for when mainnet goes live.
After speaking with the team, they wanted to wait until next month for the listing on Pingpub. They are on a 'testnet' right now in prep for Mainnet. Current testnet is being treated as mainnet.
Sorry for the bouncing around.
This morning the Vidulum chain was showing all validators as red and missed blocks.
There might be a more inline way to do the logic but it wasn't comparing both to be greater than 1. After making sure both were compared against, the update for Vidulum was resolved.
I also spot checked a few other chains to ensure their uptimes were showing properly and they were.
Some of the chain files I updated were done on an older chain file, and so some of the new information was lost.
I went through all chains that I found a github link for, verified the cosmos sdk version and change it respectively.
Some of the chains do not have a link to github. Others have an improper link to their repo, some links go to another project within their repo and some were just wrong.
Probably worth figuring out how to auto fetch the current SDK version instead of it being a manual configuration.
This feature add's the discord chat link if one exists inside the `chat_url`. I filter and search for a link containing `discord`. Then if matching, displays the link.
There were a few odd issues with some of the RPC's blocking certain calls for some chains. I don't know all affected, as I only use a few that the true ping.pub repository uses.
Stargaze was one.
I have added Polkachu and Notional API and RPC endpoints.
I have updated the git ignore file to exclude some of the yarn files created when running that command.
