candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

Introducing PAPI Rescue: A Recovery Service for Compromised Polkadot Wallets

What&rsquo;s the intended data/storage consumption design for a social Polkadot Product?

Tommi Enenkel / Alice und Bob | Mangata

What's the intended data/storage consumption design for a social Polkadot Product?

How can I fix &ldquo;no allowance set for account&rdquo;?

How can I fix "no allowance set for account"?

<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

Introducing Birdbrain — a shared memory for the Kusama flock

birdbrain

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

Tech Talk

InsufficientAuthorizerBudget failures on Polkadot Products DevNet Bulletin chain authorisation

Pricey

Polkadot Products Devote - Feedback (Privacy)

Rust Syndicate

Polkadot Products Devnet - Feedback

Karim | Applied Engineering @ Parity

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

**[Updated Pre-Proposal Discussion] DOT Recovery Loan to Hyperbridge Exploit Victims**

HyperbridgeVictim

Concentration of Moderator and Curator Roles Among Same Individuals

muddles

Should Kusama spend its treasury onboarding members instead of selling KSM? [RFC-001]

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

Ecosystem

A request for clarity before JAM: the people who funded this deserve a straight answer

Leemo

New Multix instance

Polkadot Socials Daily Digest: 2026-08-04

OpenShore

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>5,797.30 Euros*</p>
<p>Fuck ChaosDAO.</p>
<p>You can find our comment on the ref here: <a href="https://polkadot.subsquare.io/referenda/821" class="inline-onebox" rel="noopener nofollow ugc">Free Beer Stand &amp; BD/Networking Space at Polkadot Decoded</a></p>
<p>You can find a tweet about this here: <a href="https://x.com/ChaosDAO/status/1826359993630957958" class="inline-onebox" rel="noopener nofollow ugc">ChaosDAO ☯️ on X: "Why did ChaosDAO do this? 😩 We have published the final report for @Polkadot referendum #821. Out of the 4,504 DOT awarded we have returned 3,454.61 DOT to the treasury ✅ See the report (including detailed budget breakdown): https://t.co/oqPI2YsElP https://t.co/c5HdudjGkS" / X</a></p>
<p>You can read the report here: <a href="https://docs.google.com/document/d/1AEvy-WIgMvKydtGc2uB1hvihoivTLxg6QXz_TFAxEWY/pub" class="inline-onebox" rel="noopener nofollow ugc">ChaosDAO Beer Stand Report</a></p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/1/11d4a4675fa50897fa6ecc5ee4014e410e6bb62a.png" data-download-href="/uploads/short-url/2xJHrVQGdkDyxynrtkEHWAhDAOC.png?dl=1" title="image" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/11d4a4675fa50897fa6ecc5ee4014e410e6bb62a_2_690x464.png" alt="image" data-base62-sha1="2xJHrVQGdkDyxynrtkEHWAhDAOC" width="690" height="464" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/11d4a4675fa50897fa6ecc5ee4014e410e6bb62a_2_690x464.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/11d4a4675fa50897fa6ecc5ee4014e410e6bb62a_2_1035x696.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/1/11d4a4675fa50897fa6ecc5ee4014e410e6bb62a_2_1380x928.png 2x" data-dominant-color="E8E8EA"><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">image</span><span class="informations">1612×1086 116 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>Gm,</p>
<p>Since a while and the fall of ibp.network the site multix.cloud has been down, i managed to find the source code of multix and forked it and managed to get it to work with polkadot-assethub, kusama-assethub and paseo.</p>
<p>Check out this public instance:</p><aside class="onebox allowlistedgeneric" data-onebox-src="https://multix.shield.markets">
  <header class="source">
      <img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/0/0e5a1d6694abc65982a3d5e8d3d3fd21fc53c39c.png" class="site-icon" alt="" data-dominant-color="4B65A9" width="48" height="48">

      <a href="https://multix.shield.markets" target="_blank" rel="noopener nofollow ugc">multix.cloud</a>
  </header>

  <article class="onebox-body">
    <div class="aspect-image" style="--aspect-ratio:690/241;"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/c/c5e3702057ca96cf3cf093eccb7f8871bb5c3402_2_690x241.png" class="thumbnail" alt="" data-dominant-color="6279B5" width="690" height="241"></div>

<h3><a href="https://multix.shield.markets" target="_blank" rel="noopener nofollow ugc">Multix</a></h3>

  <p>The best interface to create and manage multisigs on Polkadot. All your multi-signature accounts, across many chains and parachains, with or without a pure proxy</p>


  </article>

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

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

<p>It should auto detect all multisigs you have on-chain, as its running several indexers in the background</p>

<p>Solved, and my first Polkadot app is now live!</p>
<p>I’ve wanted to do this for almost 6 years, and now it’s finally easy enough for someone like me <img src="https://emoji.discourse-cdn.com/twitter/sweat_smile.png?v=15" title=":sweat_smile:" class="emoji" alt=":sweat_smile:" loading="lazy" width="20" height="20"></p>

<h2><a name="p-40442-technical-infrastructure-1" class="anchor" href="#p-40442-technical-infrastructure-1" aria-label="Heading link"></a>Technical &amp; Infrastructure</h2>
<ul>
<li>A community explainer emphasized that Polkadot activity should be assessed across chains such as AssetHub, Hydration and Peaq, noting that staking, governance and balances moved to AssetHub during the 2025 migration (via <a href="https://x.com/thatMediaWag/status/2084183400961978826" rel="noopener nofollow ugc">thatMediaWag</a>, <a href="https://x.com/thatMediaWag/status/2084183433107079240" rel="noopener nofollow ugc">thatMediaWag</a>, <a href="https://x.com/thatMediaWag/status/2084183451461435583" rel="noopener nofollow ugc">thatMediaWag</a>).</li>
<li>Polkadot devnet activity continued to expand, with 116 <code>.dot</code> names, apps, contracts and pages reportedly published so far (via <a href="https://x.com/D0tSama/status/2084365672579006954" rel="noopener nofollow ugc">D0tSama</a>).</li>
<li>A security reminder advised users to verify any Manta Atlantic-related migration or recovery links through official Manta channels following its Polkadot parachain slot expiry and deprecation (via <a href="https://x.com/BTCWire/status/2084293969333109108" rel="noopener nofollow ugc">BTCWire</a>).</li>
</ul>
<h2><a name="p-40442-ecosystem-products-2" class="anchor" href="#p-40442-ecosystem-products-2" aria-label="Heading link"></a>Ecosystem &amp; Products</h2>
<ul>
<li>Web3 Foundation research highlighted the commercial value generated by internet users and framed the opportunity around returning more value to creators and users (via <a href="https://x.com/AcademyPolkadot/status/2084269703573234155" rel="noopener nofollow ugc">AcademyPolkadot</a>).</li>
<li>Builders showcased creative experiments on Polkadot’s product devnet, including a synth with rhythm and loop-station functionality and the Radioactive Drums music-focused test (via <a href="https://x.com/cocokrypt/status/2084072860813795604" rel="noopener nofollow ugc">cocokrypt</a>, <a href="https://x.com/Joshuwa/status/2084248808133709933" rel="noopener nofollow ugc">Joshuwa</a>).</li>
<li>Community posts framed Polkadot’s product direction around identity, payments, apps, communication, decentralized compute, People Chain, Bulletin Chain, <code>.dot</code> domains, PolkaVM and JAM (via <a href="https://x.com/D0tSama/status/2084049638378660269" rel="noopener nofollow ugc">D0tSama</a>).</li>
<li>Polkadot’s digital agency narrative gained a data-rights angle, emphasizing user-defined ownership, consent and reuse (via <a href="https://x.com/DaBlockDAO/status/2084145113505411145" rel="noopener nofollow ugc">DaBlockDAO</a>).</li>
</ul>
<hr>
<h2><a name="p-40442-processing-log-3" class="anchor" href="#p-40442-processing-log-3" aria-label="Heading link"></a>PROCESSING LOG</h2>
<ul>
<li><strong>Report Generated:</strong> 2026-08-04 10:04:28</li>
<li><strong>Total X posts curated:</strong> 687</li>
<li><strong>Posts Filtered and Analysed:</strong> 661</li>
<li><strong>Data Source:</strong> X (Twitter)</li>
</ul>
<hr>
<p><sup>This report is auto-generated and provided for informational purposes only by OpenShore, a Pala Labs initiative. The content is based on posts from X and may contain inaccuracies. We do not guarantee its completeness or correctness.</sup></p>

<p>MiniJAM is a distinct community-driven project. JAM will create many new forms of applications, while also requiring a large amount of new infrastructure. We therefore want to use MINI as an incentive resource that can be continuously invested back into the ecosystem.</p>
<p>Even on the forum alone, the community launches new products almost every week. Many of them are valuable tools, applications, and infrastructure projects, yet they often struggle to reach a real market. This cannot simply be explained as “the market does not need them.”</p>
<p>For Web3 products, product discovery itself carries a cost. Users need to spend time understanding a project, trying the product, and accepting the risks of using something at an early stage. The more mature the infrastructure and the larger the user base, the lower this friction becomes. Otherwise, active incentives are needed to help products be discovered, used, and shared.</p>
<p>Treasury and committee funding played an important role in the early growth of the ecosystem, but they also have clear limitations.</p>
<p>First, these decisions are usually binary. A project either receives support or it does not. This makes it difficult to express the different preferences and levels of support held by different groups.</p>
<p>A more important issue is that projects initially face a small group of reviewers and governance participants rather than the market itself. A grant may help a project get started, but it cannot continuously answer a more important question: do users still need it?</p>
<h2><a name="p-40440-h-1-the-incentive-market-1" class="anchor" href="#p-40440-h-1-the-incentive-market-1" aria-label="Heading link"></a>1. The Incentive Market</h2>
<p>Over the past period, we have extensively tested a range of incentive products across different ecosystems. They have given us many useful ideas.</p>
<p>Based on those experiences, we abstracted a general-purpose incentive protocol. It allows projects to face the market directly and receive a continuous stream of incentive resources based on their ongoing market performance.</p>
<p>Every project can establish its own market. Users express their judgment by trading, holding, and staking, while the protocol continuously distributes MINI according to these market signals.</p>
<p>A project’s incentives are therefore no longer determined by a single decision. They adjust continuously as its market performance changes.</p>
<h2><a name="p-40440-h-2-core-concepts-2" class="anchor" href="#p-40440-h-2-core-concepts-2" aria-label="Heading link"></a>2. Core Concepts</h2>
<ul>
<li>
<p><strong>Alpha</strong>: Every project has its own Alpha. It is used to establish liquidity, participate in staking, and receive the incentives allocated to the project.</p>
</li>
<li>
<p><strong>Project Market</strong>: A project creates an independent Alpha/MINI liquidity pool. User trading and holding activity produces continuously changing price and liquidity signals.</p>
</li>
<li>
<p><strong>Staking Vault</strong>: Users can deposit Alpha into a project’s Staking Vault. By giving up some liquidity and taking on project risk, stakers express longer-term support.</p>
</li>
<li>
<p><strong>Emissions</strong>: The protocol releases a fixed amount of MINI in each period and allocates it according to the market performance of each project. Part of the allocated MINI enters the liquidity pool together with newly issued Alpha, while the remaining emissions are distributed to stakers and builders.</p>
</li>
<li>
<p><strong>Owner Share</strong>: Owner Share defines the portion of Alpha emissions allocated to the project’s builders, allowing them to receive continuing incentives as the project develops.</p>
</li>
</ul>
<h2><a name="p-40440-h-3-sub-protocols-3" class="anchor" href="#p-40440-h-3-sub-protocols-3" aria-label="Heading link"></a>3. Sub-Protocols</h2>
<p>The main protocol is intentionally simple. It does not care where the initial liquidity comes from, nor does it determine how Alpha should ultimately be distributed. Once a project has established an Alpha/MINI market, the main protocol allocates emissions according to its market performance.</p>
<p>The main protocol may not even need its own frontend. In practice, it does not directly serve users or projects.</p>
<p>Different projects require different launch and incentive mechanisms. Some may be better suited to crowdfunding, while others may use auctions. Some may want to reward early users, while others may release incentives according to product usage or development progress. A sub-protocol may also provide additional services, such as stricter project audits.</p>
<p>This allows the incentive protocol to serve different market needs.</p>
<p>A sub-protocol mainly controls three areas:</p>
<ul>
<li>
<p><strong>Initial Distribution</strong>: How Alpha is distributed among users, liquidity, and builders.</p>
</li>
<li>
<p><strong>Ongoing Emissions</strong>: How the project uses its allocated emissions and under what conditions they are released.</p>
</li>
<li>
<p><strong>Owner Share</strong>: How much is allocated to builders and how those allocations are unlocked.</p>
</li>
</ul>
<p>By controlling these three areas, a sub-protocol can define a complete project mechanism, including how users enter, how the project raises funds, what happens if the launch fails, and under what conditions users and builders receive rewards.</p>
<p>For example, Workers could provide computation, data, or other services. AI could perform an initial evaluation, while validators review the results. The sub-protocol could then distribute the project’s Alpha emissions among Workers, validators, and builders according to those results. In this way, it would be possible to create a sub-protocol similar to a Bittensor subnet.</p>
<p>In return, a sub-protocol can receive the majority of the liquidity fees generated by its related markets. The sub-protocol is the actual user-facing layer.</p>
<h2><a name="p-40440-h-4-public-goods-4" class="anchor" href="#p-40440-h-4-public-goods-4" aria-label="Heading link"></a>4. Public Goods</h2>
<p>Most public goods are not suitable for issuing their own Alpha. The protocol therefore reserves a separate portion of emissions for them.</p>
<p>When staking Alpha, users receive corresponding voting weight, which they can use to support different public goods. The incentive protocol then distributes the MINI reserved for public goods according to these votes.</p>
<h2><a name="p-40440-h-5-current-progress-5" class="anchor" href="#p-40440-h-5-current-progress-5" aria-label="Heading link"></a>5. Current Progress</h2>
<p>The core contracts for the first phase have been completed. Once the MINI liquidity pool has been successfully established, the incentive market will officially launch.</p>
<ul>
<li>
<p>Protocol code: <a href="https://github.com/ArcheLabs/incentive-market" rel="noopener nofollow ugc">https://github.com/ArcheLabs/incentive-market</a></p>
</li>
<li>
<p>Draft protocol documentation: <a href="https://docs.minijam.xyz/docs/incentive-protocol" class="inline-onebox" rel="noopener nofollow ugc">Incentive Protocol | MiniJAM Documentation</a></p>
</li>
</ul>

robert

Accelerating the Polkadot/JAM Ecosystem with the MiniJAM Incentive Protocol

Bastian Köcher

Proposal: Introduce a Permanent Burn Account for Polkadot

<p>you can wrap rpc calls into a tor proxy client side, but it requires the users to run a heavy wasm binary in the browser which slows things down, shield.markets have a poc of it, might be worth checking out: <a href="https://pse.dev/projects/tor-js" class="inline-onebox" rel="noopener nofollow ugc">tor-js | PSE</a> (the alternative is to make a lighter implementation of snowflake proxy in wasm)</p>
<p>long term it would be nice to have some privacy preserving light client protocol thats not to complicated(like maybe: <a href="https://cypherpunks.ca/~iang/pubs/Sphinx_Oakland09.pdf" rel="noopener nofollow ugc">https://cypherpunks.ca/~iang/pubs/Sphinx_Oakland09.pdf</a>)</p>

<p>Thanks for pushing on this, Christ — these are exactly the kind of questions we need answered before this goes further.</p>
<p>To be upfront: Voultra is still early and under active development, and feedback like this is genuinely shaping the direction, not just something we’re nodding along to.</p>
<p>On sellers — you’re right, the current plan leans too heavily on the buyer side. We’re working through an approach that includes direct outreach to sellers already on eBay/Amazon who are paying high commission fees, starting with a narrower category (electronics) rather than going broad, real short-term incentives (reduced/zero fees, VLT rewards) for early sellers, and partnerships with wholesalers rather than recruiting one by one.</p>
<p>On governance — fair challenge. “DOT holders will handle disputes” was underspecified. We’re rethinking how moderation and dispute resolution actually get staffed early on, before decentralized governance is mature enough to carry that load by itself.</p>
<p>Would genuinely value you staying in this thread as we flesh it out further — this kind of scrutiny is what the proposal needs right now.</p>

Amir Yousfi

Chris T

[IDEA] Voultra DAO - First Decentralized Electric &amp; Hardware Marketplace on Polkadot Asset Hub

[IDEA] Voultra DAO - First Decentralized Electric & Hardware Marketplace on Polkadot Asset Hub

<p><a class="mention" href="/u/thomasr">@ThomasR</a> <a class="mention" href="/u/bill_w3f">@bill_w3f</a> <a class="mention" href="/u/seunlanlege">@seunlanlege</a> **<br>
**<br>
This situation is no longer acceptable, and I want to state clearly, on record, where things stand from the perspective of an affected LP.</p>
<p>Around four months after the exploit, the affected liquidity providers have received no substantive engagement from any of the responsible parties. There is no update on the Binance recovery. No update on the ~100,000 DOT frozen at BC.Game. No compensation plan of any kind. Requests across Discord, email and this forum have gone unanswered, and critical questions in the Bifrost Discord have been removed and user accounts asking about the remaining vDOT even get BANNED by Bifrost.</p>
<p>At the same time, Bifrost referendum 287 moved roughly 91,750 vDOT out of the Hyperbridge module account, on a whitelisted fast track with 3.40% support, distributed to one group of users, while the affected LPs who lost their principal have received nothing and no explanation of how, or whether, the undistributed DeFi Singularity vDOT from Referendum 1439 relate to this. When Polytope was asked directly, the answer was that the funds “were held on Bifrost chain and used to compensate their users.” That answer raises far more questions than it settles, and none of them have been addressed.</p>
<p>I am describing what is observable: the parties responsible for this infrastructure and its failure have gone silent, the only readily available assets have been moved elsewhere, and the victims have been left without answers.</p>
<p><strong>If the strategy here is to wait this out and rely on attrition until the affected parties give up, I want to be equally clear that this will not happen. There are victims who will not accept being left in the rain.</strong></p>
<p>If there continues to be no movement, and no clarification on both the Bifrost module account actions and the disposition of the Singularity vDOT, <strong>then these events will be documented and raised publicly and permanently, across independent media, X, and dedicated write-ups, until the parties involved engage with them.</strong> I would vastly prefer not to reach that point. Every party named here has a standing, open invitation to respond and resolve this factually. That door remains open.</p>
<p>What affected LPs are asking for has never changed and has never been unreasonable: the vDOT that were allocated as LP rewards under Referendum 1439 should reach the LPs who lost their principal. There is a live Wish for Change referendum on Polkadot to that effect. Engagement from the responsible parties, and from delegates, is what is needed now.</p>

<h1><a name="p-40430-further-thoughts-on-jamkb-dynamic-pricing-proposal-1" class="anchor" href="#p-40430-further-thoughts-on-jamkb-dynamic-pricing-proposal-1" aria-label="Heading link"></a>Further thoughts on JAMKB Dynamic Pricing Proposal</h1>
<h2><a name="p-40430-abstract-2" class="anchor" href="#p-40430-abstract-2" aria-label="Heading link"></a>Abstract</h2>
<p>Following community feedback and further internal analysis, we are withdrawing our proposed dynamic pricing and state-decay mechanism for DOTDAO-held JAMKB. Further analysis showed that the mechanism could not provide the predictable costs and state-retention guarantees required by long-lived services and smart contracts because a persistent state requires predictable cost, retention, and lifecycle guarantees.</p>
<p>Dynamic reclamation also conflicts with common execution assumptions, introduces opportunities for manipulation, and depends on unresolved service-level delegation rules. These are structural limitations rather than parameter-setting problems, so we are setting the proposal aside.</p>
<h2><a name="p-40430-introduction-3" class="anchor" href="#p-40430-introduction-3" aria-label="Heading link"></a>Introduction</h2>
<p>Further analysis and community feedback exposed a more fundamental problem: the mechanism made the cost and continued availability of persistent state dependent on future network conditions. For applications that rely on durable state, this creates unacceptable uncertainty across pricing, execution, and security.</p>
<p>We express our sincere gratitude to the community members, researchers, and engineers who actively engaged with this exploratory note. The qualitative feedback, edge-case analysis, and scenario modeling contributed by the ecosystem have proved invaluable in evaluating the practical viability of this approach.</p>
<p>Further internal analysis and community review, under closer scrutiny, revealed systemic flaws. The model masks implementation complexities, game-theoretic exploits, non-deterministic user costs, and execution-layer security risks that cannot be resolved through simple parameter adjustments or fine-tuning. Furthermore, the model imposes strict structural rigidities on how services manage and delegate storage credits, contradicting the flexible, composable nature required for a general smart contract ecosystem.</p>
<p>Below, we formalize the core architectural failure modes and economic trade-offs that inform our decision to step back from this approach. The issues identified through further analysis are not equal in weight, with the most fundamental concern being that the mechanism makes the cost of continued availability of persistent state dependent on future network conditions. The execution, security, economic, and implementation problems described below largely follow from that underlying conflict.</p>
<h3><a name="p-40430-h-1-persistent-state-requires-predictable-lifecycle-guarantees-4" class="anchor" href="#p-40430-h-1-persistent-state-requires-predictable-lifecycle-guarantees-4" aria-label="Heading link"></a>1. Persistent State Requires Predictable Lifecycle Guarantees</h3>
<p>The mechanism cannot provide state holders with predictable costs or retention periods, and this problem becomes most acute as network utilization approaches saturation, when both acquisition prices and deposit-decay rates rise. Under the proposed model, the rate at which a holder’s deposit declines is determined partly by congestion that occurs after the allocation has been made. Although the holder cannot lose more than the original deposit, they cannot calculate in advance how quickly that deposit will erode or how long their allocation is likely to remain economically viable.</p>
<p>The timing of state reclamation is similarly unpredictable. Unexpected demand can accelerate reclamation and shorten the grace period available to top up a deposit. This means that services cannot reliably determine how long their state will remain available when they initially commit to an allocation.</p>
<p>For persistent application state, this uncertainty is not simply a pricing inconvenience because long-lived services and smart contracts require clear guarantees about cost, retention and expiry. Making those guarantees dependent on future network utilization introduces uncertainty into the application lifecycle itself.</p>
<h3><a name="p-40430-h-2-execution-layer-incompatibility-and-adversarial-reclamation-5" class="anchor" href="#p-40430-h-2-execution-layer-incompatibility-and-adversarial-reclamation-5" aria-label="Heading link"></a>2. Execution-Layer Incompatibility and Adversarial Reclamation</h3>
<p>Non-deterministic reclamation velocity introduces an adversarial attack primitive: during periods of elevated state scarcity, a malicious actor can strategically acquire marginal state capacity specifically to accelerate the reclamation of targeted third-party state, profiting from the resulting application failures.</p>
<p>At the execution layer, dynamic state deletion violates a foundational invariant of major smart contract execution environments (including the EVM and standard Substrate WASM runtimes): state persistence is monotonic unless explicitly mutated or deleted by the owning context. Allowing the underlying JAM protocol layer to asynchronously purge state primitives breaks this assumption, forcing contract toolchains, static analyzers, and developer frameworks to implement defensive fallbacks for arbitrary variable vanishing. This appears incompatible with standard EVM assumptions without significant additional machinery.</p>
<p>While state-rent mechanisms have been investigated in the Ethereum ecosystem since 2018, their deployment has been constrained by these exact execution-model incompatibilities. While JAM supports alternative execution paradigms, applications using these execution models could inherit similar vulnerabilities if dynamic reclamation is maintained.</p>
<p>This risk may arise in JAMKB lending designs that permit non-deterministic reclamation. Nonetheless, the unpredictability of reclamation time in this design makes the failure mode harder to avoid. Predictable alternatives exist, e.g., using a fixed-period lease. That would resolve much of this unpredictability and provide a far better user experience but would further complicate pricing and fairness. This indicates that the design space here is still genuinely open.</p>
<h3><a name="p-40430-h-3-unresolved-service-level-architecture-6" class="anchor" href="#p-40430-h-3-unresolved-service-level-architecture-6" aria-label="Heading link"></a>3. Unresolved Service-Level Architecture</h3>
<p>Finalizing a lower-layer pricing mechanism is premature while the surrounding service-level framework remains unstandardized. In particular, things that still need to get resolved:</p>
<ul>
<li>How the Polkadot service lends JAMKB.</li>
<li>How storage held by other services is cleanly reclaimed.</li>
<li>Whether services with delegated JAMKB can themselves delegate further.</li>
</ul>
<p>Any of these factors could fundamentally reshape the pricing problem. Let us further examine how these last two might affect the model:</p>
<ul>
<li><strong>Reclamation Concurrency and Hardware Costs:</strong> At the physical infrastructure level, deleting or compressing database state imposes non-zero disk I/O overhead on validator nodes. State reclamation mechanics must be bounded and paid for explicitly rather than treated as a cost-free protocol side-effect.</li>
<li><strong>The Question of Sub-delegation:</strong> If services are allowed to further delegate the JAMKB they are lent, then this would give rise to secondary markets, reintroducing the speculation that this mechanism was designed to avoid. On the other hand, if services cannot delegate their borrowed JAMKB further, then this would create a strong bias toward monolithic service design, as modular service architectures are economically penalized if they cannot dynamically route storage capacity. Even sub-delegation would imply an explicit, hierarchical authority framework. This strict hierarchy restricts JAM services to a rigid, top-down tree model—a constraint that fails entirely for a general-purpose, peer-to-peer smart contract ecosystem requiring flexible, horizontal composition.</li>
</ul>
<h3><a name="p-40430-h-4-mechanism-level-economic-exploits-7" class="anchor" href="#p-40430-h-4-mechanism-level-economic-exploits-7" aria-label="Heading link"></a>4. Mechanism-Level Economic Exploits</h3>
<p>Beyond targeted exploitation, the mechanism introduces structural distortions that incentivize rational agents toward protocol-adverse behaviors:</p>
<p><strong>Sub-allocation Arbitrage (Violation of Subadditivity):</strong> To mitigate bulk state acquisition, the proposal prices allocations based on the terminal occupancy state rather than the initial state. However, because this pricing rule is non-subadditive across discrete intervals, an agent seeking a large allocation block achieves a lower aggregate cost by partitioning the request into sequential sub-allocations, each evaluated at a lower marginal cost point.</p>
<p><strong>Decay-Resetting Arbitrage (“Decay Laundering”):</strong> During low-utilization regimes, agents whose deposits have decayed toward the price floor are incentivized to voluntarily release their state allocation and immediately re-allocate the identical state within the same execution block. This operation allows the agent to reclaim their remaining floor deposit and reset their allocation to a fresh, lower-decay trajectory, introducing systemic mempool bloat, state churn, and transaction overhead across market cycles.</p>
<h3><a name="p-40430-h-5-parameter-sensitivity-and-cold-start-calibration-8" class="anchor" href="#p-40430-h-5-parameter-sensitivity-and-cold-start-calibration-8" aria-label="Heading link"></a>5. Parameter Sensitivity and Cold-Start Calibration</h3>
<p>The design mandates a closed-form pricing curve whose operational stability depends heavily on parameter selection. Scoping and formally proving the stability of this parameter space represents a substantial engineering footprint with questionable utility relative to simpler alternatives.</p>
<p>Furthermore, while reusing the same occupancy-and-flow response function for both initial acquisition pricing and deposit decay creates parameter hyper-sensitivity. A singular miscalibration propagates simultaneously across entry costs and ongoing carrying costs, severely narrowing the system’s margin for error. Decoupling these functions—as noted in our initial proposal—expands the already large parameter space and reintroduces strategic arbitrage opportunities that the unified function was designed to eliminate.</p>
<p>Compounding these design risks is a fundamental cold-start problem: because JAMKB is not yet operational, baseline empirical demand data does not exist. Critical parameters—including the floor price, local curve steepness, and flow-response coefficients—would necessarily be set a priori without observable market signals, forcing the protocol to launch prior to acquiring the data necessary for stable parameter tuning.</p>
<h2><a name="p-40430-conclusion-9" class="anchor" href="#p-40430-conclusion-9" aria-label="Heading link"></a>Conclusion</h2>
<p>This work has made it clear that our initial scheme was lacking consideration of many aspects. By trying to isolate pricing, we overlooked how tightly it’s bound to delegation, reclamation, and real-world service composition. A viable JAMKB allocation mechanism demands a much deeper handling of cost predictability, state-lifecycle guarantees, and execution model compatibility than our design allowed for. e. For that reason, we are setting it aside, keeping the wider design space open while those requirements are explored.</p>
<p>Jonas &amp; Kremena</p>

jonas

Dynamically priced JAMKB via decaying deposits

<p>It’s about time we updated you on the activities of the <a href="https://art.ksm.vision" rel="noopener nofollow ugc">KSM Art &amp; Social Experiments Initiative</a>. Although our first applications date back to early spring this year, we began a new social media campaign promoting our Open Call at the beginning of July, something that has triggered a fresh influx of applications.</p>
<p>It’s invigorating for us as curators to know there is plenty of energy in the world among artists, experimenters and creators for crafting the visions and ideas that will help take the Web3 vision forward.</p>
<p>In the eight-day period between July 7th and July 14th, we received an average of one new application every day. Since then we have received a further four proposals, taking us to 35 proposals in all since the Initiative was first formed in January.</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/3/300f486b12376dfe810bedc516d95ec7349ec61a.jpeg" data-download-href="/uploads/short-url/6R9F2LhV936PfBRP7awMBp79uXg.jpeg?dl=1" title="HMijaN1W0AATcLf" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/300f486b12376dfe810bedc516d95ec7349ec61a_2_499x499.jpeg" alt="HMijaN1W0AATcLf" data-base62-sha1="6R9F2LhV936PfBRP7awMBp79uXg" width="499" height="499" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/300f486b12376dfe810bedc516d95ec7349ec61a_2_499x499.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/300f486b12376dfe810bedc516d95ec7349ec61a_2_748x748.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/3/300f486b12376dfe810bedc516d95ec7349ec61a_2_998x998.jpeg 2x" data-dominant-color="38373A"><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">HMijaN1W0AATcLf</span><span class="informations">1546×1546 215 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>Between them, these projects reflect a broad spectrum of decentralized creativity, both geographically and thematically. While the majority of these submissions have ultimately been rejected after careful consideration, the most recent remain under active review. But the good news is that the curators are happy to announce that two foundational projects have been accepted. Consider them proof-of-concepts, if you like: examples that show technical infrastructure can double as a canvas for cultural expression.</p>
<p>The first accepted project is a hyper-local governance experiment that places low-cost, off-grid hardware and scanning equipment into physical community hubs, allowing members to build and collectively govern their own local digital archives from leaflets, cuttings, books, and recordings on their own terms. The second is a sculptural initiative exploring the physical materiality of cypherpunk concepts, utilizing contrasting mediums like blown glass, wax, light, crystals, and hand-woven chainmail - constructs that reflect both the vulnerability and permanence of decentralized networks.</p>
<p>Once these two projects are fully onboarded, we will of course happily provide further details and showcase them on our website. They will then be used to help extend our outreach, since many mainstream foundations and institutions would appreciate tangible examples of what a successful proposal entails. And this promises to be an exciting period of growth.</p>
<p>Up to now, most applicants have a historic connection to the Polkadot ecosystem. We expect - and hope - that in the remaining part of the year, the majority will instead be projects from individuals or collectives who are primarily artists and experimenters with little, if any knowledge of the Polkadot ecosystem.</p>
<p>For the sake of transparency, we wish to place on record one fact: the Initiative has had a succession of obstacles tossed in its path through which we are determined, in any case, to proceed. We are five curators with a blend of skills that broadly cover:</p>
<ul>
<li>
<p>The technical requirements of funding teams in the Web3 model</p>
</li>
<li>
<p>Past experience working in contemporary art institutions both in gallery and institutional/public context. Experience as curators, jury and producing art projects.</p>
</li>
<li>
<p>Past experience of onboarding artists via Open Calls</p>
</li>
<li>
<p>The marketing skills to promote the Initiative</p>
</li>
</ul>
<p>We also have the enthusiasm to make the project a success. However, our progress has been slowed by the fact we have had no long-term permanent co-ordinator assigned to the three Kusama Vision bounties from either the Web3 Foundation (which ultimately supplies the funds to pay the artists) or Parity Technologies, by far the largest collective driving the growth of Polkadot.</p>
<p>We are assured somebody will be assigned to us in due course, but in the meantime we have concerns over legal protection and the low curatorial salary (which is based on last year’s DOT valuation). We have flagged these issues but they cannot easily be addressed in the continued absence of the co-ordinator.</p>
<p>There have been a few other delays and technical problems, but the outlook is better. We are reasonably confident, in fact, that from August onwards we will slowly see a semblance of normality return. Once our first projects receive their first milestone payments, we will step up our active outreach. Thus we expect that through the power of networks and the delivery of funding, a flywheel effect will promote some strong applications for future funding in September and through to the end of the year.</p>
<p>As ever, if you’re interested and genuinely meet the criteria, <a href="https://art.ksm.vision/#participate" rel="noopener nofollow ugc">please do apply</a>. And of course, if you know someone whose work is in tune with what we’re looking to fund, let them know about us. Thanks for reading.</p>

KSM Art and Social Experiments Iniative

The KSM Arts Initiative: Where We&rsquo;ve Got To

The KSM Arts Initiative: Where We've Got To

<h1><a name="p-40425-pr-campaign-proposal-making-polkadot-the-place-where-anyone-can-build-1" class="anchor" href="#p-40425-pr-campaign-proposal-making-polkadot-the-place-where-anyone-can-build-1" aria-label="Heading link"></a>PR Campaign Proposal: Making Polkadot the Place Where Anyone Can Build</h1>
<h2><a name="p-40425-the-opportunity-2" class="anchor" href="#p-40425-the-opportunity-2" aria-label="Heading link"></a>The Opportunity</h2>
<p>Polkadot has a compelling story to tell — but the story needs to be made visible again.</p>
<p>The current Devnet demonstrates something potentially game-changing: with Claude and Polkadot, developers <strong>and non-developers can deploy functional apps with dramatically less technical friction</strong>. What previously required significant blockchain expertise can increasingly be turned into a working application through natural-language interaction.</p>
<p>This is not simply another developer feature. It has the potential to fundamentally change <strong>who can build on Polkadot</strong>.</p>
<p>The rollout of the Polkadot App should therefore be accompanied by a focused PR campaign designed to turn this capability into a public narrative — and position Polkadot as one of the most accessible and forward-looking ecosystems for building in the AI era.</p>
<h2><a name="p-40425-core-message-3" class="anchor" href="#p-40425-core-message-3" aria-label="Heading link"></a>Core Message</h2>
<p><strong>“If you can describe an app, you can build it on Polkadot.”</strong></p>
<p>The campaign should make the experience tangible rather than explaining it technically.</p>
<p>Instead of talking about AI-assisted development, we demonstrate it:</p>
<ul>
<li>
<p><em>“I asked Claude to build this. It deployed on Polkadot.”</em></p>
</li>
<li>
<p>Live demos from idea → code → deployment.</p>
</li>
<li>
<p>Non-developers building simple applications.</p>
</li>
<li>
<p>Developers showing how much faster AI-assisted deployment makes them.</p>
</li>
<li>
<p>A series of increasingly ambitious experiments using the Devnet.</p>
</li>
</ul>
<p>The goal is to create a <strong>“Wait… you can actually do that?” moment.</strong></p>
<h2><a name="p-40425-campaign-distribution-4" class="anchor" href="#p-40425-campaign-distribution-4" aria-label="Heading link"></a>Campaign Distribution</h2>
<h3><a name="p-40425-x-the-main-conversation-layer-5" class="anchor" href="#p-40425-x-the-main-conversation-layer-5" aria-label="Heading link"></a>X — The Main Conversation Layer</h3>
<p>Launch a coordinated series of short videos, demos, threads and quote-ready visuals from Polkadot, ecosystem projects, developers and community members.</p>
<p>Potential formats:</p>
<p><strong>“Build this in 10 minutes”</strong><br>
Real-time Claude → Polkadot deployment challenges.</p>
<p><strong>“Could a non-dev build this?”</strong><br>
Give creators a simple idea and let them attempt to deploy it.</p>
<p><strong>“Built with Claude. Deployed on Polkadot.”</strong><br>
A recognizable campaign format that can be replicated across dozens of examples.</p>
<p>The emphasis should be on <strong>proof, speed and surprise</strong>, not marketing claims.</p>
<h3><a name="p-40425-brave-browser-crypto-native-media-6" class="anchor" href="#p-40425-brave-browser-crypto-native-media-6" aria-label="Heading link"></a>Brave Browser + Crypto-Native Media</h3>
<p>Use Brave as a distribution and discovery channel for the campaign, supported by targeted placements and native content where appropriate.</p>
<p>In parallel, pitch the story to crypto and Web3 media as a broader narrative:</p>
<p><strong>AI is changing software development. Polkadot is making blockchain development accessible to everyone.</strong></p>
<p>This gives journalists a story beyond “Polkadot launches another app.”</p>
<h3><a name="p-40425-developers-creators-as-the-pr-engine-7" class="anchor" href="#p-40425-developers-creators-as-the-pr-engine-7" aria-label="Heading link"></a>Developers &amp; Creators as the PR Engine</h3>
<p>The strongest amplification should come from people actually using the product.</p>
<p>Provide selected developers, AI builders, creators and ecosystem teams with early access, simple challenges and campaign assets.</p>
<p>Give them a reason to post:</p>
<blockquote>
<p><strong>“Give me an idea. I’ll build and deploy it on Polkadot.”</strong></p>
</blockquote>
<p>The resulting content becomes distributed proof that the technology works.</p>
<h2><a name="p-40425-the-bigger-narrative-8" class="anchor" href="#p-40425-the-bigger-narrative-8" aria-label="Heading link"></a>The Bigger Narrative</h2>
<p>The campaign should not primarily be about promoting an app.</p>
<p>It should be about <strong>repositioning Polkadot</strong>.</p>
<p>The narrative is:</p>
<p><strong>Blockchain is entering an AI-native development era. Polkadot is where this becomes accessible.</strong></p>
<p>If executed well, the campaign can shift the conversation from <em>“What is Polkadot doing?”</em> to:</p>
<p><strong>“Wait — you can actually build and deploy this on Polkadot with Claude?”</strong></p>
<p>That is the kind of narrative that can put Polkadot back on the radar — not through another announcement, but by showing people something they haven’t seen before.</p>

PR: Build It. Deploy It. Polkadot

<p>Hey <a class="mention" href="/u/alice_und_bob">@alice_und_bob</a> , Danke for the exhaustive thread and writing about your experience.</p>
<p>Regarding deeplinks, I used an example in my W3S talk here: <a href="https://youtu.be/7-dSloWKDUU?t=1099" rel="noopener nofollow ugc">https://youtu.be/7-dSloWKDUU?t=1099</a></p>
<p>The decoded QR code gives: <code>polkadotapp://proofoftalk.dot/#/bafk2bzacec7a3yqiexpn63zptf65oe2p37jrwpkng7yx2qt5dztxs7if566m4</code></p>
<p>So the format is <code>polkadotapp://&lt;dotns_url&gt;/#&lt;parameters&gt;</code> for the use case of “point me to this SPA in this page or with these parameters”. The SPA should then handle the proper routing.</p>
<p>There are other schemes for SSO pairing etc. I agree this should be in the docs.</p>

<h2><a name="p-40419-general-updates-1" class="anchor" href="#p-40419-general-updates-1" aria-label="Heading link"></a>General Updates</h2>
<ul>
<li>Polkadot daily Relay Chain transactions reportedly rose to nearly 1,000 over 24 hours (via cryptodotnews: <a href="https://x.com/cryptodotnews/status/2083731005391687876" rel="noopener nofollow ugc">post</a>, Daniel_Launchly: <a href="https://x.com/Daniel_Launchly/status/2083903463163940996" rel="noopener nofollow ugc">post</a>)</li>
<li>Polkadot Cloud published its July 2026 validator report, reporting 314.586 DOT earned and stating that rewards were fully retained and compounded. (via TheWeb3Cloud: <a href="https://x.com/TheWeb3Cloud/status/2083802696260452736" rel="noopener nofollow ugc">post</a>, rossbulat: <a href="https://x.com/rossbulat/status/2083803649361535291" rel="noopener nofollow ugc">post</a>)</li>
<li>Launch tooling expanded around Polkadot: Launchly + MoonPay listed Polkadot among supported chains (via Daniel_Launchly: <a href="https://x.com/Daniel_Launchly/status/2084012748392853772" rel="noopener nofollow ugc">post</a>)_</li>
</ul>
<hr>
<h2><a name="p-40419-processing-log-2" class="anchor" href="#p-40419-processing-log-2" aria-label="Heading link"></a>PROCESSING LOG</h2>
<ul>
<li><strong>Report Generated:</strong> 2026-08-03 10:04:37</li>
<li><strong>Total X posts curated:</strong> 706</li>
<li><strong>Posts Filtered and Analysed:</strong> 680</li>
<li><strong>Data Source:</strong> X (Twitter)</li>
</ul>
<hr>
<p><sup>This report is auto-generated and provided for informational purposes only by OpenShore, a Pala Labs initiative. The content is based on posts from X and may contain inaccuracies. We do not guarantee its completeness or correctness.</sup></p>

Polkadot Socials Daily Digest: 2026-08-03

<p>Let’s, for a second, assume that JAM will be completed in less than a year and a half from now.</p>
<p>The question every Polkadot user and/or DOT holder would ask is: what do we do in the meantime? Why should we stay around? Why not simply leave and see how things are in late 2027?</p>

Truth

Jonathan

JAM Timeline Update Inquiry

<p>MiniJAM Stage 0 Testnet is now live and is expected to run for around 12 days.</p>
<p>The primary goal of this stage is to collect operational data and prepare for the next phase: the full testnet. We have now implemented nearly the complete end-to-end JAM workflow on a parachain, and expect to need another three to four weeks to reach the full testnet stage.</p>
<p>At the moment, you can:</p>
<ol>
<li>Write services in C/C++ directly in your browser, compile them, deploy them to the network, and interact with them:<br>
<a href="https://playground.minijam.xyz/" rel="noopener nofollow ugc">https://playground.minijam.xyz/</a></li>
<li>Compile services locally and deploy them to the network through the API:<br>
<a href="https://docs.minijam.xyz/docs/minijam/developers/playground-api" class="inline-onebox" rel="noopener nofollow ugc">Playground API | MiniJAM Documentation</a></li>
</ol>
<p>More resources:</p>
<p>Official website:</p><aside class="onebox allowlistedgeneric" data-onebox-src="https://minijam.xyz/">
  <header class="source">
      <img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/7/7b48041cff7d48e7dd0afac61bcd0a99cd8f8e62.png" class="site-icon" alt="" data-dominant-color="3E74AE" width="64" height="64">

      <a href="https://minijam.xyz/" target="_blank" rel="noopener nofollow ugc">minijam.xyz</a>
  </header>

  <article class="onebox-body">
    

<h3><a href="https://minijam.xyz/" target="_blank" rel="noopener nofollow ugc">MiniJAM</a></h3>

  <p>JAM running on a parachain.</p>


  </article>

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

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

<p>Documentation:</p><aside class="onebox allowlistedgeneric" data-onebox-src="https://docs.minijam.xyz/">
  <header class="source">
      <img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/2/2cf3d6e844f7bb9bc1afa01ce6be104b5bb952e7.svg" class="site-icon" alt="" data-dominant-color="" width="457" height="451">

      <a href="https://docs.minijam.xyz/" target="_blank" rel="noopener nofollow ugc">docs.minijam.xyz</a>
  </header>

  <article class="onebox-body">
    

<h3><a href="https://docs.minijam.xyz/" target="_blank" rel="noopener nofollow ugc">MiniJAM Documentation</a></h3>

  <p>Documentation for the MiniJAM ecosystem.</p>


  </article>

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

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

<p>As mentioned previously, we will also launch the economic system soon. The incentive protocol design is now largely complete, and an initial version of the contract library has been implemented.</p>

MiniJAM: A Parachain Running a Streamlined JAM

<h2><a name="p-40407-product-app-ecosystem-1" class="anchor" href="#p-40407-product-app-ecosystem-1" aria-label="Heading link"></a>Product &amp; App Ecosystem</h2>
<ul>
<li>The Polkadot/Trinity app stack was presented as supporting free deployment of uncensorable apps through primitives for storage, identity, hosting and domains, alongside desktop and web clients (via <a href="https://x.com/itsbirdo_/status/2083390122893201799" rel="noopener nofollow ugc">itsbirdo_</a>, <a href="https://x.com/OpenShorex/status/2083441405616443395" rel="noopener nofollow ugc">OpenShorex</a>, <a href="https://x.com/DaBlockDAO/status/2083441583006085365" rel="noopener nofollow ugc">DaBlockDAO</a>).</li>
<li>Peoplebook launched as a way to browse the on-chain registry and discover users to DM from the Polkadot App (via <a href="https://x.com/thewhiterabbitM/status/2083618392150348155" rel="noopener nofollow ugc">thewhiterabbitM</a>).</li>
<li>ComputeFlux is now live on Polkadot’s new Devnet and listed among the 100 apps indexed by the ecosystem app tracker (via <a href="https://x.com/cao_lab/status/2083651450627092900" rel="noopener nofollow ugc">cao_lab</a>).</li>
<li>SoverStore Drops went live on Polkadot Products, enabling paid digital releases where smart contracts record purchases and cryptography gates file access without accounts, backend servers or server-side access control (via <a href="https://x.com/sergejns_/status/2083568833017573530" rel="noopener nofollow ugc">sergejns_</a>).</li>
</ul>
<h2><a name="p-40407-infrastructure-network-2" class="anchor" href="#p-40407-infrastructure-network-2" aria-label="Heading link"></a>Infrastructure &amp; Network</h2>
<ul>
<li>KusamaShield highlighted private DOT transfers and cross-network swaps, including BTC, via open-source zero-knowledge smart contracts, citing a cost of 0.0156 DOT per shielded transfer on the hub (via <a href="https://x.com/KusamaShield/status/2083307897526906901" rel="noopener nofollow ugc">KusamaShield</a>).</li>
<li>Binance’s hot wallet on Polkadot Asset Hub was reportedly topped up with 5M USDC, adding notable stablecoin liquidity on-chain (via <a href="https://x.com/SO_DA_zone/status/2083517273290014965" rel="noopener nofollow ugc">SO_DA_zone</a>).</li>
</ul>
<h2><a name="p-40407-general-updates-3" class="anchor" href="#p-40407-general-updates-3" aria-label="Heading link"></a>General Updates</h2>
<ul>
<li>Polkadot referenda 1926 and 1927 drew support from Saxemberg, who voted AYE on the Wish for Change proposal to burn 100% of DOT revenue from JAMKB sales rather than route it to treasury build-up or grants (via <a href="https://x.com/saxemberg/status/2083682438845243823" rel="noopener nofollow ugc">saxemberg</a>).</li>
<li>XodeNet announced an upcoming AMA and opened the floor for community questions (via <a href="https://x.com/XodeNet/status/2083461240429670653" rel="noopener nofollow ugc">XodeNet</a>).</li>
</ul>
<hr>
<h2><a name="p-40407-processing-log-4" class="anchor" href="#p-40407-processing-log-4" aria-label="Heading link"></a>PROCESSING LOG</h2>
<ul>
<li><strong>Report Generated:</strong> 2026-08-02 10:03:10</li>
<li><strong>Total X posts curated:</strong> 676</li>
<li><strong>Posts Filtered and Analysed:</strong> 651</li>
<li><strong>Data Source:</strong> X (Twitter)</li>
</ul>
<hr>
<p><sup>This report is auto-generated and provided for informational purposes only by OpenShore, a Pala Labs initiative. The content is based on posts from X and may contain inaccuracies. We do not guarantee its completeness or correctness.</sup></p>

Polkadot Socials Daily Digest: 2026-08-02

<p>From what I understand from previous proposals, third-party projects are no longer being funded. Instead, they are being encouraged to seek funding from VCs.</p>

Dr.CAO

ComputeFlux: The First OpenAI-Compatible AI Gateway for Polkadot

Kusama Shield new release

<p>This question wasn’t directed at me, but I’d still like to share my perspective.</p>
<p>Lately, I’ve been thinking about how AI applications have made life much easier for crypto projects. When we use AI products professionally, we consume tokens that we pay for with real money, and we do it without hesitation or complaints because those products solve real problems for us. In return, they help us generate value, whether that’s financial or professional.</p>
<p>So I think the idea that users are unwilling to pay has largely been disproven. People are perfectly willing to pay when they believe a product is genuinely valuable.</p>
<p>In the current crypto landscape, I think the most practical approach is to put stablecoins first because of their massive adoption, while implementing a mechanism (smart contracts, for example) that also benefits the ecosystem’s native token, all without the user even noticing.</p>
<p>To me, that’s where the real opportunity lies.</p>
<p>I also think the key to success is making everything as simple as possible for users. People don’t want unnecessary complexity anymore, they want solutions they can adopt quickly without facing a steep learning curve. After all, that was one of the things that pushed away the first wave of people who came to Polkadot.</p>
<p>I may have drifted a bit from your original question, but I think it’s closely related.</p>

Liliana Mendez

First Edition of &ldquo;Advice Nobody Asked Me For&rdquo; for the Polkadot Ecosystem

First Edition of "Advice Nobody Asked Me For" for the Polkadot Ecosystem

<h2><a name="p-40386-technical-developer-activity-1" class="anchor" href="#p-40386-technical-developer-activity-1" aria-label="Heading link"></a>Technical &amp; Developer Activity</h2>
<ul>
<li>Builders tested the Polkadot Products devnet with prototypes including streaming payments, a revocable trustgraph reputation system, and a fully on-chain drumpad built with Fable 5 (via <a href="https://x.com/zerokn0wledge_/status/2083150392964047143" rel="noopener nofollow ugc">zerokn0wledge</a><em>, <a href="https://x.com/keeganquigley_/status/2083022202601906197" rel="noopener nofollow ugc">keeganquigley</a></em>).</li>
<li>On-chain gaming experiments continued on Polkadot’s Bulletin Chain, including fully on-chain NES-style games (via <a href="https://x.com/thewhiterabbitM/status/2083134855202677163" rel="noopener nofollow ugc">thewhiterabbitM</a>).</li>
<li>KusamaShield showcased ZK-powered private DOT transfers and cross-network swaps, citing a 0.0156 DOT cost per shielded transfer on the Hub (via <a href="https://x.com/KusamaShield/status/2083307897526906901" rel="noopener nofollow ugc">KusamaShield</a>).</li>
</ul>
<h2><a name="p-40386-general-ecosystem-2" class="anchor" href="#p-40386-general-ecosystem-2" aria-label="Heading link"></a>General Ecosystem</h2>
<ul>
<li>The Polkadot staking dashboard added Russian and Japanese support, bringing its total to 10 languages based on top user locales, and reported over 11,000 monthly unique visitors while inviting feedback on DOT staking management improvements (via <a href="https://x.com/TheWeb3Cloud/status/2083182194659348515" rel="noopener nofollow ugc">TheWeb3Cloud</a>, <a href="https://x.com/TheWeb3Cloud/status/2083227689142391112" rel="noopener nofollow ugc">TheWeb3Cloud</a>, <a href="https://x.com/TheWeb3Cloud/status/2083219887531671836" rel="noopener nofollow ugc">TheWeb3Cloud</a>, <a href="https://x.com/TheWeb3Cloud/status/2083251848346308788" rel="noopener nofollow ugc">TheWeb3Cloud</a>).</li>
<li>Chainspect data cited by BSC News showed Polkadot daily transactions rising to 986, an 11,300% one-day increase (via <a href="https://x.com/BSCNews/status/2083320551347486959" rel="noopener nofollow ugc">BSCNews</a>).</li>
</ul>
<hr>
<h2><a name="p-40386-processing-log-3" class="anchor" href="#p-40386-processing-log-3" aria-label="Heading link"></a>PROCESSING LOG</h2>
<ul>
<li><strong>Report Generated:</strong> 2026-08-01 10:03:10</li>
<li><strong>Total X posts curated:</strong> 666</li>
<li><strong>Posts Filtered and Analysed:</strong> 643</li>
<li><strong>Data Source:</strong> X (Twitter)</li>
</ul>
<hr>
<p><sup>This report is auto-generated and provided for informational purposes only by OpenShore, a Pala Labs initiative. The content is based on posts from X and may contain inaccuracies. We do not guarantee its completeness or correctness.</sup></p>

Polkadot Socials Daily Digest: 2026-08-01

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)

PoP Bounty — June 2026 Transparency Report

test

PoP Bounty – April 2026 Transparency Report

⚠️ Warning to all Kusama nominators

- Subscan is a tool to see what happens on Kusama.
- It will work for all of 2026.
- The community pays a small amount each month.
- If service is bad, the community can stop paying.
- The price is lower than before.

Subscan Enterprise Explorer License - Kusama 2026 Milestone-Based Service

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

Kusama

treasury31

discussions1398