Polkassembly Logo

Head 1
Head 3
Head 4
Head 2
Create Pencil IconCreate
TRACKS
ORIGINS
Report an issueNeed help with something?
Foot 1
Foot 2
Foot 3
Foot 4
OpenGov
View All Small Spender
Requested:49K USDT
Executed

RegionX Hub – New Features & Improvements

inSmall Spender
2 months ago
BeneficiaryBeneficiary:

(49K USDT)

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
TaskDescriptionReporting & Delivery Methods
Urgent renewalsFrom 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 renewalsDisplay 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 dashboardsProvide different dashboards with relevant information tailored to each user type:Existing teams that already have a project on PolkadotNew project teamsCoretime resellersEnthusiastThe development of this task can be monitored on the public GitHub repository. The end results can be seen on the RegionX Hub website.
Help centersGaining 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 & improvementsIntegrate 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/

Comments (6)

44 days ago

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.

2 months ago

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

Load more comments
PleaseLogin to comment

Proposal Passed

3

of 3

Summary

0%

Aye

AyeNay

0%

Nay

Aye (58)0.0 DOT

Support0.0 DOT

Nay (8)0.0 DOT

Voting Data

Approval%

Support%

Threshold0.00%

Threshold0.00%

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2025

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy