[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)

bafybeicojgusyhv2exbvel6xfjsl7scpft7utwqbxgoptisf4hrtt5yfim

2024-03-19 Technical Fellowship OpenDev Call

[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)

bafybeid2lzrwuit26rkdylfpzlidvzke6izdpmo6ssttky2qg6y7i7lvqa

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

bafybeih5lbkbqgncyohuaeoirikxrdpsrac5odoxbuwqupmfj3ctjdbtrm

2024 April Polkadot OpenGov Report

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)

bafybeiecsax7iql57ap3oxbtzndhvdirnysqqcfzopkfcoadmdjfnlgdmy

2024-05-21 Technical Fellowship OpenDev Call

**The first few hours and days understanding the Polkadot/Kusama/Substrate ecosystem can be rough. Where do you start your journey? Where do you get information? What can you trust?**

To find your way around, we created this little guide with the most important websites and communities for your journey into the ecosystem.

We will look into:
* Core information and sources
* News & Latest Developments
* Social Media

This article is also available as video:
https://youtu.be/lxRS-3qAEeM

## Core Information & Sources
The single most important source when you are just starting out is the official [Polkadot Wiki](https://wiki.polkadot.network/docs/getting-started). It explains basic concepts and is not shy to go deep an relevant concepts that they introduce into the blockchain world. The [Kusama Wiki](https://guide.kusama.network/docs/kusama-getting-started/) will go into details where things get more experimental or might be different from Polkadot.
### On-Chain
To get insights into what is happening on-chain, use the [Polkadot.js.org App](https://polkadot.js.org/apps/#/) (aka Portal) and see what is happening in governance via [Polkassembly](https://polkadot.polkassembly.io/).
### Explorers
There are three commonly known blockchain explorers, these are [subscan.io](https://www.subscan.io/), [polkascan.io](https://polkascan.io/) and [polkastats.io](https://kusama.polkastats.io/)
### Official Channels
The [Community page](https://wiki.polkadot.network/docs/community) offers all the channels. Communication of the core community happens mostly in Riot/Element.
### Price
The best aggregator for price information so far is [dotmarketcap.com](https://dotmarketcap.com/). They also offer info on Tokens and Tokenomics.
## News & Latest Developments
### YouTube
The YouTube Bubble isn't too big yet and next to [yours truly](https://www.youtube.com/channel/UC0alQ35JKnMo_ctzYITthbw), only a few channels exist:
* [KryptosChain](https://www.youtube.com/channel/UC0XiJui2llg9PHUz45jfycw): Daily News, mostly about the Dotsama ecosystem
* [PromoTeam](https://www.youtube.com/channel/UCrvyFYM29oQ-EAejZgYqmWA): Updates on the relevant developments
* [Crypto Elementary](https://www.youtube.com/channel/UCGGamrWe1ZK9IetVxi_VvhA): Parachain Auctions and Technicals so far
* [Jay Chrawnna](https://www.youtube.com/channel/UCqNw3CEyOD-bjjYYaxVyG3Q): A lot of FAQ explainers and commentary on Parachain Slot Auctions
* [DotsamaDeFi](https://www.youtube.com/channel/UCH73JWCVLkRVyCTq89rrEfA): Focus on DeFi
### Podcasts
* [Parachain Auctions Podcast](https://www.youtube.com/playlist?list=PL1fKlftNZ_xHakccBbVMJqOt5HehxQS40) by Kraken
* Layer 0 Podcast by [Teriyaki Don](https://twitter.com/TheTeriyakiDon)

### Social Media
* The ecosystem has a strong **Twitter** game with a lot of core people participating there. Our Twitter account has curated lists of important channels: [Lists](https://twitter.com/alice_und_bob/lists)
* **Medium** is another medium where a lot of information is exchanged. Again, a list of [channels we follow](https://aliceundbob.medium.com/following) can give you a jump start.
* **[Subsocial](https://app.subsocial.network/)** is an actual dedicated Social Network built on Substrate. Which means as long as you can't buy tokens and the faucet is only giving you a little, you will mostly be able to read there.
* **Reddit** game is weak so far but you can find a lot of questions being answered in the offical Subreddits.

## Ready to become part of the system?
**Then start by staking your KSM right on chain and earn higher interest than on exchanges:** Don't just let your KSM sit in your account doing nothing while you wait for the right moment. You can earn interest on your KSM and also support our channel.

Get all the details here: [Alice und Bob want your nomination!](https://aliceundbob.medium.com/alice-und-bob-want-your-nomination-b727c2111716)

bafyreifn3wogx6jtnhm45op45ooymknax65qzmoikn7bdmaujy3foalko4

How to become part of the Polkadot/Kusama ecosystem

Starting next week, the Kusama Parachain Slot Auctions will see a drop in slot prices. Quartz is about to win the next slot tomorrow and currently the bid is 51k $KSM.


bafyreifcjjjnekdry4t6hohnajr5wcw25j4banwh7qa3x6sdcexhbniynm

Parachain slot prices decreasing

After [announcing Subscrape to the world for the first time](https://twitter.com/alice_und_bob/status/1493714489014956037) a little over a month ago, the library has grown quite a bit and today I am proud to announce v1.0 of Subscrape and present the roadmap for Subscrape 2.0

## Releasing Subscrape v1.0
**Subscrape is a Python scraper for Substrate chains that uses Subscan.**

It is configured by a config file through which you use to tell the scraper which data to get. It is stored locally on disk and can then be queried and transformed to your needs.

[Subscrape v1.0](https://github.com/ChaosDAO-org/subscrape/releases/tag/v1.0) has just been released on the ChaosDAO Github. It allows for the scraping of extrinsics on any Subscan supported chain. The [Subscrape README](https://github.com/ChaosDAO-org/subscrape/blob/main/README.md) provides the basic documentation needed to understand the mechanics. If you have additional questions, feel free to reach out via DM on Twitter: [@alice_und_bob](https://twitter.com/alice_und_bob)

## The Roadmap to Subscrape 2.0
Subscrape is a personal project that evolves with my needs. As I see that it might serve the needs of others too, I am open sourcing it and give you a chance to influence what I do with it or for you to pick it up and continue development. Version 1.0 served the purpose of extracting crowdloan related data and further process it in a Spreadsheet.

Version 2.0 will focus on helping me do my taxes. Taxes in Substrate are a topic that is not yet deeply explored and could prove to become very difficult in the future. My country recently introduced a rather degen friendly legislation for crypto taxes, but it is still a huge challenge.

To do my taxes, I plan to introduce utilities to understand the capital flows of the following mechanics:
- Transfers in, out and between several owned accounts
- Staking rewards
- Crowdloan participation
- Airdrops/Paradrops
- Treasury tips
- XCM transfers between parachains
- DeFi
  - Swaps
  - Liquidity Provision
  - liquidity mining
- NFTs buys and sells
  -  RMRK buys and sells

This does not mean that this will be full-fledged application that supports all those cases. It means I will implement just as much as needed to fulfull my tax obligations. Corners might be cut sharply.

I welcome any collaboration on this repository. I will especially share any knowledge you are interested in to get up to speed quickly. But please do not expect that feature requests might be fulfilled if they do not fit my agenda.

I post updates on the project to Twitter from time to time. You will find the latest info by searching for the hashtag [#Subscrape](https://twitter.com/hashtag/Subscrape)

Feel free to retweet the [announcement tweet](https://twitter.com/alice_und_bob/status/1506040033899335680).

bafyreidjeklklumyxjv7tqi3cuipnzmbhum2dejcat4dufjxbzoy3ficve

Subscrape: Releasing v1.0 & Roadmap for v2.0

**aka: “FINALLY I can get my Polkadot taxes done!”**

Since March 2022, I have been building an analytics engine for Polkadot. The first product to launch on Polkalytics is personal reports of your on-chain activities that will finally enable you to do your taxes. In the future, Polkalytics will offer consulting services and additional products for tax consultancies, businesses, parachains, and protocols.

In this post, you will learn about the types of analytics that are becoming possible and about **Polkalytic’s first product: Polkadot Tax Reports.** And I will share the report that was generated for my personal main Polkadot and Kusama addresses.

* Visit [www.polkalytics.io](http://www.polkalytics.io) now to apply for the Closed Alpha program.
* Follow on Twitter: [@polkalytics](https://twitter.com/home)

# Polkadot lacks Analytics

*What’s my crypto profit and loss? How much revenue are parachains actually making? Where is money flowing in the ecosystem? Who is the best RMRK NFT flipper? Which DeFi protocols are actually gaining traction? Whom should I copy-trade?*

There are a million questions about Polkadot in our collective mind every day. Most of them haven’t been answered before. For some, you can use tools like the [Subscan Blockchain Explorer](https://www.subscan.io/) or put in the effort and do your own Spreadsheet and programming magic.

But let’s be honest: Polkadot is still very inaccessible when it comes to gaining insights into *what is actually happening on-chain*. There is no universal analytics tool and because of the diversity of parachains, we are still far away from it.

To make things easier, I released the open-source library Subscrape in March 2022 ([Announcement](https://polkaverse.com/@alice-und-bob/subscrape-releasing-v1-0-and-roadmap-for-v2-0-32075))

[![](https://ipfs.subsocial.network/ipfs/QmaaVr9coMJKSNe6KtyvxD2b5CdAeqczzUvpXkawt8ahmr)](https://twitter.com/alice%5Fund%5Fbob/status/1506040033899335680)

Over the months, I have used Subscrape to do all kinds of analytics, like

* [Mangata X DEX stats](https://twitter.com/alice%5Fund%5Fbob/status/1609629338520981506)
* [Crowdloan Analysis](https://twitter.com/alice%5Fund%5Fbob/status/1504844681338929152)
* [XCM Netflows](https://twitter.com/alice%5Fund%5Fbob/status/1567540375698415616)
* [Investigating on-chain flows after the aUSD error mint](https://twitter.com/alice%5Fund%5Fbob/status/1558895707398045697)

As I went down deeper into the rabbit hole, I had many conversations with people from the Polkadot ecosystem and they all had the same pain point: “I can’t file taxes for my on-chain activities”.

# Polkalytics Tax Reports

Polkalytics Tax Reports is a service that generates personalized reports of your on-chain activities that enable you to file your Polkadot taxes.

If you use Binance or Kraken or any other centralized exchange, you can just **click an “Export” button and get a full-fledged report that you can hand to your tax consultant.** If you are an active on-chain user of Polkadot, you are out of your luck. No “Export” button for you.

To solve the problem, I had to build something that is bigger than a simple scraper. An engine, that reads ALL data from the chain to fetch transfers, fees, staking, XCM activity, crowdloan participation, DEX swaps, and everything else.

After 3 months of long after-work evenings, the first version of Polkalytics Tax Reports was finished in early December. Since then I am serving individuals who participate in the Polkalytics Closed Alpha. To get your personal report, you can apply for the Closed Alpha program today by visiting [www.polkalytics.io](http://www.polkalytics.io).

Interested to see what the reports look like? I am publishing sample reports of my personal main account here: [Drive folder](https://drive.google.com/drive/folders/14WqTKlAR6bfb2zr5VqxOEn0WWdPsc1j1?usp=share%5Flink).

At the moment, Polkalytics Tax Reports supports the Polkadot and Kusama relay chain. Support for more chains will be added in the coming weeks. As a Polkalytics Closed Alpha program participant, you will get access to ALL upcoming Polkalytics features for the first year.

# The Analytics Boutique opens Shop

Polkalytics is more than just tax reports.

**Polkalytics offers specialized reports for parachains** that want to learn more about what is actually going on on-chain, gather protocol KPIs, and offer transparency to their communities.

**Polkalytics gives crypto tax consultancies an edge** by offering services that none of their competitors can.

**Polkalytics helps investors understand what happens on-chain,** to get capture signals as they happen, and make informed decisions faster.

Polkalytics uses the power of Google Cloud to index all chains. The goal is to generate insights on demand at Google-scale.

If you think that Polkalytics can help you achieve your goals faster or better, [reach out](https://www.polkalytics.io/contact) and we’ll have a conversation.

# Stay in the Loop

* Visit [www.polkalytics.io](http://www.polkalytics.io) now to apply for the Closed Alpha program.
* Follow on Twitter: [@polkalytics](https://twitter.com/home)
* Share the [announcement thread](https://twitter.com/alice%5Fund%5Fbob/status/1609629330061119489)

bafyreiekzcieqyn4zlmlbe6y4xbnwd5bm37gzwh3kb74hfoibwxswjie3y

Polkalytics - A Google-Scale Analytics Service for Polkadot

# Hook

* The name is decided: [DotSwap](https://twitter.com/csaint02/status/1626181757295816706)

# What is it?

A DEX on the common goods parachain Statemint (& Statemine) on Polkadot, with these goals:

* Provide DOT liquidity against external tokens: BTC, ETH, KSM, USDT, USDC  
   * yes, USDC is coming to Statemint
* Enable Sufficient assets: Onboarding to Polkadot without owning DOT  
   * bring your own gas: pay fees in any sufficient asset
* Allow other DOT-bound pairs

# Details

* Mechanics  
   * Exchange commission of 0.3% goes to LPs  
   * Uniswap V1-like: only XYK curve planned, nothing fancy  
   * only pairs against DOT
* Tokens  
   * Parachains can register their native assets on Statemint  
   * permissionless pool creation  
   * BridgeHub as a message router
* Logistics  
   * Audit by SRLabs  
   * Runtime upgrade expected in Q2  
   \* But: [The prediction market thinks differently](https://app.zeitgeist.pm/markets/90)

# UIs/Analytics

* Parity only builds pallets, they won’t offer a UI
* anyone is invited to create one  
   * think grants

# FAQ

* Will it be on Kusama too  
   * “yes”, and “likely”
* Are there already deals with market makers  
   * but, it is permissionless, anyone can do it
* Incentives? ([Discussion](https://forum.polkadot.network/t/statemint-e-swap-discussion/1498))  
   * DOT  
   * Other tokens?

# Discussion

* Will provide much-needed liquidity relief
* Resistance is futile. It will be “the monopoly” in the mid-term and it will command the flow
* It will be a net positive for the ecosystem
* DEXes have a more challenging time now, fearing “the monopoly”  
   * They will have to provide superior value to traders and liquidity providers
* This creates a tectonic power shift, as a lot of attention now goes into how to work with it  
   * Lots of implications in fields like capital onboarding flows, XCM use cases, potential liquidity reuse
* Prediction: Statemint will become a trusted intermediary and settlement chain ([Tweet](https://twitter.com/alice%5Fund%5Fbob/status/1621111336104230912), [Forum](https://forum.polkadot.network/t/statemint-as-a-trusted-intermediary-and-settlement-chain-for-token-transfers/1951))

# Open Questions

* Would DOT incentives put DOT at risk of becoming a security?
* Can the Treasury become a liquidity provider and hold protocol-owned liquidity?
* Can LP be reused cross-chain?  
   * With XCM V3 Remote Locking?  
   * synchronicity is the key problem

# Further Reading

* [2022-11 Statemint Roadmap](https://forum.polkadot.network/t/statemint-update-roadmap/1200)
* [2022-12 Discussion Thread](https://forum.polkadot.network/t/statemint-e-swap-discussion/1498)
* [2022-12 Twitter Space with Robert Habermaier](https://www.youtube.com/watch?v=zYQxvZUhlEQ)
* [2023-01 Summary Thread](https://twitter.com/alice%5Fund%5Fbob/status/1615741740916375552)
* [2023-02-02 Statemint will become a trusted intermediary and settlement chain](https://twitter.com/alice%5Fund%5Fbob/status/1621111336104230912)
* [2023-02 Community Vote on Name: DotSwap](https://twitter.com/csaint02/status/1626181757295816706)
* [2023-02-16 Current thoughts](https://twitter.com/alice%5Fund%5Fbob/status/1626174409055563777)

bafyreigovpf3pnrewicddrsq65ajlmszyvttrnsl7kge2j7v76bwgup5ne

The Latest on DotSwap - February 2023

[Share on Twitter](https://polkaverse.com/@alice-und-bob/latest-on-dot-swap-february-2023-37489)

# Hook

* The name is decided: [DotSwap](https://twitter.com/csaint02/status/1626181757295816706)

# What is it?

A DEX on the common goods parachain Statemint (& Statemine) on Polkadot, with these goals:

* Provide DOT liquidity against external tokens: BTC, ETH, KSM, USDT, USDC  
   * yes, USDC is coming to Statemint
* Enable Sufficient assets: Onboarding to Polkadot without owning DOT  
   * bring your own gas: pay fees in any sufficient asset
* Allow other DOT-bound pairs

# Details

* Mechanics  
   * Exchange commission of 0.3% goes to LPs  
   * Uniswap V1-like: only XYK curve planned, nothing fancy  
   * only pairs against DOT
* Tokens  
   * Parachains can register their native assets on Statemint  
   * permissionless pool creation  
   * BridgeHub as a message router
* Logistics  
   * Audit by SRLabs  
   * Runtime upgrade expected in Q2

\* But: [The prediction market thinks differently](https://app.zeitgeist.pm/markets/90)

# UIs/Analytics

* Parity only builds pallets, they won’t offer a UI
* anyone is invited to create one  
   * think grants

# FAQ

* Will it be on Kusama too  
   * “yes”, and “likely”
* Are there already deals with market makers  
   * but, it is permissionless, anyone can do it
* Incentives? ([Discussion](https://forum.polkadot.network/t/statemint-e-swap-discussion/1498))  
   * DOT  
   * Other tokens?

# Discussion

* Will provide much-needed liquidity relief
* Resistance is futile. It will be “the monopoly” in the mid-term and it will command the flow
* It will be a net positive for the ecosystem
* DEXes have a more challenging time now, fearing “the monopoly”  
   * They will have to provide superior value to traders and liquidity providers
* This creates a tectonic power shift, as a lot of attention now goes into how to work with it  
   * Lots of implications in fields like capital onboarding flows, XCM use cases, potential liquidity reuse
* Prediction: Statemint will become a trusted intermediary and settlement chain ([Tweet](https://twitter.com/alice%5Fund%5Fbob/status/1621111336104230912), [Forum](https://forum.polkadot.network/t/statemint-as-a-trusted-intermediary-and-settlement-chain-for-token-transfers/1951))

# Open Questions

* Would DOT incentives put DOT at risk of becoming a security?
* Can the Treasury become a liquidity provider and hold protocol-owned liquidity?
* Can LP be reused cross-chain?  
   * With XCM V3 Remote Locking?  
   * synchronicity is the key problem

[Share on Twitter](https://polkaverse.com/@alice-und-bob/latest-on-dot-swap-february-2023-37489)

# Further Reading

* [2022-11 Statemint Roadmap](https://forum.polkadot.network/t/statemint-update-roadmap/1200)
* [2022-12 Discussion Thread](https://forum.polkadot.network/t/statemint-e-swap-discussion/1498)
* [2022-12 Twitter Space with Robert Habermaier](https://www.youtube.com/watch?v=zYQxvZUhlEQ)
* [2023-01 Summary Thread](https://twitter.com/alice%5Fund%5Fbob/status/1615741740916375552)
* [2023-02-02 Statemint will become a trusted intermediary and settlement chain](https://twitter.com/alice%5Fund%5Fbob/status/1621111336104230912)
* [2023-02 Community Vote on Name: DotSwap](https://twitter.com/csaint02/status/1626181757295816706)
* [2023-02-16 Current thoughts](https://twitter.com/alice%5Fund%5Fbob/status/1626174409055563777)

bafyreifck6l75bbhsayvx3w6x422gucyc5zb5nkvhjlrqvh25tdln4eh4a

Latest on DotSwap - February 2023

*This article gives the first details on Polkalytics Account Reports, follows the path of an on-chain riddle, and begins the quest to survey the Polkadot Data Ecosystem*

**It always fascinated me how tens of thousands of people rush into Polkadot** parachains to test them out and experience the cutting edge of crypto, while at the same time, they have no clue how they are going to file their Polkadot taxes at the end of the year. Sure, taxes work differently for everyone. Depending on where on this beautiful planet they reside and what legal structure they have set up for themselves, they pay 50%, 20%, 10%, 2%, 0.2%, or 0% in crypto taxes. Some pay zero, but most have to pay something.

**It’s tax season in many parts of the world.** For some businesses that are deep into Polkadot, this means they have 50 or more accounts for all the parachains they use. And they need to report on all of those for their tax filings. The most common questions they need to get answered are: Which assets and how many did we have at the start of the year and at the end of the year? How much did we earn through staking?

**I was sure that someone would take that opportunity** and build a reporting tool that helps all those Polkadot community members get this problem solved. But after 1.5 years of waiting, it still didn’t happen. So I decided to take the engine I built to uncover the secrets of the chain ([including the 1337Riddle of Kusama](https://www.youtube.com/watch?v=gy-DNSpyROs)). I picked up the challenge to develop a tool that fully explains everything that happened on an account: Polkalytics Account Reports.

**After the official** [**announcement of the Polkalytics Closed Alpha Program**](https://polkaverse.com/10716/polkalytics-a-google-scale-analytics-service-for-polkadot-37079)**,** over 30 people applied to participate. 8 were able to get into the program so far and I worked personally with them to generate personalized reports and to file their taxes on time. After validating the product and getting feedback that it actually helps people, it’s time to share some details.

## How does Polkalytics Account Reports work?

Polkalytics holds a complete Google BigQuery (Big as in Big Data) database of all blocks, transactions, and events that ever happened on Polkadot and Kusama. When Polkalytics Account Reports gets tasked with generating a report for an address (or many addresses), it

1. analyzes all historical transactions and balance changes for that account.
2. It then classifies all account actions into potential tax categories according to what happened, e.g. transfers, staking rewards, etc. You then can use this report to apply the rules of your tax jurisdiction to it.

### Types of Transactions

The Polkadot and Kusama relay chains are already supported by Polkalatics Account Reports with the following classifications:

* Transfers
* Crowdloan participation
* XCM transfers
* Staking Rewards
* Fees
* Other minor stuff (index reservations, reserve repatriations, dust lost for deleting accounts)

## Apply for the Closed Alpha

After having successfully helped the first few users, Polkalytics is opening up for more participants. The fee to participate is 50 USD and will work on a first-come, first-served basis as capacity is available. Work in the coming months will focus on adding more chains and making reports available to as many people as possible at affordable prices.

If you want to skip the line, the current asking price is 125 USD.

There will be some promotional offers from time to time. Make sure to get them by subscribing to the [Polkalytics Newsletter](http://www.google.com/url?q=http%3A%2F%2Feepurl.com%2FihmNQ5&sa=D&sntz=1&usg=AOvVaw0nePZNUu6mJSYizfyZqqw3) and following [@Polkalytics on Twitter](https://www.google.com/url?q=https%3A%2F%2Ftwitter.com%2Fpolkalytics&sa=D&sntz=1&usg=AOvVaw2fHM8QbM5d%5FHTZj5U6OBGU).

bafyreigzjenujj4xbeoz7ihg5o2bxohjbenawdb7isvsnx7dtnmgme2nhu

Introducing Polkalytics Account Reports

*This article gives the first details on Polkalytics Account Reports, follows the path of an on-chain riddle, and begins the quest to survey the Polkadot Data Ecosystem.*

**It always fascinated me how tens of thousands of people rush into Polkadot** parachains to test them out and experience the cutting edge of crypto, while at the same time, they have no clue how they are going to file their Polkadot taxes at the end of the year. Sure, taxes work differently for everyone. Depending on where on this beautiful planet they reside and what legal structure they have set up for themselves, they pay 50%, 20%, 10%, 2%, 0.2%, or 0% in crypto taxes. Some pay zero, but most have to pay something.

**It’s tax season in many parts of the world.** For some businesses that are deep into Polkadot, this means they have 50 or more accounts for all the parachains they use. And they need to report on all of those for their tax filings. The most common questions they need to get answered are: Which assets and how many did we have at the start of the year and at the end of the year? How much did we earn through staking?

**I was sure that someone would take that opportunity** and build a reporting tool that helps all those Polkadot community members get this problem solved. But after 1.5 years of waiting, it still didn’t happen. So I decided to take the engine I built to uncover the secrets of the chain ([including the 1337Riddle of Kusama](https://www.youtube.com/watch?v=gy-DNSpyROs)). I picked up the challenge to develop a tool that fully explains everything that happened on an account: Polkalytics Account Reports.

**After the official** [**announcement of the Polkalytics Closed Alpha Program**](https://polkaverse.com/10716/polkalytics-a-google-scale-analytics-service-for-polkadot-37079)**,** over 30 people applied to participate. 8 were able to get into the program so far and I worked personally with them to generate personalized reports and to file their taxes on time. After validating the product and getting feedback that it actually helps people, it’s time to share some details.

## How does Polkalytics Account Reports work?

Polkalytics holds a complete Google BigQuery (Big as in Big Data) database of all blocks, transactions, and events that ever happened on Polkadot and Kusama. When Polkalytics Account Reports gets tasked with generating a report for an address (or many addresses), it

1. analyzes all historical transactions and balance changes for that account.
2. It then classifies all account actions into potential tax categories according to what happened, e.g. transfers, staking rewards, etc. You then can use this report to apply the rules of your tax jurisdiction to it.

### Types of Transactions

The Polkadot and Kusama relay chains are already supported by Polkalatics Account Reports with the following classifications:

* Transfers
* Crowdloan participation
* XCM transfers
* Staking Rewards
* Fees
* Other minor stuff (index reservations, reserve repatriations, dust lost for deleting accounts)

## Apply for the Closed Alpha

After having successfully helped the first few users, Polkalytics is opening up for more participants. The fee to participate is 50 USD and will work on a first-come, first-served basis as capacity is available. Work in the coming months will focus on adding more chains and making reports available to as many people as possible at affordable prices.

If you want to skip the line, the current asking price is 125 USD.

There will be some promotional offers from time to time. Make sure to get them by subscribing to the [Polkalytics Newsletter](http://www.google.com/url?q=http%3A%2F%2Feepurl.com%2FihmNQ5&sa=D&sntz=1&usg=AOvVaw0nePZNUu6mJSYizfyZqqw3) and following [@Polkalytics on Twitter](https://www.google.com/url?q=https%3A%2F%2Ftwitter.com%2Fpolkalytics&sa=D&sntz=1&usg=AOvVaw2fHM8QbM5d%5FHTZj5U6OBGU).

bafyreihn2xoie7hhnkk5zzh4jrsopnpitcorkr7zob66yhsivn3ubtfms4

**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>

bafybeidf2tzbzwe73oozoww4n25cgxf7s6kj4gseqgnoxmzxapikqi2wii

OpenGov Scraper

**You are not thinking big enough!**

You think that on-chain Governance will decide inflation parameters or if we rather spend money on marketing or development or if we dig ourselves out of some narrative hole. You miss the bigger picture.

**Web3 is not yet a reality.**

The future of Web3 is fought out right now between the big crypto ecosystems and their VCs and it will be decided by who can bring the best utility to actual humans.

**To solve the big problems...**

Governance is not about your battle of the day. It's about the question: Can we solve the BIG problems that stand in the way between us and Web3 becoming a reality?

**... we need to build a cybernetic brain**

Web3 is too complex to be solved by foundations and core devs. We need a bigger brain. We need to build a system that is able to confront the big challenges of Web3 and develop solutions.

**You are the neuron.**

Governance is the way to decentralize problem-solving to hundreds and eventually thousands of network participants.

**Be hungry to win!**

We need grand strategies! We need to not only have great tech, but beat the competition. Build the stronger ecosystem. The better community. The more liquid capital base.

**Your mission**

You are not thinking big enough and it's about to get time! Switch gears and let your brain start grinding away. You need to think about solutions for the big problems.

**Web3 is a promise. OpenGov is the way.**

With Polkadot OpenGov, we maximize the rate of innovation, faster than any other eco. Together we will make it happen. This is our time!

bafybeibkqgzwmfrgwulx7qgiubnqk4hxddt642brfbin5ul3uavjgcz334

Our strategy to win Web3

A first attempt at integrating Grill with OpenGov.Watch

I’m just not very experienced in hacking Docusaurus 😅

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

bafybeigwdzv4lvjdptjm2ebqjp6hkxv7jt3kkagnykgylg2vwuryerjxka

**Should Polkadot Decoded tickets be free?**

Polkadot Decoded is right after ETH CC. Right now, tickets cost 150 EUR and ETH CC participants have lots of other free options.

It would be great if Decoded attracts more than just the usual suspects 

<https://polkadot.polkassembly.io/post/2229>

bafybeihpgkdylxh2zxop7kpwikuvfpq6go7duy6c4orwguznchf23fnbjq

bafyreibbry5lqdwmsg7e52wjhhvkph3l2o56sykgjs4v376h5uwtcbtota

Polkalytics

bafybeidim7mdwyw7o4tljmopc3srq2djxcmdivsfbmyzsxjulwlku4sv4q

OpenGov.Watch

bafyreierofnfes7qk5qaivrgeirye4sxzg3qe3dszgstz5hln26mhyixii

Alice und Bob

bafyreibi7ne2hl5f4dqie36ec7fadi3vpo5uanx6fk5qzldqehzz6y23fu

You are not thinking big enough!

You think that on-chain Governance will decide inflation parameters or if we rather spend money on marketing or development or if we dig ourselves out of some narrative hole. You miss the bigger picture.

Web3 is not yet a reality.

The future of Web3 is fought...

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...

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.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

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...

A first attempt at integrating Grill with OpenGov.Watch

I’m just not very experienced in hacking Docusaurus 😅

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...

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

Should Polkadot Decoded tickets be free?

Polkadot Decoded is right after ETH CC. Right now, tickets cost 150 EUR and ETH CC participants have lots of other free options.

It would be great if Decoded attracts more than just the usual suspects

https://polkadot.polkassembly.io/post/2229

A Google-Scale Analytics Service for Polkadot

With Polkalytics Tax Reports, you can finally get your Polkadot taxes done!

After announcing Subscrape to the world for the first time a little over a month ago, the library has grown quite a bit and today I am proud to announce v1.0 of Subscrape and present the roadmap for Subscrape 2.0

Releasing Subscrape v1.0

Subscrape is a Python scraper for Substrate chains that...

aka: “FINALLY I can get my Polkadot taxes done!”

Since March 2022, I have been building an analytics engine for Polkadot. The first product to launch on Polkalytics is personal reports of your on-chain activities that will finally enable you to do your taxes. In the future, Polkalytics will...

Starting next week, the Kusama Parachain Slot Auctions will see a drop in slot prices. Quartz is about to win the next slot tomorrow and currently the bid is 51k $KSM.

Share on Twitter

Hook

The name is decided: DotSwap

What is it?

A DEX on the common goods parachain Statemint (& Statemine) on Polkadot, with these goals:

Provide DOT liquidity against external tokens: BTC, ETH, KSM, USDT, USDC

yes, USDC is coming to Statemint

Enable Sufficient assets...

The first few hours and days understanding the Polkadot/Kusama/Substrate ecosystem can be rough. Where do you start your journey? Where do you get information? What can you trust?

To find your way around, we created this little guide with the most important websites and communities for your...

Hook

The name is decided: DotSwap

What is it?

A DEX on the common goods parachain Statemint (& Statemine) on Polkadot, with these goals:

Provide DOT liquidity against external tokens: BTC, ETH, KSM, USDT, USDC

yes, USDC is coming to Statemint

Enable Sufficient assets: Onboarding to Polkadot...

This article gives the first details on Polkalytics Account Reports, follows the path of an on-chain riddle, and begins the quest to survey the Polkadot Data Ecosystem

It always fascinated me how tens of thousands of people rush into Polkadot parachains to test them out and experience the...

This article gives the first details on Polkalytics Account Reports, follows the path of an on-chain riddle, and begins the quest to survey the Polkadot Data Ecosystem.

It always fascinated me how tens of thousands of people rush into Polkadot parachains to test them out and experience the...

bafybeihajth7lcs3uebq6djscvybxzsrij3hmazoazktohymdbi5yq2kua