Hi all,
As some of you may know, I was involved in development of the Gateway service while working with Radix Foundation and formerly at RDX.Works.
With the ecosystem continuing to evolve toward more community-driven ownership and contribution, I wanted to open a discussion around the future needs of Gateway development and long-term maintenance.
We already have a discussion for Gateway hosting and infrastructure maintenance, but what seems less clear is whether there is demand for continued development support and engineering maintenance of the Gateway itself.
1. Is there interest in ongoing Gateway development maintenance?
To clarify, this is not about infrastructure monitoring itself, as Gateway infrastructure monitoring is already discussed on another topic.
I’m talking more about the software engineering maintenance side, such as:
-
upgrading dependencies and packages
-
keeping compatibility with potential ecosystem changes
-
bug fixing
-
performance improvements
-
technical debt reduction
-
reliability improvements
-
long-term codebase maintenance
Would the community or DAO see value in ensuring continued engineering maintenance for the Gateway codebase going forward?
2. Is there interest in Gateway feature development?
Is the current Gateway functionality sufficient for the near future, with focus mainly on stability and compatibility?
Or are there specific features, improvements, integrations, APIs, indexing capabilities, performance upgrades, or developer tooling that the community would like to see developed further?
It would be very useful to hear:
- what pain points you would like to fix
- if there are any features missing you’d like to implement
At this stage I mainly want to understand
- whether there is actual demand
- what expectations exist
If the community sees value in any of the above, and our expectations align, I’d be happy to discuss potential funding models, ownership structure, development priorities, or long-term maintenance approaches.