View All Small Spender

Polkadot OpenGov Voting Observer Twitter Bot

inSmall Spender
2 years ago
treasury
development
bot
marketing
Rejected

Dear Community,

I am thrilled to present the "Polkadot OpenGov Observer" project, We are seeking funding of 200 KSM ($8,730) to support the growth and development of this initiative.

Project Overview:

The Polkadot OpenGov Observer is a tool designed to showcase real-time OpenGov activities on Twitter, providing a comprehensive monthly overview of Polkadot OpenGov Treasury and voters' charts. The primary objective is to enhance community engagement, encourage participation in OpenGov voting, and foster a better understanding of the Polkadot ecosystem.

Beneficiary Information:

  • Beneficiary: Polkadot OpenGov Observer Multisig

  • Image

  • Address:

    DZL1jjADYBhsRY9oJp8ETYtHV64Z4iz97Rvtj8pv2VP1nEN

Requested Amount:

  • 200 KSM ($8,730)

Purpose:

Funding

Mission and Impact:

Our mission is to expand the adoption of Polkadot OpenGov across different communities. By leveraging social platforms like Twitter, where 90% of the web3 ecosystem is active, we aim to make concepts surrounding OpenGov more accessible and engaging.

Currently, only 13.1% of DOT holders participate in governance. We believe that increasing this percentage to 40% will lead to more informed and fair decisions within the Polkadot OpenGov system. Our strategy involves showcasing the activities of voters on Polkadot through the OpenGov Observer, making it a valuable tool for evaluating and choosing the best delegates.

Image

Image

Open Source GitHub Repository

Polkadot OpenGov Observer Github repo

List of Tools and Api's used for Twitter Bot

Subscan Api

polkassembly Api

Node js

Twitter Api

Express

Polkadot Js Api

Coin Gecko Api

Current Stats:

  • Active Voters: 1,868,686.843
  • Referenda Participation: 13.10%

Future Impacts and Plans:

The project is focused on making OpenGov widely used and accessible to everyone. Our implemented features include OpenGov Activity Monitoring, displaying new vote activities in real-time, and providing a monthly overview of OpenGov, voters, and the treasury. This will be instrumental in attracting those interested in OpenGov, whether they are new to the concept or seeking funding for their web3 projects. We aim to build a vibrant and active community of developers within the web3 space.

As we move forward, we will continue to refine and expand our project, ensuring that Polkadot OpenGov becomes a central hub for decentralized decision-making and community involvement.

Thank you for considering our proposal, and we look forward to contributing to the growth and success of the Polkadot ecosystem.

Best regards, Ashutosh Singh (Project Creator and Head, Polkadot OpenGov Observer)

Comments (1)

2 years ago

I honestly don't understand why this is being NAY'd. Maybe people don't want their votes on blast! But that's exactly what we need more of in the ecosystem. People should be held accountable for their votes - if they have on-chain identities then there's no reason to think their votes aren't a public signal.

I have a few technical concerns.

  • I see you're using direct chaindata for timestamps and identities, but you're using secondhand sources on votes. While mostly reliable, using subscan & polkassembly APIs isn't the best practice when tapping into chaindata. Running a local full archive is very expensive but you can always use public RPC endpoints. I'd prefer this approach for your project. I know that complicates things but it's crucial in my opinion.
  • You'll obviously need to maintain this bot. What's your plan for continued support? How can we be sure this persists?
  • Do you plan on supporting referenda on Kusama? Seems like it'd be appropriate since you're asking for funds from the KSM Treasury.
  • One Xeet per vote can get spammy… Would you be open to making threads every hour that contain voting activity for that hour? You could consolidate votes if someone decides to change their vote 1,000 times throughout an hour - you don't want people abusing your bot.
  • It doesn't seem this bot keeps a memory of votes. It would be nice if when someone decided to change their vote the bot say "this person changed their vote to AYE blah blah blah…"
  • How do you intend to address nested calls? For example, how can you be sure to record a vote made from a proxy of a proxy of a proxy of a multisig of a proxy... etc. I know it's an extreme edgecase but it still needs to be addressed.

I think this is worth getting off the ground, so you get an AYE from me. Please let me know your thoughts on my concerns. Thank you!

2 years ago

ChatGPT

@AdamClaySteeber, thanks for voting Aye.

  1. While it's true that using public RPC endpoints is more effective, the implementation can be complicated due to their slower nature. Subscan and Polkassembly APIs are faster, but for real-time updates, we might need the OnFinality premium API, costing around $588 annually.

  2. Annual maintenance is essential, covering Twitter API V2 plan renewal, hosting, and potentially OnFinality API renewal.

  3. We plan to make our bot live on Kusama, with tweets from the same account.

  4. Blocking spammers is a priority. Specific criteria will be established to identify and prevent abuse.

  5. Twitter API currently allows 50 tweets per day. Increasing to 1500 with Twitter API V2 is crucial for project sustainability.

  6. Minimizing tweets can be achieved by creating a database for every vote and implementing scripts.

  7. We initially aimed for a simple vote demonstration, but in response to your request, the new feature will be integrated.

Thanks again for voting Aye, we understand your concern and based on that some major changes will be made in our Twitter Bot.

PleaseLogin to comment

Requested

DOT
20.00K DOT

Proposal Failed

Summary

0%

Aye

AyeNay

0%

Nay

Aye (52)0.0 DOT

Support0.0 DOT

Nay (201)0.0 DOT

    Polkassembly - Referendum #346