Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement tspend vote choice selection #3184

Closed
matheusd opened this issue Jan 26, 2021 · 3 comments · Fixed by #3718
Closed

Implement tspend vote choice selection #3184

matheusd opened this issue Jan 26, 2021 · 3 comments · Fixed by #3718

Comments

@matheusd
Copy link
Member

Requires decred/vspd#234

This will be needed once (if) the treasury agenda activates, so that stakeholders can make a choice regarding approving/disapproving tspends.

Ideally, a review of the tspend should be fetched from Politeia so that stakeholders can make an informed choice.

@jholdstock
Copy link
Member

decred/vspd#234 requires decred/dcrwallet#2051

@xaur
Copy link
Contributor

xaur commented Jun 6, 2021

Ideally, a review of the tspend should be fetched from Politeia so that stakeholders can make an informed choice.

I think it should be CMS and not Politeia. Or Politeia could cache it to not have CMS bombarded by wallet requests. But in any case CMS is the data source I think.

In any case, the bigger problem with the "informed choice" part is that there is almost no infrastructure to serve that data. Afaik, at the current stage the only goal was to "decentralize custody" without providing any information what stakeholders are voting on. Since the very proposal 2 years ago and to this date I've seen no backend changes, UI mockups, or even discussions on how it should work.

With that in mind, I think this issue should be focused on exposing tspend vote choices, and a new one should be created for the getting informed part where stakeholders could learn what they're voting on.

@xaur
Copy link
Contributor

xaur commented May 15, 2022

"What is being voted on" partially covered by #3762.

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 a pull request may close this issue.

3 participants