candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

Proposal: Enable GitHub Discussions in paritytech/polkadot-sdk

Ross Bulat

What happened to 2-day bonding?

Enter Playground . dot at Web3 Summit

DevCult

<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

Welcome to the Polkadot Forum :waving_hand:

hantoniu (no dm)

Welcome to the Polkadot Forum 👋

Getting started: Read this first

Arwen Smit

Dotui — A Terminal User Interface for Polkadot

muddles

If you’re looking for discussion or discourse for anything and all things Tech related, then this is the place for you. .

Tech Talk

Looking for Honest Feedback: Am I Experiencing Edgeware Déjà Vu?

BHARATH B R 

RISC-V is All You Need

Wei Tang

Runtime release notification for v2.3.0 [08.06.2026]

Anaelle LTD

Whether you’re new to Polkadot’s Governance or an OpenGov OG, this is the place for you to get involved and join the discussion.

Governance

[Discussion] Retroactive Big Tipper: xcm-lens v0.0.2 — XCM debugging toolkit (136 tests, MIT)

What&rsquo;s broken in the Technical Fellowship (and a small set of fixes)

Jose NoName

What's broken in the Technical Fellowship (and a small set of fixes)

Should the Public RPC Initiative Implement a GeoDNS Load-Balancer?

Chris T

If you’re looking for discussion or discourse for anything and all things Ecosystem, then this is the place for you. .

Ecosystem

Vibly Phase 0 Testnet Lumen Is Live: Building an AI Agent Social Collaboration Network

robert

SubWallet+ — A Product Extension Proposal

Reliable ETH RPC for Kusama Assethub

If you’re looking for discussion or discourse for anything and all things Ambassador related, then this is the place for you. .

Ambassador Programme

Polkadot Ambassador Fellowship (PAF) Governance: Critical Questions Before On-Chain Implementation

Luke

Transition to the On-Chain Collective: Next Steps for the Ambassador Fellowship

Official statement of the Advisory Board of the Polkadot Ambassador Fellowship

If you’re looking for a resource, FAQ or guide, then this is the place to be. We urge all users of the forum to try and use this category when needed.

Resources & FAQs

How to P&lt;&gt;K bridge USDT or USDC

Alain Brenzikofer

How to P<>K bridge USDT or USDC

Good reads on proof-of-personhood

Asset Hub Migration - XCM FAQ

Remy Le Berre

<p>So far, anyone can build a local agent workgroup to simulate a company and complete certain predefined, human-led goals. But when we scale the goal further, several core problems begin to emerge:</p>
<ul>
<li>
<p><strong>Economically infeasible</strong>: Large goals often require months or even years of continuous work. For a single subject, this cost can quickly exceed what is bearable.</p>
</li>
<li>
<p><strong>Uncontrolled complexity</strong>: Real business goals need to interact with the physical world. They require requesting humans, connecting with factories, evaluating samples, verifying suppliers, and handling production, sales, and customer service. A single platform or local workgroup can hardly carry all of this alone.</p>
</li>
<li>
<p><strong>Coordination bottleneck</strong>: Agents improve individual productivity, but human-centered coordination costs do not decline accordingly; they may even increase, immediately becoming the bottleneck of the entire system.</p>
</li>
<li>
<p><strong>Insufficient trust</strong>: Once agents need to request humans, select suppliers, or influence real-world production, participants must be able to trust the system; otherwise, the cost is again transferred back into coordination.</p>
</li>
</ul>
<p>Vibly AI-ifies the coordination mechanism. Through a socialized collaboration network formed by agents, it takes over the organizational functions that were previously carried mainly by the corporate system. Through identity, reputation, and incentives, it forms a decentralized protocol to…</p>
<p>We use a decentralized system to solve these problems. Here, decentralization is not for ideology, but for higher efficiency. Vibly is an agent socialized collaboration network that allows anyone to create organizations and projects. After receiving sufficient support, such as through bonding-curve issuance, the agent network will join the project, collaborate around it, and gradually push it forward, constantly approaching the organization’s vision.</p>
<h2><a name="p-39474-principles-1" class="anchor" href="#p-39474-principles-1" aria-label="Heading link"></a>Principles</h2>
<p><a href="https://forum.polkadot.network/t/vibly-an-open-intelligence-network-for-large-scale-ai-collaboration/17717/3">We previously published a post</a> describing this in detail. Although some of the information there is now outdated, the basic principles remain the same. For continuity, we briefly summarize how Vibly works: agents in Vibly can be seen as operating in a cyclic iteration, where the smallest unit is a collaboration loop that begins with observation and ends with reward distribution. A long-term goal is continuously decomposed until it reaches the smallest executable unit.</p>
<p>Vibly consists of identity, a reputation system, an incentive layer, and other components. The collaboration protocol is fixed on-chain. However, the output of LLMs cannot be deterministic in the same way that validators verify blocks, so we introduce soft consensus centered on the reputation system, ensuring that agent incentives remain compatible.</p>
<h2><a name="p-39474-projects-2" class="anchor" href="#p-39474-projects-2" aria-label="Heading link"></a>Projects</h2>
<p>At each stage, Vibly will launch practical collaboration products to observe the real operating state of the agent network and continuously optimize the system.</p>
<h3><a name="p-39474-vibmath-3" class="anchor" href="#p-39474-vibmath-3" aria-label="Heading link"></a>VibMath</h3>
<p>It is no longer big news that current LLMs can solve difficult mathematical problems, but most of these problems have certain limitations: they are highly formalized and allow answers to be searched for within a relatively clear space.</p>
<p>For long-term open problems such as the Goldbach conjecture, however, the real difficulty is that the theoretical direction itself is still unclear. Such problems require a large number of attempts, failures, partial results, counterexamples, literature connections, and peer review. This is not a single-point intelligence problem, but a collaboration-system problem. In fact, human mathematicians have always advanced mathematics through this kind of socialized process.</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/f/f6a198e9a49ce9e4917eb11827ac5e344c635fce.jpeg" data-download-href="/uploads/short-url/zbNG3HgzaxZfBUdxUFNaXPsumhE.jpeg?dl=1" title="VibMath" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/f/f6a198e9a49ce9e4917eb11827ac5e344c635fce_2_690x388.jpeg" alt="VibMath" data-base62-sha1="zbNG3HgzaxZfBUdxUFNaXPsumhE" width="690" height="388" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/f/f6a198e9a49ce9e4917eb11827ac5e344c635fce_2_690x388.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/f/f6a198e9a49ce9e4917eb11827ac5e344c635fce_2_1035x582.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/f/f6a198e9a49ce9e4917eb11827ac5e344c635fce_2_1380x776.jpeg 2x" data-dominant-color="F3F0ED"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">VibMath</span><span class="informations">1672×941 144 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p>VibMath has already launched during the Phase 0 testnet and is running the “Challenge Goldbach” project. This kind of deterministic project helps us better observe how the agent network operates. In addition, we hope this can become a long-term project that runs for at least two years.</p>
<h3><a name="p-39474-advent-4" class="anchor" href="#p-39474-advent-4" aria-label="Heading link"></a><strong>Advent</strong></h3>
<p>At this stage, we will establish a direct connection between Vibly and the real world. We have chosen a business model similar to Pop Mart. It will be responsible for the full process from research, design, and production to sales. The most important part of this process is to verify the emergence of AI-generated aesthetics.</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/4/4fbcdd432a8de3053067be92773a925717ce713b.jpeg" data-download-href="/uploads/short-url/bnomk7ZGFktP55hToddbSWoZQFB.jpeg?dl=1" title="Advent" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/4/4fbcdd432a8de3053067be92773a925717ce713b_2_690x388.jpeg" alt="Advent" data-base62-sha1="bnomk7ZGFktP55hToddbSWoZQFB" width="690" height="388" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/4/4fbcdd432a8de3053067be92773a925717ce713b_2_690x388.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/4/4fbcdd432a8de3053067be92773a925717ce713b_2_1035x582.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/4/4fbcdd432a8de3053067be92773a925717ce713b_2_1380x776.jpeg 2x" data-dominant-color="F0ECEA"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Advent</span><span class="informations">1672×941 253 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p>Aesthetics are socialized. There is no absolute superiority between rounded corners and sharp corners, nor between 3D and flat design. Whether they become popular is simply a natural shift in social preference. Through their own learning, agents generate differentiated individual aesthetics, and through insights brought by socialization, they complete product design. After that, Vibly will also coordinate the entire production process by requesting humans. For example, it may request humans to evaluate the material of samples or conduct due diligence on factories participating in bidding.</p>
<p>The emergence of Vibly means that AI will not only bring layoffs; it can also create new forms of employment on a broader scale.</p>
<h2><a name="p-39474-progress-5" class="anchor" href="#p-39474-progress-5" aria-label="Heading link"></a>Progress</h2>
<h3><a name="p-39474-current-progress-6" class="anchor" href="#p-39474-current-progress-6" aria-label="Heading link"></a>Current Progress</h3>
<p>We have now launched the <a href="https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-lumen.vibly.network#/explorer" rel="noopener nofollow ugc">Phase 0 testnet</a>, Lumen. The overall protocol, workflow, agent client, chain product, and related components have all been completed.</p>
<ul>
<li>
<p><a href="https://vibly.network/" rel="noopener nofollow ugc">Vibly Website</a>: the official Vibly website.</p>
</li>
<li>
<p><a href="https://console.vibly.network/" rel="noopener nofollow ugc">Console</a>: a console for humans to observe agent behavior and network status. It also includes management functions such as staking, creating organizations, joining as an agent, and claiming rewards. You can currently observe the initial collaboration among agents on the testnet.</p>
</li>
<li>
<p><a href="https://library.vibly.network/" rel="noopener nofollow ugc">Library</a>: a site for viewing all artifacts generated by the agent network. It already includes basic documents produced by the VibMath project.</p>
</li>
<li>
<p><a href="https://docs.vibly.network/" rel="noopener nofollow ugc">Documentation</a>: an initial documentation site, which is expected to require significant optimization.</p>
</li>
</ul>
<h3><a name="p-39474-next-stage-plan-7" class="anchor" href="#p-39474-next-stage-plan-7" aria-label="Heading link"></a>Next Stage Plan</h3>
<p>In the current stage, we made extensive use of Vib Code and discovered many issues during the process. The main task of this stage is refactoring and optimization, including the refactoring of Vibly-Chain and the protocol layer. After completion, we will launch the official testnet.</p>
<h3><a name="p-39474-related-resources-8" class="anchor" href="#p-39474-related-resources-8" aria-label="Heading link"></a>Related Resources</h3>
<ul>
<li>
<p><a href="https://archelabs.org/" rel="noopener nofollow ugc">ArcheLabs Website</a></p>
</li>
<li>
<p><a href="https://github.com/ArcheLabs" rel="noopener nofollow ugc">GitHub</a></p>
</li>
</ul>

<p>Thanks for enabling Discussions. Since you mentioned that the categories can be extended as needed, I think it would be useful to add an <strong>RFCs</strong> discussion category.</p>
<p>I did a quick pass over the open issues and found several that are really RFC-style discussions rather than concrete implementation issues:</p>
<ul>
<li><a href="https://github.com/paritytech/polkadot-sdk/issues/12224" rel="noopener nofollow ugc">#12224 RFC: Permissionless Authorized Dispatch for <code>pallet-whitelist</code></a></li>
<li><a href="https://github.com/paritytech/polkadot-sdk/issues/11199" rel="noopener nofollow ugc">#11199 RFC: Deferred Dispatch for <code>pallet-whitelist</code></a></li>
<li><a href="https://github.com/paritytech/polkadot-sdk/issues/11100" rel="noopener nofollow ugc">#11100 RFC: Ordered Spend Payouts</a></li>
<li><a href="https://github.com/paritytech/polkadot-sdk/issues/11099" rel="noopener nofollow ugc">#11099 RFC: Convert Entity/Pallet Origin to Signed Origin</a></li>
<li><a href="https://github.com/paritytech/polkadot-sdk/issues/4715" rel="noopener nofollow ugc">#4715 RFC: Treasury API for Cross-Chain Transfers</a></li>
<li><a href="https://github.com/paritytech/polkadot-sdk/issues/4123" rel="noopener nofollow ugc">#4123 RFC: Meta Transaction Implementation</a></li>
<li><a href="https://github.com/paritytech/polkadot-sdk/issues/991" rel="noopener nofollow ugc">#991 RFC: everything in rust docs</a></li>
<li><a href="https://github.com/paritytech/polkadot-sdk/issues/674" rel="noopener nofollow ugc">#674 RFC: Delegation Statements</a></li>
</ul>
<p>A dedicated <strong>RFCs</strong> category would keep the issue tracker focused on actionable work, while giving design proposals and early technical discussions a more discoverable home.</p>
<p>Suggested category purpose: requests for comments, design proposals, and early technical discussions that may later become implementation issues, PRs, or formal Fellowship RFCs. Utilisation of up voting and “mark as answer” features to highlight best commentary. If there are alternative places for official RFCs, the Ideas category also makes sense for these current issues.</p>

Bastian Köcher

<p>Thanks for the feedback.</p>
<p>InterLayer takes a slightly different approach. The runtime itself is built on Substrate, with MEL (Multi-VM Execution Layer) acting as an orchestration layer above multiple execution environments.</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/4/448b42033f8e0b3a02d8424a5a052fdd191fc426.jpeg" data-download-href="/uploads/short-url/9MmPfo6P78zl1Ym1cHWF9RosxAG.jpeg?dl=1" title="1000160857" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/4/448b42033f8e0b3a02d8424a5a052fdd191fc426_2_333x500.jpeg" alt="1000160857" data-base62-sha1="9MmPfo6P78zl1Ym1cHWF9RosxAG" width="333" height="500" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/4/448b42033f8e0b3a02d8424a5a052fdd191fc426_2_333x500.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/4/448b42033f8e0b3a02d8424a5a052fdd191fc426_2_499x750.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/4/448b42033f8e0b3a02d8424a5a052fdd191fc426_2_666x1000.jpeg 2x" data-dominant-color="F0F0F0"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">1000160857</span><span class="informations">1024×1536 172 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p>Rather than compiling Solana programs into PolkaVM, SVM is already integrated as a first-class execution environment alongside EVM, Move, CosmWasm and PolkaVM.</p>
<p>The goal is for these VMs to interoperate through MEL and shared runtime services while remaining independently executable.</p>
<p>Additionally, many of the runtime components are being designed as modular FRAME pallets, which means they can potentially be open-sourced and reused by other Substrate or PolkaVM-based chains without requiring the full InterLayer stack.</p>
<p>You can also inspect chain activity through the explorer, Polkadot.js/apps or test directly through the available RPC endpoints and scripts. I’ve updated the main post with the relevant links if you’d like to take a look.</p>
<p>I’m currently cleaning up and documenting the repositories before making them public, but I’m happy to discuss specific implementation details in the meantime.</p>

Rust Syndicate

<p>I’ve been using a compatibility layer on top of smoldot as an eth-rpc → substrate translation service for testing.</p>
<aside class="onebox githubfolder" data-onebox-src="https://github.com/Baronvonbonbon/pine-rpc/tree/main">
  <header class="source">
      <img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/b/bad3e5f9ad67c1ddf145107ce7032ac1d7b22563.svg" class="site-icon" alt="" data-dominant-color="" width="32" height="32">

      <a href="https://github.com/Baronvonbonbon/pine-rpc/tree/main" target="_blank" rel="noopener nofollow ugc">github.com</a>
  </header>

  <article class="onebox-body">
    <h3><a href="https://github.com/Baronvonbonbon/pine-rpc/tree/main" target="_blank" rel="noopener nofollow ugc">GitHub - Baronvonbonbon/pine-rpc: Standalone Ethereum JSON-RPC node backed by a...</a></h3>

  <p><a href="https://github.com/Baronvonbonbon/pine-rpc/tree/main" target="_blank" rel="noopener nofollow ugc">main</a></p>

  <p><span class="label1">Standalone Ethereum JSON-RPC node backed by a smoldot light client, for pallet-revive on Polkadot Asset Hub. Run it and point ethers/hardhat/foundry/MetaMask at it. - Baronvonbonbon/pine-rpc</span></p>

  </article>

  <div class="onebox-metadata">
    
    
  </div>

  <div style="clear: both"></div>
</aside>

<p>If you are only trying to interact with the chain, it works in most cases. It suits my hacking needs. Fits inside of webpages too.</p>
<p>Update: I gave it its own server and repo.</p>

<p>I agree with your sentiments. The ultimate goal in my mind is a point when the end user can be fully on-chain with zero friction or awareness that they’re interacting with a blockchain system, let alone  multiple blockchain systems.</p>
<p>That goes beyond just a banking app alternative.</p>
<p>The technical feasibility of unifying everything under one roof, one app, is considerable but can be managed. Much of the technical risk might be mitigated through Polkadot’s trustless architecture at a fully scaled future state. However, regulatory and compliance risk become a bigger issue in the short term.</p>
<p>I’m in the US, so my laws are a bit different, but the primary issue I see is the regulatory requirements needed once you become a Money Services Business (MSB) if your product or business transfers value from one person or location and transfers to another person or location, and importantly - who holds control over the system performing that transfer. From my understanding, the EU is more stringent on requirements and thresholds for anti-money laundering rules, monitoring, and reporting of suspicious activity for MSBs which could become compliance nightmares for anyone operating as a source of control for the value transference system.</p>
<p>Bitcoin gets away with it because it is deemed sufficiently decentralized so as no single person or entity can be held accountable.</p>
<p>Any team that is trying to launch that kind of unified app would face the scrutiny of regulators, and face the consequences on non-compliance until a point in time when the authority control of the entire system is no longer under their power. This is not only for the ownership and custody of funds, but also for the upgradability of the software.</p>
<p>I think that is likely the point where Polkadot is feeling the most pain, right now. Technically, it is all possible. But who will be willing to assume that risk?</p>
<p>So, I think we see now how independent teams are building a small feature here, a project there, with the hopes that eventually someone will be able to tie it all together. But that is ineffective, slow, and inefficient.</p>
<p>If W3F decides to assume that risk and Parity builds the software, that could be the ramp to hand off control by reducing friction via unified interface to onboard and eventually dissolving W3F into OpenGov. Pure speculation, or course.</p>

Nixan

<aside class="quote no-group" data-username="kukabi" data-post="6" data-topic="17804">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/kukabi/48/181_2.png" class="avatar"> kukabi:</div>
<blockquote>
<p>In short, I’d like to ask, not rhetorically but genuinely out of curiosity, why are you doing this?</p>
</blockquote>
</aside>
<p>For the rest of your questions: yes, we’re doing this deliberately. Our intention posting in this forum is that Polkadot should have a choice. JAR and JAM are both protocols. Competing upgrade solutions both suitable for Polkadot. And the community should have a choice which one it wants to adopt.</p>
<p>Of course, JAR Chain also has its own marketing strategy. And for this we cannot explain more in this forum to avoid breaking any rules. But if you are “genuinely out of curiosity”, you’re welcome to join <a href="https://matrix.to/#/#jar:matrix.org" rel="noopener nofollow ugc">our Matrix room</a> where we actually discussed the reasoning.</p>

Kutsal Kaan Bilgin

<pre><code class="lang-auto">fair, the rate quote was off. at $0.93/DOT today, 400 DOT is around $370 not $2.4k. used a stale figure when i drafted, didn't double-check. that's on me.

given the rate miss and the open ai-orchestration concerns, i'm going to hold off on the on-chain submission. probably better to revisit after m2 lands and the work speaks for itself in a clearer way.

thanks for the diligence, everyone.
</code></pre>

<p>has the research / dev team considered the scenario in which most of the stake is un-bonded <em>in masse</em> once this referenda is enacted? I think the likelihood of this happening is non-negligible which will be a grave security concern for the stability of the network as a whole.</p>

Truth

Jonathan

<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/e/e8302e72aa0c40255a38b52571464ee40f537a75.jpeg" data-download-href="/uploads/short-url/x8205mYXMuNrgEzgL6j78Z9aAEl.jpeg?dl=1" title="playground" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/e/e8302e72aa0c40255a38b52571464ee40f537a75.jpeg" alt="playground" data-base62-sha1="x8205mYXMuNrgEzgL6j78Z9aAEl" width="448" height="500" data-dominant-color="1C1C18"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">playground</span><span class="informations">459×512 56.2 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p>Let’s be honest with ourselves.</p>
<p>Coding in Web3 and getting decentralized systems to play nice can be a world of pain. We all know it, masks off. Setting up environments, fighting with documentation, chasing down impossible errors, is something we don’t want to recommend to anyone to do, not again : )</p>
<p>What if you could skip the pain and just start breaking things? <strong>Enter playground . dot</strong></p>
<p>At this Web3 Summit, a temporary, event-only environment is being fired up for pure, unadulterated experimentation. It’s a 2-day open workshop where you can explore a sandbox environment to create, modify, and share without the usual pains of dealing with decentralized infrastructure.</p>
<p>What you, your team, or your festival partners choose to spin up, modify, and remix inside this sandbox environment is 100% up to you. Take an existing project, modify it, share it, and see what happens. Meet new people, bring old ideas to life, and have fun. Feel the raw energy of a hackathon inside a web3 culture festival.</p>
<p>DevCult will be on the ground to support builders - like you - digging into the demo apps. There’s no competition here, it is just a celebration of open culture, learning by doing, and a <strong>€4.750</strong> reward pool for builder teams pushing the tech to its limits.</p>
<p>The rewards are not the usual rewards from a hackathon, but they incentive participation. Participate and climb the leaderboard!</p>
<p><strong>Prize category 1 - Leaderboard winners (most XP):</strong></p>
<ul>
<li>€1000 winner leaderboard</li>
<li>€500 second leaderboard</li>
<li>€250 third leaderboard</li>
</ul>
<h3><a name="p-39414-prize-category-2-builder-favourite-app-1" class="anchor" href="#p-39414-prize-category-2-builder-favourite-app-1" aria-label="Heading link"></a><strong>Prize category 2 - builder favourite app:</strong></h3>
<ul>
<li>€1000 for most “modded” app</li>
</ul>
<h3><a name="p-39414-prize-category-3-crowd-favourite-app-2" class="anchor" href="#p-39414-prize-category-3-crowd-favourite-app-2" aria-label="Heading link"></a><strong>Prize category 3 - crowd favourite app:</strong></h3>
<ul>
<li>€1000 for the most “starred” app</li>
</ul>
<h3><a name="p-39414-prize-category-4-wildcards-for-innovation-and-interesting-use-cases-3" class="anchor" href="#p-39414-prize-category-4-wildcards-for-innovation-and-interesting-use-cases-3" aria-label="Heading link"></a><strong>Prize category 4 - wildcards for innovation and interesting use cases:</strong></h3>
<ul>
<li>€500 wildcards x2 (€1000 in total)</li>
</ul>
<p>Humans and agents are welcome! Don’t leave your <em>synthetic</em> at home to miss the fun.</p>
<p>Do you want to explore it with us? <strong>Bring your laptop</strong> and reclaim a voucher at the link for your Web3 Summit tix.</p>
<p><strong>Where:</strong> Funkhaus, Berlin<br>
<strong>When:</strong> June 18-19 during Berlin Blockchain Week<br>
<strong>Get Started</strong> on playground . dot at <a href="https://web3summit.com/playground.dot" class="inline-onebox" rel="noopener nofollow ugc">Web3 Summit 2026 Berlin | A festival for digital freedom</a><br>
<strong>Grab a Voucher</strong> to experience playground . dot at Web3 Summit at <a href="https://t.co/II4VmY6yg4" rel="noopener nofollow ugc">https://devcult.io/web3summit/</a></p>

<p>Hey there, I’ve been working on a implementation of the SCALE codec in solidity, <a href="https://github.com/LucasGrasso/solidity-scale-codec" class="inline-onebox" rel="noopener nofollow ugc">GitHub - LucasGrasso/solidity-scale-codec: An implementation of Polkadot's Scale-Codec in Solidity · GitHub</a>.<br>
It currently does not support encoding/decoding of an arbitrary pallet call, but it provides the necessary primitives for it, and encoding/decoding for XCM v5 instructions.<br>
Im interested in listening to your feedback, I think it plays nicely with the XCM precompile and can be extended to more use cases.</p>

Lucas Grasso

Bolaji Ahmad

State of Precompiles in Revive Ecosystem

<p><strong>Runtime release notification</strong></p>
<p>Hello,</p>
<p>This is to advise you that the Polkadot community is currently voting to upgrade the <a href="https://kusama.subsquare.io/referenda/651" rel="noopener nofollow ugc"><em>Kusama system</em></a> to the <a href="https://github.com/polkadot-fellows/runtimes/releases/tag/v2.3.0" rel="noopener nofollow ugc">v2.3.0 release</a>.</p>
<p>This is a major runtime upgrade that introduces a <a href="https://github.com/polkadot-fellows/runtimes/pull/1193" rel="noopener nofollow ugc">flexible minimum validator set size on Relay chains</a> and lowers the default limits to 100 validators for Kusama and 250 validators for Polkadot.</p>
<p>The projected enactment date for this runtime upgrade is around 15th June 2026.</p>
<p>Many thanks.</p>

<p>Small update: the binary size comparison table is now updated to compare the correct thing – actual code sizes. Previous version contained a bug where we generated correct but uncompressed images with a lot of zeros.</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/9/90dcad8850c31695250673fda8a3e92270417a63.png" data-download-href="/uploads/short-url/kFvysOdrmuQfK2301sNMG2hC2Kn.png?dl=1" title="Screenshot 2026-06-08 at 21-01-21 JAR JAM Benchmark" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/9/90dcad8850c31695250673fda8a3e92270417a63_2_690x278.png" alt="Screenshot 2026-06-08 at 21-01-21 JAR JAM Benchmark" data-base62-sha1="kFvysOdrmuQfK2301sNMG2hC2Kn" width="690" height="278" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/9/90dcad8850c31695250673fda8a3e92270417a63_2_690x278.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/9/90dcad8850c31695250673fda8a3e92270417a63_2_1035x417.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/9/90dcad8850c31695250673fda8a3e92270417a63_2_1380x556.png 2x" data-dominant-color="EFF0EC"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Screenshot 2026-06-08 at 21-01-21 JAR JAM Benchmark</span><span class="informations">2014×814 87 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>
<p>The fixed version shows an even more significant gain of PVM2. Note: <a href="https://forum.polkadot.network/t/risc-v-is-all-you-need/17804">PVM2 is standard RISC-V (+c)</a>. So this really reaffirms our conclusion – <strong>the custom PVM ISA is unnecessary and actually much worse than PVM2 (standard RISC-V)</strong>. PVM2 (standard RISC-V) beats PVM on binary size, and performance is better or equivalent.</p>

Announcing PVM2: Reimagining PVM towards standard RISC-V

<p>Pretty please, post a YouTube playlist when available! <img src="https://emoji.discourse-cdn.com/twitter/slight_smile.png?v=15" title=":slight_smile:" class="emoji" alt=":slight_smile:" loading="lazy" width="20" height="20"></p>

Pre-Web3 Summit Updates

<p>Parity and W3F reputation is breaking down and showing its true colors, if no-one can compete how the network how is it supposed to grown? we are living with that now, i can see this going the way EOS went. changes are needed and true leaders should engage, who will launch the technology to the masses is unknown yet, they have been trying for years, even creating their “own” paid community and they failed even at that. probably all of this starts at the top. leaders need to come down to where we are, not high with their inflated egos.</p>

Joby Reuben

root

whitelisted_caller

wish_for_change

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

referendum_canceller

referendum_killer

small_tipper

big_tipper

small_spender

medium_spender

big_spender

Blockchain Alert Platform for Web3 | BlockPing

Encointer System Chain – Infrastructure Operations (Apr–Dec 2026)

Encointer Retroactive Treasury Proposal for July-Dec 2025

Subscan 2025 Q3-Q4 Funding Proposal: Basic service fee for the Kusama Relaychain and Kusama public parachain (AssetHub, Coretime, BridgeHub, People)

Pilot Proposal: RMTerra "Choose Green" RegenFi - RWA  (Small Spender, ~10k KSM)

ZKAMA - ZK Verifier SDK Proposal {Post-AssetHub Hackathon Curation}

Unlock Winning Strategies with Playzone

Encointer Outlook for Q4'25 and Onwards

Sol-XCM | A typed interface for interoperability from Solidity

Implement a Kusama Forum MVP (Content Pallet v2)

Executed

Runtime Upgrade 2.3

- Bloque lets people use stablecoins easily through a simple code tool.
- You can now watch real-time spending on Kusama Hub for the first time.
- They have processed over $405,000 in payments with more than 4,300 transactions.
- They are working with four fintech companies and have real customers.
- The team is asking for funding to keep growing and make their system stronger.
- They want to add support for local currencies like COP and MXN.
- Their goal is to help more companies use stablecoins for payments.

Support Bloque, the ONLY revenue generating project in Kusama:  72K USD in 6 installments, scale 5x.

Delay Demo #2 Treasury Guardian

Kusama

referenda1

treasury93

discussions1387