Conversation
- add Creator Chain Testnet to registry
🦋 Changeset detectedLatest commit: 0662227 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
📝 WalkthroughWalkthroughAdds Creator Chain Testnet configuration to the registry: a changeset for a minor version bump and two YAML files providing network metadata and on-chain addresses for the new testnet deployment. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @chains/creatorchaintestnet/metadata.yaml:
- Line 19: Update the metadata key technicalStack from "other" to "zksync" so
the entry matches other zkSync-based networks; locate the technicalStack field
in the metadata (the line currently reading technicalStack: other) and replace
its value with technicalStack: zksync.
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
chains/creatorchaintestnet/logo.svgis excluded by!**/*.svg
📒 Files selected for processing (3)
.changeset/good-sails-pull.mdchains/creatorchaintestnet/addresses.yamlchains/creatorchaintestnet/metadata.yaml
🧰 Additional context used
📓 Path-based instructions (2)
**/*.{yaml,yml}
📄 CodeRabbit inference engine (CLAUDE.md)
YAML files must have keys sorted alphabetically
Files:
chains/creatorchaintestnet/addresses.yamlchains/creatorchaintestnet/metadata.yaml
chains/*/{metadata,addresses}.yaml
📄 CodeRabbit inference engine (CLAUDE.md)
Chain directories must contain metadata.yaml (chain metadata including chainId, RPC URLs, block explorers, native token), addresses.yaml (deployed contract addresses including mailbox, ISM factories, hooks), and logo.svg (chain logo)
Files:
chains/creatorchaintestnet/addresses.yamlchains/creatorchaintestnet/metadata.yaml
🧠 Learnings (7)
📓 Common learnings
Learnt from: xeno097
Repo: hyperlane-xyz/hyperlane-registry PR: 788
File: chains/unichain/metadata.yaml:3-4
Timestamp: 2025-07-23T21:28:47.407Z
Learning: In the hyperlane-registry repository, API keys in chain metadata YAML files (like in chains/*/metadata.yaml) are intended for public usage and are not sensitive credentials that need to be hidden.
Learnt from: CR
Repo: hyperlane-xyz/hyperlane-registry PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-18T23:00:58.850Z
Learning: Applies to chains/*/{metadata,addresses}.yaml : Chain directories must contain metadata.yaml (chain metadata including chainId, RPC URLs, block explorers, native token), addresses.yaml (deployed contract addresses including mailbox, ISM factories, hooks), and logo.svg (chain logo)
Learnt from: paulbalaji
Repo: hyperlane-xyz/hyperlane-registry PR: 1302
File: deployments/warp_routes/USDC/paradex-deploy.yaml:43-55
Timestamp: 2025-12-23T12:47:42.372Z
Learning: In Hyperlane warp route deployment YAML files (deployments/warp_routes/**/*-deploy.yaml), omitting the `contractVersion` field for a chain is intentional when you want that chain to use the latest contract version, while other chains with explicit `contractVersion` values remain on their specified versions without requiring upgrades.
Learnt from: CR
Repo: hyperlane-xyz/hyperlane-registry PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-18T23:00:58.850Z
Learning: Applies to src/**/*.ts : Export chain metadata, addresses, and warp route configs in multiple formats: individual chain imports via `hyperlane-xyz/registry/chains/{chainName}`, combined maps (chainMetadata, chainAddresses, warpRouteConfigs), and Registry classes for programmatic access
📚 Learning: 2025-07-23T21:28:47.407Z
Learnt from: xeno097
Repo: hyperlane-xyz/hyperlane-registry PR: 788
File: chains/unichain/metadata.yaml:3-4
Timestamp: 2025-07-23T21:28:47.407Z
Learning: In the hyperlane-registry repository, API keys in chain metadata YAML files (like in chains/*/metadata.yaml) are intended for public usage and are not sensitive credentials that need to be hidden.
Applied to files:
.changeset/good-sails-pull.md
📚 Learning: 2025-12-18T23:00:58.850Z
Learnt from: CR
Repo: hyperlane-xyz/hyperlane-registry PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-18T23:00:58.850Z
Learning: Applies to src/**/*.ts : Export chain metadata, addresses, and warp route configs in multiple formats: individual chain imports via `hyperlane-xyz/registry/chains/{chainName}`, combined maps (chainMetadata, chainAddresses, warpRouteConfigs), and Registry classes for programmatic access
Applied to files:
.changeset/good-sails-pull.md
📚 Learning: 2025-12-18T23:00:58.850Z
Learnt from: CR
Repo: hyperlane-xyz/hyperlane-registry PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-18T23:00:58.850Z
Learning: Applies to chains/*/{metadata,addresses}.yaml : Chain directories must contain metadata.yaml (chain metadata including chainId, RPC URLs, block explorers, native token), addresses.yaml (deployed contract addresses including mailbox, ISM factories, hooks), and logo.svg (chain logo)
Applied to files:
chains/creatorchaintestnet/addresses.yamlchains/creatorchaintestnet/metadata.yaml
📚 Learning: 2026-01-04T18:42:03.307Z
Learnt from: paulbalaji
Repo: hyperlane-xyz/hyperlane-registry PR: 1312
File: chains/hemi/addresses.yaml:7-7
Timestamp: 2026-01-04T18:42:03.307Z
Learning: In the hyperlane-registry repository, when performing updates to default interchainSecurityModule (ISM) addresses across multiple chains, use multisig batches as the standard approach. This applies to YAML configuration files under the chains directory and should be followed for batch ISM updates to ensure proper authorization, traceability, and consistency across chains.
Applied to files:
chains/creatorchaintestnet/addresses.yamlchains/creatorchaintestnet/metadata.yaml
📚 Learning: 2026-01-04T00:51:28.461Z
Learnt from: paulbalaji
Repo: hyperlane-xyz/hyperlane-registry PR: 1308
File: chains/krown/metadata.yaml:1-21
Timestamp: 2026-01-04T00:51:28.461Z
Learning: In chain metadata YAML files (chains/*/metadata.yaml), omit the blockExplorers field if the chain has no block explorer. Do not include the field or set it to null; this keeps metadata concise and avoids implying non-existent explorers.
Applied to files:
chains/creatorchaintestnet/metadata.yaml
📚 Learning: 2026-01-04T01:15:33.449Z
Learnt from: paulbalaji
Repo: hyperlane-xyz/hyperlane-registry PR: 1310
File: chains/krown/metadata.yaml:19-20
Timestamp: 2026-01-04T01:15:33.449Z
Learning: In chains/krown/metadata.yaml, the RPC URL http://18.134.110.61:8545 using HTTP with an IP address instead of HTTPS with a domain is intentional.
Applied to files:
chains/creatorchaintestnet/metadata.yaml
🔇 Additional comments (4)
.changeset/good-sails-pull.md (1)
1-5: Changeset looks good.The minor version bump is appropriate for adding a new testnet chain to the registry, and the format follows the standard changeset structure.
chains/creatorchaintestnet/metadata.yaml (2)
7-16: Chain metadata configuration looks solid.The chainId and domainId match (278701), the testnet flag is properly set, and the native token configuration is standard for an EVM-compatible chain. The RPC endpoint uses HTTPS, which is the right way to do it.
1-19: logo.svg exists in the chain directory. No action needed.chains/creatorchaintestnet/addresses.yaml (1)
1-13: All contracts are properly deployed on Creator Chain Testnet.The addresses in this file check out—all 13 contracts are live on the chain at their specified locations, and the keys are sorted alphabetically as required. The chain directory's got everything it needs: metadata.yaml, logo.svg, the works. No layered onions here, just a solid registry entry.
- add deployer to creatorchaintestnet metadata - change technical stack to other
- update explorer api url - update explorer name - update explorer family to blockscout to work with custom verifier
2 participants
Description
Backward compatibility
Yes
Testing
Yes
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.