Skip to content

Monitor governance referendas on Polkadot/Kusama - Create a thread for each referenda for internal users to discuss before proxy account makes the vote.

License

Notifications You must be signed in to change notification settings

ChaosDAO-org/InternalGov-2.0

Repository files navigation

ChaosDAO Governance bot

GitHub License GitHub commits since latest release

A dedicated discussion forum within your Discord server, specifically designed to facilitate thoughtful and constructive conversations around ongoing proposals. This interactive platform empowers members to openly share their insights, perspectives, and opinions on each referendum prior to the submission of an official vote by the designated proxy account on behalf of the collective or DAO.

The primary objective of this forum is to foster an environment of collaboration and informed decision-making, ensuring that every voice within the community is acknowledged and taken into consideration. By harnessing the collective wisdom of your community, you can make well-informed decisions that truly represent the best interests of the entire group.

We encourage everyone to actively participate in these discussions, as your input and feedback are invaluable in shaping the direction and outcomes of your collectives endeavors. Together, we can forge a stronger, more unified community that thrives on the principles of transparency, cooperation, and shared vision.

alt text


Initial setup

IMAGE ALT TEXT HERE

This file should be renamed from .env.sample -> .env


Installing prerequisite libraries / tooling

cd InternalGov-2.0
pip3 install -r requirements.txt
Installing PM2 (Process Manager)
PM2 is a daemon process manager that will help you manage and keep your application/bot online 24/7

npm install pm2 -g

Daemonize the bot to run 24/7 with PM2
cd InternalGov-2.0/bot/
pm2 start main.py --name ksmgov2 --interpreter python3
pm2 save

Autonomous voting

alt text

When the bot votes is dictated by /data/vote_periods. Each origin of a proposal has its own setting on when the first vote should be made & second. A second vote will only be made if the result differs from the first vote. If the first vote is AYE and it remains AYE on the second period then no vote will be made on the network.
Polkadot vote periods
Kusama vote periods

vote settings

Kusama vote periods
Role Decision Period (days) Internal Vote Period (days) Revote Period (days)
Root 14 5 10
WhitelistedCaller 14 3 10
StakingAdmin 14 5 10
Treasurer 14 5 10
LeaseAdmin 14 5 10
FellowshipAdmin 14 5 10
GeneralAdmin 14 5 10
AuctionAdmin 14 5 10
ReferendumCanceller 7 2 4
ReferendumKiller 14 2 10
SmallTipper 7 1 4
BigTipper 7 1 4
SmallSpender 14 5 10
MediumSpender 14 5 10
BigSpender 14 5 10
WishForChange 14 5 10

Example:

A proposal is submitted with its origin designated as 'Treasurer'. Following a period of five days after its on-chain introduction, a vote is conducted in accordance with the predetermined internal outcome. Should there be a shift in the voting stance from 'AYE' to 'NAY', a subsequent vote will be executed on the tenth day of the proposal's on-chain presence. In instances where the initial decision remains unaltered and the proposal has aged ten days or more, no further on-chain voting action will be undertaken.


Polkadot vote periods
Role Decision Period (days) Internal Vote Period (days) Revote Period (days)
Root 28 7 20
WhitelistedCaller 28 2 20
StakingAdmin 28 7 20
Treasurer 28 7 20
LeaseAdmin 28 7 20
FellowshipAdmin 28 7 20
GeneralAdmin 28 7 20
AuctionAdmin 28 7 20
ReferendumCanceller 7 2 4
ReferendumKiller 28 4 20
SmallTipper 7 2 4
BigTipper 7 2 4
SmallSpender 28 7 20
MediumSpender 28 7 20
BigSpender 28 7 20
WishForChange 28 7 20

Example:

A proposal is submitted with its origin designated as 'AuctionAdmin'. Following a period of seven days after its on-chain introduction, a vote is conducted in accordance with the predetermined internal outcome. Should there be a shift in the voting stance from 'AYE' to 'NAY', a subsequent vote will be executed on the twentieth day of the proposal's on-chain presence. In instances where the initial decision remains unaltered and the proposal has aged ten days or more, no further on-chain voting action will be undertaken.


Support

For assistance or inquiries, please refer to the following official channels of communication:

Platform User UID/URL
Telegram n4droj Telegram
Discord n4dro Discord
Twitter n4dro Twitter

About

Monitor governance referendas on Polkadot/Kusama - Create a thread for each referenda for internal users to discuss before proxy account makes the vote.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages