Executed

Requested:

8.00 KSM

#76 Open Governance Test

Proposer:

Paradox

in Treasury

Beneficiary:

(8.00 KSM)

22nd Jan '23

Description

AI Summary

Votes Bubble

Timeline

Evaluation

On Chain Info

Stats

Dear community,

This referendum was opened to test another aspect of OpenGov. I can't divulge the specifics at this point in time as it would introduce a bias. I can however say that the outcome of the vote is inconsequential.

Even with that said I would prefer a successful outcome to continue funding the account used by a public staking payout bot.

For those not familiar with my previous test please view the details here.

Have fun voting.

Regards,

Users are saying...

Based on all comments and replies

Overall 50 % of users are feeling optimistic. Thank you for your dedication and commitment to serving others. Your selflessness is truly admirable, making a positive impact on those around you. We appreciate all that you do!

Overall 50 % of users are feeling neutral. The goal was to manipulate vote levels and delay confirmation for a referendum by reducing support during its decision period. The attempt seemed successful but Al's late voting with substantial KSM disrupted the process, rendering the manipulation irrelevant. Further investigation is planned, and all funds from the failed test were returned to the treasury.

AI-generated from comments

GP7L...po99

22nd Jan '23

Thank-you for your service

Paradox

27th Jan '23

Voted Aye

The goal of this exercise was to trick the system into thinking that the support levels were not maintained thus delaying entry into the confirmation period. My thoughts were that I could do this repeatedly delaying the track and nullifying gov 2 agility. I hoped to achieve this by unvoting / revoting near the end of the decision period.

This appeared to work but I think Al voted with 4000 KSM and that threw things off. I will investigate further and report.

Update:

I attempted to coax the system into returning to a deciding state from a confirming state by altering the levels of support just as the confirmation period began. I anticipated that reduced support would change the global state into thinking that the vote had not attained enough support and thus was not in a sufficient position to be confirmed.

I was discrete with the details because I wanted a regular (smaller) turnout (~16-20k KSM) so that my vote would have a more profound impact on support levels.

Alistair's vote near the end of the decision period increased the support levels to a point that my vote became irrelevant and thus I couldn't test this properly.

Thanks for those who participated and note that funds were returned to the treasury.

Code reference .

Paradox

30th Jan '23

Voted Aye

Please note that in light of the test failing; all funds were returned to the treasury.

Paradox

30th Jan '23

Voted Aye

When a referendum in the decision state reaches the appropriate levels of support and approval it transitions into a state of confirmation. During this time it continues to confirm until it is no longer passing or the confirmation time elapses, after which it passes. If, however, the passing state changes then the referendum re-enters the decision state with some time added.

I attempted to reduce support levels at the very onset of entering the confirmation period to reduce support levels thus making the result of this function return false and reverting the state to deciding.

My tests were inconclusive as I was unable to properly time my execution during the short (10 minute) confirmation time of the Small Tipper track. Additionally, there was a large vote near the end that made my vote (or removal thereof) irrelevant.

Funds received from the referendum were returned to the treasury. I hope to revisit this with a better methodology.

If anyone thinks this is futile, please let me know.

Regards,

Discover similar proposals

#508

KSM

Submitted