These items improve the developer and user experience. They are currently maintained by the Foundation/subsidiaries but represent prime opportunities for community teams to take over or build superior alternatives.
Impact:
Some services (e.g., RadQuest) carry ongoing monthly costs.
If there is no clear desire to maintain them, shutting them down would:
Reduce recurring operational expenses
Maximize the asset value transferred to the community
Streamline post-transition responsibilities
Input Needed:
The community is asked to provide input on the desired handover, open-sourcing, or shutdown of each P3 service.
Make sure to participate in the Google Form shared below to vote on the future of each P3 service. This is an informal input not the main vote.
Asset service: Simple service that presents foundation managed assets such as icons for foundation managed Dapp and tokens
Image Service: Image service that provides compression and caching on Cloudflare for community and foundation image assets.
Token Price and NFT Price Service: this service uses a third party API to populate the token/NFT prices in the Radix Wallet both overall, and per account.
Dashboard: This is a page that indexes Radix transactions and history for users. It also enables a UX for interacting with network staking. Community alternatives, such as Radxplorer already exist.
RadQuest: This is a guided onboarding dApp for Radix users. Both the front-end and essential backend/on-chain services are maintained by the Foundation.
Gumball Club: This is a very simple demo application that users can interact with when onboarding with the Radix wallet.
IDOS Proof-of-Personhood: A small dApp that integrates with the IDOS system to issue badges on Radix.
wallet.radixdlt.com: A simple front-end that guides the install and setup of the Radix Wallet.
Radix Rewards: A front-end and back-end system that monitors on-chain activity and issues reward points.
Radix Consultation dApp: A front-end and back-end system that enables admins to submit proposals for token holders to input on.
Developer Tooling
Radix dApp Toolkit: A github repo that handles the wallet<>dapp interactions and connect button.
Dev Console: This is an app to assist developers when interacting with the Radix network.
Sandbox: An app that assists developers when interacting with the Radix network.
Arculus CSDK: This is a private repo that is required to build a new release of the Radix Wallet that can support the Arculus card.
academy.radixdlt.com: An educational course that guides learning Scrypto basics. Live but not maintained.
learn.radixdlt.com: A knowledge-base directed to non-technical users to learn about Radix. Currently hosted on Webflow.
Fullstack Dapp Example: An example dApp for developers
Miscellaneous
XRD Supply API: this is a simple API that provides supply details for CoinGecko
dApp Catalog Service: This is a simple service that is used to populate the dApp directory in the Radix Walet.
Olympia-explorer: A legacy network explorer for the Olympia Radix Network.
Foundation Validators: Two validator nodes operated by the Radix Foundation for network monitoring and participation.
Olympia Radix Wallet: An old desktop wallet that can be used for updating to Babylon. End-of-life and no longer maintained.
Stokenet Gateway and Stokenet nodes: Run the Radix testnet.strong text
Important: If you are interested in contributing to, maintaining, or taking ownership of any of these P3 services; please specify which service and how you’d like to be involved in the thread below or share these details in the google form.
Please include your Telegram handle and/or email address so the foundation can contact you directly.
Stokenet Gateway and nodes , and also the dashboard and the dev console both for mainnet and stokenet are useful for existing and hopefully new dApps to come.
Image and prices service should also remain. same for IDOS and the consultation dApp that is really useful.
GitHub repo could be moved in the new repo and that should be quite simple.
Educational contents is useful but if only some should be mantained i’d say to take docs.radixdlt.
This isn’t a simple keep or shutdown Farah and I do not particularly enjoy the fact that it’s being done like this.
For each of these items we need to know what they technically require and how they can be taken over and properly supported by the community - the FND is not providing those and it needs to.
Not to mention the costs associated with each item.
PPL will be blindly choosing without no knowledge of what technically entails to keep or shutdown each item and how much it costs - what kind of decisions even are these then??
The FND as all of these tangled-up and interconnected, in such a way that some items, although presented as individual, are in fact dependent of others.
What would be helpful, instead of just the enumeration and brief description of the items, would be a proper clarification of the requirements each has and most importantly the dependency map between them, and ho much it costs to run them in their present form - should we want to just assume that.
If we don’t get costs for each of these it is USELESS. How should we propose alternatives if we don’t know the cost? It’s one thing to determine them critical for operations and another one to get involved in maintaining them.
In my opinion we should merge a lot of these including with some from P2 into one. Many are hosted as subdomains from the main website.
How I would do it is to simplify everything, and merge in one website that holds:
Website:
Radix Homepage
Blog
Wallet page that just redirects to download on github or appstores.
Docs (merge here Academy, Knowledge base, Docs) (some standard Starlight/Docusaurus)
Developer Hub page with redirects to gits and tools
* Most of these I think can be migrated to Cloudflare pages and hosting is nearly zero. It’s more the transition some work at the beginning.
Network operation:
wallet apps: iOS+Android
Stokenet nodes
Developer console + tools
Dashboard and explorer
Gits for all code: nodes, wallet, gateways, etc. Basically P1+P2
For the Radix Website plus Blog and all the other subpages, I would just pay for a couple of months the Webflow account, 250 usd/ mo or whatever Adam said, and just work in parallel on a new Website that has new design and is easier to maintain and has lower costs.
It’s just not worth migrating all this stuff specially when it’s bloated and a lot of content outdated.
I’d do some Redesign + Blog and use Astro + Cloudflare. Maybe even some headless CMS.
I already did a RFC regarding the website and blog, but didn’t put exactly costs for the new website as i have to map the entire content to realize what i’m getting myself into.
So I started scraping the existing website and blog, made a local copy and now trying already to link it to a CMS to push to Cloudflare. This in the idea to save what we have as content but also to build a platform to migrate towards.
Either way, my comments were more towards the core infrastructure, like node running, gateways, price/image api services, etc. It’s not my cup of tea that part, but whoever should take them, needs more details if they are to jump. So hopefully your proposal with the NDA works.
Make sure to participate in the Google Form shared below to vote on the future of each P3 service. This is an informal input not the main vote.