Hi, after updated to new version of Cosmostation, I've sent HEART tokens Erc20 from another wallet to Erc20 Ethereum address on Cosmostation,but I can't see my tokens.
I've checked transaction and been 'Succesful'
Can you help me please?

Add Kujira Network (kaiyo-1) again.

My validator is TienThuatToan (https://www.mintscan.io/neutron/ics-validators/neutronvaloper13ql36flc4cdjhx08hke5vpr4dyv03aafgdg9rg).
Neutrond shows that my validator has missed 722 blocks. But I see that Mintscan hasn't recorded any missed blocks since Neutron launched. Can you check it?
Please take the look https://imgur.com/FpT0ocd.
Smartstake also records missed blocks https://analytics.smartstake.io/neutron/val/cosmosvaloper1ff0dw8kawsnxkrgj7p65kvw7jxxakyf8n583gx

Requesting my CRO coins back please? I believe your validator took them or send them out occuring to the transaction information I have proof .he or she send/tranfer out my cRO coins to his cosmo acc# i decided to unstake my cro coin on the beginning of December 5 2022 , I had to wait for the 28days unstake waiting period requirement. Which I'm reaching to you for guidance I need this resolved please I have the information whom done the transactions I dont recognizes this person or who ever it is..

His/Hers ID:

cro1y95famfqkazfy3zs0uq86j529udvm5wlkyrhez

Txid: 850CB079BEA9FE651AE51587D01595EE6479D7BB2B9575BDAB8D997900D768EB

(CRO Amount 996.016 )

Txid:
FB560C3B00D3BEEC96725D5C9F13104BF835080A3395A101CB4E03314B549FAE

( Cro coin amount 1,491)

This My ID
Beginning with [cro1et3ht5]

I had 2 unbounding transactions ended from.

( December 5 2022- January 2 2023 )
Any questions please respond back asoon as possible

Here's a screenshot of the transactions they did without my authorization I dont know who or how is this possible ..

Email me ([email protected] ) if u have any questions!

Greetings.
I am operating the following Cosmos Hub validator: https://www.mintscan.io/cosmos/validators/cosmosvaloper1xqz9pemz5e5zycaa89kys5aw6m8rhgsvw4328e
I did a rebranding shortly after it went active, from freak12techno to Quokka Stake.
But somehow the link in the "Additional Info" block leads to this page https://hub.mintscan.io/validators/stats/freak12techno/cosmos/cosmosvaloper1xqz9pemz5e5zycaa89kys5aw6m8rhgsvw4328e, which includes my older moniker.
Is there anything I should/can do to get it updated?

(Sorry if this is a wrong repository to report it to, didn't find any other one that suits it.)

Hi,

I made a PR a few days ago to update the Terra Classic logo for TerraCVita, which was merged (#377)

However, the logo did not update on the restake app (https://restake.app/terra/terravaloper1uymwfafhq8fruvcjq8k67a29nqzrxnv9m6m427) and still points to https://raw.githubusercontent.com/cosmostation/cosmostation_token_resource/master/moniker/terra/terravaloper1uymwfafhq8fruvcjq8k67a29nqzrxnv9m6m427.png.

Is that the expected behavior?

Regards,
Thomas

Scope

• Created this issue to restart a convo as a follow-up to a previous PR. The outcome of the closed PR was that Injective agreed to automate the addition of token metadata to your chain/injective/assets.json file. The automation script will live within injective's open-source injective-ts repo.

Sandbox environment

• forked injective-ts and added the script, which can be found here
• forked cosmostation/chainlist and ran the automation script from injective-ts, which opened a test PR to the forked cosmostation/chainlist repo

Limitations of the script

• script will not replace any existing assets in the chain/injective/assets.json except for adding a coingeckoId if not present. Otherwise, the script ONLY appends new assets to chain/injective/assets.json
• cant guarantee the origin_chain will always have a value since we don't always have this on our end. Please check this when reviewing each PR to cosmostation, if it's a required field
• can't get origin_type as we do not store that info in injective-ts hardcoded assets list
• please check if decimals and coingeckoId are included on the new assets added in the PR to cosmostation, as we need those for defillama calc. else, please add if possible
• cannot get image property
• script does not yet support the additional ibc or bridge token type properties of an asset for now as I'm trying to keep it simple. If needed, please add manually for now

Todo

• please review the example PR and see if the file changes are formatted properly enough. I understand y'all may have to add additional properties on these automated PR's, but I hope it's at least better than having to do them all from scratch. Also, the first PR we make using this approach will obviously have many assets to add, like in example PR. But, all subsequent PR's should be much easier
• After the script is deemed to be producing adequate metadata for you guys, I will move the script over to our canonical injective-ts repo and use it to create a PR to the canonical cosmostation/chainlist repo
• happy to hear any thoughts or improvements y'all may have

Hello. Use keybase.io identity from validator metadata to get logo instead of PR. This is much more convenient for validators!
The validator sends metadata information to the blockchain when registering a validator account.

Example for Cosmos-like validators

osmosisd tx staking create-validator \
--website="<website>" \
--details='<desc>' \
--identity=<keybase.io identity > \
...

Doc

The --identity can be used as to verify identity with systems like Keybase or UPort. When using Keybase, --identity should be populated with a 16-digit string that is generated with a keybase.io (opens new window) account. It's a cryptographically secure method of verifying your identity across multiple online networks. The Keybase API allows us to retrieve your Keybase avatar. This is how you can add a logo to your validator profile.

How to get Logo URL by public identity key

key_suffix=<identity>

$ curl -s "https://keybase.io/_/api/1.0/user/lookup.json?key_suffix=E73AFD8985423B14&fields=pictures" | jq .them
[
  {
    "id": "5764d5f1a9c055df1c71a9c71e993519",
    "pictures": {
      "primary": {
        "url": "https://s3.amazonaws.com/keybase_processed_uploads/128efcca8fffd52fed0cae7aa9f25d05_360_360.jpg",
        "source": null
      }
    }
  }
]

Hello Mintscan Team,

I hope this message finds you well. I am reaching out to inquire about the process and requirements for integrating a new blockchain, which is built using the Cosmos SDK, into the Mintscan explorer.

Our team has developed a public chain based on the Cosmos SDK and we are keen on making it accessible through Mintscan to enhance its visibility and usability within the Cosmos ecosystem. Could you please provide us with detailed information on the following:

Compatibility Requirements: Are there any specific versions of the Cosmos SDK or other technical standards that our chain needs to comply with to be eligible for integration into Mintscan?

Integration Process: Could you outline the steps involved in the integration process? Additionally, is there any documentation available that we could follow?

API Requirements: What specific APIs do we need to provide for Mintscan to fetch data from our chain? Details on the required endpoints, data formats, and any other technical specifications would be greatly appreciated.

Submission Guidelines: Is there a formal submission process or form that we need to complete? Also, whom should we contact for further discussions or clarifications regarding our integration?

Testing and Validation: Before finalizing the integration, what kind of testing or validation processes are involved? We would like to prepare in advance to ensure a smooth integration.

We are fully committed to facilitating this process from our end and are ready to provide any additional information or assistance required. Our chain details are as follows:

Chain Name: yymmchain
Chain ID: yymmchain
Cosmos SDK Version: cosmos-sdk v0.50.2
Other Relevant Information: https://www.bitverse.zone/
We believe that being part of Mintscan will not only benefit our chain's community by providing them with a robust and user-friendly explorer but will also contribute to the Cosmos ecosystem as a whole.

Thank you for considering our request. We look forward to your guidance and hope to successfully complete the integration with your support.

Best regards,

lee
bitverse

Our validators' website doesn't appear in the Mintscan but it appears in the Ping.
My validator is https://ping.pub/cosmos/staking/cosmosvaloper13ql36flc4cdjhx08hke5vpr4dyv03aafnmvtnc, https://www.mintscan.io/cosmos/validators/cosmosvaloper13ql36flc4cdjhx08hke5vpr4dyv03aafnmvtnc
I think Mintscan's code doesn't understand the .ventures domain.

Hi team,

You recently added CRBRUS support to several additional chains beyond osmosis. However I noticed it is not showing up on Terra (phoenix-1). See previous PR for reference: #1233

Currently the proposal participation on mintscan is shown for all times even when a validator entered the active set later. So this gives values like 40/71 even though a validator participated in all proposals, but as a validator joined later, they were not able to participate in the earlier ones.
This should be changed to a proportion reflecting the available proposals or a limited timeframe like 1 year, especially because it favors big validators and does not support decentralization as intended by enhancements of the active set.

This issue should actually be in the mintscan repo, but I guess it is private, so I can't open an issue there

Please open upload files..
Thanks
Screenshot
https://snipboard.io/MsZ2Ha.jpg

Unknown github user created a pool request to add logo of POSTHUMAN validator in Kava:
https://github.com/cosmostation/chainlist/commits?author=qraga77

POSTHUMAN validator doesn't have validator in Kava

The list of our core-team members are available here:
https://github.com/Validator-POSTHUMAN/core-team

It's not a problem, it's something I'm worried about. I made a pull request for the Shido chain on April 5th, 2024, and it was successfully merged and closed. But I haven't seen my Shido chain on Mintscan yet. Is there a specific time when it will show up on Mintscan?

here is the Request link "#1581"