Conversation
paulbalaji
reviewed
Feb 25, 2026
paulbalaji
approved these changes
Mar 5, 2026
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded a changeset for a registry minor bump, updated Changes
Estimated Code Review Effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 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}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 15
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.changeset/tender-sloths-bake.md:
- Line 5: Update the release note text that currently reads "Trontestnet" to the
deployed network name "Tronshasta" (replace the string "Trontestnet" with
"Tronshasta"), ensuring capitalization matches existing style and the
surrounding sentence remains grammatically correct; locate the occurrence of
"Trontestnet" in the changeset content and perform the replacement.
In `@chains/arbitrumsepolia/addresses.yaml`:
- Line 6: The interchainSecurityModule address was changed without provenance;
update the addresses YAML by adding a short provenance entry next to the
interchainSecurityModule key that cites the authoritative source (e.g.,
transaction hash, PR number, or other verifiable reference) and a one-line
context note (e.g., "updated via tx 0x... on YYYY-MM-DD" or "added in PR
`#1234`"); ensure the provenance field is clearly named (e.g., provenance or
source) and placed immediately adjacent to the interchainSecurityModule entry so
reviewers can verify the change.
In `@chains/basesepolia/addresses.yaml`:
- Line 6: Update the interchainSecurityModule entry in
chains/basesepolia/addresses.yaml to include provenance details: add a comment
or adjacent field referencing the deployment or batch transaction (e.g., PR
number and/or on‑chain tx hash) that verifies this new address, so the
interchainSecurityModule: "0x0d78C8412dA3135a645Ed531B86A04CB8F491a6b" change is
traceable and follows the chains/**/addresses.yaml guideline.
In `@chains/bsctestnet/addresses.yaml`:
- Line 6: Update the addresses.yaml entry for interchainSecurityModule to
include provenance metadata for the address change: add a provenance field or
inline comment next to interchainSecurityModule listing the deployment or batch
transaction reference (tx hash), PR link, or other source of truth and the date;
ensure the new metadata follows the existing chains/**/addresses.yaml convention
(e.g., provenance: "tx:0x..., pr:`#123`") so reviewers can trace this update.
In `@chains/celosepolia/addresses.yaml`:
- Line 6: Add provenance metadata for the ISM address change by annotating the
interchainSecurityModule entry with its source (e.g., batch transaction hash,
deployment PR number, or other authoritative reference); update the
addresses.yaml so the interchainSecurityModule:
"0x51C44fbBB62C5206B0B9fc1d21Df5bFD9f1bcA2d" line includes a nearby comment or
adjacent provenance field stating the exact tx hash/PR and date and, if
applicable, a short note like "ISM address swap" to satisfy the repository
guideline requiring source breadcrumbs for address changes.
In `@chains/cotitestnet/addresses.yaml`:
- Line 6: Add a provenance annotation for the interchainSecurityModule address
in chains/cotitestnet/addresses.yaml by appending a source comment or metadata
field indicating the transaction hash or PR/batch reference that established
this address; update the interchainSecurityModule entry (the
"interchainSecurityModule" key) to include a provenance line (e.g., source:
"<tx-hash-or-pr-number>") or an inline comment with the tx hash so auditors can
trace the change.
In `@chains/fuji/addresses.yaml`:
- Line 6: The interchainSecurityModule address update for symbol
interchainSecurityModule ("0x1b601775F20054b842249A553CFA166D7FC4256F") lacks
provenance; update chains/fuji/addresses.yaml to include a source reference
(e.g., PR number, transaction hash, block number, or other authoritative
citation) adjacent to this entry—either as a YAML comment or a dedicated field
like source/provenance—so future trace/debug can identify where this address
change originated.
In `@chains/hyperliquidevmtestnet/addresses.yaml`:
- Line 6: Add provenance metadata for the changed interchainSecurityModule
address by recording the source (e.g., PR number, transaction hash, block
number, or authoritative announcement) next to the updated value; update the
addresses.yaml entry for interchainSecurityModule (the key
"interchainSecurityModule" with value
"0x2165f5608d89b0D8516c2368687b89495aE88c22") to include either an adjacent
provenance field (e.g., interchainSecurityModule_provenance: "<tx|PR|source>")
or a YAML comment on the same line with the source details so auditors can trace
the change.
In `@chains/incentivtestnet/addresses.yaml`:
- Line 6: The interchainSecurityModule address update in
chains/incentivtestnet/addresses.yaml is missing provenance; add a source
reference (e.g., tx hash, block, PR number or release note) next to the
interchainSecurityModule entry—either as an inline comment or a new metadata
field (e.g., interchainSecurityModule: "0x..." # source: tx/0x..., or add
provenance: { interchainSecurityModule: "tx/0x..." }) so the change is
traceable; update the entry for interchainSecurityModule accordingly and ensure
the provenance string includes the unique identifier (PR number or transaction
hash) and date.
In `@chains/modetestnet/addresses.yaml`:
- Line 6: The interchainSecurityModule address was changed but lacks provenance;
update the addresses.yaml entry for the interchainSecurityModule key by adding a
source field or inline comment that records the PR number and/or transaction
hash that justified the swap (e.g., "source: PR `#123` / tx 0xabc..."), ensuring
the provenance is adjacent to the interchainSecurityModule: "0x52e09..." entry
so reviewers can trace the change.
In `@chains/optimismsepolia/addresses.yaml`:
- Line 6: Update the interchainSecurityModule entry in
chains/optimismsepolia/addresses.yaml to include provenance information (e.g.,
the transaction hash or PR reference) next to the changed address; locate the
interchainSecurityModule key and append a comment or adjacent field with the
source (tx hash or PR#) and a short descriptor so the change is properly
attributed.
In `@chains/polygonamoy/addresses.yaml`:
- Line 6: The interchainSecurityModule address entry needs a provenance note:
update the addresses.yaml entry for interchainSecurityModule to include the
source of the ISM rotation (e.g., transaction hash, block number, and/or PR
link) either as a YAML comment directly above the interchainSecurityModule line
or as a sibling metadata field (e.g., interchainSecurityModule_source) so the
rotation can be traced; ensure the note mentions the tx hash/batch id and date
and follows the existing chains/**/addresses.yaml comment style.
In `@chains/sepolia/addresses.yaml`:
- Line 6: The addresses.yaml entry for interchainSecurityModule needs provenance
metadata; update the interchainSecurityModule entry to include a source field
(e.g., tx hash, PR number, or batch provenance) explaining where/when the
rotation came from and who authorized it (for example add a sibling key like
"interchainSecurityModule_source" or add a nested map with "address" and
"source") so the change is traceable; ensure the symbol interchainSecurityModule
is annotated with the tx hash or PR reference per the repository's
addresses.yaml conventions.
In `@chains/tronshasta/addresses.yaml`:
- Around line 1-22: The new Tronshasta address set (e.g., aggregationHook,
mailbox, interchainSecurityModule, etc.) lacks provenance; add a concise
provenance note to the addresses.yaml (as per chains/**/addresses.yaml
guidelines) that records the source (deployment tx hash(es), PR number, or
canonical artifact link) and date — either a top-level "provenance" field or a
YAML comment at the top referencing the specific tx hash/PR for these entries so
future readers can trace each contract entry.
In `@chains/tronshasta/metadata.yaml`:
- Around line 29-30: The added top-level field solidityGrpcUrls is not allowed
by the chains/schema.json and breaks validation; remove solidityGrpcUrls and
place its entry under the existing grpcUrls array (e.g. add
"http://grpc.shasta.trongrid.io:50052" as an item in grpcUrls) so the metadata
conforms to the schema, or if you intentionally need a new property, update
chains/schema.json/types in this PR to accept solidityGrpcUrls instead
(preferred: move to grpcUrls).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: bc109140-2707-47fb-9525-9f2d30429941
⛔ Files ignored due to path filters (1)
chains/tronshasta/logo.svgis excluded by!**/*.svg
📒 Files selected for processing (15)
.changeset/tender-sloths-bake.mdchains/arbitrumsepolia/addresses.yamlchains/basesepolia/addresses.yamlchains/bsctestnet/addresses.yamlchains/celosepolia/addresses.yamlchains/cotitestnet/addresses.yamlchains/fuji/addresses.yamlchains/hyperliquidevmtestnet/addresses.yamlchains/incentivtestnet/addresses.yamlchains/modetestnet/addresses.yamlchains/optimismsepolia/addresses.yamlchains/polygonamoy/addresses.yamlchains/sepolia/addresses.yamlchains/tronshasta/addresses.yamlchains/tronshasta/metadata.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Tronshasta deployment:
Corresponding monorepo PR
Backward compatibility
Testing
Summary by CodeRabbit
New Features
Chores