Added LDC correctly

[7sxnc]

I'm trying to create this pull request:

New Listing: LDC

• Identity Name: Limones Digital Coin
• Authbase: 4d621027246ae61b3de5887e69523eebcc4e3d6e7e031a2aa6010ccc5272ed08

Evidence Linking Authbase to Identity

• Select one:
  • [X] Direct evidence: a chain-resolved registry at the authhead provides substantially equivalent metadata for this authbase. The Authhead TXID is provided below:
  • [ ] Indirect evidence: the identity is burned or provably locked within a covenant, so the authbase can safely be linked using indirect evidence. Details and two or more corroborating, third party-archived URLs of reputable sources vouching for this association are provided below:

Evidence Linking Identity to Authbase

Evidence Linking Authbase to Categories

• Select one:
  • [X] Token category is equal to the authbase for all Identity Snapshots.
  • [ ] Evidence is provided for differing category values below:

Proof: https://explorer.salemkode.com/tx/4d621027246ae61b3de5887e69523eebcc4e3d6e7e031a2aa6010ccc5272ed08 ## Substantiation of Other Claims

• Select one:
  • [X] The submission (esp. the description) includes no claims requiring substantiation.
  • [ ] The claims in this submission can be corroborated with the following evidence:

Checklist

• [X] I have reviewed the OpenTokenRegistry inclusion criteria, and this listing can be included in the registry.
• [X] The listing completes all required fields:
  • name
  • [X] Objective, authoritative, and neutral tone
  • [X] No longer than 20 characters; exceptions may be allowed for existing legal names (please provide evidence above including the jurisdiction(s) in which the legal name is established).
  • description
  • [X] Objective, authoritative, and neutral tone
  • [X] Descriptions is appropriate for use in user interfaces without a disclaimer by unaffiliated, neutral, third parties (wallets, block explorers, exchanges, etc.); no exclamations, calls to action, or disputable statements.
  • [X] All claims are substantiated above.
  • token information (if applicable)
  • [X] Token category is defined.
  • [X] If fungible tokens exist for the category, decimals is defined.
  • symbol
    • [X] Globally-unique base symbol, including among assets not listed in OpenTokenRegistry.
    • [X] Valid symbol (regular expression: /^[A-Z0-9]+[-A-Z0-9]*$/)
    • [X] Appropriate minimum length (For new, primarily-fungible base symbols: minimum of 4 characters; non-fungible base symbols: minimum of 6 characters; see Symbol Length Recommendations)
    • [X] No longer than 13 characters for base symbols
    • [X] No longer than 26 characters for full symbols
  • uris.icon
  • [X] Uses IPFS with a v1 CID. To convert a v0 CID (begins with Qm...), try dweb.link. For example, bafybeifv5l6foaqrxeux4dl7mj55d4a4lsthbrsyba3v6yqtarzbxcmn2m is a v0 CID. It can be viewed at https://d391b93f5f62d9c15f67142e43841acc.ipfscdn.io/ipfs/bafybeifv5l6foaqrxeux4dl7mj55d4a4lsthbrsyba3v6yqtarzbxcmn2m/a21966af10fabce599678eb258e69158.png, which redirects to a subdomain equal to the v1 CID: https://d391b93f5f62d9c15f67142e43841acc.ipfscdn.io/. The correct URI for this icon is: ipfs://QmaanKpq3bsHUrpJuASynqDurDeQbTYz6v35BLaD2BDmzS/a21966af10fabce599678eb258e69158.png.
  • [X] Either SVG format OR 400px by 400px AVIF, WebP, or PNG
  • https://limonia.org
  • https://bcl.limonia.org/en
  • [X] Domain name is owned by the issuing project or organization
  • [X] Either HTTPS protocol OR ongoing activity demonstrated via optional URI identifiers (described in Substantiation of Other Claims)
  • [X] Includes relevant historical information in previous snapshots OR this token has never been rebranded, redenominated, or reissued
  • [X] All static data (images, animations, videos, binary files, etc.) uses IPFS with v1 CIDs to ensure file integrity (e.g. ipfs://ba...).

[georgedonnelly]

Hi, welcome and thanks for your PR!

I would love to support your request, however, I have a few observations to share:

1. 4d621027246ae61b3de5887e69523eebcc4e3d6e7e031a2aa6010ccc5272ed08 is your genesis transaction but your token's category appears to be b1899ba19c167d4ea9dcc64516b6295cdd7616b179b4146f461aacc623e14be6. This is not correctly presented in your BCMR.
2. You appear to have no on-chain BCMR. This would be good to have.
3. Your ticker symbol is 3 characters but OTR guidelines suggest a minimum of 4.
4. I'm not finding your token category on your website... have you considered putting a little text there claiming it? For example: "LDC is Limonia's token for .... The Token ID is xxx. (with a link to an explorer)"
5. Your commit deletes the entire registry, leaving only the BCMR data for your token. You are meant to add your token's BCMR to what is there.
6. Your description could use some work to improve grammar.
7. Instead of "youtube": "None",, you can simply omit the ones with value None.

You may find my tutorial series helpful with these tasks. Here is the latest one: https://www.bitcoincashsite.com/blog/token-pioneers-cashtokens-tutorial-3

You can request more personalized help in the CashToken Devs group, where you are very welcome to ask as many questions as you like!

https://t.me/cashtoken_devs

Thanks again and I welcome your fixes so we can proceed!

[7sxnc]

Hi, thanks. I fixed my error, check again!