<p>Polkassembly is an integral part of Polkadex governance. It is dedicated to fostering transparent governance and active participation within the Polkadex ecosystem. The team is excited to announce its application to become a registrar on Polkadex after our registrar application and success on Polkadot. Please refer to this tweet for details on our <a href="https://twitter.com/polk_gov/status/1735702644965122179">Polkadot Registrar Statistics</a>.</p>
<p>&nbsp;</p>
<p><strong>Why are identity verifications important?</strong></p>
<ul>
<li>&mdash; On-chain identities in the Polkadot ecosystem are crucial for trust, accountability, and interoperability. An on-chain identity fosters a reliable and verifiable framework for participants within the Polkadex ecosystem. It enables seamless integration and collaboration between different projects and stakeholders.</li>
<li>&mdash; It also builds accountability as the participants are vetted and there are multiple points of contact for an individual/team. Hence, when requesting funds or proposing changes, the network and its resources have an additional layer of protection via the verification process.</li>
<li>&mdash; The goal of setting an on-chain identity is to enhance transparency, security, and the overall ease of interaction between the participants of the Polkadex ecosystem.</li>
<li>&nbsp;</li>
</ul>
<p><strong>Problems in current on chain identity system</strong></p>
<ul>
<li>&mdash; The current process for verifying the identity is extremely fragmented</li>
<li>&mdash; The process requires a heavy reliance on navigating through PolkadotJS, which can be overwhelming to those who are new to the ecosystem</li>
<li>&mdash; The process is also broken away from the governance and proposal creation interface, which makes it difficult for a lot of the community as they need to adapt to multiple tools for serving different use cases.</li>
<li>&nbsp;</li>
</ul>
<p><strong>Objective for Registrar Application</strong></p>
<ul>
<li>&mdash; The primary objective of creating the registrar application is to build an easy and integrated governance experience for all users within Polkassembly.</li>
<li>&mdash; This involves building for automation of proposal creation, addition of education nudges on proposal evaluation, verification of on chain identities and comprehensive user level profiling with leaderboards and gamification for governance participants</li>
<li>&mdash; Taking the onus for ensuring verification of users and building security for funds requested from treasury As mentioned in our Polkadot Proposal, which went live earlier this year</li>
<li>&mdash; The time required for identity registration and verification will be reduced by more than 75%, enhancing the adoption of the feature and enabling a more robust and secure treasury management.</li>
<li>&mdash; The number 75% was deduced by using the average time difference between the two methods for 3 unique users</li>
<li>&mdash; The time required by the earlier method was 20-25 mins, and via Polkassembly will be approximately 5 mins</li>
<li>&nbsp;</li>
</ul>
<p><strong>How will Polkassemby enable users to apply for on chain identity verification? </strong></p>
<p>&nbsp;</p>
<p>Attached below is a step wise explanation of how Polkassembly plans to receive and process on chain delegations</p>
<p><strong>Step 1 - </strong></p>
<p>&mdash; Discovery on on chain identity setup</p>
<p>&mdash; Users will be provided with contextual nudges on Polkassembly for setting up on chain identity</p>
<p><img src="https://i.ibb.co/CnNt3bY/Screenshot-2023-12-16-at-2-30-30-PM-1.png" alt="" width="640" height="353" /></p>
<p><strong>Step 2 - </strong></p>
<p>&mdash; Educating users on what is on-chain identity and why is it important</p>
<p>&mdash; Explaining the process of setting up and on chain identity and how verification works</p>
<p>&mdash; Helping users understand how to identify users with a valid on chain identity</p>
<p>&mdash; Clear communication on the total amount required (Please note the amount mentioned is representative and may vary based on market conditions)</p>
<p>&mdash; The breakdown of the feed will also be provided</p>
<p><img src="https://i.ibb.co/fMm8cGB/image-47.png" alt="" width="640" height="613" /></p>
<p><strong>Step 3 -</strong></p>
<p>&mdash; Providing the user with an interface to share all their social and contact information</p>
<p>&mdash; The user will be allowed to choose any one of their address which they want to verify &mdash; They can choose their legal and display name</p>
<p>&mdash; They can identify their social handles for further communication with the community</p>
<p>&mdash; They are informed about the bond, which is mandatory while setting up an on chain identity</p>
<p>&mdash; They are also informed about the fees charged for setting up or changing the social handles, which will be the fee per handle * # of handles being verified</p>
<p><img src="https://i.ibb.co/Fx4Tn9C/image-48.png" alt="" width="640" height="617" /></p>
<p><strong>Step 4 -</strong></p>
<p>&mdash; Confirming the fees and initiating the step by step identity verification process</p>
<p>&mdash; Each social handle will need to be independently verified after the input is provided</p>
<p>&mdash; Once all verifications are completed the success states will be provided</p>
<p><img src="https://i.ibb.co/fvtTJJ4/image-49.png" alt="" width="640" height="295" /></p>
<p><img src="https://i.ibb.co/bs4kKXR/image-51.png" alt="" width="563" height="640" /></p>
<p>&nbsp;</p>
<p>Other detailed steps and complete proposal can be found <a href="https://docs.google.com/document/d/1wYkC09wMjC6KstW2E9VtHLgoRd1bV_GLhYoTOQ8gv8U/edit">here</a>. We look forward to feedback from the community, suggestions to improve the product flow and support on our efforts to challenge the complex UX challenges of the Kusama ecosystem.Stats regarding our performance and details can be found in our latest tweet <a href="https://twitter.com/polk_gov/status/1735702644965122179">here</a></p>
<p>Regards, Polkassembly Team</p>

<p>Polkassembly is an integral part of Polkadex governance. It is dedicated to fostering transparent governance and active participation within the Polkadex ecosystem. The team is excited to announce its application to become a registrar on Polkadex after our registrar application and success on Polkadot. Please refer to this tweet for details on our <a href="https://twitter.com/polk_gov/status/1735702644965122179">Polkadot Registrar Statistics</a>. Why are identity verifications important?</p>
<p>&mdash; On-chain identities in the Polkadot ecosystem are crucial for trust, accountability, and interoperability. An on-chain identity fosters a reliable and verifiable framework for participants within the Polkadex ecosystem. It enables seamless integration and collaboration between different projects and stakeholders.</p>
<p>&mdash; It also builds accountability as the participants are vetted and there are multiple points of contact for an individual/team. Hence, when requesting funds or proposing changes, the network and its resources have an additional layer of protection via the verification process.</p>
<p>&mdash; The goal of setting an on-chain identity is to enhance transparency, security, and the overall ease of interaction between the participants of the Polkadex ecosystem. Problems in current on chain identity system</p>
<p>&mdash; The current process for verifying the identity is extremely fragmented &mdash; The process requires a heavy reliance on navigating through PolkadotJS, which can be overwhelming to those who are new to the ecosystem</p>
<p>&mdash; The process is also broken away from the governance and proposal creation interface, which makes it difficult for a lot of the community as they need to adapt to multiple tools for serving different use cases. Objective for Registrar Application</p>
<p>&mdash; The primary objective of creating the registrar application is to build an easy and integrated governance experience for all users within Polkassembly.</p>
<p>&mdash; This involves building for automation of proposal creation, addition of education nudges on proposal evaluation, verification of on chain identities and comprehensive user level profiling with leaderboards and gamification for governance participants</p>
<p>&mdash; Taking the onus for ensuring verification of users and building security for funds requested from treasury As mentioned in our Polkadot Proposal, which went live earlier this year</p>
<p>&mdash; The time required for identity registration and verification will be reduced by more than 75%, enhancing the adoption of the feature and enabling a more robust and secure treasury management.</p>
<p>&mdash; The number 75% was deduced by using the average time difference between the two methods for 3 unique users</p>
<p>&mdash; The time required by the earlier method was 20-25 mins, and via Polkassembly will be approximately 5 mins How will Polkassemby enable users to apply for on chain identity verification? Attached below is a step wise explanation of how Polkassembly plans to receive and process on chain delegations</p>
<p><strong>Step 1 - </strong></p>
<p>&mdash; Discovery on on chain identity setup</p>
<p>&mdash; Users will be provided with contextual nudges on Polkassembly for setting up on chain identity</p>
<p><img src="https://i.ibb.co/CnNt3bY/Screenshot-2023-12-16-at-2-30-30-PM-1.png" alt="" width="640" height="353" /></p>
<p><strong>Step 2 - </strong></p>
<p>&mdash; Educating users on what is on-chain identity and why is it important</p>
<p>&mdash; Explaining the process of setting up and on chain identity and how verification works</p>
<p>&mdash; Helping users understand how to identify users with a valid on chain identity</p>
<p>&mdash; Clear communication on the total amount required (Please note the amount mentioned is representative and may vary based on market conditions)</p>
<p>&mdash; The breakdown of the feed will also be provided</p>
<p><img src="https://i.ibb.co/fMm8cGB/image-47.png" alt="" width="640" height="613" /></p>
<p>Step 3 -</p>
<p>&mdash; Providing the user with an interface to share all their social and contact information</p>
<p>&mdash; The user will be allowed to choose any one of their address which they want to verify &mdash; They can choose their legal and display name</p>
<p>&mdash; They can identify their social handles for further communication with the community</p>
<p>&mdash; They are informed about the bond, which is mandatory while setting up an on chain identity</p>
<p>&mdash; They are also informed about the fees charged for setting up or changing the social handles, which will be the fee per handle * # of handles being verified</p>
<p><img src="https://i.ibb.co/Fx4Tn9C/image-48.png" alt="" width="640" height="617" /></p>
<p>Step 4 -</p>
<p>&mdash; Confirming the fees and initiating the step by step identity verification process</p>
<p>&mdash; Each social handle will need to be independently verified after the input is provided</p>
<p>&mdash; Once all verifications are completed the success states will be provided</p>
<p><img src="https://i.ibb.co/fvtTJJ4/image-49.png" alt="" width="640" height="295" /></p>
<p><img src="https://i.ibb.co/bs4kKXR/image-51.png" alt="" width="563" height="640" /></p>
<p>Other detailed steps and complete proposal can be found <a href="https://docs.google.com/document/d/1wYkC09wMjC6KstW2E9VtHLgoRd1bV_GLhYoTOQ8gv8U/edit">here</a>. We look forward to feedback from the community, suggestions to improve the product flow and support on our efforts to challenge the complex UX challenges of the Kusama ecosystem.Stats regarding our performance and details can be found in our latest tweet <a href="https://twitter.com/polk_gov/status/1735702644965122179">here</a></p>
<p>Regards, Polkassembly Team</p>

Polkassembly Registrar Application for Polkadex

Polkassembly is an integral part of Polkadex governance. It is dedicated to fostering transparent governance and active participation within the Polkadex ecosystem. The team is excited to announce its application to become a registrar on Polkadex after our registrar application and success on Polkadot. Please refer to this tweet for details on our [Polkadot Registrar Statistics](https://twitter.com/polk_gov/status/1735702644965122179).
Why are identity verifications important?

— On-chain identities in the Polkadot ecosystem are crucial for trust, accountability, and interoperability. An on-chain identity fosters a reliable and verifiable framework for participants within the Polkadex ecosystem. It enables seamless integration and collaboration between different projects and stakeholders.
— It also builds accountability as the participants are vetted and there are multiple points of contact for an individual/team. Hence, when requesting funds or proposing changes, the network and its resources have an additional layer of protection via the verification process.
— The goal of setting an on-chain identity is to enhance transparency, security, and the overall ease of interaction between the participants of the Polkadex ecosystem.
Problems in current on chain identity system
— The current process for verifying the identity is extremely fragmented
— The process requires a heavy reliance on navigating through PolkadotJS, which can be overwhelming to those who are new to the ecosystem
— The process is also broken away from the governance and proposal creation interface, which makes it difficult for a lot of the community as they need to adapt to multiple tools for serving different use cases.
Objective for Registrar Application
— The primary objective of creating the registrar application is to build an easy and integrated governance experience for all users within Polkassembly.
— This involves building for automation of proposal creation, addition of education nudges on proposal evaluation, verification of on chain identities and comprehensive user level profiling with leaderboards and gamification for governance participants
— Taking the onus for ensuring verification of users and building security for funds requested from treasury
As mentioned in our Polkadot Proposal, which went live earlier this year
— The time required for identity registration and verification will be reduced by more than 75%, enhancing the adoption of the feature and enabling a more robust and secure treasury management.
— The number 75% was deduced by using the average time difference between the two methods for 3 unique users
— The time required by the earlier method was 20-25 mins, and via Polkassembly will be approximately 5 mins
How will Polkassemby enable users to apply for on chain identity verification?
Attached below is a step wise explanation of how Polkassembly plans to receive and process on chain delegations

Step 1 -
— Discovery on on chain identity setup
— Users will be provided with contextual nudges on Polkassembly for setting up on chain identity
Step 2 -
— Educating users on what is on-chain identity and why is it important
— Explaining the process of setting up and on chain identity and how verification works
— Helping users understand how to identify users with a valid on chain identity
— Clear communication on the total amount required (Please note the amount mentioned is representative and may vary based on market conditions)
— The breakdown of the feed will also be provided
Step 3 -
— Providing the user with an interface to share all their social and contact information
— The user will be allowed to choose any one of their address which they want to verify
— They can choose their legal and display name
— They can identify their social handles for further communication with the community
— They are informed about the bond, which is mandatory while setting up an on chain identity
— They are also informed about the fees charged for setting up or changing the social handles, which will be the fee per handle * # of handles being verified
Step 4 -
— Confirming the fees and initiating the step by step identity verification process
— Each social handle will need to be independently verified after the input is provided
— Once all verifications are completed the success states will be provided

Other detailed steps and complete proposal can be found [here](https://docs.google.com/document/d/1wYkC09wMjC6KstW2E9VtHLgoRd1bV_GLhYoTOQ8gv8U/edit). We look forward to feedback from the community, suggestions to improve the product flow and support on our efforts to challenge the complex UX challenges of the Kusama ecosystem.Stats regarding our performance and details can be found in our latest tweet [here](https://twitter.com/polk_gov/status/1735702644965122179)

Regards,
Polkassembly Team





<div class="c-message_kit__blocks c-message_kit__blocks--rich_text" style="box-sizing: inherit; max-width: none; margin-bottom: 4px; font-family: Slack-Lato, Slack-Fractions, appleLogo, sans-serif; font-size: 15px; font-style: normal; font-variant-ligatures: common-ligatures; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background- text-decoration-thickness: initial; text-decoration-style: initial;">
<div class="c-message__message_blocks c-message__message_blocks--rich_text" style="box-sizing: inherit; max-width: none; overflow-wrap: break-word;" data-qa="message-text">
<div class="p-block_kit_renderer" style="box-sizing: inherit; width: 454px;" data-qa="block-kit-renderer">
<div class="p-block_kit_renderer__block_wrapper p-block_kit_renderer__block_wrapper--first" style="box-sizing: inherit; display: flex;">
<div class="p-rich_text_block" dir="auto" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0; user-select: text; text-align: left; width: 454px; overflow-y: hidden; font-size: 15px; line-height: 1.46668;">
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">Polkassembly is an integral part of&nbsp;<strong style="box-sizing: inherit;" data-stringify-type="bold">Polkadex</strong> governance. It is dedicated to fostering transparent governance and active participation within the Polkadex ecosystem. The team is excited to announce its application to become a registrar on Polkadex <strong style="box-sizing: inherit;" data-stringify-type="bold">after our registrar application and success on Polkadot.&nbsp;</strong>Please refer to this tweet for details on our&nbsp;<a class="c-link" style="box-sizing: inherit; text-decoration: none;" href="https://twitter.com/polk_gov/status/1735702644965122179" target="_blank" rel="noopener noreferrer" data-stringify-link="https://twitter.com/polk_gov/status/1735702644965122179" data-sk="tooltip_parent">Polkadot Registrar Statistics</a>.Why are identity verifications important?</div>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;"><br style="box-sizing: inherit;" />&mdash; On-chain identities in the Polkadot ecosystem are crucial for trust, accountability, and interoperability. An on-chain identity fosters a reliable and verifiable framework for participants within the Polkadex ecosystem. It enables seamless integration and collaboration between different projects and stakeholders.<br style="box-sizing: inherit;" />&mdash; It also builds accountability as the participants are vetted and there are multiple points of contact for an individual/team. Hence, when requesting funds or proposing changes, the network and its resources have an additional layer of protection via the verification process.<br style="box-sizing: inherit;" />&mdash; The goal of setting an on-chain identity is to enhance transparency, security, and the overall ease of interaction between the participants of the Polkadex ecosystem.Problems in current on chain identity system</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The current process for verifying the identity is extremely fragmented</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The process requires a heavy reliance on navigating through PolkadotJS, which can be overwhelming to those who are new to the ecosystem</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The process is also broken away from the governance and proposal creation interface, which makes it difficult for a lot of the community as they need to adapt to multiple tools for serving different use cases.</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;"><strong style="box-sizing: inherit;" data-stringify-type="bold">Objective for Registrar Application</strong></div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The primary objective of creating the registrar application is to build an easy and integrated governance experience for all users within Polkassembly.</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; This involves building for automation of proposal creation, addition of education nudges on proposal evaluation, verification of on chain identities and comprehensive user level profiling with leaderboards and gamification for governance participants</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Taking the onus for ensuring verification of users and building security for funds requested from treasury</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">As mentioned in our Polkadot Proposal, which went live earlier this year</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The time required for identity registration and verification will be reduced by more than 75%, enhancing the adoption of the feature and enabling a more robust and secure treasury management.</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The number 75% was deduced by using the average time difference between the two methods for 3 unique users</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The time required by the earlier method was 20-25 mins, and via Polkassembly will be approximately 5 mins</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;"><strong style="box-sizing: inherit;" data-stringify-type="bold">How will Polkassemby enable users to apply for on chain identity verification?</strong><br style="box-sizing: inherit;" />Attached below is a step wise explanation of how Polkassembly plans to receive and process on chain delegations<br style="box-sizing: inherit;" />Step 1 -</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Discovery on on chain identity setup</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Users will be provided with contextual nudges on Polkassembly for setting up on chain identity</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">Step 2 -</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Educating users on what is on-chain identity and why is it important</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Explaining the process of setting up and on chain identity and how verification works</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Helping users understand how to identify users with a valid on chain identity</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Clear communication on the total amount required (Please note the amount mentioned is representative and may vary based on market conditions)</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The breakdown of the feed will also be provided</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">Step 3 -</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Providing the user with an interface to share all their social and contact information</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The user will be allowed to choose any one of their address which they want to verify</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; They can choose their legal and display name</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; They can identify their social handles for further communication with the community</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; They are informed about the bond, which is mandatory while setting up an on chain identity</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; They are also informed about the fees charged for setting up or changing the social handles, which will be the fee per handle * # of handles being verified</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">Step 4 -</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Confirming the fees and initiating the step by step identity verification process</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Each social handle will need to be independently verified after the input is provided</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Once all verifications are completed the success states will be provided</li>
</ul>
<p>&nbsp;</p>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">Other detailed steps and complete proposal can be found&nbsp;<a class="c-link" style="box-sizing: inherit; text-decoration: none;" href="https://docs.google.com/document/d/1wYkC09wMjC6KstW2E9VtHLgoRd1bV_GLhYoTOQ8gv8U/edit" target="_blank" rel="noopener noreferrer" data-stringify-link="https://docs.google.com/document/d/1wYkC09wMjC6KstW2E9VtHLgoRd1bV_GLhYoTOQ8gv8U/edit" data-sk="tooltip_parent">here</a>. We look forward to feedback from the community, suggestions to improve the product flow and support on our efforts to challenge the complex UX challenges of the Kusama ecosystem.Stats regarding our performance and details can be found in our latest tweet&nbsp;<a class="c-link" style="box-sizing: inherit; text-decoration: none;" href="https://twitter.com/polk_gov/status/1735702644965122179" target="_blank" rel="noopener noreferrer" data-stringify-link="https://twitter.com/polk_gov/status/1735702644965122179" data-sk="tooltip_parent">here</a><br /><br />Regards,<br style="box-sizing: inherit;" />Polkassembly Team</div>
</div>
</div>
</div>
</div>
</div>
<div class="c-message_kit__attachments" style="box-sizing: inherit; max-width: 600px; font-family: Slack-Lato, Slack-Fractions, appleLogo, sans-serif; font-size: 15px; font-style: normal; font-variant-ligatures: common-ligatures; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background- text-decoration-thickness: initial; text-decoration-style: initial;">
<div class="c-message_attachment" style="box-sizing: inherit; align-items: stretch; max-width: 600px; margin: 0px 0px 8px; display: flex; position: relative;">
<div class="c-message_attachment__delete_container" style="box-sizing: inherit; width: 20px; position: absolute; top: 0px; bottom: 0px; left: -20px;">&nbsp;</div>
</div>
</div>

<div class="c-message_kit__blocks c-message_kit__blocks--rich_text" style="box-sizing: inherit; max-width: none; margin-bottom: 4px; font-family: Slack-Lato, Slack-Fractions, appleLogo, sans-serif; font-size: 15px; font-style: normal; font-variant-ligatures: common-ligatures; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background- text-decoration-thickness: initial; text-decoration-style: initial;">
<div class="c-message__message_blocks c-message__message_blocks--rich_text" style="box-sizing: inherit; max-width: none; overflow-wrap: break-word;" data-qa="message-text">
<div class="p-block_kit_renderer" style="box-sizing: inherit; width: 454px;" data-qa="block-kit-renderer">
<div class="p-block_kit_renderer__block_wrapper p-block_kit_renderer__block_wrapper--first" style="box-sizing: inherit; display: flex;">
<div class="p-rich_text_block" dir="auto" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0; user-select: text; text-align: left; width: 454px; overflow-y: hidden; font-size: 15px; line-height: 1.46668;">
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">Polkassembly is an integral part of&nbsp;<strong style="box-sizing: inherit;" data-stringify-type="bold">Polkadex</strong>&nbsp;governance. It is dedicated to fostering transparent governance and active participation within the Polkadex ecosystem. The team is excited to announce its application to become a registrar on Polkadex&nbsp;<strong style="box-sizing: inherit;" data-stringify-type="bold">after our registrar application and success on Polkadot.&nbsp;</strong>Please refer to this tweet for details on our&nbsp;<a class="c-link" style="box-sizing: inherit; text-decoration: none;" href="https://twitter.com/polk_gov/status/1735702644965122179" target="_blank" rel="noopener noreferrer" data-stringify-link="https://twitter.com/polk_gov/status/1735702644965122179" data-sk="tooltip_parent">Polkadot Registrar Statistics</a>.Why are identity verifications important?</div>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;"><br style="box-sizing: inherit;" />&mdash; On-chain identities in the Polkadot ecosystem are crucial for trust, accountability, and interoperability. An on-chain identity fosters a reliable and verifiable framework for participants within the Polkadex ecosystem. It enables seamless integration and collaboration between different projects and stakeholders.<br style="box-sizing: inherit;" />&mdash; It also builds accountability as the participants are vetted and there are multiple points of contact for an individual/team. Hence, when requesting funds or proposing changes, the network and its resources have an additional layer of protection via the verification process.<br style="box-sizing: inherit;" />&mdash; The goal of setting an on-chain identity is to enhance transparency, security, and the overall ease of interaction between the participants of the Polkadex ecosystem.Problems in current on chain identity system</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The current process for verifying the identity is extremely fragmented</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The process requires a heavy reliance on navigating through PolkadotJS, which can be overwhelming to those who are new to the ecosystem</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The process is also broken away from the governance and proposal creation interface, which makes it difficult for a lot of the community as they need to adapt to multiple tools for serving different use cases.</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;"><strong style="box-sizing: inherit;" data-stringify-type="bold">Objective for Registrar Application</strong></div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The primary objective of creating the registrar application is to build an easy and integrated governance experience for all users within Polkassembly.</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; This involves building for automation of proposal creation, addition of education nudges on proposal evaluation, verification of on chain identities and comprehensive user level profiling with leaderboards and gamification for governance participants</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Taking the onus for ensuring verification of users and building security for funds requested from treasury</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">As mentioned in our Polkadot Proposal, which went live earlier this year</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The time required for identity registration and verification will be reduced by more than 75%, enhancing the adoption of the feature and enabling a more robust and secure treasury management.</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The number 75% was deduced by using the average time difference between the two methods for 3 unique users</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The time required by the earlier method was 20-25 mins, and via Polkassembly will be approximately 5 mins</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;"><strong style="box-sizing: inherit;" data-stringify-type="bold">How will Polkassemby enable users to apply for on chain identity verification?</strong><br style="box-sizing: inherit;" />Attached below is a step wise explanation of how Polkassembly plans to receive and process on chain delegations<br style="box-sizing: inherit;" />Step 1 -</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Discovery on on chain identity setup</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Users will be provided with contextual nudges on Polkassembly for setting up on chain identity</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">Step 2 -</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Educating users on what is on-chain identity and why is it important</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Explaining the process of setting up and on chain identity and how verification works</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Helping users understand how to identify users with a valid on chain identity</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Clear communication on the total amount required (Please note the amount mentioned is representative and may vary based on market conditions)</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The breakdown of the feed will also be provided</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">Step 3 -</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Providing the user with an interface to share all their social and contact information</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; The user will be allowed to choose any one of their address which they want to verify</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; They can choose their legal and display name</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; They can identify their social handles for further communication with the community</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; They are informed about the bond, which is mandatory while setting up an on chain identity</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; They are also informed about the fees charged for setting up or changing the social handles, which will be the fee per handle * # of handles being verified</li>
</ul>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">Step 4 -</div>
<ul class="p-rich_text_list p-rich_text_list__bullet" style="box-sizing: inherit; margin: 0px; padding: 0px; list-style-type: none;" data-stringify-type="unordered-list" data-indent="0" data-border="0">
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Confirming the fees and initiating the step by step identity verification process</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Each social handle will need to be independently verified after the input is provided</li>
<li style="box-sizing: inherit; margin-bottom: 0px; margin-left: 28px; list-style-type: none;" data-stringify-indent="0" data-stringify-border="0">&mdash; Once all verifications are completed the success states will be provided</li>
</ul>
<p>&nbsp;</p>
<div class="p-rich_text_section" style="box-sizing: inherit; counter-reset: list-0 0 list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0;">Other detailed steps and complete proposal can be found&nbsp;<a class="c-link" style="box-sizing: inherit; text-decoration: none;" href="https://docs.google.com/document/d/1wYkC09wMjC6KstW2E9VtHLgoRd1bV_GLhYoTOQ8gv8U/edit" target="_blank" rel="noopener noreferrer" data-stringify-link="https://docs.google.com/document/d/1wYkC09wMjC6KstW2E9VtHLgoRd1bV_GLhYoTOQ8gv8U/edit" data-sk="tooltip_parent">here</a>. We look forward to feedback from the community, suggestions to improve the product flow and support on our efforts to challenge the complex UX challenges of the Kusama ecosystem.Stats regarding our performance and details can be found in our latest tweet&nbsp;<a class="c-link" style="box-sizing: inherit; text-decoration: none;" href="https://twitter.com/polk_gov/status/1735702644965122179" target="_blank" rel="noopener noreferrer" data-stringify-link="https://twitter.com/polk_gov/status/1735702644965122179" data-sk="tooltip_parent">here</a>Regards,<br style="box-sizing: inherit;" />Polkassembly Team</div>
</div>
</div>
</div>
</div>
</div>
<div class="c-message_kit__attachments" style="box-sizing: inherit; max-width: 600px; font-family: Slack-Lato, Slack-Fractions, appleLogo, sans-serif; font-size: 15px; font-style: normal; font-variant-ligatures: common-ligatures; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background- text-decoration-thickness: initial; text-decoration-style: initial;">
<div class="c-message_attachment" style="box-sizing: inherit; align-items: stretch; max-width: 600px; margin: 0px 0px 8px; display: flex; position: relative;">
<div class="c-message_attachment__delete_container" style="box-sizing: inherit; width: 20px; position: absolute; top: 0px; bottom: 0px; left: -20px;">&nbsp;</div>
</div>
</div>

<p>Polkassembly is an integral part of Polkadex governance. It is dedicated to fostering transparent governance and active participation within the Polkadex ecosystem. The team is excited to announce its application to become a registrar on Polkadex after our registrar application and success on Polkadot. Please refer to this tweet for details on our <a href="https://twitter.com/polk_gov/status/1735702644965122179">Polkadot Registrar Statistics</a>.</p>
<p>&nbsp;</p>
<p><strong>Why are identity verifications important?</strong></p>
<ul>
<li>&mdash; On-chain identities in the Polkadot ecosystem are crucial for trust, accountability, and interoperability. An on-chain identity fosters a reliable and verifiable framework for participants within the Polkadex ecosystem. It enables seamless integration and collaboration between different projects and stakeholders.</li>
<li>&mdash; It also builds accountability as the participants are vetted and there are multiple points of contact for an individual/team. Hence, when requesting funds or proposing changes, the network and its resources have an additional layer of protection via the verification process.</li>
<li>&mdash; The goal of setting an on-chain identity is to enhance transparency, security, and the overall ease of interaction between the participants of the Polkadex ecosystem.</li>
<li>&nbsp;</li>
</ul>
<p><strong>Problems in current on chain identity system</strong></p>
<ul>
<li>&mdash; The current process for verifying the identity is extremely fragmented</li>
<li>&mdash; The process requires a heavy reliance on navigating through PolkadotJS, which can be overwhelming to those who are new to the ecosystem</li>
<li>&mdash; The process is also broken away from the governance and proposal creation interface, which makes it difficult for a lot of the community as they need to adapt to multiple tools for serving different use cases.</li>
<li>&nbsp;</li>
</ul>
<p><strong>Objective for Registrar Application</strong></p>
<ul>
<li>&mdash; The primary objective of creating the registrar application is to build an easy and integrated governance experience for all users within Polkassembly.</li>
<li>&mdash; This involves building for automation of proposal creation, addition of education nudges on proposal evaluation, verification of on chain identities and comprehensive user level profiling with leaderboards and gamification for governance participants</li>
<li>&mdash; Taking the onus for ensuring verification of users and building security for funds requested from treasury As mentioned in our Polkadot Proposal, which went live earlier this year</li>
<li>&mdash; The time required for identity registration and verification will be reduced by more than 75%, enhancing the adoption of the feature and enabling a more robust and secure treasury management.</li>
<li>&mdash; The number 75% was deduced by using the average time difference between the two methods for 3 unique users</li>
<li>&mdash; The time required by the earlier method was 20-25 mins, and via Polkassembly will be approximately 5 mins</li>
<li>&nbsp;</li>
</ul>
<p><strong>How will Polkassemby enable users to apply for on chain identity verification? </strong></p>
<p>&nbsp;</p>
<p>Attached below is a step wise explanation of how Polkassembly plans to receive and process on chain delegations</p>
<p><strong>Step 1 - </strong></p>
<p>&mdash; Discovery on on chain identity setup</p>
<p>&mdash; Users will be provided with contextual nudges on Polkassembly for setting up on chain identity</p>
<p><img src="https://i.ibb.co/CnNt3bY/Screenshot-2023-12-16-at-2-30-30-PM-1.png" alt="" width="640" height="353" /></p>
<p><strong>Step 2 - </strong></p>
<p>&mdash; Educating users on what is on-chain identity and why is it important</p>
<p>&mdash; Explaining the process of setting up and on chain identity and how verification works</p>
<p>&mdash; Helping users understand how to identify users with a valid on chain identity</p>
<p>&mdash; Clear communication on the total amount required (Please note the amount mentioned is representative and may vary based on market conditions)</p>
<p>&mdash; The breakdown of the feed will also be provided</p>
<p><img src="https://i.ibb.co/fMm8cGB/image-47.png" alt="" width="640" height="613" /></p>
<p><strong>Step 3 -</strong></p>
<p>&mdash; Providing the user with an interface to share all their social and contact information</p>
<p>&mdash; The user will be allowed to choose any one of their address which they want to verify &mdash; They can choose their legal and display name</p>
<p>&mdash; They can identify their social handles for further communication with the community</p>
<p>&mdash; They are informed about the bond, which is mandatory while setting up an on chain identity</p>
<p>&mdash; They are also informed about the fees charged for setting up or changing the social handles, which will be the fee per handle * # of handles being verified</p>
<p><img src="https://i.ibb.co/Fx4Tn9C/image-48.png" alt="" width="640" height="617" /></p>
<p><strong>Step 4 -</strong></p>
<p>&mdash; Confirming the fees and initiating the step by step identity verification process</p>
<p>&mdash; Each social handle will need to be independently verified after the input is provided</p>
<p>&mdash; Once all verifications are completed the success states will be provided</p>
<p><img src="https://i.ibb.co/fvtTJJ4/image-49.png" alt="" width="640" height="295" /></p>
<p><img src="https://i.ibb.co/bs4kKXR/image-51.png" alt="" width="563" height="640" /></p>
<p>&nbsp;</p>
<p>Other detailed steps and complete proposal can be found <a href="https://docs.google.com/document/d/1B4xP7A4X9wtOAA6eJpdmWLmhjrzMMJCW2xg-lpwd96Q/edit?usp=sharing">here</a>. We look forward to feedback from the community, suggestions to improve the product flow and support on our efforts to challenge the complex UX challenges of the Kusama ecosystem.Stats regarding our performance and details can be found in our latest tweet <a href="https://twitter.com/polk_gov/status/1735702644965122179">here</a></p>
<p>Regards, Polkassembly Team</p>

Problem Statement:
- The current process for verifying on-chain identities in the Polkadot ecosystem is fragmented, overwhelming, and disconnected from the governance and proposal creation interface.

Significance:
- On-chain identities are important for trust, accountability, and interoperability within the Polkadex ecosystem.
- An integrated and user-friendly identity verification process will enhance transparency, security, and ease of interaction among participants.

Proposed Solution:
- Create a registrar application on Polkassembly to streamline the identity verification process and provide an easy and integrated governance experience.
- Automate proposal creation, add education nudges on proposal evaluation, and implement comprehensive user profiling with leaderboards and gamification.
- Take responsibility for verifying users and building security for funds requested from the treasury.

Expected Outcomes:
- Reduce the time required for identity registration and verification by more than 75%.
- Enhance adoption of on-chain identities and enable more robust and secure treasury management.

#2387 Polkassembly Registrar Application for Polkadex

No Active Proposals