Skip to content

Conversation

Riateche
Copy link
Contributor

@Riateche Riateche commented Sep 4, 2025

Summary

  • Add allowed feed IDs to publisher state data.
  • Add feature flags to state. They can be used in the future to alter the aggregator's behavior while keeping it deterministic.
  • Add aggregated data to feed state.
  • Add governance actions for new fields (except aggregated data).

Rationale

Implementing state and governance.

How has this been tested?

  • Current tests cover my changes
  • Added new tests
  • Manually tested the code

@Riateche Riateche requested a review from darunrs as a code owner September 4, 2025 11:49
Copy link

vercel bot commented Sep 4, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
api-reference Ready Ready Preview Comment Sep 4, 2025 2:59pm
component-library Ready Ready Preview Comment Sep 4, 2025 2:59pm
developer-hub Ready Ready Preview Comment Sep 4, 2025 2:59pm
entropy-explorer Ready Ready Preview Comment Sep 4, 2025 2:59pm
insights Ready Ready Preview Comment Sep 4, 2025 2:59pm
proposals Ready Ready Preview Comment Sep 4, 2025 2:59pm
staking Ready Ready Preview Comment Sep 4, 2025 2:59pm

@danimhr
Copy link
Contributor

danimhr commented Sep 4, 2025

@Riateche
I assumed you'll update the version later

// [required] If true, the publisher is active, i.e. it's allowed to publish updates.
optional bool is_active = 4;
// IDs of the feeds for which the publisher's price will be included in the aggregate.
repeated uint32 allowed_feed_ids = 5;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i was wondering which one makes more sense, allowed_feed_ids per publishers or allowed_pub_ids per price feeds?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a symmetric many-to-many relationship, so it's fine in either case. In the memory representation we can also reverse it if needed. Having a property on publisher makes governance actions look more natural.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like line 140 anticipated it being added in Feed, outdated now:
// TODO: list of permissioned publisher IDs.

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.

5 participants