<img src="https://i.ibb.co/5hGp66X3/banner.png" alt="DotShield" width="681" height="227" /> Introducing DotShield, a Web3-native bot designed to improve moderation, verification, and scam prevention in Telegram and Discord communities within the Polkadot and Kusama ecosystem. Currently, existing Telegram bots lack customizable Web3 verification, relying instead on captchas that are easily bypassed. While some Discord bots support Web3 verification, there is no Polkadot-native solution. DotShield solves this problem by enabling dynamic chain state verification, allowing groups to set their own desired criteria, such as balance thresholds and membership conditions, including but not limited to council membership, validator and other on-chain attributes. 
Why This Matters
<ul>
<li>Telegram &amp; Discord groups are primary communication hubs for Web3 communities but suffer from spam, bot invasions, and scam attempts.</li>
<li>Existing bots do not use cryptographic verification for users, meaning scam bots can easily bypass security measures. No Polkadot-native bot exists (or even web3 in general for Telegram that I'm aware of!) that integrates with the ecosystem for seamless verification.</li>
<li>Expanding DotShield ensures better security, community discussions, and fraud prevention across the entire Polkadot ecosystem.</li>
</ul>
&nbsp;
The Story Behind DotShield
I've been a moderator/admin of several Telegram group chats and have been searching for an effective solution to combat spam and bot invasions for years. Existing solutions, such as Rose and Shieldy, rely on traditional Web2 captchas, which are no longer effective. Frustrated with the lack of viable options, I decided to teach myself how to code and build my own solution. After countless all-nighters debugging and researching, I finally created DotShield&mdash;designed specifically to meet the needs of the Polkadot and Kusama ecosystem.
Core Features
<ul>
<li>Dynamic Chain State Verification: Group admins can set criteria based on on-chain balances, governance roles, or other identity markers.</li>
<li>Single Sign-In for Web3 Users: No need to constantly sign transactions; DotShield seamlessly verifies users if they save their wallet as default.</li>
<li>Flexible Moderation: Admins can override verification, allowing them to manually add or remove members.</li>
<li>Scam Prevention &amp; Fraud Mitigation: Dotshield is capable of implementing automated detection, user reporting mechanisms, and external scam database collaboration.</li>
<li>Expansion to Discord: Addresses the lack of a Polkadot-native verification bot for Discord, ensuring Web3 security across both platforms.</li>
</ul>
&nbsp;
Funding Request &amp; Milestone-Based Payment Structure
I am requesting treasury funding to support both the initial deployment and expansion to Discord. Payments will be structured as follows:
<ol>
<li>First Installment &ndash; Covers completed milestones (Telegram bot, core verification, UI, performance upgrades). Total hours: 460</li>
<li>Second Installment &ndash; After successful completion of Discord expansion and verification. Total projected hours: 470</li>
</ol>
Total hours: 930
I am seeking USD$60/hr to cover:
<ul>
<li>Development Server &amp; Infrastructure Costs</li>
<li>Ongoing Maintenance &amp; Feature Requests</li>
<li>Security &amp; Scam Prevention Enhancements</li>
</ul>
 <a href="https://docs.google.com/document/d/1T30qpqw9mudbWZ9Y1Pr-jAs8hNblQiEFlSYhzlmKKeg/edit?usp=sharing">Full Proposal</a> 
Feedback
I&rsquo;d love to hear your thoughts on how DotShield can be improved, whether additional features should be included, or if the funding structure needs adjustment.
Here&rsquo;s a summary of recent user feedback:
<ul>
<li>Average Overall UX Rating: 8.8 / 10</li>
<li>Average UI Satisfaction (DotShield.app): 8.9 / 10</li>
<li>Average Ease of Understanding Instructions: 9.1 / 10</li>
<li>Common Bug Reports: Minimal bugs reported. Some mentioned minor onboarding issues, such as unclear steps for setting up a supergroup. </li>
<li>Comfort Linking Wallets: While some users expressed initial skepticism about connecting wallets (due to common web3 security concerns), many gained confidence thanks to positive community reputation. </li>
<li>Transparency Requests: Users would like clearer communication about how DotShield handles data, including open-sourcing certain elements or publishing technical documentation to build further trust. </li>
<li>Recommendation Likelihood: The majority of respondents would recommend DotShield to others, citing the value in protecting Polkadot ecosystem communities from scams and spam. </li>
<li>Improvement Suggestions:
<ul>
<li>Provide more detailed onboarding guides and user-facing documentation</li>
<li>Increase transparency around wallet connection and data handling</li>
<li>Enhance first-time user experience, especially for non-technical audiences </li>
</ul>
</li>
<li>Polkadot Ecosystem Adoption: Users are highly supportive of DotShield becoming a standard security layer across Telegram and Discord for the Polkadot ecosystem. </li>
<li>Likelihood to share with other community managers: Average score of 8.1 / 10</li>
</ul>
Here are some group chats I&rsquo;ve set up for testing purposes: <a href="https://t.me/DotShieldOfficial">https://t.me/DotShieldOfficial</a> <a href="https://t.me/wndtester">https://t.me/wndtester</a> <a href="https://t.me/Polkadot_Sign_Only">https://t.me/Polkadot_Sign_Only</a>

<img src="https://i.ibb.co/5hGp66X3/banner.png" alt="DotShield" width="681" height="227" /> Introducing DotShield, a Web3-native bot designed to improve moderation, verification, and scam prevention in Telegram and Discord communities within the Polkadot and Kusama ecosystem. Currently, existing Telegram bots lack customizable Web3 verification, relying instead on captchas that are easily bypassed. While some Discord bots support Web3 verification, there is no Polkadot-native solution. DotShield solves this problem by enabling dynamic chain state verification, allowing groups to set their own desired criteria, such as balance thresholds and membership conditions, including but not limited to council membership, validator and other on-chain attributes. 
Why This Matters
<ul>
<li>Telegram &amp; Discord groups are primary communication hubs for Web3 communities but suffer from spam, bot invasions, and scam attempts.</li>
<li>Existing bots do not use cryptographic verification for users, meaning scam bots can easily bypass security measures. No Polkadot-native bot exists (or even web3 in general for Telegram that I'm aware of!) that integrates with the ecosystem for seamless verification.</li>
<li>Expanding DotShield ensures better security, community discussions, and fraud prevention across the entire Polkadot ecosystem.</li>
</ul>
&nbsp;
The Story Behind DotShield
I've been a moderator/admin of several Telegram group chats and have been searching for an effective solution to combat spam and bot invasions for years. Existing solutions, such as Rose and Shieldy, rely on traditional Web2 captchas, which are no longer effective. Frustrated with the lack of viable options, I decided to teach myself how to code and build my own solution. After countless all-nighters debugging and researching, I finally created DotShield&mdash;designed specifically to meet the needs of the Polkadot and Kusama ecosystem.
Core Features
<ul>
<li>Dynamic Chain State Verification: Group admins can set criteria based on on-chain balances, governance roles, or other identity markers.</li>
<li>Single Sign-In for Web3 Users: No need to constantly sign transactions; DotShield seamlessly verifies users if they save their wallet as default.</li>
<li>Flexible Moderation: Admins can override verification, allowing them to manually add or remove members.</li>
<li>Scam Prevention &amp; Fraud Mitigation: Dotshield is capable of implementing automated detection, user reporting mechanisms, and external scam database collaboration.</li>
<li>Expansion to Discord: Addresses the lack of a Polkadot-native verification bot for Discord, ensuring Web3 security across both platforms.</li>
</ul>
&nbsp;
Funding Request &amp; Milestone-Based Payment Structure
I am requesting treasury funding to support both the initial deployment and expansion to Discord. Payments will be structured as follows:
<ol>
<li>First Installment &ndash; Covers completed milestones (Telegram bot, core verification, UI, performance upgrades). Total hours: 460</li>
<li>Second Installment &ndash; After successful completion of Discord expansion and verification. Total projected hours: 470</li>
</ol>
Total hours: 930
I am seeking USD$60/hr to cover:
<ul>
<li>Development Server &amp; Infrastructure Costs</li>
<li>Ongoing Maintenance &amp; Feature Requests</li>
<li>Security &amp; Scam Prevention Enhancements</li>
</ul>
&nbsp;
Feedback
I&rsquo;d love to hear your thoughts on how DotShield can be improved, whether additional features should be included, or if the funding structure needs adjustment.
Here&rsquo;s a summary of recent user feedback:
<ul>
<li>Average Overall UX Rating: 8.8 / 10</li>
<li>Average UI Satisfaction (DotShield.app): 8.9 / 10</li>
<li>Average Ease of Understanding Instructions: 9.1 / 10</li>
<li>Common Bug Reports: Minimal bugs reported. Some mentioned minor onboarding issues, such as unclear steps for setting up a supergroup. </li>
<li>Comfort Linking Wallets: While some users expressed initial skepticism about connecting wallets (due to common web3 security concerns), many gained confidence thanks to positive community reputation. </li>
<li>Transparency Requests: Users would like clearer communication about how DotShield handles data, including open-sourcing certain elements or publishing technical documentation to build further trust. </li>
<li>Recommendation Likelihood: The majority of respondents would recommend DotShield to others, citing the value in protecting Polkadot ecosystem communities from scams and spam. </li>
<li>Improvement Suggestions:
<ul>
<li>Provide more detailed onboarding guides and user-facing documentation</li>
<li>Increase transparency around wallet connection and data handling</li>
<li>Enhance first-time user experience, especially for non-technical audiences </li>
</ul>
</li>
<li>Polkadot Ecosystem Adoption: Users are highly supportive of DotShield becoming a standard security layer across Telegram and Discord for the Polkadot ecosystem. </li>
<li>Likelihood to share with other community managers: Average score of 8.1 / 10</li>
</ul>
Here are some group chats I&rsquo;ve set up for testing purposes: <a href="https://t.me/DotShieldOfficial">https://t.me/DotShieldOfficial</a> <a href="https://t.me/wndtester">https://t.me/wndtester</a> <a href="https://t.me/Polkadot_Sign_Only">https://t.me/Polkadot_Sign_Only</a>

DotShield - Take back control of your community

- Problem Statement: Lack of effective Web3-native bot for moderation and verification in Polkadot and Kusama Telegram and Discord communities.
- Significance: Current bots lack cryptographic verification, leading to spam, bot invasions, and scams, hindering community security.
- Proposed Solution: DotShield offers dynamic chain state verification, single sign-in for Web3 users, flexible moderation, and scam prevention features.
- Expected Outcomes: Enhanced security, improved community discussions, and fraud prevention in the Polkadot ecosystem.

#2660 DotShield - Take back control of your community