Skip to content

Add KONET Mainnet metadata and update explorer URL#2646

Open
zekto-dev-hong wants to merge 2 commits into
DefiLlama:mainfrom
zekto-dev-hong:feat/update-konet-icon-explorer
Open

Add KONET Mainnet metadata and update explorer URL#2646
zekto-dev-hong wants to merge 2 commits into
DefiLlama:mainfrom
zekto-dev-hong:feat/update-konet-icon-explorer

Conversation

@zekto-dev-hong
Copy link
Copy Markdown

Link the service provider's website (the company/protocol/individual providing the RPC):

https://konetmain.com

Provide a link to your privacy policy:

No publicly linked privacy policy was found on the official KONET site or explorer page.

If the RPC has none of the above and you still think it should be added, please explain why:

This PR is not adding a new third-party RPC provider.
It adds the public source metadata for KONET Mainnet (chainId 17217) and updates the explorer URL to:
https://konetexplorer.io/

The existing RPC remains:
https://api.kon-wallet.com

@zekto-dev-hong
Copy link
Copy Markdown
Author

Hi maintainers,

The metadata PR for KONET Mainnet (chainId 17217) has been submitted.

For the icon:

  • the chain metadata uses icon: "konet"
  • https://chainlist.org/rpcs.json already includes icon: "konet" for chainId 17217
  • but the icon asset does not seem to resolve from the icons host
  • https://icons.llamao.fi/icons/chains/rsz_konet.jpg returns 404
  • while a known working example such as https://icons.llamao.fi/icons/chains/rsz_monad.jpg returns 200

I am attaching the official KONET logo asset to this comment.
Could you please confirm the correct path to add or update the KONET icon asset for the konet icon key?

Thank you.
konet_symbol

@Define101
Copy link
Copy Markdown
Member

@zekto-dev-hong
Copy link
Copy Markdown
Author

zekto-dev-hong commented Apr 21, 2026

Hi @Define101, thanks for the pointer.

I understood your comment to mean that the upstream metadata should be updated first, so I opened a PR in ethereum-lists/chains to update the KONET Mainnet explorer information:

ethereum-lists/chains#8239

Also, I wanted to mention one remaining issue I still observe on chainlist.org/chain/17217:
the network is currently shown with the default Ethereum-style fallback icon instead of the KONET icon.
image

Could you please let me know whether this chainlist PR should remain open for that icon issue, or if the icon is handled through a separate sync/cache/pipeline after the upstream metadata is updated?

If the upstream PR is the only required step, I am happy to close this PR once that change is merged.

Thank you.

@github-actions
Copy link
Copy Markdown

Validation failed for chain files. Please check the workflow logs for details.

Error message:

Validation failed for chainid-42429.js: Cannot find module '/home/runner/work/chainlist/chainlist/constants/additionalChainRegistry/chainid-42429.js' imported from /home/runner/work/chainlist/chainlist/.github/scripts/validate-chain-files.js
Validation failed for chainid-5042.js: Chain name should be an object
Validation failed for chainid-5900.js: Cannot find module '/home/runner/work/chainlist/chainlist/constants/additionalChainRegistry/chainid-5900.js' imported from /home/runner/work/chainlist/chainlist/.github/scripts/validate-chain-files.js

@zekto-dev-hong
Copy link
Copy Markdown
Author

Hi team,

I updated the KONET explorer URL to align with the merged upstream ethereum-lists/chains data:

https://konetexplorer.io

The only change is removing the trailing slash from the explorer URL.

Could someone please help review this PR when available?

Thank you.

@zekto-dev-hong zekto-dev-hong force-pushed the feat/update-konet-icon-explorer branch from 0109130 to 81b0b15 Compare May 11, 2026 00:32
@zekto-dev-hong
Copy link
Copy Markdown
Author

zekto-dev-hong commented May 11, 2026

Update: I rebased this PR on the latest upstream main, and the validation check is now passing.

The KONET explorer URL remains aligned with the merged ethereum-lists/chains data:

https://konetexplorer.io

Could someone please help review this when available?

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants