Skip to content

Conversation

johnletey
Copy link
Contributor

@johnletey johnletey commented Sep 25, 2025

Description

Add nobleapplayerdevnet metadata and addresses.

Backward compatibility

Yes

Testing

N/A

Summary by CodeRabbit

  • New Features
    • Added support for the Noble Applayer Devnet testnet, including full chain metadata (chain ID, naming, native token, protocol, deployer, domain, block timing, and reorg settings).
    • Integrated RPC endpoint and block explorer details for improved tooling and wallet compatibility.
    • Configured core interchain components (security module, mailbox, merkle tree hook) to enable messaging and dapp connectivity on this network.

Copy link

changeset-bot bot commented Sep 25, 2025

⚠️ No Changeset found

Latest commit: de27cef

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Sep 25, 2025

📝 Walkthrough

Walkthrough

Adds three address entries to chains/nobleapplayerdevnet/addresses.yaml and introduces a new chains/nobleapplayerdevnet/metadata.yaml defining chain metadata (IDs, protocol, explorer, RPC, timing, and reorg settings) for the Noble Applayer Devnet testnet.

Changes

Cohort / File(s) Summary
Noble Applayer Devnet addresses update
chains/nobleapplayerdevnet/addresses.yaml
Added keys: interchainSecurityModule, mailbox, merkleTreeHook with specified contract addresses.
Noble Applayer Devnet metadata addition
chains/nobleapplayerdevnet/metadata.yaml
New file defining chain metadata: chainId, testnet flag, names, native token, protocol, deployer, display name, domainId, explorer config, RPC URL, block timing, and reorg settings.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • paulbalaji
  • yjamin

Poem

New paths carved through the swampy devnet glen,
Addresses sprout, three sturdy oaks again.
A fresh map pinned—metadata’s bright sign,
Explorer to the left, RPC on the line.
Trudge on, boots clean—configs set, we’re fine. 🧭✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title Check ✅ Passed That title’s clear as day, it calls out adding metadata and addresses for the nobleapplayerdevnet chain without any muddy bits or extra fluff.
Description Check ✅ Passed The PR description lays out the Description, Backward compatibility, and Testing sections just as the template asks, providing clear answers under each heading without any muck.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a4bf508 and de27cef.

⛔ Files ignored due to path filters (1)
  • chains/nobleapplayerdevnet/logo.svg is excluded by !**/*.svg
📒 Files selected for processing (2)
  • chains/nobleapplayerdevnet/addresses.yaml (1 hunks)
  • chains/nobleapplayerdevnet/metadata.yaml (1 hunks)
🔇 Additional comments (2)
chains/nobleapplayerdevnet/metadata.yaml (1)

1-26: All the metadata lines up cleanly.

Everything here smells right—IDs, explorer, and timing knobs are all set like a well-kept swamp trail.

chains/nobleapplayerdevnet/addresses.yaml (1)

1-3: Addresses look ready for the stroll.

Checksum casing and mappings fit the usual groove with no surprises lurking in the reeds.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


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

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

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.

1 participant