Skip to content

Conversation

@LeonardoVieira1630
Copy link
Member

@LeonardoVieira1630 LeonardoVieira1630 commented Jan 22, 2026

The Notification System needs a route the returns votingPower historical variations for all the users of a DAO. On this pr we:

  • add historicalVotingPower route
  • refactor old "historicalVotingPower" to be named as historicalVotingPowerByAccount

@LeonardoVieira1630 LeonardoVieira1630 self-assigned this Jan 22, 2026
@vercel
Copy link

vercel bot commented Jan 22, 2026

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

Project Deployment Review Updated (UTC)
anticapture Ready Ready Preview, Comment Jan 28, 2026 6:20pm
anticapture-storybook Ready Ready Preview, Comment Jan 28, 2026 6:20pm

Request Review

@vercel vercel bot temporarily deployed to Preview – anticapture-storybook January 22, 2026 18:51 Inactive
Copy link
Member

@pikonha pikonha left a comment

Choose a reason for hiding this comment

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

some coments need to fixed and also the conflicts

Base automatically changed from fix/token-holder-balance-history to dev January 28, 2026 14:59
description: "Returns a list of voting power changes.",
tags: ["proposals"],
request: {
query: HistoricalVotingPowerGlobalQuerySchema,
Copy link
Member

Choose a reason for hiding this comment

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

what's the difference between this one and the historicalVotingPowerByAccountId if both receive just an address as an argument?

Copy link
Member Author

Choose a reason for hiding this comment

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

On this one the address is not necessary. I let address as an possible argument, but it is optional. The other one (/voting-power/{address}/historical) needs the address.

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