Skip to content

feat: add chain context to SchemaDeployment message for v1.0.4#6

Merged
cyberstorm-daemon merged 2 commits intomainfrom
fix/chain-id
Sep 13, 2025
Merged

feat: add chain context to SchemaDeployment message for v1.0.4#6
cyberstorm-daemon merged 2 commits intomainfrom
fix/chain-id

Conversation

@cyberstorm-daemon
Copy link
Member

Summary

Adds essential chain context fields to the message to enable proper multi-chain support.

Changes

  • Add field (uint64): EVM chain ID for programmatic identification (e.g., 1 = Ethereum mainnet, 137 = Polygon)
  • Add field (string): Human-readable chain name for display purposes

Problem Solved

Previously, message processors receiving information had no way to determine:

  • Which blockchain the deployment was on
  • How to route deployments to the correct chain
  • How to validate deployments against expected chain context

Impact

  • ✅ Enables proper multi-chain deployment tracking
  • ✅ Allows message processors to route deployments correctly
  • ✅ Provides both programmatic (chain_id) and human-readable (chain_name) chain identification
  • ✅ Maintains backward compatibility (new fields are optional)

Version

This change corresponds to the v1.0.4 release.

Proto Changes

Test Plan

  • Proto file validates successfully
  • Generated clients compile without errors
  • Backward compatibility maintained
  • Documentation reflects new fields

- Add chain_id field (uint64) for EVM chain identification
- Add chain_name field (string) for human-readable chain names
- Enables message processors to properly route and validate deployments across multiple chains
@cyberstorm-daemon cyberstorm-daemon merged commit 2b203a6 into main Sep 13, 2025
1 check passed
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