This proposal was changed due to a runtime upgrade. Check proposal [#36](https://moonbeam.polkassembly.network/referendum/36)

Polkadotters proposes a comprehensive plan to increase awareness and engagement within the Polkadot ecosystem. Their strategy includes regular content creation, event organization, community engagement, and infrastructure support. Initiatives like weekly news updates, governance news, and Polkadot meetups are prioritized, alongside Twitter spaces, AMAs and Zealy quests. The team seeks funding for 12 months to support their activities and commits to provide regular reports on their progress.

Publish 120 articles related to Polkadot on PolkaWorld Wechat Official Account.

Interview 6 team members from Polkadot eco-projects.

Host 3 meetups with at least 50 participants joining the face-to-face meetup.

Host 6 online broadcasts:3 for the parachain ecosystem/Crowdloans/dapp topic with 3 Polkadot ecosystem teams and 3 for Q&A from the community.

Add 6 new live broadcasts, with 3 broadcasts in each series.

Add 3 larger online live broadcasts.

Create 12 English education videos with both English and Chinese subtitles.

Interview 6 parachains or eco-projects and edit into full videos to help the community learn about parachains that have won the slot auctions and projects built with the Polkadot tech stack.

Send a batch of dispatch calls and atomically execute them.
The whole transaction will rollback and fail if any of the calls failed.

May be called from any origin.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then call are dispatch without checking origin filter. (This includes
bypassing `frame_system::Config::BaseCallFilter`).

# <weight>
- Complexity: O(C) where C is the number of calls to be batched.
# </weight>

- There was a proposal that got changed because of an upgrade.
- You can check the details of the proposal by clicking on the link.
- The proposal number is 36.
- The change happened because of a runtime upgrade.
- The proposal is about something called Polkassembly Referendum.

#35 Set Polkadot TransactInfo and Register Lido

No Active Proposals