We present the latest Polkadot Treasury Report, concluding the year 2023\. This report shows the Polkadot Treasury has spent DOT in 2023 and prior and breaks spending up into categories and subcategories to give a detailed look into how the Polkadot DAO is investing in research, development, operations, outreach, and HR.

This report will give an overview of 2023 spending, and then dig down into analysis by quarters and by categories to give the reader a solid understanding of Polkadot’s past priorities. We express our gratitude to the Web3 Foundation for funding this report as part of the [OpenGov.Watch](http://OpenGov.Watch) initiative.

## Key Insights

* Spending grew from 12m USD in 2022 to 34m USD in 2023.
* Top spending categories in 2023 are: development (48%), outreach (24%), HR (14%), and operations (11%).
* 2023-Q4 saw a sharp spending increase with 15m USD being spent.
* In Q4, 2.45m USD was paid out more than originally proposed due to DOTUSD price volatility in the market uptrend.
* The Polkadot Treasury has now spent 48 million USD over its lifetime.

## 2023 - The year of OpenGov

In 2023, Polkadot Governance transitioned to full token-holder governance, called Open Governance (OpenGov). Since July 2023, all spending decisions were made collectively by all token holders, without any intermediary bodies. Together with this transformation, the ecosystem discovered an increased need to remain competitive with other ecosystems and increased its spending by 3x compared to 2022\. 33.5m USD (6.2m DOT) were spent in 2023.

![](https://ipfs.subsocial.network/ipfs/bafybeietwm36sostbw7g62m2zr5hu33nkiqmrdwrbwlma3fq3pwiblusqm)

### Categories

For this report, we have chosen the main categories of *Development*, *Outreach*, *HR, Operations,* and *Research*. Some additional costs are covered as *Other*.

* **Development** primarily covers any kind of software development that is funded
* **Outreach** covers all social activities and media productions, advertising, and business development.
* **HR** consists of anything that upskills people in the ecosystem, like hackathons, academies, recruiting, and incubation.
* **Operations** include software and hardware costs incurred to operate the network and auxiliary services like explorers.
* **Research** covers original research, reports, and analytics

![](https://ipfs.subsocial.network/ipfs/bafybeihz3cavqjeui4i4vair6zmqqzje2v6elqslu3654ljy4hvnmq5f5y)

In 2023, software development of wallets, bridges, SDKs, and more made up almost half of the spending. Outreach activities like marketing, advertising, and business development made up a quarter, and the last quarter is composed of HR, operations, and research.

### Top 10 spends

Looking at the top individual spends, we see Snowbridge (2.7m USD), the Polkadot Blockchain Academy (1.2m USD), Polkadot at Coindesk Consensus (925k USD), Ledger Apps (918k USD), and KAGOME (898k USD)

![](https://ipfs.subsocial.network/ipfs/bafybeiahchnd5wlzh4insdqcdbpx63q5ecizxp3t5zk4hord4sqzx6nj2i)

### Treasury Balance

Overall, Polkadot started the year with 42.7m DOT and ended with 43.8m DOT, keeping a balance between inflows and outflows.

![](https://ipfs.subsocial.network/ipfs/bafybeibhowi6uhbzgc5ew5kmiwutcyrp27irghcg6sod2dyncvhazffa3m)

## 2023 by the quarters

Looking at a quarterly analysis, we see that 3 of 4 quarters in 2023 surpassed any of the previous quarters in the history of the Treasury. The last quarter of 2023 saw a marked increase in spending: Almost 15m USD (2.7m DOT) were spent.

![](https://ipfs.subsocial.network/ipfs/bafybeibsu2akfew2xknzuz3kou7fyw623q2hyaw5ffqdvxrlcmfa3b2vwm)

### Quarters by Categories

Zooming in, we can see that Development and Outreach are an ongoing priority for the Treasury, while other cost factors are more irregular.

![](https://ipfs.subsocial.network/ipfs/bafybeickjgvm4onlqr3vclreslpavzqygeeljmgf2czqi2bmxic2jrq4j4)

The quarter saw increased spending in each category, but also more overall weight on Outreach, HR, and Operations thanks to a few already anticipated heavy hitters at the end of the year.

![](https://ipfs.subsocial.network/ipfs/bafybeihz3cavqjeui4i4vair6zmqqzje2v6elqslu3654ljy4hvnmq5f5y)![](https://ipfs.subsocial.network/ipfs/bafybeiekclwj4556tt6y5qmrdfpks7gdfwxyhtnhxa7pxwqwbrmsx475ai)

### Volatility leads to overpaying

Volatile market conditions with a general uptrend in the DOTUSD exchange rate have led to the eventual USD values being significantly above the originally proposed values. Since the Treasury pays out in DOT but many participants denominate in USD, this creates a contrast.

On aggregate, the difference between the proposed time and payout time has led to 2.45m being in total “overpaid”. Compared to a total spend of 14.6m USD in that quarter, on aggregate the Treasury has paid out 17% more in USD than was originally requested. In the most extreme cases, the USD-denominated value at payout day was 45% above the requested amount.

![](https://ipfs.subsocial.network/ipfs/bafybeidx7dlgpqq6iyuvkhw4uwawt7dydpmssroilgbzrvhcdanc4yvqoi)

## A deep dive into categories

![](https://ipfs.subsocial.network/ipfs/bafybeifbwicoejpffscwqk6qhxyuyjnkvsnunswd4mqyvdqd7noehe52hm)

Let’s look into the different categories.

### Development

Development cost 16m USD (3m DOT). Most development efforts went into wallets (5.4m USD), bridging (3m USD), Substrate implementations and tooling (2m USD), and SDKs (920k). A range of other development categories have been supported too.

![](https://ipfs.subsocial.network/ipfs/bafybeifzzfwkvxywnvchecvdl6ii6ea4rgsuau5ga4ottgzciwqg3bcjg4)

### Outreach

8.1m USD (1.4m DOT) have been spent on outreach. The biggest positions were media production and distribution (2.9m USD), conference hosting (2.1m USD) and conference attendance (1.3m USD), and various community-building efforts (820k USD)

![](https://ipfs.subsocial.network/ipfs/bafybeifodakznumuv3djuvk2sa2phbw63q2fxp37kadz4bgonl72bcyywu)

### HR

HR took 4.8m USD (930k DOT). Of those, most went to the Polkadot Blockchain Academy and hackathons (4.4m USD). Other components included recruiting (177k USD), incubation (140k), and other educational activities (48k USD).

![](https://ipfs.subsocial.network/ipfs/bafybeib6rojga52kkonuzfxsytcphuwbnfcncbzek22hjiu76rlieyooqi)

### Operations

Keeping the network running has cost 3.6m USD (640k DOT). Indexing (1.2m USD) and explorers (800k USD) took the biggest portion, and even Governance tools (508k USD) came before RPCs and nodes (436k USD)

![](https://ipfs.subsocial.network/ipfs/bafybeigj6uu5mcjtn65j7vzifyypipbtvex2g2q4bqu6r6igzepe6oqvuy)

### Research

Various small research projects together were paid 576k USD (100k DOT)

![](https://ipfs.subsocial.network/ipfs/bafybeig66zvivdqetechqslwr32qlzqygstqkc24feq5jy4lxb7m345ozu)

# Closing Remarks

This report shows that Polkadot achieved a balance of inflows and outflows in 2023 with 33m USD deployed into the ecosystem, while the general spending trend is going up. 2024-Q1 looks like it almost matches the spending of the full 2023 and we look forward to further explore this in the next report.

# Notes

* The raw data for this report can be found in the following places:  
   * Google Sheet with pivot tables and charts: [Sheet](https://docs.google.com/spreadsheets/d/1HLo%5FMdSDMcNXk6Q7fc7pQFansyGJJN3r/edit#gid=626441615)  
   * Github: [Report](https://github.com/OpenGov-Watch/data/blob/a205987fbb81bef7c78cbba396f798dd31101d5c/2023-polkadot-treasury-spends.xlsx)
* Missing data and future work: This proposal only considers direct spends. The data is incomplete and skewed in some ways:  
   * Bounties are not yet considered  
   * Sometimes proposers refund money, which is not necessarily reflected in the data (example: Ref 140)  
   * Some referenda are loans (e.g. Bifrost liquid staking loans), which are repaid later. This is also not reflected.  
   * Accounting for the Multi-Asset Treasury: This is not yet an issue in the current report, but the Treasury is becoming a Multi-Asset Treasury. So swaps from DOT into USDT and USDC are not really spends, as they keep the value as active assets in the Treasury
* Propose date vs. execution date vs. payout date  
   * The [previous Report](https://forum.polkadot.network/t/polkadot-treasury-report-2023-q3/4333) took the propose date as the point of reference. This current report has focused on the payout date to better reflect the USD value at payout time. Traditional accounting practices might alternatively suggest to consider the execution date as point of reference. This needs to be further considered in the future.
* Category Changes  
   * Introduce Outreach-Advertising  
   * Introduce HR  
         * Move Outreach-Training/Hackathons to HR-Training/Hackathons  
         * Move Outreach-Education to HR-Education  
         * Introduce HR-Recruiting  
         * Introduce HR-Incubation  
   * Outreach→Media & Outreach split into  
         * Outreach→Media  
         * Outreach→Local Outreach
* Other Notes  
   * Proposals often are composed of work packages that would have to be designated to different categories. We designate categories by the primary intention of the proposal. A hackathon that also publishes content and markets the hackathon is still primarily a hackathon.  
   * The keyword “maintenance” doesn’t strictly indicate a category. If a Python library (Development → SDKs) is maintained, it is still a development effort. It doesn’t become operations. Thus typically the word “maintenance” should be ignored when determining the category.  
   * SmallTipper proposals by the bot are attributed to Development→Polkadot SDK
* Polkassembly API  
   * We worked with the Polkassembly API to fetch our date. While generally reliable, we discovered a few hurdles along the way. Fetching data from the Treasury primitive is missing a DOT value and a reference to the original referendum. This can be confirmed by checking Treasury endpoints in the Polkassembly frontend, which do not leave breadcrumbs to the original proposal. This creates situations were the DOT value is not retrievable and available to us for further processing. Logically Polkassembly should be able to support this, as it those traits are available in the Subsquare UI.  
   * A referendum can also be missing the DOT value if more than one spend\_local call is included in the extrinsic (e.g. Ref 288)

We present the latest Polkadot Treasury Report, concluding the year 2023. This report shows the Polkadot Treasury has spent DOT in 2023 and prior and breaks spending up into categories and subcategories to give a detailed look into how the Polkadot DAO is investing in research, development...

Polkadot Treasury Report - 2023

[Watch the Recording](https://www.youtube.com/watch?v=zSKiAE7fBPI)

## Fellowship Updates[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#fellowship-updates)

* New Members  
   * Collective #81 [philoniare to Dan 1](https://collectives.polkassembly.io/referenda/81)  
   * Collective #82 [Ermal Galeci to Dan 1](https://collectives.polkassembly.io/referenda/82)
* New Dashboard <https://polkadot-fellows.github.io/dashboard/#/members>
* Accepted RFCs  
   * [RFC-13 Prepare Core runtime API for MBMs](https://polkadot-fellows.github.io/RFCs/approved/0013-prepare-blockbuilder-and-core-runtime-apis-for-mbms.html)  
   * [RFC-0045: Lowering NFT Deposits on Asset Hub](https://polkadot-fellows.github.io/RFCs/approved/0045-nft-deposits-asset-hub.html#rfc-0045-lowering-nft-deposits-on-asset-hub)  
   * [RFC-0078: Merkleized Metadata](https://polkadot-fellows.github.io/RFCs/approved/0078-merkleized-metadata.html)  
 \* superseded [RFC-46](https://github.com/polkadot-fellows/RFCs/pull/46)  
\* Needed for Ledger, Polkadot Vault, and Kampela signers  
\* Will roll out in 1.3
* New Element channel for public consultation with the Tech Fellowship - <https://app.element.io/#/room/#fellowship-open-channel:parity.io>

## Hot Topics[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#hot-topics)

### JAM & Polkadot 2.0 Roadmap[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#jam--polkadot-20-roadmap)

* JAM is a candidate design, it is not Polkadot 2.0
* We clarified the project dependencies to make JAM a reality  
   * [Alice und Bob summary doc](https://hackmd.io/@alice-und-bob/polkadot2)  
   * [Alice und Bob project tracking sheet](https://docs.google.com/spreadsheets/d/1YjeKrCjiQHu6szxHdMhR6fHywRT-w0cxou5Ep-UpJFQ/edit#gid=836474213)

#### Questions[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#questions)

* Oliver: How can we ensure we get different client implementations  
   * Gavin sees two important things: Having a clear spec. And having proper incentives for different implementations
* Bryan: Ways for devs to participate in development?  
   * Gavin: There will be a fund for developers that are helping to build it

#### ISMP as candidate implementation for XCMP[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#ismp-as-candidate-implementation-for-xcmp)

* Seun presented ISMP as a potential implementation of XCMP
* Gavin wasn’t against it :)

### Snowbridge[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#snowbridge)

* Vincent from Snowbridge presented the problem of having to set the DOTETH exchange rate regularly in the BridgeHub storage to properly calculate weights for Ethereum transactions.
* Gavin suggested that users have to obtain wrapped ETH to pay for transactions. This way we could avoid complicating designs.

## Collectives[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#collectives)

### Technical Fellowship[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#technical-fellowship)

#### Release Cadence[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#release-cadence)

* QA and release tempo were discussed.
* Bryan presented a proposal for a [standard release checklist](https://github.com/polkadot-fellows/runtimes/issues/140#issuecomment-1920399473)
* Basti mentioned that writing a QA bounty could be very helpful

#### Fellowship Secretary[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#fellowship-secretary)

Basti proposed to hire a Fellowship secretary: <https://github.com/polkadot-fellows/help-center/issues/8>

#### Salaries[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#salaries)

* Salaries were accidentally 12\_000\_000 times the intended amount. Payouts luckily capped out at some defined limits.
* Bryan wrote a script to fix it: [Link](https://collectives.subsquare.io/fellowship/referenda/84)
* Three users got paid out too much and [refunded the excess amount](https://assethub-polkadot.subscan.io/account/13w7NdvSR1Af8xsQTArDtZmVvjE8XhWNdL4yed3iFHrUNCnS?tab=transfer)

## Roadmap[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#roadmap)

### Polkadot SDK[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#polkadot-sdk)

* The latest version during the call was [v1.8.0](https://github.com/paritytech/polkadot-sdk/releases/tag/polkadot-v1.8.0)
* The latest version as of writing this summary is [v1.9.0](https://github.com/paritytech/polkadot-sdk/releases/tag/polkadot-v1.9.0)

### Polkadot Runtime[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#polkadot-runtime)

* 1.1.3 was released as bugfix release  
   * Controllers Stashes, Staking, Staking Ledgers may get corrupted  
   * recover corrupted accounts
* [1.2](https://github.com/polkadot-fellows/runtimes/issues/140) \- based on Polkadot SDK 1.7  
   * state trie migration  
   * BridgeHub: Add Snowbridge to Kusama and Polkadot runtimes  
   * Encointer: update encounter runtime to 6.1  
   * Coretime  
 \* refund leases that have not started #206  
\* cancel auctions on coretime launch #215  
\* add the Kusama Coretime Chain runtime #212  
   * Peoplechain  
   * [Async Backing Phase 1 on Kusama](https://github.com/polkadot-fellows/runtimes/pull/228)
* [1.3](https://github.com/polkadot-fellows/runtimes/issues/186)  
   * Coretime on Polkadot  
 \* on-demand coretime → governance config  
   * Async Backing on Polkadot and Kusama
* coretime chain end of june on polkadot
* Elastic Scaling is on the way, and internal testnet

### XCM[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#xcm)

* XCM v4 is just a renaming release, it is removing the “Multi-” in Multilocation and Multiasset
* Bryan: [Improve XCM development and release process](https://forum.polkadot.network/t/improve-xcm-development-and-release-process/6497)
* It is suggested that all parachains test their XCM functionality on Rococo/Paseo

## Collectives[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#collectives-1)

### Unbrick Collective[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#unbrick-collective)

Chains can brick and need fast recovery. Bryan is proposing an Unbrick Collective

<https://hackmd.io/zmBeWsX8Tki0APQieq9dTQ?view>

## Coretime[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#coretime)

### Agile Coretime[​](http://localhost:3000/technical%5Ffellowship/2024-03-19-opendev-call#agile-coretime)

* [Async Backing Phase 1 on Kusama](https://github.com/polkadot-fellows/runtimes/pull/228)

Watch the Recording

Fellowship Updates​

New Members

Collective #81 philoniare to Dan 1

Collective #82 Ermal Galeci to Dan 1

New Dashboard https://polkadot-fellows.github.io/dashboard/#/members

Accepted RFCs

RFC-13 Prepare Core runtime API for MBMs

RFC-0045: Lowering NFT Deposits on Asset...

2024-03-19 Technical Fellowship OpenDev Call

**Today we are releasing the OpenGov Scraper**

If you are a regular watcher of Polkadot Governance, this is for you! It's a small Jupyter Notebook (Python script) that helps you to fetch the 100 latest proposals into an Excel file. (no coding skills necessary)

![](https://ipfs.subsocial.network/ipfs/bafybeicm76zohnsfwu62bot4qryxcdkbismina3lakgwekt3ignn5dbr5m)

The data is fetched from the Polkassembly API. The script conveniently adds the current USD value (or the USD value at the time of execution if that already happened)

The notebook comes with instructions and should be usable for you even if you don't have coding skills but a Google account.

![Image](https://pbs.twimg.com/media/GHVpFOeXYAAXjW4?format=jpg&name=medium)![](https://ipfs.subsocial.network/ipfs/bafybeidt3uuz3v7m6z5oyc44zexuhlq7zjm7hf2b22u46davznzfx5ye5y)

This is only the first prototype, and we will keep iterating on the OpenGov Scraper. We are especially looking for feedback on how to develop this further. We plan to develop the scraper into a state where we can provide an always-updated Google spreadsheet of the ongoing Governance proceedings.

Check out the Notebook here: <https://colab.research.google.com/drive/1Rwu8Xw2k6EsxtVc%5Ff6rEQYL1CBqTqc5Y#scrollTo=cWk-rOIwcez5>

Git repo: <https://github.com/OpenGov-Watch/opengov-scraper>

Today we are releasing the OpenGov Scraper

If you are a regular watcher of Polkadot Governance, this is for you! It's a small Jupyter Notebook (Python script) that helps you to fetch the 100 latest proposals into an Excel file. (no coding skills necessary)



The data is fetched from the...

OpenGov Scraper

OpenGov.Watch

OpenGov.Watch develops governance operations and culture in the Polkadot ecosystem. We provide regular reports and pioneer initiatives to help governance participants to stay informed, find consensus, and coordinate on projects.

Video: [https://www.youtube.com/watch?v=War1weBu7yU 2](https://www.youtube.com/watch?v=War1weBu7yU)

# Fellowship

* New Members  
   * [clangenb to rank 1 2](https://collectives.subsquare.io/fellowship/referenda/94)  
   * [pandres95 to rank 1 1](https://collectives.subsquare.io/fellowship/referenda/105)
* [New process for submitting evidence](https://github.com/polkadot-fellows/Evidences) for Fellowship members by Basti  
   * Members are also now submitting first requests for promotions. The first one is to [promote Oliver (ggwpez) to rank 3 1](https://collectives.subsquare.io/fellowship/referenda/115)  
   * Promotions for higher ranks will be an in-person event, in August or September
* Accepted RFCs  
   * [RFC 48 - Generate ownership proof for SessionKeys 1](https://github.com/polkadot-fellows/RFCs/pull/48)  
         * This will ensure that SessionKeys submission cannot be censored
* The Fellowship Secretary was accepted. The Fellowship is now also getting to work to build a [secretary collective 1](https://github.com/polkadot-fellows/help-center/issues/10)
* Salaries can be tracked here: [Subsquare | Collectives Fellowship Salary 1](https://collectives.subsquare.io/fellowship/salary)

# Celebrations

## Coretime - Andrei

* The first sale just happened on Kusama. The Fellowship sees a few minor issues to be improved: Andrei reports PR for changing pricing, missing impl for revenue information, fix some on-demand events
* No information on the call for on-demand coretime sales. Donal can answer about on-demand

## People Chain - Joe

Launched on Kusama. Deposits are now \~0.06 KSM. Identities no longer sit on the relay chain. UIs have to adapt and show identities from the new chain.

## BridgeHub - Adrian

### Snowbridge

* [Launched](https://polkadot.subsquare.io/referenda/680)
* [but got stuck](https://github.com/polkadot-fellows/runtimes/pull/313). The Polkadot side didn’t understand a message from the Ethereum side and stopped as a safety precaution.
* Fix is part of 1.2.4
* Example UI: [https://rococo-app.snowbridge.network/ 3](https://rococo-app.snowbridge.network/)

### P<>K

* [Launched](https://forum.polkadot.network/t/polkadot-kusama-bridge/2971/25)
* [but got stuck](https://forum.polkadot.network/t/polkadot-kusama-bridge/2971/45). An unexpected edge case in the collator set change of Kusama has led Polkadot to no longer accept messages.
* Fix was part of 1.2.2
* Adrian also mentioned the [Asset transfer API 1](https://github.com/paritytech/asset-transfer-api), saying the typescript wrappers are very useful

## Async Backing

* [Async backing is live](https://polkadot.subsquare.io/referenda/688)  
   * Discussing the rollout of async backing to system chains, Someone gave a briefing, mentioning that it is coming to People Chain first. ([Github](https://github.com/polkadot-fellows/runtimes/pull/266#issuecomment-2071906386))

# Roadmap

## Latest Release: 1.2.4 - Joe

* [Version 1.2.4 got tagged](https://github.com/polkadot-fellows/runtimes/issues/288) and is submitted to Kusama for approval
* [Ambassador Program](https://www.google.com/url?q=https://github.com/polkadot-fellows/runtimes/pull/291&sa=D&source=editors&ust=1716381183055319&usg=AOvVaw0S7Be7ATjXXQ6JpznPb1mT) is part of the release (only for Polkadot)
* [Drop ED Requirement for Transaction Payment with Exchangeable Asset #310](https://github.com/polkadot-fellows/runtimes/pull/310) allows users to transfer the entire balance of an asset (e.g. USDT) to another account. This was for example requested by Binance.
* [kusama chains: allow arbitrary XCM execution #261](https://github.com/polkadot-fellows/runtimes/pull/261)  
   * e.g. to make an asset transfer that is chain-agnostic  
   * one example is to make an XCM currency transfer, even within a chain
* [Allow Sending XCM messages using a Signed origin on Kusama #290](https://github.com/polkadot-fellows/runtimes/pull/290)  
   * this now allows anyone to run an XCM program, as requested by [Kreivo 1](https://forum.polkadot.network/t/opengov-for-everyone-1-ksm-1-dao/7781)
* While discussing XCM, we got on a tangent about XCQ  
   * [It now has a proof-of-concept built on PolkaVM](https://forum.polkadot.network/t/cross-consensus-query-language-xcq/7583/10)  
   * Gavin: PolkaVM is soon in a state where it could reasonably be deployed on Kusama
* And another tangent: There is a [proposal on Kusama to request 10m DOT from Polkadot 1](https://kusama.subsquare.io/referenda/399)  
   * Web3 Foundation should give out a communication at some point to explain its position of giving out 1% of the DOT genesis supply to Kusama.

## Next version: 1.2.5 - Basti, Joe

* will contain support for the new universal Ledger app
* before Decoded hopefully
* Coretime might be 1.3

## Stabilizing Polkadot - Oliver, Kian

* Omni-Node. Currently [gathering feedback](https://forum.polkadot.network/t/polkadot-parachain-omni-node-gathering-ideas-and-feedback/7823)
* [Making the life of parachain devs easier with a new template](https://github.com/paritytech/polkadot-sdk/pull/4369)

## Wish for Change Track Discussion - Gavin

* Was recently introduced and is already maxed out with 10/10 proposals on the WFC track
* Accepted proposals  
   * [EVM Collective](https://polkadot.subsquare.io/referenda/704)  
   * [Implement Optimistic Project Funding](https://polkadot.subsquare.io/referenda/712)  
   * [Reducing duration of spend period](https://polkadot.subsquare.io/referenda/705)
* Debate  
   * We discussed how WFC fits into the overall process of Polkadot  
   * What mandate does the Fellowship have? Does it have to pick it up?  
         * “There is no protocol in place, to get a WFC turned into reality”  
         * From the \[Fellowship manifesto\](<file:///C:/Users/tommi/Downloads/manifesto.pdf>): “While members may engage in any number of activities beyond immediate technical work (designing, programming, debugging), the goal of the organisation is nonetheless that of building technical knowledge critical for the continued existence and evolution of the network protocol itself.”  
         * The Fellowship is self-sovereign, but acts in the interest of the network, and thus might support the implementation of such wishes.  
         * The Fellowship however is not mandated to drop every other work if a WFC is AYEd.  
         * Anyone can submit a PR to get a feature into Polkadot and if it is agreed by a WFC, the Fellowship will at a minimum not block it (except if it is dangerous for the network)  
   * On proposals that are unspecific  
         * Proposals might be so unspecific that they cannot be implemented.  
         * Possible reactions might be  
                  * to respond that it is not possible to implement it,  
                  * to implement and interpret where possible  
                  * to start an RFC process  
                  * let other parties implement it  
   * The Fellowship might need a forum to respond to WFC requests  
   * In summary, there is a pipeline forming from potentially very abstract wishes via WFC, following discussions, RFCs, and then the actual implementation

# Discussions

## RFC 89 - Kian

* [Flexible Inflation #89 1](https://github.com/polkadot-fellows/RFCs/pull/89)
* Mechanism to allow Governance to configure inflation, also improves the flexibility in the code
* It’s unopinionated about what the inflation should be, and rather leaves it up to parameterization
* might consider fixed income for Treasury or Collectives/Subtreasuries
* Kian is looking for further feedback. Because it is very opinionated, so far there hasn’t been any pushback.

## OnPollStatusChange for pallet-referanda - Pablo

* `OnPollStatusChange`[ for ](https://github.com/paritytech/polkadot-sdk/issues/4227)`pallet-referenda`[ · Issue #4227 · paritytech/polkadot-sdk · GitHub](https://github.com/paritytech/polkadot-sdk/issues/4227)
* The idea is to make pallets aware of state changes
* Gavin offered two criticisms  
   * It won’t work in async environments and with XCM.  
   * The hook implementations could be critical for weights. If the hook is very heavy, the weight of the extrinsic would be different from the execution
* Pablo asked what a good way to achieve the intention would be, to which Gavin responded, that `Tasks` are the solution that has been devised for such situations.

## Define and implement Hold for Assets - Pablo

* [Define and implement ](https://github.com/paritytech/polkadot-sdk/issues/4315)`Hold`[ for Assets · Issue #4315 · paritytech/polkadot-sdk · GitHub](https://github.com/paritytech/polkadot-sdk/issues/4315)
* The idea is to allow inspection of the fungibles::holds traits
* Kian responded that there is definitions in the new currency system and he will send them to Pablo

## Invitation to join the Polkadot Blockchain Academy - Nikos

* <https://page.polkadot.academy/pba-faculty-application>[ 1](https://page.polkadot.academy/pba-faculty-application?hs%5Fpreview=GtGJHBHU-167474363287)
* The PBA is expanding its faculty and will hold remote academies.
* There is an open invitation to join the PBA as contributor

# News

## Polkadot Tooling Collective (PoToC) - Oliver

* currently making a list of projects to support
* would maintain these projects, e.g. PAPI, Polkadot.js, Dev tooling
* overlap between the Fellowship and PoToc would be marginal

## Elastic Scaling - Andrei

* First iteration will be an MVP  
   * with a few constraints  
         * 3 cores (so, more like fixed scaling for now)  
         * collator set not open  
   * timeline:  
         * implemented for the relay chain  
         * awaiting audit  
         * todo: documentation, cumulus integration  
         * rollout: “on testnets soon” → first part of June
* elasticity should come in the second half of the year

## JAM

* spec  
   * recently it occurred to Gavin that we could take what happens in Extrinsic IO and repurpose it into two separate components: imports and exports for cores  
         * allows doubling the bandwidth for use case of placing continuations in each core  
   * pre-release of the new spec released a few days ago. Will now get more formalized over the next month  
   * in the Graypaper repo
* dev is ongoing  
   * good interest from new teams to make new impls  
   * first implementation in Rust by the JAM team is continuing  
   * hoping to have a testnet by decoded
* JAM lecturing tour  
   * Buenos Aires, Stanford done. more to come in Europe and Asia over the following weeks
* “pretty clear idea about node requirements”  
   * storage throughput, load  
   * they look doable, but high
* “I tweaked some of the numbers a bit”  
   * 800k/s for bandwidth into the (same as DOT)  
   * moved to 2.5MB/s. that was maybe too high. probably gonna settle at around 2MB/s”
* next weeks  
   * more work on the availability system  
   * PolkaVM sub-instances  
   * getting the testnet going, derisking on uncertainties

# Q&A

## EVM on Coretime Chain?

* Phil from Lastic asked about having EVM on the Coretime chain. Is this possible?
* Gavin: Not against EVM. Rob Habermaier was quite in favor. If Lastic are keen on making a PR, I don’t see any problem

## Wen Voting in Nomination Pools?

* Ankan: Got approval for the PR last week Friday. Will be merged tomorrow. Audit scheduled and should happen in the next 3 weeks. Next to next release in Kusama (I think was implied to be 1.2.5)

Video: https://www.youtube.com/watch?v=War1weBu7yU 2

Fellowship

New Members

clangenb to rank 1 2

pandres95 to rank 1 1

New process for submitting evidence for Fellowship members by Basti

Members are also now submitting first requests for promotions. The first one is to promote Oliver...

2024-05-21 Technical Fellowship OpenDev Call

The March 2024 Governance Report from [OpenGov.Watch](http://OpenGov.Watch) dives into the latest twists and turns in the OpenGov, mainly focusing on the initiation of Decentralized Voices (DV) and the shift in power dynamics it caused. We are digging into the political and operational layers of OpenGov, exploring how different players are making waves, and speculating about constitutional questions for the recent dramas. From funding proposals to community feedback and strategic shifts in major projects, this report gives you the scoop on how the latest events are shaping OpenGov.

## Enter Decentralized Voices

March began with a significant change in OpenGov’s political structure as the Web3 Foundation appointed [the first round of](https://medium.com/web3foundation/decentralized-voices-round-1-candidates-announced-23d9a800b260) Decentralized Voices (DV). In short, W3F delegated 42 million DOTs voting power for three months to the selected members and organizations within the community to amplify community involvement in the decision-making in the OpenGov. As Bill Laboon stated during his [weekly office hours on X](https://twitter.com/BillLaboon/status/1771174687629840670), the delegations will be limited to one term and we will see brand new DV delegates at the beginning of June. You can check out [the initial announcement](https://medium.com/web3foundation/decentralized-voices-program-93623c27ae43) for the details about the application and start preparing if you intend to be a DV delegate for the next term.

Although there are no formal requirements for justifying their votes, some DV delegates have established specific Telegram groups to communicate and share their feedback with governance participants. We have observed Jimmy Tudeski, Saxemberg, and Chaos DAO providing weekly explanations for their voting behavior on the X platform, while others offer their feedback on governance platforms like Polkassembly and AAG. One delegate, Kukabi [even launched a website](https://gov.helikon.io/) dedicated to sharing all his feedback.

As OpenGov Watch, we have had meetings with all the delegates after they got appointed and got a glimpse into their initial experiences. The most common feedback was that they all felt a great responsibility for their appointment, consuming considerable time and energy as they analyzed and provided feedback on all the proposals they reviewed. The delegates have also made some concerning reports, including rumors about threats and attempts at bribery against influential voters.

## The Balance of Power

The introduction of DV in OpenGov disrupted the existing balance of power, primarily dominated by the executive whale Giotto. Even before the official introduction, Giotto started publicly criticizing the DV program and the criticisms became attacks as [The DED Bounty](https://polkadot.subsquare.io/referenda/556) proposal encountered great opposition. During this time, Giotto heavily targeted DV delegates as if they were a unified entity and voted unanimously, while in fact, this is not the case on most of the proposals. In one of his criticisms, we observed that Giotto used wrong data which showed the impact of DV votes on the outcome of the OpenGov referenda. Although community members [quickly pointed out](https://twitter.com/1percentup/status/1770802168649437399) that this data was based on misconfigured queries after Giotto shared it, [the post remains live](https://x.com/giottodf/status/1770773122452471938?s=20) on his X profile.

![](https://ipfs.subsocial.network/ipfs/bafybeigdzkdavdu5nidjcpzbjbztxw77t4h7x5wklf7uqe6am6d6n7zlei)

The actual situation however shows minimal impact of DV delegates (10%) on the outcome of most OpenGov proposals. You can follow the DV impact live on the [Dune dashboard](https://dune.com/substrate/polkadot-and-kusama-decentralized-voices).

![](https://ipfs.subsocial.network/ipfs/bafybeiclg6t4dirftfeesssbciktost6bdtog7f7vvbaoumyl6k2ze2ibe)

In this period Giotto also targeted all the DV delegates with accusations of bribery and signing of NDAs in favor of the [Transistor proposal](https://polkadot.subsquare.io/referenda/507). No factual evidence has been provided for these accusations and NDA allegations have been denied by the Transistor team [during a live X space](https://x.com/transistor%5Fwtf/status/1769015706761228462?s=20). Some of the DV delegates also publicly announced they were not part of any kind of agreement. We do not have further information about this claims and continue to closely monitor the developments.

## Fast & Faulty

The [proposal seeking](https://polkadot.subsquare.io/referenda/514) funding for Conor Daly's Indy 500 racing sponsorship with an amount of $2.1 million has passed without any controversy. However, [the proposal's execution failed](https://x.com/AdamSteeber1/status/1772715317787025556?s=20), leading to a series of events.

Since the funding hasn’t reached the proposer and there are overdue payments that were waiting for the treasury grant, several agents from the network started collecting ‘donations’ to be paid back in the future with a [replacement proposal](https://polkadot.subsquare.io/referenda/616) that is currently being voted on. The community collected the targeted amount of 130,000 DOT in 7 days, with Giotto being the largest contributor, providing over half of the target with 73,000 DOTs.

This is a particularly interesting topic as the events uncover several political aspects for OpenGov.

1. As the social layer of the network found a solution, there was an interesting technical discussion on the background about the origin of the error. Adam Steeber, who is the original poster that alerted the community about the error, claimed this might not be a bug and [the issue might have originated](https://x.com/AdamSteeber1/status/1773812160507805908?s=20) from a simple human error that had been made during submission, contrary to the [post-mortem report](https://hackmd.io/@XuVYQ1rUQjGv8uRzzsdzuw/SkVai0WkA).
2. It is a very unique example where legislation and execution are almost completely separated. In a sense, the execution layer of the network failed to implement a legislative decision made by the OpenGov. Although there are several -not very easy- solutions available to fix this on the technical level, we have been informed that the technical fellowship abstained from fast-tracking a replacement proposal.
3. Another unique aspect of this proposal is that the second proposal seeks the same amount of DOT as the previous one, although the DOT price has risen nearly 40% since the original proposal. In this way, the longstanding tradition of relying on the EMA of DOT prices is practically overruled.

All these points have the potential to open up interesting constitutional debates.

For many years the mantra was ‘code is law’. But as we can see in new on-chain governance systems like OpenGov, the discussion becomes more complex. Should we consider this proposal as failed, and separate the new proposal from the previous one? Would it make a difference if this is a human error or a protocol bug? Which body is mainly responsible for fixing the problem then? Can we have strict standards for proposals? So, is keeping the old EMA in the new proposal acceptable?

These rhetorical questions are all waiting to be answered in future proposals, and we should start exploring these dilemmas as OpenGov evolves.

## Funding is DED

Another controversy centered on the funding of the DED memecoin. Discussions began with [a proposal](https://polkadot.subsquare.io/referenda/548) seeking $300,000 in funding for the Existential Deposit airdrop on the AssetHub chain and snapshot tooling. Following the community’s reaction to the unpredictability of future DED proposals, [another proposal](https://polkadot.subsquare.io/referenda/556) was posted asking for $10 million to cover all memecoin costs in a unified and undefined package. Both proposals are currently failing.

Resistance from the community to the DED bounty led to a directional shift in the development of the DED memecoin. The DED foundation redirected the project to seek private investors after losing community funding, and reduced the community allocation to 5% from the previously advertised 100%. The decision created one of the biggest controversies of OpenGov, as the foundation that made this decision [is funded by](https://polkadot.subsquare.io/referenda/469) the Polkadot treasury (for about $140,000) and the treasury [also funded](https://polkadot.subsquare.io/referenda/385) the initial marketing efforts of DED with another grant worth $700,000.

## Notable Mentions

* **7000² Feet Under:** What a swing! The [proposal from the Transistor team](https://polkadot.subsquare.io/referenda/507) that seeks $3.2 million in funding for their NYC office swung right and left through the month. Starting with very little support, the proposal managed to pass a 60% approval rate at some point and kept its position for some time. But in the end, the proposal failed with only a 30% support rate after extensive discussions on social media, which were mainly led by Giotto’s anti-DV narrative. There was also an impact of Transistor’s inconclusive Decentralized Futures grant application on the outcome of the referendum.
* **OG Tracker is Introduced:** Another project that keeps an eye on OpenGov by tracking deliverables of the previous referenda went live this month. You can view the progress of proposals approved by OpenGov on [OG Tracker](https://app.ogtracker.io/dashboard) and provide feedback on the website to contribute to future versions.
* **Marketing Intensifies:** The [Marketing Bounty](https://polkadot.subsquare.io/referenda/402) #33 that Giotto initiated [received a refill](https://polkadot.subsquare.io/referenda/529) worth $2.6 million and another refill worth $4.6 million is currently [being voted](https://polkadot.subsquare.io/referenda/596). Earlier this year, this bounty had [already been refilled](https://polkadot.subsquare.io/referenda/596) with $800,000\. [Initially starting](https://polkadot.subsquare.io/treasury/bounties/33) with $600,000 in February and currently has $2.5 million available to spend.
* **Bounties Clashing:** Another marketing bounty, the [Autonomous Marketing Initiative bounty](https://polkadot.subsquare.io/referenda/562) spearheaded by Adam Steeber is currently being voted on OpenGov, requesting $2 million from the treasury. If approved, Polkadot governance will simultaneously have two active marketing bounties. The bounty mechanism is becoming increasingly popular, with a growing number of bounties proposed to OpenGov. Bounties will be our main focus in April.
* **Million DOT Liquidity Campaigns:** Three big spender proposals are currently being voted on OpenGov regarding DeFi products worth $9.5 million each.  
   * [Liquidity provision for Hydra DX](https://polkadot.subsquare.io/referenda/561), in which the treasury will act as a liquidity provider, and the funds will remain in the control of OpenGov.  
   * [Liquidity incentive program for Hydra DX](https://polkadot.subsquare.io/referenda/561), which aims to fund Hydra DX to conduct a campaign to attract more liquidity to their platform.  
   * The [liquidity incentive program for StellaSwap](https://polkadot.subsquare.io/referenda/580) aims to fund StellaSwap to conduct a campaign to attract more liquidity to their platform. Unlike Hydra DX, StellaSwap is not a Polkadot parachain itself but a dApp built on the Moonbeam parachain.
* **Airdrop Frenzy:** After extensive discussions initiated by Giotto on governance platforms and social media, Zeitgeist has decided to commence an airdrop to DOT holders on top of their deliverables in their [Futarchy proposal](https://polkadot.subsquare.io/referenda/502). This proposal aims to integrate prediction markets into OpenGov and the decided airdrop amount is equal to 1% of the ZTG supply. Although the eligibility details have not yet been announced, we expect this event to set a precedent for future proposals, as teams might consider including an airdrop allocation in their OpenGov proposals.

---

* Follow us on X: [@xcjeeper](https://twitter.com/xcjeeper) [@alice\_und\_bob](https://twitter.com/alice%5Fund%5Fbob)
* Check out [OpenGov.Watch](http://OpenGov.Watch)

The March 2024 Governance Report from OpenGov.Watch dives into the latest twists and turns in the OpenGov, mainly focusing on the initiation of Decentralized Voices (DV) and the shift in power dynamics it caused. We are digging into the political and operational layers of OpenGov, exploring how...

2024 March OpenGov Report

The latest episode of our monthly OpenGov report is here. We report on

* Giotto pressing charges against Guppies
* The new Wish-for-Change track and how it changes the power dynamics in OpenGov
* The epic match for a certain sports sponsorship
* and more…

 To receive future updates, [subscribe to our newsletter](https://www.polkalytics.io/).

## The Trial

Anons on trial! Without a doubt, the biggest drama on OpenGov this month was Giotto [pressing charges](https://twitter.com/giottodf/status/1783283026019135668) for defamation and slander against a couple of anons on X and Telegram as well as the owner of the [Guppies](https://t.me/dotguppies) Telegram group.

Although some of the anons that Giotto has sued repeatedly insulted him on different platforms, it is also a concern that the fear of lawsuits has become another aspect that suppresses people from making public criticisms.

Of course, as OpenGov.Watch, we cannot approve of random insults posing as freedom of speech. But it is also important to underline that free speech in OpenGov is deteriorating due to certain factors such as fears of disapproval of governance proposals by certain groups, getting bullied, and ultimately, even lawsuits.

## Law & Order

The “Wish for Change” (WfC) track is finally introduced on OpenGov. This new track enables users to make requests for off-chain actions like instructing the Technical Fellowship or other forms of social contracts. Before WfC, these changes were requested using the root track, which has a very high decision deposit and the limit of one root track referendum that could be active at a time. This created a blocker for change requests since all the code changes of the main protocol also require root track referenda.

With the introduction of Wish for Change, OpenGov has already received a couple of WfC referenda. Giotto proposed three WfC referenda which aim to [reduce inflation](https://polkadot.subsquare.io/referenda/706), [restrict the delegation feature](https://polkadot.subsquare.io/referenda/702) on root and treasurer tracks, and [reduce the duration](https://polkadot.subsquare.io/referenda/705) of treasury spend periods. Others have also posted proposals on the WfC track to [establish an EVM collective](https://polkadot.subsquare.io/referenda/704) and implement [optimistic project funding](https://polkadot.subsquare.io/referenda/712), aiming to alter the nomination system to enable people to nominate their tokens directly to projects to help them grow by providing an income stream through their nominations.

While the latter proposes practical features, the inflation and delegation referenda are the most interesting from a judiciary perspective. Once again within a constitutional debate, we are witnessing a legalization process of previously technical features. For example, the result of the delegation referenda will make the delegation feature a decision by the token holders, which can be considered as establishing a precedent for the right to delegations in OpenGov, while it was merely a technical feature before. Similarly, the token holders will be making a legislative decision on the inflation, while it was an executive decision made by the initial builders of the network until now.

## An epic Match

The biggest turnout and the most violent swings happened on a [sports sponsorship referendum](https://polkadot.subsquare.io/referenda/644). With an ask of 8.8 million USD, the sponsorship referendum was kicked out twice from the confirmation period until an anonymous whale voted Aye with 19 million DOT voting power which seemingly made the decisive call. The swings on the referendum caused much confusion while it also attracted some sleeping giants with 6 million DOT voting power that had never voted in OpenGov before and only went active with this referendum on the Nay side. A last-minute name and description change of the referendum also attracted questions from the community. Information relating to the proposal has been removed “upon request of the rights holder due to details relating to price, benefits, and term of the agreement being considered sensitive and confidential”. The referendum is currently passing on the last days of its confirmation period.

## Alice in Chains

[The Chainalysis referendum](https://polkadot.subsquare.io/referenda/684) seems like a good candidate to be the biggest drama of next month with another huge ask of $10 million for the integration of the Polkadot relay chain to their platform. It has been claimed that Chainalysis “[is a surveillance platform](https://twitter.com/saxemberg/status/1781546776702386393)” and its “close ties” with [intelligence agencies](https://twitter.com/TugyTur/status/1781740481749061635) around the world have been underlined by different ecosystem agents. A very [heated discussion](https://x.com/TheKusamarian/status/1783866123441656000) took place on AAG during the presentation by the Chainalysis team as well. With the big whales on the Aye side and most of the DV on the Nay side, we will be observing this referendum closely in its following stages.

To receive future updates, [subscribe to our newsletter](https://www.polkalytics.io/).

## Notable mentions

* OpenGov Crowdloan: The [replacement Indy500 referendum](https://polkadot.subsquare.io/referenda/616) for the referendum that previously failed to execute has been approved and the funds [have been returned](https://polkadot.subscan.io/transfer?extrinsic=20398862-5) to the community members who crowdloaned earlier.
* Can’t Tip This: A [proposal to tip](https://polkadot.subsquare.io/referenda/637) seven Decentralized Voices delegates has been posted, but most of the DV voted against the referendum with different justifications. As [OpenGov.Watch](http://OpenGov.Watch), we agree that the kind of effort and due diligence currently done by DVs should be compensated, but we also want to underline that each DV contributes differently to the OpenGov, and thus should be compensated accordingly. This opened the discussion for how and by whom due diligence on proposals should be performed in the future. You can see the stats of DV from [Dune Analytics](https://dune.com/substrate/polkadot-and-kusama-decentralized-voices) and their socials from the [OpenGov.Watch the guides](https://www.opengov.watch/decentralized-voices) section.
* Upcoming Elections: The ambassadors collective is expected to go live with the Polkadot 1.3 runtime upgrade. With this new ambassador program, all the head ambassadors will have to be elected through OpenGov and will possess certain powers as well as have a monthly payment for their services to the network. People who wish to be ambassadors are expected to send their applications to the [Polkadot forum](https://forum.polkadot.network/c/ambassador-programme/30). You can get more detailed information from [the related Twitter space](https://twitter.com/i/spaces/1ynJOyokXBvKR).
* The Party is Over: Giotto proposed [to close the Event Bounty](https://polkadot.polkassembly.io/referenda/691) based on the intense negative feedback he received. Curators of the events bounty partially confirmed the concerns but claimed that the lack of speed is due to careful evaluation of each proposal. This is the first time a bounty is proposed to be closed while it is still operative.

## OpenGov.Watch News

Strategy is a major topic in Polkadot. How should OpenGov approach its growth challenges? After countless online and offline discussions, we have curated a decentralized strategy for Polkadot 2.0\. It captures the current state of the ecosystem and its challenges and distills the shared themes into objectives. From there, it proposes solutions on how to address the challenges.

The main objectives we have identified are:

1. Improve the developer experience
2. Improve user experience
3. Improve the public perception of the Polkadot ecosystem
4. Establish efficient BD infrastructure
5. Build capital rails, increase liquidity
6. Increase the number of new chains & apps
7. Improve Accountability in OpenGov

Our next step will be to help with the implementation of those objectives through dedicated Governance Initiatives.

Read the full strategy here: [Polkadot 2.0 Strategy](https://opengovwatch.notion.site/Polkadot-2-0-Strategy-264b338f38184248acbf630879f8386f?pvs=74)

### What else?

Here is a summary of our other activities this month:

* New [OpenGov.Watch](http://OpenGov.Watch) Infodesk Guide: How to “[Prepare and Submit](https://www.opengov.watch/guides/proposals%5Fprepare%5Fsubmit)” a proposal
* Activism  
   * Spreading awareness for the new spend() extrinsic via [Ref 708](https://polkadot.subsquare.io/referenda/708)
* Monitoring  
   * Added [Treasury](https://docs.google.com/spreadsheets/d/1itB8Mj1zDoE1-94QZfKi%5FyPUnHqxyXOO-aOfA9tFeII/edit#gid=386637000) Monitoring sheet  
   * Added [Bounties](https://docs.google.com/spreadsheets/d/1itB8Mj1zDoE1-94QZfKi%5FyPUnHqxyXOO-aOfA9tFeII/edit#gid=1976913229) overview
* Technical Fellowship  
   * 2024-04-23 Technical Fellowship OpenDev Call  
   \* [Report](https://forum.polkadot.network/t/2024-04-23-technical-fellowship-opendev-call/7592)  
   \* [Recording](https://www.youtube.com/watch?v=n6U-UbX546E)
* 15 Bookable Calls  
   * 10 calls with teams seeking consultation to submit proposals to OpenGov or other support  
   * 4 calls with ecosystem agents to coordinate activities  
   * 1 call with Cardano Governance participants for cross-ecosystem collaboration
* AAG participation  
   * [2024-04-11](https://www.youtube.com/watch?v=KlHH7Dskrg4)  
   * [2024-04-25](https://www.youtube.com/watch?v=zWu7ZBDzl%5FQ)
* OpenGov.Watch Office Hours  
   * [2024-04-09](https://twitter.com/i/spaces/1BRJjPLbqLZKw)  
   * [2024-04-16](https://twitter.com/i/spaces/1jMJgmqnEWPKL)  
   * [2024-04-23](https://twitter.com/i/spaces/1mrxmynWmOWxy)  
   * [2024-04-30](https://twitter.com/i/spaces/1LyxBnyEXVExN)

## Stay in the Loop

* Follow us on X: [@xcjeeper](https://twitter.com/xcjeeper) [@alice\_und\_bob](https://twitter.com/alice%5Fund%5Fbob)
* Check out [OpenGov.Watch](https://www.opengov.watch/)
* Find us on [Grill](https://grillapp.net/12859?ref=9409)
* [Subscribe to our newsletter](https://www.polkalytics.io/) to receive monthly updates

The latest episode of our monthly OpenGov report is here. We report on

Giotto pressing charges against Guppies

The new Wish-for-Change track and how it changes the power dynamics in OpenGov

The epic match for a certain sports sponsorship

and more…

To receive future updates, subscribe to our...

2024 April Polkadot OpenGov Report

## Good Morning![​](https://www.opengov.watch/#good-morning)

**We are** [**OpenGov.Watch**](http://OpenGov.Watch)**.**

We are here to help Polkadot Governance grow up and transform Polkadot into the most impactful Web3 ecosystem this beautiful planet has ever seen! We will do this by providing information, leading initiatives, and developing Polkadot governance structures.

We now *could* talk about the problems we see in this space and how we intend to (help) solve them, and we certainly will in the coming days. But right now we want to use the opportunity to talk about something bigger: Our vision for what Polkadot can become.

Before you read on, make sure to follow our socials:

* [Twitter](https://twitter.com/alice%5Fund%5Fbob)
* [YouTube](https://www.youtube.com/@alice%5Fund%5Fbob)

## You were born just right...[​](https://www.opengov.watch/#you-were-born-just-right)

*"We are the middle children of history. Born too late to explore earth, born too early to explore space."*

We were told that we can change the course of history. We watch in awe as AI is writing history. Our lives are enriched by constantly updating technology and watch in fear as the same technology is used in wars to end human lives. We have built a global information network and handed over control to big corporations and nation-states. We are participating in a global economy that is being weaponized without our consent.

And in the midst of all that, we decide to spend our time in the deep in blockchain technology. If you are reading this post, chances are that you think that crypto can be part of the solution to many of those problems. You were born just right for Web3.

## Walking in the footsteps of Satoshi[​](https://www.opengov.watch/#walking-in-the-footsteps-of-satoshi)

Crypto is not apolitical. Bitcoin was born out of the need to create money that is independent of central banks, nation-states, and institutions. A trustless peer-to-peer transaction system. It's a radical and subversive idea. This idea caught on in the minds of many people and created the industry we are confronted with today. Something that might be bigger than even Satoshi envisioned.

But crypto is not just an industry. Web3 is not just about the Internet. We are in the first act of a global revolution that will be transforming the society, economy, and politics.

How will the revolution turn out? Success is not a given. We already handed over Web2 to the institutions and if we are not careful, it could happen again. Our revolution is at risk of being taken off course by regulators and ponzinomists. We must not drop the ball on one of the most essential inventions of the modern age!

To find the right path forward, we need to channel our inner Satoshi and ask: "How can we make sure that we are not turning this into the next big dystopia? What do we have to do to make sure that crypto maintains its radical and subversive character long enough to finish this mission?"

The outcome of this revolution is up to you. Your decisions in the coming months and years will decide if crypto will decide the fate of the coming generations.

## Web3 is a promise[​](https://www.opengov.watch/#web3-is-a-promise)

To stay on course in this time of uncertainty, we have to orient ourselves on a north star: Web3

Web3 is a promise. The promise of a free and open Internet. An Internet that belongs to the people who create it and is not monopolized by corporations that leverage network effects to accumulate all the good tech in their hands.

Web3 is the promise we can cooperate with others in a way that benefits the common good.

Web3 is the promise that we can finally get access to the tools to achieve freedom and sovereignty from the undue influence of others. Web3 is our secret hope that once we have built a global network of like-minded people who work together to establish new structures of sovereignty, this new freedom will create a spill-over effect into fields outside of the Internet. It is the hope of sparking new social movements, new economies, and new systems of doing politics and building (networked) states.

## OpenGov is the way[​](https://www.opengov.watch/#opengov-is-the-way)

The problem with Web3 is that it is a feel-good umbrella term for our ambitions and dreams. It might be a set of technologies, or ideologies, or practices, but how do we get there? After all, we are seeking to replace structures that have been growing over a long time.

We essentially want to rewrite the social fabric of reality. We want to invent a better society. But all new societies are thrown in front of the same problems: "How do we live together?" It is the age-old question. The reason why we have politics. Because there are different individuals with different interests and very likely not everyone will get everything that they desire.

We build society through politics. But how do we do good politics? The truth is: We don't know. We have some good ideas. We have a few thousand years of experience. We have theories and empirical knowledge and experiments and studies. But we haven't found the silver bullet.

So let's not be cocky. We are inexperienced in politics and will make rookie mistakes. Our job is to learn this politics thing as fast as possible, develop structures and processes, stay open to learn and adapt, and yet be steadfast and firm to make sure actual things happen.

What we do also have is a few hundred million dollars in on-chain Treasury funds to make things happen. That is enough incentive to attract a few thousand people that would be willing to give this thing a try.

This is the context in which Polkadot OpenGov is born. The aggregate of all the people that were digging deep enough into crypto to discover Polkadot. A Web3 ecosystem that actually cares about the future. All of us who participate in this journey are called to ensure that Polkadot will make a strong positive impact on the world.

**OpenGov is the way how we negotiate the future while we build it.**

And you were born just right to be a part of it!

## Watchers of the Gov[​](https://www.opengov.watch/#watchers-of-the-gov)

Polkadot Governance is young and disorganized. But its potential is huge! Polkadot OpenGov could become the most impactful DAO of Web3.

And just as OpenGov gets introduced to the world, we enter the scene. [OpenGov.Watch](http://OpenGov.Watch) will be here to monitor day-to-day operations and provide reporting and analysis. But we are not going to be passive actors only. Because OpenGov just being traditional politics with factions fighting over who has their interests represented would be boring.

We see Polkadot OpenGov as a way for a blockchain ecosystem to become smart and intentional. OpenGov is the brain of Polkadot. We are going to lead discussions to identify problems, find suggestions for solutions, and synthesize them into Governance initiatives that will together form a holistic strategy that covers the full range of everything Polkadot needs to do as an ecosystem to become successful and impactful.

We will offer to take the lead on some initiatives, with the full understanding that Polkadot OpenGov emerges from the bottom-up and crypto in essence is all about decentralization. We will stay agile and flexible, seek cooperation and offer coordination.

Our watch has started.

## Let's connect![​](https://www.opengov.watch/#lets-connect)

We will publish more in the coming days. Let's connect so that you'll be there when it happens:

* Twitter: [@alice\_und\_bob](https://twitter.com/alice%5Fund%5Fbob) & [@xcjeeper](https://twitter.com/xcjeeper)
* YouTube: [@alice\_und\_bob](https://www.youtube.com/@alice%5Fund%5Fbob/)
* Telegram: [@alice\_und\_bob](https://t.me/alice%5Fund%5Fbob), [@jeepso](https://t.me/jeepso)
* LinkedIn [Tommi Enenkel](https://www.linkedin.com/in/tommi-enenkel/)

Good Morning​

We are OpenGov.Watch.

We are here to help Polkadot Governance grow up and transform Polkadot into the most impactful Web3 ecosystem this beautiful planet has ever seen! We will do this by providing information, leading initiatives, and developing Polkadot governance structures...

Web3 is a promise. OpenGov is the way.

Alice und Bob

Alice und Bob take in-depth looks at the Kusama and Polkadot ecosystem. They make complicated facts understandable for the broader community.

jeeper

bafybeid2lzrwuit26rkdylfpzlidvzke6izdpmo6ssttky2qg6y7i7lvqa

bafyreibi7ne2hl5f4dqie36ec7fadi3vpo5uanx6fk5qzldqehzz6y23fu

bafybeidim7mdwyw7o4tljmopc3srq2djxcmdivsfbmyzsxjulwlku4sv4q

bafybeiaw6x6iwhmnwlihiph7uzoticgpa6ycuv2fblh2d3jycbhnn4uh44

bafyreidoyjugm7crkc7lkttunhhyr2ynuuksyajevz56rrdj643nbte5gy

bafybeieiynnm6q4zddi5m7uc4uzosxxvzwzlypn7bhghp3obsrzyb5szte

bafybeih5lbkbqgncyohuaeoirikxrdpsrac5odoxbuwqupmfj3ctjdbtrm

bafybeiecsax7iql57ap3oxbtzndhvdirnysqqcfzopkfcoadmdjfnlgdmy

bafybeihp7k4zcngryo6r6d5q3wn6ujhu47wqr3lvqqbaoyq53lu7ubeatq

bafybeidf2tzbzwe73oozoww4n25cgxf7s6kj4gseqgnoxmzxapikqi2wii