Add Vikasa Network (VIK) token metadata for Polygon

[vikasanetwork]

Vikasa Network (VIK) — Polygon

This PR adds Vikasa Network (VIK) token metadata and icon for Polygon PoS.

• Token: Vikasa Network
• Symbol: VIK
• Network: Polygon PoS
• Contract: 0x2921D67Ac78EBDA0020F952e51e931ed125e00C1
• Decimals: 18
• Standard: ERC-20
• Max Supply: 24,000,000 VIK

Official Links

• Website: https://www.vikasanetwork.com
• PolygonScan: https://polygonscan.com/token/0x2921d67ac78ebda0020f952e51e931ed125e00C1
• Whitepaper: https://www.vikasanetwork.com/whitepaper.pdf
• Documentation: https://github.com/vikasanetwork/vikasa-network-docs

The VIK contract is verified on PolygonScan and the project has an active website, documentation, community channels, and a live Android application.

Thank you for reviewing this submission.

---

Note

Low Risk
Metadata-only addition with no application or on-chain logic changes.

Overview
Adds Vikasa Network (VIK) to the Polygon PoS token catalog via a new metadata entry for contract 0x2921D67Ac78EBDA0020F952e51e931ed125e00C1.

The JSON registers the display name, 18 decimals, symbol VIK, ERC-20 flag, and a logo path under icons/eip155:137/…, matching the existing Polygon ERC-20 metadata pattern.

^{Reviewed by Cursor Bugbot for commit 6631398. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d561ff0. Configure here.}

[cursor]

Metadata nested under extra key

High Severity

The token fields sit under a CAIP-19 key instead of at the file root. buildindex.js already uses the file path as the map key, so consumers will not see name, symbol, decimals, or logo on this token.

 

^{Reviewed by Cursor Bugbot for commit d561ff0. Configure here.}