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

Balance is shown as active even though it isn't counted as active in the court #340

Open
john-light opened this issue May 20, 2020 · 2 comments · May be fixed by #355
Open

Balance is shown as active even though it isn't counted as active in the court #340

john-light opened this issue May 20, 2020 · 2 comments · May be fixed by #355

Comments

@john-light
Copy link
Contributor

In the following screenshot, my active balance is shown as 10,000,000 ANJ (on the usability test network) and my drafting odds are shown as <1 in 100+ cases even though with an active balance of 10 million ANJ my odds should really be like 1 in 2 cases.

Screenshot_2020-05-20 Aragon Court Dashboard(1)

I was told that this is probably because the court will not recognize my balance as actually being active until the next term after I activated my tokens begins. And sure enough, once the next term began my odds shown changed.

Screenshot_2020-05-20 Aragon Court Dashboard(16)

I think to prevent confusion about this we should indicate some "pending activation" state that will change to "activated" once the next term begins.

@fabriziovigevani
Copy link
Contributor

Ah yes good catch.

Maybe we could change pending activation to effective on next term or something around that? The reason i ask this is because the amount is actually active (meaning that you can deactivate the full amount on the same term you activated it) even though it won't be taken into account for drafting.

@john-light
Copy link
Contributor Author

⏳ 10,000,000 ANJ Effective next term could be a good option

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.

2 participants