candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Miscellaneous

What is the status of JAM development?

Brave Wallet - Status updates

Mike

Request for Feedback - Web3 Ad Targeting Marketplace

<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

Polkadot Forum Super Admin

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

Decentralized storage in JAM with erasure encoding on IPFS

Polykrate

Submerge Crystal: Open-Source Indexer API for Polkadot SDK Chains

Kutsal Kaan Bilgin

Substrate Java RPC Client

Mehrdad

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

Polkadot Staking Changes: Progress &amp; Timeline

De And De

Polkadot Staking Changes: Progress & Timeline

Polkadot-API Project Update

Jose NoName

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

Ecosystem

Security Audit &amp; Tech Debt Remediation: BEEFY, GRANDPA, BABE, Snowbridge, XCM, staking-async + Compensation Request

Vincent Geddes

Security Audit & Tech Debt Remediation: BEEFY, GRANDPA, BABE, Snowbridge, XCM, staking-async + Compensation Request

ArcheLabs Progress Report: Laying the Infrastructure for AI on Polkadot

Nathan

ContribNet — decentralized contributor compensation and project governance on Kusama

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

Good reads on proof-of-personhood

Alain Brenzikofer

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

How to P<>K bridge USDT or USDC

Asset Hub Migration - XCM FAQ

Remy Le Berre

<aside class="quote no-group" data-username="prodigalwon" data-post="1" data-topic="17647">
<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/prodigalwon/48/10964_2.png" class="avatar"> prodigalwon:</div>
<blockquote>
<p>When a message is successfully delivered through Snowbridge, the relayer who delivered it gets a reward. The pallet was storing the pending delivery nonce but not who should receive the reward. When the receipt arrived from Ethereum, the reward defaulted to whoever submitted the receipt transaction, meaning anyone watching the mempool could jump ahead of the legitimate relayer and steal their payout.</p>
</blockquote>
</aside>
<p>This is false. The reward recipient is selected by the P-&gt;E relayer who specifies the final reward account <a href="https://github.com/Snowfork/snowbridge/blob/5e8864550cbd724dde684556cefe4246fe4ef9b2/contracts/src/Gateway.sol#L405" rel="noopener nofollow ugc">here</a>. That transaction is practically always submitted through Flashbots to prevent front-running. Any relayer can relay the delivery receipt back to BridgeHub, and the reward recipient cannot be altered because the relayer needs to supply a valid Ethereum receipt proof that is cryptographically verified onchain.</p>
<p>I can’t take the Snowbridge reports seriously unless you give provide some actual evidence. Now that we’re in the age of AI, serious-sounding but invalid security reports are a dime a dozen.</p>
<p>Our bug bounty is hosted at <a href="https://hackenproof.com/programs/snowbridge-on-chain-code" rel="noopener nofollow ugc">https://hackenproof.com/programs/snowbridge-on-chain-code</a>.</p>

<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/e/e2521d8568cd5b799c121b66598ee2946828c154.jpeg" data-download-href="/uploads/short-url/wi7Q3kBOqcol9qVEjfpyQCvsGuo.jpeg?dl=1" title="1000053022" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/e/e2521d8568cd5b799c121b66598ee2946828c154_2_230x500.jpeg" alt="1000053022" data-base62-sha1="wi7Q3kBOqcol9qVEjfpyQCvsGuo" width="230" height="500" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/e/e2521d8568cd5b799c121b66598ee2946828c154_2_230x500.jpeg, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/e/e2521d8568cd5b799c121b66598ee2946828c154_2_345x750.jpeg 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/e/e2521d8568cd5b799c121b66598ee2946828c154_2_460x1000.jpeg 2x" data-dominant-color="EFF0F1"><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">1000053022</span><span class="informations">1080×2340 320 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><a class="mention" href="/u/bill_w3f">@bill_w3f</a></p>
<p><a class="mention" href="/u/danicuki">@danicuki</a></p>

<p>This is a really interesting direction, especially the focus on protocols instead of just another AI-facing app. The AHIP idea makes a lot of sense to me, since current chat interfaces do feel limiting when you try to do anything beyond text. Turning interaction itself into a portable layer could be a big deal if multiple hosts actually adopt it. I’m a bit more skeptical about the payment and identity side though, mostly because <a href="https://tropical-casino.com/" rel="noopener nofollow ugc">website</a> coordination and trust models get messy fast outside controlled environments. Vibly sounds ambitious, but I’d be curious to see how it handles real user behavior rather than ideal flows. Overall, promising but still very early.</p>

<p>Hello everyone,</p>
<p>I thought about trying to modify an IPFS Kubo node to accept cid push request with crypto guarantee instead of only pulling cid.</p>
<p>The idea will be the following :</p>
<ol>
<li>In the storage in Jam, keep the hash, it’s the key, but replace the value by a Reed Solomon sharding (erasure root, the shards cid, k and m). If a node assigned to a core need the value of a service, it will load it from its Kubo node, then check the result against the hash of the key. But how can you be sure the validators will have the needed cid to execute the service ?</li>
<li>Create a ts dapp with a Jam service where Polkadot account can rent their browser’s IPFS node(Helia) for a determined period of time, then add onchain their Libp2p address. The dapp has a Jam light node and read the world state, for each shards cid, it compute if it needs to be on their Helia node.</li>
<li>Once the world state is read and all the shards in the browser’s IPFS node, the storage renter can enter the protocol. The dapp reads the waiting pool of the extrinsic, check the services needed, if they are supposed to have a shard of it, and if it’s the case, sign its metadata with the bloc number and send it to the Kubo node of the validators.</li>
<li>Modify the Kubo node to read the Jam waiting pool, check the services required, check theirs cid shards, and listen to push of cid from eligible storage renter (present in the Jam service and supposed to possess this shard).</li>
<li>On accumulate, their could be a lottery for the storage’s participants to be rewarded if they provided the needed shards.</li>
</ol>
<p>That way, the data are prepared for the Jam node, it can focus on STF without stocking a lot of data.</p>
<p>A few of the limits of this protocol are :</p>
<ul>
<li>how to quickly verify for the lottery’s reward if a data renter is supposed to possess this cid on chain ?</li>
<li>how can I be sure there is no hole in the repartitions of the shards on the IPFS node at any given time ?</li>
</ul>
<p>Do you think it could be useful and does anybody want to do it with me to see it that works ?</p>

<p>Following Referendum 1412 (approved March 2025), the treasury committed ~3M USD for a full Brave Wallet integration with a 12-month delivery target (March 2026).</p>
<p>From the updates in this thread, the situation appears to reflect a pattern that is common in engineering-heavy environments: timelines are treated as flexible because technical complexity is inherently unpredictable.</p>
<p>However, from a governance perspective, that assumption is precisely what becomes problematic at treasury scale.</p>
<p>When funding is approved on a fixed-time, fixed-scope basis, delays should not be treated as an expected norm of execution — they should be treated as a deviation from the agreed conditions.</p>
<p>What we are seeing here is a gap between two models:</p>
<p>- an engineering-driven model where timelines naturally shift during implementation,</p>
<p>- and a treasury governance model that approved a time-bound deliverable under the assumption of predictable execution.</p>
<p>The issue is that only one of these models is currently being enforced in practice.</p>
<p>As a result:</p>
<p>- the 12-month commitment becomes non-binding in effect,</p>
<p>- delays carry no financial or structural consequence,</p>
<p>- and ecosystem capital absorbs execution uncertainty by default.</p>
<p>This is not about individual teams or competence. It is about whether OpenGov treats delivery timelines as real commitments or as approximate estimates that can slide without governance impact.</p>
<p>At the scale of Referendum 1412, that distinction matters.</p>

Kyle Den Hartog

<aside class="quote no-group" data-username="Hackvictim" data-post="25" data-topic="17552">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://avatars.discourse-cdn.com/v4/letter/h/c57346/48.png" class="avatar"> Hackvictim:</div>
<blockquote>
<p>Broader engagement<br>
Would you be open to bringing this proposal to other voters and delegates? In particular, the Web3 Foundation deserves direct engagement. W3F initially funded Hyperbridge as their inaugural funding initiative, the W3F CEO publicly endorsed it as embodying “the highest standards of security,” and the protocol is documented on the W3F-copyrighted Polkadot Wiki. Their involvement in this discussion should not be optional. Active outreach from a respected voice like Saxemberg would carry significantly more weight than from affected LPs alone.</p>
</blockquote>
</aside>
<p>you can expect zero broader engagement from other parties and anything will be a massive plus. Members of the web 3 foundation are definitely reading this and their silence already express their position. More than pointing out to PR/marketing lines on past announcements, a real connection is the founding partnership announced a few months back.</p>
<aside class="onebox allowlistedgeneric" data-onebox-src="https://coinpaper.com/5356/web3-foundation-and-scytale-lead-2-5-million-seed-investment-in-hyperbridge-to-build-the-end-game-for-blockchain-interoperability-on-polkadot">
  <header class="source">
      <img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/b/b760509425cd9be5ff4dcb08da2d51bb2a4441f0.png" class="site-icon" alt="" data-dominant-color="000000" width="16" height="16">

      <a href="https://coinpaper.com/5356/web3-foundation-and-scytale-lead-2-5-million-seed-investment-in-hyperbridge-to-build-the-end-game-for-blockchain-interoperability-on-polkadot" target="_blank" rel="noopener nofollow ugc" title="01:06PM - 11 September 2024">Coinpaper – 11 Sep 24</a>
  </header>

  <article class="onebox-body">
    <img width="69" height="69" src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/9/93daded22c271bf70f11e68f89378d8f382346e5_2_69x69.jpeg" class="thumbnail onebox-avatar" alt="" data-dominant-color="191919">

<h3><a href="https://coinpaper.com/5356/web3-foundation-and-scytale-lead-2-5-million-seed-investment-in-hyperbridge-to-build-the-end-game-for-blockchain-interoperability-on-polkadot" target="_blank" rel="noopener nofollow ugc">Web3 Foundation and Scytale Lead $2.5 Million Seed Investment in Hyperbridge...</a></h3>

  <p>Boston, Massachusetts, September 11th, 2024, Chainwire</p>


  </article>

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

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

<p>Lead investors usually have a close connection to said investments so probably they are already in touch with Polytope and it is most certainly a deliberate choice not to participate in public conversation or it might actually be what Thomas said that they are not interacting with the issue at all. Both of which are likely options. In any event we could attempt some further communication now that the April 30th window has closed and real figures can emerge.</p>
<p>Recoverable amounts should already be known despite of them being recovered or not.</p>
<p>As for Bifrost, Thomas already mentioned that they are a user and it’s not in their responsibility to engage or bail out anything from this event though they definitely will suffer from the reputational fallout.</p>
<p>Hopefully these parties can emerge or are already engaged significantly.</p>
<aside class="quote no-group" data-username="Hackvictim" data-post="25" data-topic="17552">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://avatars.discourse-cdn.com/v4/letter/h/c57346/48.png" class="avatar"> Hackvictim:</div>
<blockquote>
<p>A practical question: do you (or coordinated parties) hold sufficient BRIDGE to pass a WFC Referendum on the Hyperbridge Chain? The voting power distribution between Polytope Labs, Hyperbridge Foundation, and external holders is not fully transparent to me. If Polytope retains majority voting power, they could block the WFC against their own interests. Understanding this helps us assess whether the May 20 deadline creates real pressure or primarily symbolic pressure (both have value, but they are different strategically).</p>
</blockquote>
</aside>
<p>It should be possible to pass such vote unless the BRIDGE treasury votes against, something that shouldn’t happen as it’s meant for distribution. If the vote were to be blocked then the only parties that hold enough BRIDGE to veto it should be developers and lead investors (refer to the linked article). In which case you can know for sure and which party wouldn’t want that to happen. Until then, all these parties should have weighed their opinion one way or another.</p>
<aside class="quote no-group" data-username="Hackvictim" data-post="25" data-topic="17552">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://avatars.discourse-cdn.com/v4/letter/h/c57346/48.png" class="avatar"> Hackvictim:</div>
<blockquote>
<p>May 20 deadline and beyond<br>
Fully agree to wait until May 20 for a substantive Hyperbridge post-mortem with concrete numbers, deadlines, and refund mechanism. That is fair.</p>
</blockquote>
</aside>
<p>The self-imposed April 30th window has already passed so all these numbers should become known as well as a realistic plan for refunds of the existing tokens. Large portions allegedly remain recoverable so hopefully this realistic plan comes in time.</p>

Hackvictim

<p>Submerge Crystal API v0.1.1 is now available for Polkadot Bridge Hub, Collectives, Coretime, and People. Documentation is available at <a href="https://docs.submerge.io/crystal-api" rel="noopener nofollow ugc">docs.submerge.io/crystal-api</a> (sometimes a refresh is necessary to view the changes), and OpenAPI v3.1.0 specification is available <a href="https://raw.githubusercontent.com/helikon-labs/submerge/refs/heads/main/submerge-crystal/api-spec/submerge-crystal-api.json" rel="noopener nofollow ugc">here</a>. Current endpoints:</p>
<ul>
<li><code>https://bridge-hub.polkadot.crystal.api.submerge.io/v1</code></li>
<li><code>https://collectives.polkadot.crystal.api.submerge.io/v1</code></li>
<li><code>https://coretime.polkadot.crystal.api.submerge.io/v1</code></li>
<li><code>https://people.polkadot.crystal.api.submerge.io/v1</code></li>
</ul>
<p>Polkadot relay chain and Asset Hub currently indexing, targeting next week. Kusama deployment, platform-specific clients, and applications to follow.</p>
<p>PS. This can still be considered as an early alpha release, with ongoing performance and ergonomics improvements. Please post under this thread or reach out via DM for any issues or feedback.</p>

<p>If proposers cannot clearly define how the funds will be used, what outcomes are expected, or lack even a basic execution plan, then approving such funding risks wasting resources and undermining community trust. Over time, this can weaken the credibility of the entire governance system rather than strengthen it.</p>
<p>Therefore, without clear plans and accountability, the Treasury allocation should not be increased. Instead of expanding the budget, the focus should be on improving proposal quality and strengthening review standards to ensure funds are used effectively.</p>

jonas

<p>agree, also <a class="mention" href="/u/josep">@josep</a> attitude really doesn’t work for me, he is lacking professional maturity, and needs to grow up, he is not conducive of team building… Can’t read a room.</p>

@iamflez

<p>good initiative! thanks for putting the time to think about this, this could also work under a curators structure onchain. curators could fund/curate a project and pay for that project to a group, if another group wants to help with the code on an ad-hog matter, probably the curated team (the Genesis creator’s group) should pay for that, but the curators are the ones authorizing it, not the original curated group.</p>
<p>do you have a public github of the project? (i’m a tech noob)</p>

<p>Seems to be a clear conflict of interest. they should recuse from voting, the system should and could automatically do that…</p>

Serious Concerns About Proposed Spending on Encointer Infrastructure

<p>Hyperbridge team is DOUBLING-DOWN on their threat to prosecute users of their broken bridge as CRIMINALS:</p>
<aside class="onebox twitterstatus" data-onebox-src="https://x.com/i/status/2049462214508110194">
  <header class="source">

      <a href="https://x.com/i/status/2049462214508110194" target="_blank" rel="noopener nofollow ugc">x.com</a>
  </header>

  <article class="onebox-body">
    <img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/4/4c2daff8ea77a44e4c744451d9266aef59e0468e.png" class="thumbnail onebox-avatar" alt="" data-dominant-color="212022" width="48" height="48">
<h4><a href="https://x.com/i/status/2049462214508110194" target="_blank" rel="noopener nofollow ugc">Hyperbridge</a></h4>
<div class="twitter-screen-name"><a href="https://x.com/i/status/2049462214508110194" target="_blank" rel="noopener nofollow ugc">@hyperbridge</a></div>

<div class="tweet">
    <span class="is-reply">
      <svg class="fa d-icon d-icon-reply svg-icon svg-string"><use href="#reply"></use></svg>
    </span>
  <span class="tweet-description">One day left.

After April 30, wallet addresses still holding unreturned funds will be referred to law enforcement, alongside the on-chain evidence and transaction histories our forensics partners have compiled</span>
</div>

<div class="date">
  <a href="https://x.com/i/status/2049462214508110194" class="timestamp" target="_blank" rel="noopener nofollow ugc">12:14 PM - 29 Apr 2026</a>

    <span class="like">
      <svg viewBox="0 0 512 512" width="14px" height="16px" aria-hidden="true"><path d="M462.3 62.6C407.5 15.9 326 24.3 275.7 76.2L256 96.5l-19.7-20.3C186.1 24.3 104.5 15.9 49.7 62.6c-62.8 53.6-66.1 149.8-9.9 207.9l193.5 199.8c12.5 12.9 32.8 12.9 45.3 0l193.5-199.8c56.3-58.1 53-154.3-9.8-207.9z"></path></svg>
      7
    </span>

</div>

  </article>

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

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

<p>This attitude/behaviour is what I wanted to flag in my original message. I believe this is TOTALLY AGAINST Polkadot original values. They need to be removed and their brand completely disassociated with Polkadot.</p>

Truth

Call to Polkadot Community and Web3 Foundation to distantiate from Hyperbridge Team

KYC-free offramps for DOT | Kusama Shield comes to Polkadot Hub

<p>I dont agree with the idea that the need is low. Java is one of the most popular programming languages in the world, and anything that aims to be successful should  support it. In fact, I’ve personally seen how the lack of Java tooling for Polkadot has slowed down its adoption.</p>
<p>In my previous job at a crypto exchange, our entire backend stack was Java—just like many other exchanges and enterprise systems. Java is the number‑one choice for high‑reliability platforms like exchanges. Because Polkadot didn’t have strong Java support, integrating it took significantly longer than other networks that already had mature Java tooling(we had to use JS!). That delay translated directly into slower adoption.</p>
<p>In the highly unpredictable crypto market, small technical gaps can trigger outsized effects on adoption and user behavior, I hvae seen this with my eyes!</p>

<p>The Internet is being gradually <a href="https://youtu.be/RE51m6JnYMo" rel="noopener nofollow ugc">locked down</a> like a boiling frog, undermining our potential to resist tyranny. Before long all Internet devices and services will require ID verification and VPNs will be banned.</p>
<p>Of course, in Web3, the theory is that dapps can provide peer-to-peer means of coordination. While there has been some success in this regard, it has yet to really take the world by storm in the way that the Web did in a few short years.</p>
<p>Most on-chain programs are not really permissionless and those that <em>are</em> typically require a centralized backend to function. Decoupling of transaction publishing from the backend does have a lot of good properties, but dapps reliant on backends are still vulnerable to capture.</p>
<p>For a dapp to provide a rich user experience it needs various services that are inherently centralized. For example:</p>
<ul>
<li><strong>Full Node</strong> - State needs to be queried.</li>
<li><strong>Event Indexer</strong> - State is kept as minimal as possible to keep transaction fees low. Emitting events is the solution, but there needs to be a centralized database of events that can be queried.</li>
<li><strong>IPFS Pinner</strong> - Content published via IPFS does not stay available by itself. An always-on service must “pin” content for it to be available to other users.</li>
<li><strong>IPFS Address Cache</strong> - It can take too long for a dapp to find who has the required IPFS content. An address cache can make this immediate, but this is an always-on, shared service.</li>
<li><strong>Content Search</strong> - Full text search is expected in a modern app, but this is an inherently centralized service.</li>
<li><strong>AI</strong> - Users want powerful AI features that they will not run on their local device.</li>
</ul>
<p>While these services are essentially impossible to implement in a peer-to-peer manner, they can be implemented in a federated manner provided they are standardized. If there is a flock of available backend providers to pick from, the dapp can switch ad-hoc between them.</p>
<p>When querying untrusted backends it is essential that there is a system to prove the data is correct. In the Polkadot ecosystem, the dapp can run a light client to use finality proofs to ensure state queries are correct.</p>
<p>When querying an event indexer it is also possible to verify the events are correct using finality proofs. Although, it is not possible to guarantee that the indexer has not left out some results. This can be helped by querying multiple indexers run by different groups.</p>
<p>If the IPFS hash is proven to be correct by a finality proof, then the content retrieved from IPFS is guaranteed to be correct.</p>
<p>Positive content search results can be verified by examining the content. Again, it is not possible to prove that a search service has left something out, but a dapp can query different services over time to determine which ones are trustworthy.</p>
<p>Users could use multiple IPFS pinning services to ensure content remains available.</p>
<p>As there are multiple providers, they will compete against each other on various criteria.</p>
<h2><a name="p-39023-what-is-acuity-index-1" class="anchor" href="#p-39023-what-is-acuity-index-1" aria-label="Heading link"></a>What is Acuity Index?</h2>
<p><a href="https://index.acuity.network/" rel="noopener nofollow ugc">Acuity Index</a> is part of the broader <a href="https://acuity.network/" rel="noopener nofollow ugc">Acuity</a> decentralized CMS.</p>
<p>It is a federated, multi-chain Polkadot event indexer with finality proofs, primarily intended to make dapps fully decentralized.</p>
<p>It was originally called Hybrid and was funded by two (<a href="https://github.com/w3f/Grants-Program/blob/master/applications/hybrid.md" rel="noopener nofollow ugc">1</a>, <a href="https://github.com/w3f/Grants-Program/blob/master/applications/hybrid2.md" rel="noopener nofollow ugc">2</a>) Web3 Foundation grants and a Kusama Treasury <a href="https://kusama.subsquare.io/referenda/534" rel="noopener nofollow ugc">referendum</a>. A second funding referendum <a href="https://kusama.subsquare.io/referenda/567" rel="noopener nofollow ugc">failed</a>. Treasury funding for a Kusama Forum based on Acuity Index has been <a href="https://kusama.subsquare.io/referenda/603" rel="noopener nofollow ugc">secured</a>.</p>
<p>Due to AI, reliance on funding for the development of the project is no longer necessary. The development of Acuity Index has massively accelerated. Already in 2026, more work on the indexer has been completed than in all the previous years combined. Examine the <a href="https://github.com/acuity-network/acuity-index/commits/master/" rel="noopener nofollow ugc">commit log</a>.</p>
<p><a href="https://crates.io/crates/acuity-index/0.8.0" rel="noopener nofollow ugc">Acuity Index 0.8.0</a> has just been released for experimentation. It has the following features:</p>
<ul>
<li>Config-driven indexing with support for compound keys and multi-keys</li>
<li>Index specification checkpointing. When a new checkpoint is added re-indexing will occur from that block.</li>
<li>Hot reload for accepted index-spec changes</li>
<li>Concurrent backfill and head catch-up</li>
<li>Asynchronous and multithreaded design for maximum node indexing performance<br>
(63.1k events per second on AMD Ryzen 7 6800HS Creator Edition (16) @ 4.79 GHz)</li>
<li>Finality proofs that can be verified by a light client running in the dapp</li>
<li>Key subscriptions - notify dapp as soon as the key is included in a block</li>
<li>Event variant indexing - search for or subscribe to all events of a certain type</li>
<li>Prometheus / OpenMetrics monitoring</li>
<li>Full unit and integration testing</li>
</ul>
<p>Examine the <a href="https://index.acuity.network/docs/about/problem/" rel="noopener nofollow ugc">documentation</a> to see how it works.</p>
<p>Here’s a screencast showing how a dapp can query events with Acuity Index to create a rich user interface:</p>
<p><a href="https://youtu.be/V5QZNv3niKo?t=150" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/3/34d094a6efc9d2e01775164a3ca663ad24d26dce.jpeg" data-base62-sha1="7xdI38i9ankdiCmeOh7qRiOIhnU" width="690" height="388"></a></p>
<p>Here’s the <a href="https://github.com/acuity-network/acuity-dioxus" rel="noopener nofollow ugc">repo</a> for the dapp.</p>
<h2><a name="p-39023-federated-indexing-2" class="anchor" href="#p-39023-federated-indexing-2" aria-label="Heading link"></a>Federated Indexing</h2>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/5/51d8a5d62cebb2e7ffbd5666189b4bf6ba31feee.svg" data-download-href="/uploads/short-url/bG2Q8kdBLTnu7Cr8bKq0Gp6p5g2.svg?dl=1" title="acuity-index.svg" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/5/51d8a5d62cebb2e7ffbd5666189b4bf6ba31feee.svg" data-base62-sha1="bG2Q8kdBLTnu7Cr8bKq0Gp6p5g2" width="685" height="500"><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">acuity-index.svg</span><span class="informations">1256×916 469 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>While an instance of Acuity Index can be hosted and a dapp hard-wired to use it, the intention is that there are multiple indexes available for each dapp.<br>
The idea is that anyone can host a standardized index and potentially get paid to do so. Here is how it will work.</p>
<p>The Acuity DAO will establish the correct index spec for a given chain. Anyone hosting that index for the public can pay a deposit to register their endpoint on the Acuity blockchain. There is a micropayment system where dapps can query different providers in an ad-hoc manner, determining which ones tend to work the best and charge the least. The fees are paid to the index operator in ACU, the native coin of the Acuity blockchain. The dapp user has the option to pay in any currency as this will be routed through the <a href="https://hydration.net/" rel="noopener nofollow ugc">Hydration</a> exchange on Polkadot.</p>
<p>Acuity Index will also provide access to state queries on the full node. Over time this will be expanded to all the other federated services that dapps need access to.</p>
<h2><a name="p-39023-building-the-ecosystem-3" class="anchor" href="#p-39023-building-the-ecosystem-3" aria-label="Heading link"></a>Building the Ecosystem</h2>
<p>Who I am looking for:</p>
<p><strong>Chain Builders</strong></p>
<p>I want to add all Substrate-based chains to the platform. This will involve working with the teams to determine the correct index specification for the chain and then registering this on the Acuity blockchain.</p>
<p><strong>Index Providers</strong></p>
<p>Those who are interested in running indexes and registering on-chain so dapps can utilize them.</p>
<p><strong>Dapp Developers</strong></p>
<p>Querying event indexes is an extremely powerful technique for dapps. Reach out if you would like me to help build a dapp with Acuity Index.</p>
<hr>
<p>If you are interested in participating, don’t hesitate to reach out. My contact details:</p>
<ul>
<li>telegram: <span class="mention">@ethernomad</span></li>
<li>email: jbrown@acuity.network</li>
</ul>

Jonathan

How To Build Real Dapps With Acuity Index

Nasihudeen Adegboyega Jimoh

Under Pressure: Simulating Mempool Flood Control and State Determinism

<p>By the way, could someone clarify the relationship between Paradox and these two operators who have been previously flagged as bad actors? It appears there are recurring monthly transfers between them, and it would be helpful to <a href="https://assethub-polkadot.subscan.io/account/15D2JM548bqRuE45aDmeF2WqiKC56WtNnRmCxVSree9YKwVb?tab=transfer" rel="noopener nofollow ugc">understand the nature and justification of these payments</a>.</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/6/624238940473878a32205d19b9634578814ecb6c.png" data-download-href="/uploads/short-url/e1eFxklQnbCWEBAw3cypDEGz6zi.png?dl=1" title="images" rel="noopener nofollow ugc"><img src="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/6/624238940473878a32205d19b9634578814ecb6c_2_588x500.png" alt="images" data-base62-sha1="e1eFxklQnbCWEBAw3cypDEGz6zi" width="588" height="500" srcset="https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/6/624238940473878a32205d19b9634578814ecb6c_2_588x500.png, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/6/624238940473878a32205d19b9634578814ecb6c_2_882x750.png 1.5x, https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/optimized/2X/6/624238940473878a32205d19b9634578814ecb6c_2_1176x1000.png 2x" data-dominant-color="F7F6F6"><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">images</span><span class="informations">1673×1422 342 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>If there is a legitimate operational reason for this, it should be clearly documented so the community can properly assess it.</p>

Validators running multiple identities and flipping commissions in same day

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

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)

Discovering the Dynamic Features of JLJL99

- DeServe is a new global RPC service for Kusama.
- It has 8 locations across 5 continents for fast access.
- It is 87% cheaper than the current main provider.
- It already serves over 36 million requests daily on Polkadot.
- The proposal asks for 3,003 KSM to start the Kusama service.
- Services will include Kusama, Asset Hub, and others.
- Performance and costs will be shared publicly every month.
- It is built by Helikon, a trusted Polkadot team.

Rejected

DeServe.network Global Kusama Archive RPC Deployment - Proposal #1

- Encointer is a special part of Kusama that helps prove people are real online and lets communities create their own money.
- This request is for money to keep Encointer running for 9 months, like paying for computers and websites.
- Before October 2025, just as many people used Encointer as another important part of Kusama called Asset Hub.
- Encointer helps real people in places like Tanzania and Nigeria by making local money and using solar power for computers.
- The money will pay for important things like computers that make blocks, public websites, and tools to see how the system works.
- This does not pay for making new features or growing the community, just keeping it running.
- Encointer has won awards and helped start new businesses in Africa.
- The team has gotten money from Kusama before to keep things going.

[Medium Spender] Encointer System Chain – Infrastructure Operations (Apr–Dec 2026)

- 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

referenda2

treasury256

discussions1389