GitBulletin

Repository: farcasterxyz/hub-monorepo

**Snapchain Revolutionizes Data Handling: A Game-Changer for Shuttle Integration!**

2025-04-29 22:20:02 UTC

**Newly Added Fields and Enhanced Event Structures Propel Compatibility and Efficiency in Web3 Ecosystem**

Commit Details:

feat: More Snapchain updates (#2576) ## Why is this change needed? - Add new fields from snapchain to hubble protos and libraries so shuttle can access them - Update shuttle to use getInfo for max fid - Populate data and databytes for convenience (snapchain updated to prioritize dataBytes https://github.com/farcasterxyz/snapchain/pull/454) ## Merge Checklist _Choose all relevant options below by adding an `x` now or at any time before submitting for review_ - [x] PR title adheres to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) standard - [x] PR has a [changeset](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#35-adding-changesets) - [x] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore) - [ ] PR includes [documentation](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#32-writing-docs) if necessary. <!-- start pr-codex --> --- ## PR-Codex overview This PR introduces new fields related to `snapchain` events, enhances compatibility by populating additional data, and modifies existing event structures to include `block_number`, `shard_index`, and `timestamp`. It also updates documentation for clarity. ### Detailed summary - Added `block_number`, `shard_index`, and `timestamp` fields to various stores and event structures. - Introduced `MergeFailureBody` to handle merge failures with `message`, `code`, and `reason`. - Updated comments and documentation to reflect changes in event types. - Enhanced `HubEventArgs` to omit additional fields for better compatibility. - Modified `makeMessageWithSignature` to use `dataBytes` for serialization differences. - Updated event type handling in generated files to include `MERGE_FAILURE`. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->

Search Similar