Referendum #1595

RegionX Hub – New Features & Improvements

3d ago

Executed

Content

AI Summary

Overview

With the newly deployed RegionX Hub, we have received very positive feedback so far, along with feature and improvement requests — some of which came from Parity and Fellowship members.

We fulfilled the smaller requests and covered the development costs using funds from our previous proposal. This proposal is intended to fund the development of features and improvements that would significantly enhance the overall value the RegionX Hub provides.

With recent incidents, such as failing to renew Coretime on time, it has become clear how important it is to offer an easy-to-use, intuitive interface for managing Coretime for projects.

We still feel that the majority of the community remains confused about how the Agile Coretime model works, what it offers, and how it can be used for their own purposes. We aim to address this by providing a clear, easy-to-use UI with dynamic dashboards and help centers tailored to specific types of users.

We have identified the following four types of users who use the RegionX Hub:

Existing teams that already have a project on Polkadot: These users are primarily interested in renewing their core in each sale. However, they may choose to purchase a new core from the sale if the price is significantly lower than renewing their existing one. This is why it’s important for them to track both the current state of the bulk sale and the secondary market.
New project teams: Users interested in purchasing a core either from the bulk sale or the secondary market. On the secondary market, it's possible to purchase regions that are usable immediately — unlike on bulk sale, where users must wait for the sale to end, which takes up to 28 days. The secondary market also allows users to purchase only a portion of a core, which is ideal for projects that don't require the full resources a core provides.
Coretime resellers: Users who purchase cores from the bulk sale and sell them on the secondary market for profit. They may also end up partitioning or interlacing the purchased region and selling it that way in the sale.
Enthusiast: Interested in tracking data related to Coretime sales and projects deployed on Polkadot. These individuals can be regular enthusiasts, developers, or investors monitoring Polkadot-related data.

For each user type, we want to establish a help center that provides all the relevant information specific to that user. This way, users won’t be overwhelmed by all the information about Agile Coretime, but will instead see only the parts that are relevant to them.

Also, the user-specific dashboards will display components relevant to the selected user type.

With this proposal, we aim to cover the development costs of delivering major features and improvements requested by the community and identified internally as valuable additions to the RegionX Hub.

Below is a table outlining the features and improvements covered by this proposal.

Features & Improvements
Task	Description	Reporting & Delivery Methods
Urgent renewals	From previous experience, we've seen what can happen when parachain teams don’t renew on time. If you're unfamiliar with this event, here are more details: link. Displaying ‘urgent’ renewals on the dashboard can greatly reduce the chances of this happening. Renewals that haven’t been completed but are required in the current sale cycle will be prominently displayed on the dashboard, so users are aware and can warn the parachain teams.	The development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website.
Auto renewals	Display which parachains have enabled auto-renewals and whether the parachain account has sufficient funds for the next renewal. The UI will also provide a guide for enabling auto-renewal for a parachain.	The development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website.
User specific dashboards	Provide different dashboards with relevant information tailored to each user type:Existing teams that already have a project on PolkadotNew project teamsCoretime resellersEnthusiast	The development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website.
Help centers	Gaining in-depth knowledge of the Agile Coretime model can be overwhelming for most users and also time-consuming.This is why, based on the selected dashboard type, we will provide a user-specific help center that offers only the most relevant information for that particular user type. This will reduce the likelihood of users making mistakes when interacting with the Agile Coretime model.	The development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website.
Other features & improvements	Integrate with more multisigs.	The development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website.
	Improved transaction status tracking after submitting a transaction
	Ability to connect multiple wallets simultaneously and have access to all accounts at once
	On-chain identity integration
	Batch core purchases
	Light client support

Here is the link to the full discussion: https://docs.google.com/document/d/1yNL_5FbTSN_ik68K068W8adepdwUZoFevJG6-n_4Pbs/edit?usp=sharing

RegionX Hub: https://hub.regionx.tech/

Up 1

Request

49,000USDT

Status

Decision28d

Confirmation

Attempts

Tally

70.7%Aye

50.0%Threshold

29.3%Nay

Aye

≈33.04MDOT

Nay

≈13.72MDOT

0.0%
0.0%
Threshold
0.0%

Support

0.38%

≈6.06MDOT

Issuance

≈1.58BDOT

Votes

Nested

Flattened

Actions

Check how referenda works here.

Call

Metadata

Timeline6

Votes Bubble

Statistics

Comments

14Pi...VXZa

OG Tracker Rating 3/3

Clear display of deliverables✅

Urgent renewals
Auto renewals
User specific dashboards
Help centers
Other features & improvements

Clear display of a valid direct point of contact ✅

Email: support@regionx.tech

Clear display of proposal’s duration✅

The duration of this proposal is 1.5 months.

OGT Rating aims to help voters make better informed decisions and direct proposers towards certain common-good practices. We are providing feedback based on 3 simple yet crucial criteria which we believe should be included in every OpenGov referenda.

Edited

13zn...P5ju

Dear Proposer,

Thank you for your proposal. Our first vote on this proposal is AYE.

The Small Spender track requires 50% participation and simple majority of non-abstain votes according to our voting policy v0.2, and any referendum in which the majority of members vote abstain receives an abstain vote. This proposal has received five aye and one nay votes from ten available members. Below is a summary of our members' comments:

The majority of voters expressed support for the referendum, emphasizing the importance of enhancing user experience and educational aspects. They highlighted the need for new access methods, such as auto-renewals, which they deemed essential for improvement. Many viewed the proposal positively, believing it would benefit the ecosystem and enhance team performance. However, one voter opposed it, citing dissatisfaction with the quality of the product delivered, especially given the significant financial investment made to date.

The full discussion can be found in our internal voting.

Please feel free to contact us through the links below for further discussion.

Kind regards,
Permanence DAO
Decentralized Voices Cohort IV Delegate

📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate

12mP...Eyoh

PolkaWorld votes AYE

Unanimous support from all members.

This proposal presents a well-thought-out UI design for Coretime, with user needs clearly segmented by type. The interface is intuitive and user-friendly, and once launched, it is expected to significantly improve the experience of purchasing and interacting with Coretime.

Each feature in the proposal is clearly defined, and the breakdown of work hours and compensation is especially transparent—making the proposal easy to understand and evaluate. The requested budget is reasonable and offers strong value for money.

One of our members even mentioned this is her favorite proposal so far—because it greatly streamlined the review process!

You can view our full feedback here.

13dV...6afh

Truth DAO votes AYE ✅

The RegionX team has a strong track record of delivery,
with a clear product need for Coretime platform integration.
The development budget is reasonable.

You can view the full feedback here.

13NC...8YFJ

JAM Implementers DAO votes NAY on this proposal.

While RegionX has taken some steps forward, the core issues around user experience (UX), reliability, and overall platform polish remain unresolved. Despite being a crucial tool for Agile Coretime, the current state of the product doesn't inspire confidence that these new improvements will be delivered effectively.

🔴 Poor UX persists — Multiple users have reported wallet connection failures, confusing interfaces, and inconsistent performance. These issues make the platform frustrating to use, especially for newcomers.

🔴 Missed expectations — Even after receiving prior funding, key aspects of the product remain unfinished or broken. Retroactive funding based on results might be more appropriate at this stage.

This isn’t a rejection of the mission — just a call for higher standards before treasury funds are spent.

1y2q...bmxR

✅ Why vote YES

• Solves a real user pain point: some parachains missed renewals due to poor UX.
• User-specific dashboards & help centers: tailored UI for teams, resellers, enthusiasts.
• Proactive renewal visibility: urgent alerts and auto-renewal status shown clearly.
• Community-backed roadmap: feature requests came from Parity, Fellowship, and project teams.
• Demystifies Agile Coretime: lowers confusion and risk for newer users.
• Open development: all progress tracked publicly on GitHub, deployed on RegionX Hub.

⸻

❌ Why vote NO

• Hub codebase not fully open source (though progress is public).
• Team-centralized execution: success depends on one group maintaining and iterating.
• Some features are secondary (e.g., multiple wallets or light client support).
• More UX refinement than core protocol innovation.

⸻

🎯 A user-focused UX upgrade that makes Agile Coretime accessible — though some may argue it’s not a core protocol need and better left to market forces.