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

This is a parachain host configuration scheduler change that increases the lookahead value from 3 to 5. The higher value is expected to improve the parachain block production reliability and block times.

Motivation and more details are available in this ticket comment.

Target enactment block: #31993343
Estimated Time: 2026-01-26 09:45:27 (UTC)

Whitelist: https://kusama.subsquare.io/fellowship/referenda/127

This proposal introduces activity-responsive tokenomics for Kusama through burns instead of a hard cap.

Key changes:
• Base inflation: 7.82% → 5%
• Fee burn: 50%
• Treasury inflow burn: 10%
• Treasury balance burn: 1% per period (100K KSM floor)
• Coretime burn: 25%

Result: Net inflation reduced from 7.82% to ~4.25% — a 46% reduction.

This proposal is complementary to @olanod's validator/core reduction plan. Together they address both supply side (burns) and cost side (validators).

Full proposal: https://gist.github.com/hantoniu-codeberg/b81ab97a9d31d1651e890aa12bb02610

Forum discussion: https://forum.polkadot.network/t/rfc-burn-based-tokenomics-for-kusama-the-ethereum-model-not-a-hard-cap/16540

Dear Kusama community,

I’m applying to become a registrar on the Kusama People system chain.
Here is what I stand for, and what I want to bring that doesn’t exist today.

About me

My name is Adam, I'm a cybersecurity professional and long-time contributor to the Polkadot ecosystem.

I operate two Polkadot validators:

• ECH0.RE/01 – 126cWhehuBFhQvbDqt26dWBNgELfkpc72WvJV3sx82qRogkT
• ECH0.RE/02 – 15KhD36jXQsqrAbYCjcTmguPYvBdCNdZFvEZbntAB1mrRN8Y

Details: https://ech0.re/validator

I have been selected four times by the Web3 Foundation for the whole duration of Decentralized Nodes programme (cohorts 1, 2, 2.1 and 3). I was also selected in the previous "One Thousand Validators" programme with both Kusama and Polkadot validators.

My social media accounts are linked to my on-chain identity, which currently holds a KnownGood judgement.

Why me as a registrar?

Because I combine three things not often found together:

1. Automation and technical depth

I’ve built a full registrar toolkit: teleportation (Asset Hub to People Chain), identity management, automated social verifications and KYC verification, and a full directory explorer.

2. Real human support and direct contact

Unlike institutional or company-backed registrars, I’m a single individual, available and reachable.
If you need help, you can simply send me an e-mail, DM me on X, Discord or Matrix, and I’ll personally walk you through the process.

3. Flexibility in how judgements are delivered

Even though most identity checks are automated, you are not forced to use the automated flow.
If you prefer a more human approach, I can handle everything manually via a direct conversation, even entirely by e-mail.

This combination makes the experience accessible to everyone, including newcomers who may be intimidated by technical tools and processes.

I enjoy contributing to the ecosystem, developing tools, running nodes, supporting users, and being active in community discussions.

Becoming a registrar would be a natural extension of this involvement.

As a validator, I’ve demonstrated transparency, responsibility and reliability. I intend to apply the same standards as a registrar.

What I bring that others don’t

A fair question, here’s what sets me apart:

• Human-first support: you can directly talk to me. No ticketing system, no delays. I am reachable every day, active on all channels, and people in the ecosystem already know I answer quickly.
• Complete end-to-end flow: teleport -> identity setup -> verification -> judgement -> display in directory. One single platform. Fully automated.
• Direct access to Reasonable and KnownGood judgements from the web app. Only 13 accounts in the Polkadot network and 21 in the Kusama network currently have a KnownGood judgement.
• Deep verification capabilities: already supporting X, Discord, Matrix, and e-mail. GitHub and website verifications are coming.
• Positive judgements when deserved, but also appropriate negative judgements (Erroneous, LowQuality, etc.) when signals indicate suspicious behaviour. These mechanisms exist but are almost unused today.
• Free judgements for everyone. I don't request any fee.
• Better decentralisation: increasing the registrar set strengthens the People Chain and improves neutrality in identity governance.

Where can this be tested?

My registrar application:

https://dotid.app

The support for Kusama was recently added: https://x.com/ech0re/status/2010119301563593142?s=20

Currently supports:

• Teleporting DOT or KSM from Asset Hub to People Chain
• Setting, updating, clearing on-chain identities
• Automated social + e-mail verification (OAuth2, bots, verification codes, etc.)
• Automated KYC verification with your mobile phone
• Complete identity directory with search, filtering and recent changes

Upcoming features:

• Matrix OAuth2 (replacing bot verification)
• GitHub verification
• Website verification

Important clarifications

I am already an official Polkadot registrar, approved by my previous ref on Polkadot: https://polkadot.subsquare.io/referenda/1803. As a result, I have already started giving on-chain judgements.

In addition, since the existing Polkadot & Kusama registrar PolkaIdentity was sunset, we agreed that I would temporarily take over Registrar #6 on Kusama so judgements could continue while my Kusama registrar referendum is prepared and decided.

As part of this transition, PolkaIdentity temporarily transferred Registrar #6 to me, through the following identity.setAccountId extrinsic call:

https://people-kusama.subscan.io/extrinsic/0x3552ca730e149e752f270b1f43d111296ba57281b2b602f236db889f16d53dc4

• Judgements after block 7,327,072 are mine
• Judgements before that block were issued by PolkaIdentity

This is clearly indicated via multiple disclaimers in the web app.

This temporary arrangement was made solely to serve the Kusama community and ensure continuity of on-chain identity judgements during the transition period.

Regardless of the outcome of this referendum, Registrar #6 will be transferred back to PolkaIdentity once the process is concluded.

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