[addToken] PZL to MAINNET

[github-actions]

addToken

Note This is an automated PR

Submitted by @vlzhr

Closes #1256

---

Adding token PZL on network MAINNET

Address: 0x37f3ed0186aadf2966bd75cf702ad0f31ab13318

Link to block explorer ↗︎

Description	Image
Original
Optimized

Reason

PUZZLE is the utility token of puzzle.network, the leading DeFi platform of Waves Blockchain with $10M TVL. It's actively traded for more than 4 years and is tracked by Coingecko https://www.coingecko.com/en/coins/puzzle-swap. Now we are launching LST for PUZZLE, called Staked PUZZLE (PZL) and going crosschain for it. 

We would love to have it whitelisted in CowSwap default tokens and use your platform as a primal source for trading PZL to onboard Ethereum users.

Summary by CodeRabbit

• New Features
  • Added support for the Staked PUZZLE (PZL) token on Ethereum mainnet, including token metadata and visual assets.

[coderabbitai]

Walkthrough

This pull request adds support for the Staked PUZZLE (PZL) token to the CowSwap token list on Ethereum mainnet. The changes include registering the new token in the main token list configuration and creating a corresponding metadata file with token details.

Changes

Cohort / File(s)	Summary
Token list configuration src/public/CowSwap.json	Adds new PZL (Staked PUZZLE) token entry with address 0x37f3ed0186aadf2966bd75cf702ad0f31ab13318, 18 decimals, and associated logo URI. Positioned before the SAND token entry.
Token metadata src/public/images/1/0x37f3ed0186aadf2966bd75cf702ad0f31ab13318/info.json	Creates new metadata file defining PZL token properties, including symbol, name, decimals, chainId, logoURI, and reason describing the token as a cross-chain Liquid Staking Token for PUZZLE.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Simple static data addition with no business logic changes
• Straightforward token registration following existing patterns
• Verify token address matches the linked issue and logo URI is accessible

Suggested reviewers

• alfetopito

Poem

🐰 A token hops into the light,
PZL puzzles now stake right!
From Waves to chains it takes its flight,
Staked PUZZLE shines so bright! ✨

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically identifies the main change: adding the PZL token to MAINNET, which aligns with the changeset's addition of PZL token entries.
Linked Issues check	✅ Passed	The PR adds PZL token with matching specifications from issue #1256: symbol PZL, name Staked PUZZLE, decimals 18, address 0x37f3ed0186aadf2966bd75cf702ad0f31ab13318, chainId 1 (MAINNET), and includes token metadata.
Out of Scope Changes check	✅ Passed	All changes are directly related to adding the PZL token to the MAINNET as specified in issue #1256; no unrelated modifications are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch addToken/1_0x37f3ed0186aadf2966bd75cf702ad0f31ab13318

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example:

"Create a concise high-level summary as a bullet-point list. Then include a Markdown table showing lines added and removed by each contributing author."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[vlzhr]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/public/CowSwap.json (1)

382-389: Address case inconsistency between metadata and list files.

The PZL token address differs in case between files:

• info.json (line 3): 0x37f3eD0186AaDF2966BD75cf702aD0f31AB13318 (mixed case/EIP-55)
• CowSwap.json (line 383): 0x37f3ed0186aadf2966bd75cf702ad0f31ab13318 (lowercase)

While Ethereum addresses are case-insensitive, maintaining consistent formatting across the repository improves maintainability. Consider standardizing to one format (EIP-55 checksum or lowercase) across all token references.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5b784ff and d7b7fec.

⛔ Files ignored due to path filters (1)

• src/public/images/1/0x37f3ed0186aadf2966bd75cf702ad0f31ab13318/logo.png is excluded by !**/*.png

📒 Files selected for processing (2)

• src/public/CowSwap.json (2 hunks)
• src/public/images/1/0x37f3ed0186aadf2966bd75cf702ad0f31ab13318/info.json (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: avivkeller
Repo: cowprotocol/token-lists PR: 1047
File: scripts/processRequest.mjs:38-44
Timestamp: 2025-08-04T17:57:56.851Z
Learning: In the cowprotocol/token-lists repository, the `{0}` placeholder in `prImageUrl` within `scripts/processRequest.mjs` is intentionally left as a literal template string that gets formatted/replaced when injected into comment bodies in the GitHub workflow, following the established pattern from the original `.github/workflows/processRequest.yml`.

Learnt from: avivkeller
Repo: cowprotocol/token-lists PR: 1047
File: scripts/processRequest.mjs:38-44
Timestamp: 2025-08-04T17:57:56.851Z
Learning: In the cowprotocol/token-lists repository, URLs with `{0}` placeholders in `scripts/processRequest.mjs` (like `prImageUrl`) are intentionally left as templates that get processed using GitHub Actions' `format()` function in the workflow files, where `{0}` gets replaced with operation-specific values like 'addToken' or 'addImage'.

📚 Learning: 2025-08-04T17:57:56.851Z

Learnt from: avivkeller
Repo: cowprotocol/token-lists PR: 1047
File: scripts/processRequest.mjs:38-44
Timestamp: 2025-08-04T17:57:56.851Z
Learning: In the cowprotocol/token-lists repository, the `{0}` placeholder in `prImageUrl` within `scripts/processRequest.mjs` is intentionally left as a literal template string that gets formatted/replaced when injected into comment bodies in the GitHub workflow, following the established pattern from the original `.github/workflows/processRequest.yml`.

Applied to files:

• src/public/CowSwap.json

🔇 Additional comments (2)

src/public/CowSwap.json (2)

380-397: Correct placement and valid token entry structure.

The PZL token entry is correctly positioned in ascending address order (between gtcETH and SAND) and includes all required fields (address, symbol, name, decimals, chainId, logoURI). The JSON syntax is valid with proper comma placement. Token details align with PR objectives: symbol PZL, name "Staked PUZZLE", decimals 18, and chainId 1 (Ethereum mainnet).

---

1-2087: Logo file verified—no action required.

The logo image file exists at the referenced path src/public/images/1/0x37f3ed0186aadf2966bd75cf702ad0f31ab13318/logo.png. The PR changes are complete and correct.