Add xINIT-INIT-LP

[JSHan94]

• Add xINIT-INIT-LP

Summary by CodeRabbit

• New Features
  • Added support for xINIT-INIT Liquidity Pool Token on Initia DEX, including denomination units, token metadata, and associated imagery.

[cloudflare-workers-and-pages]

Deploying registry-testnet with    Cloudflare Pages

Latest commit:	becc0f5
Status:	✅  Deploy successful!
Preview URL:	https://a2755589.initia-registry-testnets.pages.dev
Branch Preview URL:	https://add-xinit-lp.initia-registry-testnets.pages.dev

View logs

[coderabbitai]

Walkthrough

A new Liquidity Pool Token asset entry for the xINIT-INIT trading pair has been added to the Initia asset list. The entry includes LP denom units, base reference, metadata, and associated logo URIs, positioned between existing sxINIT and cabal USDC-INIT LP entries.

Changes

Cohort / File(s)	Summary
Asset List Configuration mainnets/initia/assetlist.json	Added new LP token asset entry for xINIT-INIT trading pair with complete metadata (denom units, display info, token_type set to "lp", logo/image URIs)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single-file change consisting of a straightforward JSON object addition
• No logic modifications or structural changes to existing entries
• Verify the new LP token metadata (denom units, naming conventions, URI validity) aligns with existing asset entries

Poem

🐰✨ A new LP token hops into view,
xINIT-INIT, shiny and new,
Between sxINIT and cabal it stays,
Liquidity pooled for trading days! 🌿💫

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add xINIT-INIT-LP' directly matches the main change: adding a new Liquidity Pool Token entry for the xINIT-INIT trading pair to the assetlist.json file.
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 add-xINIT-LP

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between ac36b3e and becc0f5.

⛔ Files ignored due to path filters (2)

• images/cbl-USDC-INIT.png is excluded by !**/*.png
• images/xINIT-INIT.png is excluded by !**/*.png

📒 Files selected for processing (1)

• mainnets/initia/assetlist.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Cloudflare Pages: registry-mainnet

🔇 Additional comments (1)

mainnets/initia/assetlist.json (1)

1192-1218: Well-structured LP token entry with proper formatting. ✓

The new xINIT-INIT LP asset entry is correctly formatted with consistent structure matching existing LP token entries (USDC-INIT LP, cbl USDC-INIT LP). The denom_units, base reference, display/name/symbol alignment, and token_type are all properly configured. Positioning between sxINIT and cbl USDC-INIT LP is logical.

Please verify the following before merge:

1. Image availability: Confirm that the image file xINIT-INIT.png exists at the referenced GitHub URL (https://raw.githubusercontent.com/initia-labs/initia-registry/main/images/xINIT-INIT.png)
2. Move address validity: Validate that the move module address move/c71aa9c25976a1070ccf16b6b74ec611912212d805a2575cddff875d49872151 is correct and unique for the xINIT-INIT LP on Initia
3. Schema compliance: Run any JSON schema validation that your CI pipeline uses to ensure this entry conforms to the assetlist schema

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, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

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.}

[cloudflare-workers-and-pages]

Deploying registry-mainnet with    Cloudflare Pages

Latest commit:	becc0f5
Status:	✅  Deploy successful!
Preview URL:	https://7d32376d.registry-mainnet.pages.dev
Branch Preview URL:	https://add-xinit-lp.registry-mainnet.pages.dev

View logs