Mr Hankey $SHIT verification

[SoA432]

ASCAN Token Submission

Introduction

Before submitting this PR, ensure you have followed all the requirements below and filled out all necessary details about your token.

Checklist

Please review the checklist below and check each item before submitting your token information:

• I have reviewed the submission guidelines.
• The submitted files are in the correct format and fulfill all requirements outlined below.

Asset Details

General Information

• Token Name: Mr Hankey
• Symbol: $SHIT
• Contract Address: 5F9aiiwLMPC6fFxxwqHvJpm7h5T4Xm93mJT6cpDrQnKkLFoK
• Decimals: 12

Logo

• Logo file added to the PR
• File Name: logo.png
• Size: 256x256 pixels
• File Extension: png

Metadata File

• Metadata file added to the PR
• File Name: metadata.json
• File Extension: json

Token Information File

• Token information file added to the PR
• File Name: info.json
• File Extension: json

Required Content in info.json:

{
  "name": "Mr Hankey",
  "symbol": "SHIT",
  "type": "PSP22",
  "contractAddress": "5F9aiiwLMPC6fFxxwqHvJpm7h5T4Xm93mJT6cpDrQnKkLFoK",
  "decimals": 6,
  "description": "Most famous meme $SHIT",
  "website": "https://the-shit.xyz/",
  "sourceCode": "",
  "links": [
    {
      "name": "X/Twitter",
      "url": "https://x.com/mr_hankey_shit"
    },
    {
      "name": "Telegram",
      "url": "https://t.me/mr_hankey_shit"
    },
    {
      "name": "Discord",
      "url": ""
    }
  ],
  "customTags": [
    "$SHIT Contract Address"
  ],
  "warnings": [],
  "owner": "5DMCcKK5HuEtSQ9QT9eunuzLy7owhLGX5g77Es9fsoRyhcXj",
  "minter": "5DMCcKK5HuEtSQ9QT9eunuzLy7owhLGX5g77Es9fsoRyhcXj"
}

Note on Custom Tags

The customTags field in the info.json file is optional. This field can be used to include specific tags that describe unique characteristics or features of the token, such as burner wallet. Include custom tags only if they are relevant to the token’s functionality or usage.

Note on Owner and Minter

The owner and minter fields should include the addresses of the accounts that hold these capabilities within the token's smart contract. The owner is typically the account that has administrative rights over the entire contract, while the minter might be an account with the capability to issue new tokens.

Note on Warnings

Please do not fill out the warnings field in the info.json file. This field is reserved for use by our auditing team, who will add relevant warnings such as "Mintable" or "Burnable" after thoroughly reviewing the token's smart contract. This ensures that all warnings are accurate and based on a comprehensive technical assessment.

[DamianStraszak]

Please provide source code link.

The metadata.json does not match the on-chain contract.

[SoA432]

Please provide source code link.

The metadata.json does not match the on-chain contract.

Hi @DamianStraszak
Updated sourceCode, for metadata - can you please provide more information where we can get it ? Its just copy-paste metadata from source examples.

[DamianStraszak]

You obtain metadata after compiling the contract from source. If you didn't do it yourself, you can ask the author of the source code. If you use the INW2 contract, then the same metadata should work as in some other requests.

[SoA432]

You obtain metadata after compiling the contract from source. If you didn't do it yourself, you can ask the author of the source code. If you use the INW2 contract, then the same metadata should work as in some other requests.

Yeap its from INW2, updated