Update (please vote NAY): We’ve since confirmed with the runtime/dev team that the existing bounties pallet will not support the multi-asset / DOT-based KV flow we intended. The prior plan to extend the current bounties ran into breaking changes, so the approach is now a new multi_asset_bounties pallet.

As a result, bounties #35 #36 #37 are not going to be the correct on-chain mechanism for Kusama Vision going forward. We will therefore recreate the bounties under the new pallet once it is deployed on Kusama Asset Hub, and resubmit the appropriate OpenGov actions at that time.

The curator groups remain the same; this is purely a technical substrate/pallet migration issue.

Summary:
Kusama Shield is a Zero Knowledge powered Shielded Pool, deployed as a sovereign smart contract on Kusama Assethub. Created as the first RFP on Kusama, live on the Attemps at Governance show. The first MVP version of Kusama Shield has been delivered and we now want to bring a stable version live, utilizing the power of PolkaVM to power the future of shielded tokens. Our goal is now to make the stable version of Kusama Shield the best option for EVM dapp developers that want to utilize shielded transfer into their smart contracts, by integrating Kusama Shield into the Ethereum toolkit Kohaku.

Bounty Curators:

• Erin(byteboro)
• Flipchan
• James Slusser

The Bounty curators review and moderate all milestone deliveries.

Previous referendum:
https://kusama.polkassembly.io/referenda/509

Funding:
We are requesting 75129 USD to cover ~7 months of development.
KSM EMA7 Price ( USD ): 7.022300

Links:

Landing page: https://shield.markets/

Codeberg code repo: https://codeberg.org/KusamaShield

Full proposal Link: https://docs.google.com/document/d/12LHzU0STBlRfKOXIn0bzpda11rmg59tbMoGzmXl-OUs/edit?usp=sharing

Noticeable v1 features shipped:

• Swap 40+ l1 assets, enabled 40+ non ecosystem asset to swap directly into dot with low fee’s (0.4-0.6%)
• DOT > KSM one click swaps
• First ZK Poseidon hashing function optimized for polkaVM: https://codeberg.org/KusamaShield/PoseidonPolkaVM
• Halo2 and Groth 16 ZK circuits for Kusama Assethub

This proposal requests a 6-month top-up to continue supporting Kusama System Parachain collators (AssetHub, BridgeHub, CoreTime, People, and Encointer). The goal is to sustain a reliable, decentralized collator set for critical system infrastructure by funding performance-based incentives for eligible collators (invulnerable + permissionless; developer slots are excluded). Payouts are distributed proportionally to blocks authored during each assessment period.

The proposal also includes a small monthly allocation for staking rewards (yield on 50 KSM per collator), ongoing infrastructure costs for local archive RPC access used for verification and dispute resolution (with retrospective queries limited to 3 months), and amortized development to complete a new block-author scraping tool (already partially developed and being prototyped) to reduce operational overhead and improve reliability of monthly accounting.

Ask (6 months):

• 17,456.59 KSM total (estimated), based on $7.3985 per KSM
• Equivalent to $129,152.59 USD total

Monthly estimate:

• 2,909.43 KSM/month (estimated)
• Equivalent to $21,525.43 USD/month

The proposal document can be found here -> https://gist.github.com/paradox-tt/a30a2661935a8343c39b47ae127cc5aa

Regards,
Will | Paradox

Our vision

To make moving, saving, and programming money in stablecoins as easy as integrating a single line of code, using the Kusama network as the default ledger for the next generation of fintechs and marketplaces.

Summary

Bloque is a unified SDK to embed stablecoin into digital products. With a few lines of code, teams ship wallets, local rails, global payouts, virtual accounts, cards, and swaps, bridging DeFi potential for builders who understand customer pains. Meanwhile, we absorb the complexity while safeguarding value in the Kusama Hub.

This Stage 3 request is a targeted engineering and operations scale-up to keep current production reliable and expand capability: retain the core team, add backend capacity, and extend spend support beyond dUSD to local tokens (e.g., COP, MXN, BRL) so Kusama can capture real-world commerce denominated in local currencies.

The funding request is $90,000 for 6 months ($3,000 × 5 team members × 6 months).

Previous Proposals:

1. Stage 1: Setup licenses and launch debit card: https://kusama.subsquare.io/referenda/499
2. Stage 2: 20k physical cards helped us to sign our new fintechs and marketplaces https://kusama.subsquare.io/referenda/568
3. Stage 3: This proposal focuses on strengthening our infrastructure, retaining key talent, and continuing to build a platform that makes the Kusama Hub the place where fintechs, banks, and marketplaces come to launch stablecoin financial products.

Customers

We're now the financial backend for: ColocaPayments (LatAm e-commerce payments), Tikin (LatAm payroll/rewards), Beu (creator economy marketplace), and TravelSaverz (travel marketplace). We project ~$3M monthly payment volume as they ramp.

SDK

We've already have a functional product that's used by our clients, we are an efficient team of predominantly coders and a sales/compliance member.

SDK:

• Documentation: https://docs.bloque.app/en
• SDK (js): https://github.com/bloque-app/sdk
• SDK (payments): https://github.com/bloque-app/payments
• SDK (java): https://github.com/bloque-app/sdk-kotlin

APIS:

• swaps: https://api.bloque.app/docs/swap
• origins: https://api.bloque.app/docs/origins
• ledger: https://api.bloque.app/docs/ledger
• compliance: https://api.bloque.app/docs/compliance
• payments: https://api.bloque.app/docs/payments

Real time metrics

For the first time ever, you can watch end-customer spending flow through the Kusama Hub, live. Our SDK ships virtual cards, US ACH virtual accounts, EVM wallets (starting with Polygon), Bancolombia rails, and payment links, while everything ultimately settles on Kusama AssetHub.
https://metrics.bloque.app/

Personal Note

I’ve been coding nonstop for months, Monday through almost every Sunday, to keep us moving forward. I’m honestly exhausted and starting to burn out. We’re at a point where extra hands aren’t a “nice to have,” they’re what will let us keep growing and actually make this happen.

My code talks for me, thanks for taking the time to consider this proposal, I really appreciate it.

Full Proposal Here

Replaced by https://kusama.subsquare.io/referenda/601

Deregister paraID 2114: Turing Network

The following proposal is to request Kusama Governance to deregister paraID 2114, corresponding to Turing Network.

Why Governance?

There are technical ways of being able to deregister a paraID, however none of these are currently available for paraID 2114.

First of, the paraID status is locked: true. This means that the only way deregister the paraID is by sending a message from the parachain itself. However, the team can't currently run the parachain, and thus it can't send a message to the parachain to perform the needed actions.

Encoded Key Storage: 0x3fba98689ebed1138735e0e7a5a790abcd710b30bd2eab0352ddcc26417aa1946e9b797315c3ac3942080000

Therefore, the only way to currently deregister the paraID is by governance approval on the Root track.

ParaID Ownership

The paraID is owned by account CmxJEdEniSV6hGWoKfHWLR6h4A1dh5gD1vgzmD12osJvGsk (same storage item as before), which is the account sending this de-registration request.

https://kusama.subscan.io/account/CmxJEdEniSV6hGWoKfHWLR6h4A1dh5gD1vgzmD12osJvGsk