Miscellaneous

<strong>The Forum serves as a digital town square to co-create the future of Polkadot by the ecosystem, for the ecosystem. Suggestions on how to improve the Forum live here.</strong>

The Forum serves as a digital town square to co-create the future of Polkadot by the ecosystem, for the ecosystem. Suggestions on how to improve the Forum live here.

Polkadot Forum Meta

A place for long-term, deep thinking on Polkadot technology.

Tech Talk

Governance discussion about the future of Polkadot and Kusama.

Governance

Everything that’s going on in the ecosystem, and what you wish would be going on in the ecosystem.

Ecosystem

Welcome to the Ambassador Category! Please use this space to discuss anything and everything related to the Polkadot Ambassador Programme.

Ambassador Programme

<aside class="quote no-group quote-modified" data-username="Alex" data-post="3" data-topic="7089">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/standard21/user_avatar/forum.polkadot.network/alex/48/765_2.png" class="avatar"> Alex:</div>
<blockquote>
<p>Short term allowing contracts on AssetHub is the most useful solution. Centralizing assets and contracts will no doubt provide the most value and lowest switching costs for Ethereum builders. It is most likely that this is the move that will give us the most traction in the short time. We should not be afraid of success (“AssetHub gets congested”).</p>
<p>But only if there is already a worth while ecosystem anyone would even care. We can’t expect them to go to a third party chain first. That is completely backwards. We have to put our horses behind a first party solution first (system chain) so that anybody even cares enough to look for third party scaling solutions. I firmly believe that the best candidate for a first party solution is a system chain. And more specifically AssetHub. We should not fragment the ecosystem more than we have to.</p>
</blockquote>
</aside>
<p><a class="mention" href="/u/alex">@Alex</a>  I put together this <a href="https://github.com/polkadot-fellows/RFCs/pull/66" rel="noopener nofollow ugc">RFC #66</a> – but since <a class="mention" href="/u/burdges">@burdges</a> says <a href="https://forum.polkadot.network/t/contracts-update-solidity-on-polkavm/6949" class="inline-onebox">Contracts Update: Solidity on PolkaVM</a> supersedes this RFC and polkavm contracts should definitely work, there might even be consensus on this.  However, I think its best if you + <a class="mention" href="/u/cyrill">@Cyrill</a> put an RFC together to crystalize it your way this month?</p>
<p>What is the hold up if not?</p>

Sourabh Niyogi

Hybrid system chains make Polkadot permissionless

Kazunobu Ndong

Joe Petrowski

Polkadot.js ledger support

<aside class="quote no-group" data-username="TimB" data-post="5" data-topic="7685">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://avatars.discourse-cdn.com/v4/letter/t/3e96dc/48.png" class="avatar"> TimB:</div>
<blockquote>
<p>Out of interest what would you say are the big ticket items the team wants to deliver next?</p>
</blockquote>
</aside>
<p>We always put at the very top of our priority list are the issues opened by the devs/teams that are using polkadot-api. Even if there is a lot of context-switching, we think that’s the right thing to do, because it helps at creating faster feedback loops, which we think is going to be very important for polishing the library for the delivery of the first stable version. Similarly, we try to spend as much time as possible in calls with different early adopters to better understand how they are using the library, what their thoughts are, the things that the docs didn’t explain properly, etc.</p>
<p>Then, leaving aside bug-fixing and other requested improvements, our main 3 focuses at this moment are:</p>
<h2><a name="h-1-tx-improvements-1" class="anchor" href="#h-1-tx-improvements-1"></a>1) Tx improvements:</h2>
<p>As I explained in the last <a href="https://forum.polkadot.network/t/polkadot-api-2024-q1-update/7462#transaction-enhancements-21">quarterly update</a> there are a number of improvements related with the handling of transactions that are quite urgent. Yours truly is the one leading this front. I have <a href="https://github.com/polkadot-api/polkadot-api/pull/486" rel="noopener nofollow ugc">already started</a> tackling this, but the main things that need to be improved are: revalidate transactions after they have been broadcasted (this is one of the most important items), allow advanced users to pass custom nonce when creating a transaction, inform earlier about the events related to the transaction (as of right now you have to wait until its finalized or query those on your own), and a few more items that I will eventually put in a long issue.</p>
<h2><a name="h-2-improve-docs-jsdocs-and-tests-2" class="anchor" href="#h-2-improve-docs-jsdocs-and-tests-2"></a>2) Improve docs, jsdocs and tests:</h2>
<p><a class="mention" href="/u/carlosala">@carlosala</a> is the one leading this front. We think that this is a win/win, because on the one hand it helps him at getting more familiar with the top-level API, and the other hand it gives him an opportunity to check <a href="https://github.com/polkadot-api/polkadot-api/pull/491" rel="noopener nofollow ugc">how things behave vs how things should behave</a>, etc. There is quite a lot of work to be done in this end, but I think that we are making really good progress.</p>
<h2><a name="h-3-improve-bundle-sizes-loading-times-and-typesdx-3" class="anchor" href="#h-3-improve-bundle-sizes-loading-times-and-typesdx-3"></a>3) Improve bundle-sizes, loading times and types/DX:</h2>
<p><a class="mention" href="/u/voliva">@voliva</a> is leading this end. He has already made <a href="https://github.com/polkadot-api/polkadot-api/pull/429" rel="noopener nofollow ugc">quite a bit</a> of <a href="https://polkadot-api.github.io/common-types-tool/" rel="noopener nofollow ugc">progress</a>, but there is quite <a href="https://github.com/polkadot-api/polkadot-api/issues/426" rel="noopener nofollow ugc">a bit more work</a> that needs to be done.</p>
<p>There are many other things that we would like to tackle, but we try to “pick our battles”, as they say. I mean, we also try to find some time to improve some of our inner libraries which can empower other dev-tool builders, but we think that our top priority at the moment should be to empower DApp builders.</p>

Josep

Polkadot-API updates thread

<aside class="quote no-group" data-username="davidsemakula" data-post="4" data-topic="7689">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/standard21/user_avatar/forum.polkadot.network/davidsemakula/60/2360_2.png" class="avatar"> davidsemakula:</div>
<blockquote>
<p>Do you use <a href="https://github.com/williamboman/mason.nvim" rel="noopener nofollow ugc">mason </a> or something similar?</p>
</blockquote>
</aside>
<p>im running modified <a href="https://www.lazyvim.org/" rel="noopener nofollow ugc">lazyvim</a> to make nvim more IDE-like without spending more time in configuration than actual development. its built on <a href="https://github.com/folke/lazy.nvim" rel="noopener nofollow ugc">lazy</a> does includes out of box support for Mason making plugin management very effortless. I think that would be best way to gain adaption for ink-analyzer as well.</p>

What IDE you use and where do yo learn

<p><strong>Name</strong><br>
Gatorkorps</p>
<p>** Your country and region.**<br>
France and French language countries / Europe</p>
<p>** A summary of your last six months of activities as an active member of the community.**<br>
Hey guys here is my resume:</p>
<ul>
<li>Polkadot decoded 23: video summary of developments (polkadot 2.0 explanation)<a href="https://www.youtube.com/watch?v=LP-bbPFBX4c" rel="noopener nofollow ugc">https://www.youtube.com/watch?v=LP-bbPFBX4c</a></li>
<li>Paris Dot Com 2023 organization / dj contact / NFT artist and press contact organisation/ management volunteer team <a href="https://www.youtube.com/watch?v=LurjIET95q4" rel="noopener nofollow ugc">https://www.youtube.com/watch?v=LurjIET95q4</a></li>
<li>NFT distribution and editing of all Paris Dot com panel recordings (73 vidéos  <a href="https://www.youtube.com/@polkadotfrancophonie2927/playlists" rel="noopener nofollow ugc">https://www.youtube.com/@polkadotfrancophonie2927/playlists</a></li>
<li>main media contact to organize interview about polkadot and project: <a href="https://twitter.com/20MintFR/status/1724062313290883463" rel="noopener nofollow ugc">https://twitter.com/20MintFR/status/1724062313290883463</a></li>
<li>weekly report of polkadot evolution and several gov evolution and drama ^^ (inform the french community, mainly on my twitter account) (exemple <a href="https://twitter.com/gk18_dog/status/1745778969020874820" rel="noopener nofollow ugc">https://twitter.com/gk18_dog/status/1745778969020874820</a>)</li>
<li>participation to circulated the pink games and other several games (share the good news and porpose to Phala network to jump in ) <a href="https://twitter.com/gk18_dog/status/1743226188795986084" rel="noopener nofollow ugc">https://twitter.com/gk18_dog/status/1743226188795986084</a></li>
<li>help to connect Phala and hydra DX omnipool (start in may finalize Q4 2023)</li>
<li>link between Logion (polkadot parachain) and others project <a href="https://twitter.com/gk18_dog/status/1744104450514473020" rel="noopener nofollow ugc">https://twitter.com/gk18_dog/status/1744104450514473020</a></li>
<li>share the good news (airdrop about aok, pink and peaq…)</li>
<li>to proove to the french crypto community the resilience of polkadot with encryption succes ( before doing it in real) <a href="https://twitter.com/gk18_dog/status/1747626489028214805" rel="noopener nofollow ugc">https://twitter.com/gk18_dog/status/1747626489028214805</a></li>
<li>contact with specialize french crypto media to share our polkadot vision and motivation <a href="https://twitter.com/Blockchains_FR/status/1748756794510360651" rel="noopener nofollow ugc">https://twitter.com/Blockchains_FR/status/1748756794510360651</a> (I also help to connect others parachains with them (<a href="https://www.youtube.com/watch?v=U83FwEG5FNs&amp;t=13s" rel="noopener nofollow ugc">https://www.youtube.com/watch?v=U83FwEG5FNs&amp;t=13s</a>   <a href="https://twitter.com/Blockchains_FR/status/1758892127415664865" rel="noopener nofollow ugc">https://twitter.com/Blockchains_FR/status/1758892127415664865</a> )</li>
<li>participation to the big Crypto XR (at my own cost) event to share our great ecosystem vision (polkadot is not very popular in france and we work everyday to change this <a href="https://twitter.com/gk18_dog/status/1750502578855559432" rel="noopener nofollow ugc">https://twitter.com/gk18_dog/status/1750502578855559432</a> )</li>
<li>connect with DJ to study possibility for polkadot dedicated event in paris (music and crypto meet up)) (ongoing now should be in june)</li>
<li>polkadot and parachain army to amplify our messages around big crypto account <a href="https://twitter.com/gk18_dog/status/1769350577626988620" rel="noopener nofollow ugc">https://twitter.com/gk18_dog/status/1769350577626988620</a></li>
<li>bring real use case and amplify the message of polkadot parachain in the media <a href="https://twitter.com/logion_network/status/1786443961814430029" rel="noopener nofollow ugc">https://twitter.com/logion_network/status/1786443961814430029</a></li>
<li>organisation of a Polkadot Party in Nantes (24th may you are welcome if you are available) <a href="https://www.eventbrite.com/e/polkadot-party-nantes-tickets-878867214497" class="inline-onebox" rel="noopener nofollow ugc">Polkadot Party - Nantes Tickets, Fri, May 24, 2024 at 6:00 PM | Eventbrite</a><br>
And more projects to come ! I</li>
</ul>
<p>** A paragraph explaining why you would like to benefit from sponsorship.**</p>
<p>I’d like to benefit from sponsorship to go to my 3rd decoded so I can continue to cover these events and report back to our community to show developments and be able to best present polkadot at future French events I’ll be organizing or participating in. I also think it’s very important to connect with other Ogs and ambassadors, so that we can continue to forge links and work together on different projects to help spread understanding of our ecosystem. These encounters are invaluable for gaining knowledge, discussing, debating, and moving forward towards our common goal. (as a french I also can check the croissant)</p>
<p>Merci, thanks and sorry for the long post <img src="https://emoji.discourse-cdn.com/twitter/slight_smile.png?v=12" title=":slight_smile:" class="emoji" alt=":slight_smile:" loading="lazy" width="20" height="20"></p>

gatorkorps

Decoded 2024 Sponsorship for active community members

<p>I support and participate in the  project and proposal as this will bring Polkadot into the Metaverse and bring 3D asset primitives to JAM.</p>

Douglas Kuhn

Afloat: On-chain 3D production and distribution

<p>Hi everyone,</p>
<p>The InvisibleHandLab Team is developing Kinera, a Decentralised Media Platform, for curation, moderation, audiovisual and streaming content co-creation.</p>
<p>This project has been in the works for two years, the Alfa version of the APP can be found at <a href="https://kinera.network/" rel="noopener nofollow ugc">https://kinera.network/</a>.</p>
<p>Today, we pushed a Polkassembly discussion to raise awareness about our work, receive feedback, and invite DOT holders to discuss funding to accelerate the development of the project.</p>
<p>The discussion can be found at <a href="https://polkadot.polkassembly.io/post/2297" class="inline-onebox" rel="noopener nofollow ugc">Kinera, a Decentralised Media Platform [Open discussion] | Polkassembly</a></p>
<p>Be ready for something completely new.<br>
We appreciate all constructive feedback and contributions.</p>
<p>Warm regards from the team.</p>

Miguel

Kinera, a Decentralised Media Platform [discussion]

<p>Following up on the call we had last Wednesday, here are the notes:</p>
<h3><a name="foreign-assets-registration-process-1" class="anchor" href="#foreign-assets-registration-process-1"></a>Foreign Assets Registration process</h3>
<p>Parity will enhance the documentation on <a href="https://github.com/paritytech/polkadot-sdk/issues/4335">how to create and use of foreign assets</a>, this will also be added to the <a href="https://github.com/paritytech/polkadot-sdk/pull/2633">XCM cookbook</a>.</p>
<h3><a name="user-stories-2" class="anchor" href="#user-stories-2"></a>User stories</h3>
<p><a class="mention" href="/u/joyce">@joyce</a> will be collecting use cases that are currently problematic (for users and/or for the parachains). All parachains should submit a detailed description of their use cases and the steps taken <a href="https://docs.google.com/spreadsheets/d/1Zt9eURzBxC2MQk1xTQwbBTQwLuHT9ASPYCq53LLZji8/edit#gid=0">in this sheet</a> <strong>until May, 17th</strong>. This will serve as the foundation to set up a project for: improving documentation, creating new guides and improving AH and its functionality.</p>
<p>The results of this use case investigation will be presented in the next Asset Hub Brainstorming Session. Going forward Joyce (PM) and <a class="mention" href="/u/liamaharon">@liamaharon</a> (Dev) are the main POCs for all topics related to Asset Hub.</p>
<h3><a name="velocitys-token-questionnaire-3" class="anchor" href="#velocitys-token-questionnaire-3"></a>Velocity’s Token Questionnaire</h3>
<p>The <a href="https://345paxyp4ve.typeform.com/token-economy">token economy survey</a> is still open and waiting for responses, the results for this will also be shared at the upcoming Asset Hub Brainstorming Session. For now, this questionnaire is only geared towards Parachains in order to find quick wins in terms of their token implementations/standards and bridges. In another round we can think of extending this questionnaire further to wallets and other stakeholders.</p>
<h3><a name="fee-payments-with-generic-assets-4" class="anchor" href="#fee-payments-with-generic-assets-4"></a>Fee payments with generic assets</h3>
<p>The asset conversion pallet is live on Polkadot and working, h<a href="https://github.com/TarikGul/ata-example/blob/f6c7f1d920c1d231a10eae01ef7bc1287fd9429b/index.ts">ere’s a JavaScript script</a> that Joe generated, it showcases how to create a pool, make a transaction, swapping assets in the pool in order to pay the fee and paying fees in that token.</p>
<p>We currently can’t pay XCM delivery fees with any assets other than DOT/KSM, but non-XCM transaction fee payment works fine - <a href="https://github.com/paritytech/polkadot-sdk/issues/3958">here</a> is the issue to it.</p>
<p>Long term vision for the usage of the asset conversion pallet should be that users and parachains can use Asset Hub and pay their (transaction) fees with the parachain’s assets without having any DOTs, for that we also need to maintain the pools funded.</p>
<h3><a name="existential-deposits-via-asset-conversion-5" class="anchor" href="#existential-deposits-via-asset-conversion-5"></a>Existential deposits via Asset Conversion</h3>
<p><a href="https://github.com/polkadot-fellows/RFCs/pull/11">RFC 11 (rejected)</a> proposed using asset conversion to create new accounts/funding the existential deposit. When transferring assets to accounts without existential deposits, you could convert the asset to acquire the existential deposit by debiting it via the asset that you’re sending. Problem with that was that users would be confused if the amount of assets arriving would be less than the amount sent. Another problem is that currently parachains can’t tell if the account exists/has existential deposit on asset hub or not, ideally you could pull this information from an XCM call and tell the user, which can then decide if they want to proceed with the transaction or not.</p>
<p>General goal is to allow users to do balance transfers in any asset and cross-chain, the question is now where the complexity should reside. More discussion around this will follow on the forum.</p>
<p>Ramp network has an implementation of Parachain deposits using asset conversion ready, it will be rolled out after testing and if it works Parachains can integrate it as well.</p>
<h3><a name="issue-with-dot-as-a-reserve-on-rc-and-ah-forum-post-discussion-herehttpsforumpolkadotnetworktmanaging-sas-on-multiple-reserve-chains-for-same-asset75381-6" class="anchor" href="#issue-with-dot-as-a-reserve-on-rc-and-ah-forum-post-discussion-herehttpsforumpolkadotnetworktmanaging-sas-on-multiple-reserve-chains-for-same-asset75381-6"></a>Issue with DOT as a reserve on RC and AH (forum post discussion <a href="https://forum.polkadot.network/t/managing-sas-on-multiple-reserve-chains-for-same-asset/7538/1">here</a>)</h3>
<p>Forum Post TL;DR: Migrate the DOT reserves of all parachains into Asset Hub and have Asset Hub as the main hub for the reserves of all assets, not only DOT. So you only have to have application specific channels and not asset specific channels in order to do transfers.</p>
<p>The migration should be done Parachain per Parachain and be individually adapted, so that everyone moves to the new logic - Parity is willing to support teams with technical questions to that. Still a generic migration would be desirable, for that the only solution currently proposed is to <a href="https://forum.polkadot.network/t/managing-sas-on-multiple-reserve-chains-for-same-asset/7538#automated-sas-rebalancing-4">create a pallet</a> that automatically handles your software accounts.</p>
<p>Having Asset Hub as the main reserve location could also open up the possibility of <a href="https://forum.polkadot.network/t/remote-stake-any-asset-on-asset-hub/4210">staking via Asset Hub</a>.</p>
<h3><a name="address-format-unification-forum-discussion-herehttpsforumpolkadotnetworktux-proposal-consensus-based-address-formats60721-7" class="anchor" href="#address-format-unification-forum-discussion-herehttpsforumpolkadotnetworktux-proposal-consensus-based-address-formats60721-7"></a>Address format unification (forum discussion <a href="https://forum.polkadot.network/t/ux-proposal-consensus-based-address-formats/6072/1">here</a>)</h3>
<p>Will be discussed with UX/UI teams (wallets, etc.)</p>
<h3><a name="xcm-fees-estimation-8" class="anchor" href="#xcm-fees-estimation-8"></a>XCM fees estimation</h3>
<p>Parity has designed and proposed some runtime APIs that would make it easy to estimate complex multi-hop, multi-chain asset transfers. The proposal can be found <a href="https://github.com/paritytech/polkadot-sdk/pull/3872">here</a> and they’re awaiting feedback.</p>
<h3><a name="funds-stuck-when-sending-meme-coins-through-asset-hub-9" class="anchor" href="#funds-stuck-when-sending-meme-coins-through-asset-hub-9"></a>Funds stuck when sending meme coins through Asset Hub</h3>
<p>Some users faced an issue with transferring assets from HydraX to AssetHub. USDTs were trapped during the transfer due to a misconfiguration of the fee. The amount of USDT sent was too small to cover the processing fees on AssetHub, leaving the funds stuck and inaccessible, even though the amount of DED included in the transaction was big enough to cover all the fees. There is a mechanism allowing users to claim their assets, but it doesn’t help because the trapped amount is too small to pay the necessary fees. The current claim mechanism expects all fees to be covered by the claimed amount itself, even governance won’t help here since the amounts are too little. Parity wants to work on a better claiming mechanism.</p>
<p>Related issue by <a class="mention" href="/u/xlc">@xlc</a> : <a href="https://github.com/paritytech/polkadot-sdk/issues/901">https://github.com/paritytech/polkadot-sdk/issues/901</a></p>
<h3><a name="transfers-from-kusamas-treasury-to-a-parachains-polkadot-account-10" class="anchor" href="#transfers-from-kusamas-treasury-to-a-parachains-polkadot-account-10"></a>Transfers from Kusama’s treasury to a Parachain’s Polkadot account</h3>
<p>The goal is to add KSMs to the Hydra DX Omnipool, which is on Polkadot. The plan is to transfer KSM from the Kusama treasury to Hydra using the Kusama&lt;&gt;Polkadot bridge. However, the existing reserve transfer process only allows hopping between asset hubs, preventing a direct transfer from the Kusama relay chain to HydraX.</p>
<p>Hydra is asking for a XCMs call to facilitate the transfer, which will include multiple hops from Kusama to Hydra. Parity already has a solution for that which will be included in XCMv5.</p>
<h3><a name="action-items-11" class="anchor" href="#action-items-11"></a>Action items</h3>
<p><a class="mention" href="/u/nico_a">@nico_a</a> and <a class="mention" href="/u/joyce">@joyce</a> to present the results from the token economy survey and the use cases</p>
<p><a class="mention" href="/u/joepetrowski">@joepetrowski</a> to open up the discussion on ED again</p>
<p><a class="mention" href="/u/acatangiu">@acatangiu</a> to share the XCM call for facilitating transfers from Kusama to Polkadot</p>
<p><a href="https://drive.google.com/file/d/1h_Hvqk_eQdz5RujKY7tf2dG2C5oD8FIb/view?ts=6634b81a">CALL RECORDING</a></p>

Joyce Siqueira

Asset Hub Brainstorming Session - Call Notes and Discussion Continuation

<p>Excuse me for being blunt, but who actually are you?</p>

Oliver Brett

peter

Update the Decoded logo + CoreJAM banners for Q2 Marketing

<p>This is a great post, thank you!</p>
<p>If I may add a comment from product marketing side to the product team that will build XCMP: We had a big initiative to rename XCM because of the confusion it caused with XCMP. In the end, we decided not to rename it because XCM was already established as a brand, in the ecosystem, in the code - and it’s actually a good name. We said we will, when it becomes clear who will work on XCMP, nudge the team to come up with another name.</p>
<p>Whoever is brainstorming: In general a descriptive name is good, here, a branded name (such as “Polkadot xyz”) or a non-descriptive name (such as “StreetTalk”) are not appropriate, because we are looking at a transport protocol very down in the stack.</p>
<p>Basically something like XCMP but without “XCM” in it <img src="https://emoji.discourse-cdn.com/twitter/+1.png?v=12" title=":+1:" class="emoji" alt=":+1:" loading="lazy" width="20" height="20"></p>

Natalie Tillack

XCMP Design Discussion

<p><a class="mention" href="/u/muddlebee">@muddlebee</a> Always tricky to give a timeline <img src="https://emoji.discourse-cdn.com/twitter/slightly_smiling_face.png?v=12" title=":slightly_smiling_face:" class="emoji" alt=":slightly_smiling_face:" loading="lazy" width="20" height="20">. The feature is <a href="https://github.com/paritytech/polkadot-sdk/pull/3905" rel="noopener nofollow ugc">code complete</a>, has got at least one approval and is pretty imminent on Westend. It is still undergoing audit, and if no new issues/bugs are found, could potentially go live on Kusama/Polkadot by early Q3.</p>

muddles

ParityTech update for April 2024

<h2><a name="polkadot-news-1" class="anchor" href="#polkadot-news-1"></a>Polkadot News</h2>
<p>The Ending Period of a new parachain lease auction has begun Aventus is currently in the lead. <a href="https://parachains.info/auctions" class="inline-onebox" rel="noopener nofollow ugc">Auctions and crowdloans on Polkadot &amp; Kusama networks | Parachains.info</a></p>
<p>Referendum 682, proposing to ratify moving Polkadot towards JAM, is passing almost unanimously (46 million DOT Aye to 16 DOT Nay) <a href="https://polkadot.polkassembly.io/referenda/682" class="inline-onebox" rel="noopener nofollow ugc">Proposal for JAM Ratification, Conformance, Performance by Polkadot Fellows | Polkassembly</a></p>
<p>The staking rate on Polkadot continues to increase and is now at 54.5%. <a href="https://staking.polkadot.network/#/overview" class="inline-onebox" rel="noopener nofollow ugc">Polkadot Staking Dashboard | Polkadot Staking (DOT)</a></p>
<p>The W3F Technical Education Team has announced EduChain, to be used for creating tutorials on Polkadot SDK features. <a href="https://github.com/w3f/educhain" class="inline-onebox" rel="noopener nofollow ugc">GitHub - w3f/educhain: Parachain developed and maintained by Tech Ed team</a></p>
<h2><a name="kusama-news-2" class="anchor" href="#kusama-news-2"></a>Kusama News</h2>
<p>Referendum 388, enabling the Identity pallet again (on the People chain instead of the Relay chain), is now up for vote on the Whitelisted Caller track. <a href="https://kusama.polkassembly.io/referenda/388" class="inline-onebox" rel="noopener nofollow ugc">Enable Identity Again on People Chain | Polkassembly</a></p>
<p>Note that this is part of the move towards a “hermit relay chain”, where the Relay Chain focuses on parachain validation and all other capabilities (e.g. staking, governance, etc.) move to parachains.</p>
<p>Referendum 384, proposing to register the People Chain and upgrade the Coretime chain runtime to v1.2.3, is now up for vote. <a href="https://kusama.polkassembly.io/referenda/384" class="inline-onebox" rel="noopener nofollow ugc">Register People Chain and upgrade Coretime Chain to v1.2.3 | Polkassembly</a></p>

bill_w3f

Polkadot Digest 6 May 2024

<p>Listening to your points <a class="mention" href="/u/exquisitus">@Exquisitus</a>, it sounds Discord is a very useful tool for building a community, which is incredibly important to us for the Pop platform. Thank you for the valuable feedback!</p>

Daan van der Plas

Gianluigi Davassi

R0GUE: Reimagining Polkadot Development with POP

<p>I am human.</p>
<p>Please review the Forum’s code of conduct, and if you are a non-native English user, maybe it will help if you make use of translation software like DeepL or even a chatbot–currently your posts are not very comprehensible.</p>

Alfonso Sandro Gómez Gómez

Algeciras(Cádiz) España. Meblillo co-work

<p>Koinly so far is probably the best tax and portfolio tracking software. They have the most advanced features with the nicest user interface. The only problem is they do not fully support Dot yet. I think this is part of the reason why Dot adoption has not been as successful as we had hoped it would be.</p>
<p>Currently, I have to track my Dot transactions manually and that’s fairly difficult to do. My totals always come out being a bit off. This mostly has to do with DeFi transactions on Subscan not being the most human readable. That could definitely use some improvements. But, for now I think it’s more important for our parachains to be seamless for the end user wanting to track their portfolio and tax burden.</p>
<p>I currently have a support message out asking them how much they’d need to give us priority for adding support for the existing parachains. I’ll gladly propose a referendum with funds needed from the Dot treasury once I hear back from them. But, till then I think we should discuss developing a useable solution for users. I have a feeling a ton of users are afraid of tax compliance, and that’s partially responsible for the liquidity issues many of the parachains are experiencing. Manual tracking of these transactions is just too easy to lead to misreporting of earnings for tax purposes, and any potential fine could easily outweigh any gains.</p>
<p>So, what would the community want before paying Koinly to give us priority?</p>

Koinly tax support

<p>That seems reasonable.</p>
<p>My understanding was the current use case was as you note:</p>
<aside class="quote no-group quote-modified" data-username="burdges" data-post="3" data-topic="7438">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/standard21/user_avatar/forum.polkadot.network/burdges/48/172_2.png" class="avatar"> burdges:</div>
<blockquote>
<p>It’s possible “threshold validator” would provide operational security benefits for validator operators…</p>
</blockquote>
</aside>
<p>and to do so independently of the RC configuration/preferences.</p>
<aside class="quote no-group quote-modified" data-username="burdges" data-post="3" data-topic="7438">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/standard21/user_avatar/forum.polkadot.network/burdges/48/172_2.png" class="avatar"> burdges:</div>
<blockquote>
<p>… If we needed more “decentralization” then we should adjust our parameters.</p>
</blockquote>
</aside>
<p>Agreed. Although my use case is subtly different: The Attribute X may be adequate for Property Y, but inadequate for Property Z.  That is on me - I did weakly cast this as being validator specific, but it needn’t be.  What is generic is the presence of more than one RC.</p>
<aside class="quote no-group quote-modified" data-username="burdges" data-post="3" data-topic="7438">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/standard21/user_avatar/forum.polkadot.network/burdges/48/172_2.png" class="avatar"> burdges:</div>
<blockquote>
<p>We do actively develop the relay chain, adding features &amp; improving performance, but…</p>
<p>At present, we’ve no resoruce pressure on polakdot,…</p>
</blockquote>
</aside>
<p>I’m not disputing the RC development pace, and the use case is more strategic than tactical.  But, as I acknowledged, this use case is a non-speculative token and that is categorically different from DOT.</p>
<p>So far, as best I can tell, the differences fall within the scope of parameter settings. Apologies for not being clearer, the RC code base is working its way up my todo list.</p>
<p>This should focus things: Are there integration (or unit) tests exercising the multi-RC use case? Or even documented rules-of-thumb about the trade-offs?</p>
<aside class="quote no-group" data-username="burdges" data-post="3" data-topic="7438">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/standard21/user_avatar/forum.polkadot.network/burdges/48/172_2.png" class="avatar"> burdges:</div>
<blockquote>
<p>You could bridge polkadot, kusama, and similar projects, but these bridges require 2/3rd honesty on both sides,</p>
</blockquote>
</aside>
<p>Here you mean non-BEEFY bridges? Or does BEEFY share these properties?</p>
<aside class="quote no-group" data-username="burdges" data-post="3" data-topic="7438">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/standard21/user_avatar/forum.polkadot.network/burdges/48/172_2.png" class="avatar"> burdges:</div>
<blockquote>
<p>like what cosmos assumes. You’d expect social engeneering attacks bring down cosmos-like bridge ecosystems eventually.</p>
</blockquote>
</aside>
<p>I’m inclined to agree with your GH comment that OmniLedger probably has some useful insights/results.</p>

Polkadot

referenda72

treasury151

discussions16