Remove celo testnet

[chetanbothra]

removed as this is depricated

Summary by CodeRabbit

• Chores
  • Removed testnet configuration and oracle settings, including bundler dependencies for the Celo Alfajores network.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[cloudflare-workers-and-pages]

Deploying arka with    Cloudflare Pages

Latest commit:	3cd866d
Status:	✅  Deploy successful!
Preview URL:	https://4742f280.arka-3qg.pages.dev
Branch Preview URL:	https://remove-celo.arka-3qg.pages.dev

View logs

[coderabbitai]

Walkthrough

The pull request removes configuration and constant entries for chainId 44787 (Celo Alfajores testnet) across two files: deleting bundler configurations from the default config file and removing the corresponding native oracle mapping entry.

Changes

Cohort / File(s)	Change Summary
Removal of Celo Alfajores testnet configuration backend/config.json.default	Deletes two configuration entries for chainId 44787 with bundler v1 and v2, including bundler addresses, etherspotPaymasterAddress, thresholdValue, and entryPoint settings
Removal of Celo Alfajores testnet oracle constant backend/src/constants/ChainlinkOracles.ts	Removes the NativeOracles mapping entry for chainId 44787 (Celo Alfajores testnet oracle address)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify that all references to chainId 44787 have been consistently removed from both configuration and constants layers
• Confirm no other files in the codebase contain hardcoded dependencies on this testnet configuration
• Ensure downstream services or clients won't break from this removal

Poem

🐰 Alfajores sweet, you've had your run,
Your testnet days are done, done, done!
We bid 44787 farewell with grace,
One less chain to keep its place. 🌙✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete and missing required template sections like 'Types of changes' and other structured information; only a brief note about deprecation is provided.	Add the missing 'Types of changes' section, check appropriate checkboxes, and provide more detailed explanation of why Celo testnet is being removed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Remove celo testnet' directly and clearly describes the main change: removing Celo testnet configuration entries from the codebase.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch remove_celo

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 98b2276 and 3cd866d.

📒 Files selected for processing (2)

• backend/config.json.default (0 hunks)
• backend/src/constants/ChainlinkOracles.ts (1 hunks)

💤 Files with no reviewable changes (1)

• backend/config.json.default

⏰ 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

🔇 Additional comments (2)

backend/src/constants/ChainlinkOracles.ts (2)

35-35: LGTM! EOF newline normalized.

The trailing newline after the export is a standard formatting practice.

---

1-35: Complete removal of chain 44787 verified with no remaining references.

The verification confirms that chain 44787 (Celo Alfajores testnet) and its oracle address have been entirely removed from the codebase. No references to the chainId, the specific oracle address 0x022F9dCC73C5Fb43F2b4eF2EF9ad3eDD1D853946, or "alfajores" exist anywhere in TypeScript, JavaScript, or JSON files. Celo Mainnet (chainId 42220) correctly remains in the "Yet to Support" section as a separate entry. The removal is clean with no orphaned configuration or dead code paths.

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