What is this proposal about?

We’re asking for funding to keep KuberIDE, a web-based tool for Cardano developers - running, up-to-date, and better than ever. KuberIDE lets developers write, test, and launch Plutus smart contracts right in their browser, without needing to set up complicated software. It’s already live at https://kuberide.com and helps developers focus on building instead of wrestling with technical setup.

What will we do with the funding?

Here’s our plan in simple steps:

Keep the Core Tool Up to Date: We’ll update the part of KuberIDE that turns code into working smart contracts (the Plutus compiler) so it’s faster and works well with Cardano’s latest changes.

Upgrade the Writing Space: We’ll improve the browser-based editor with features like better color-coding of code (syntax highlighting), clearer error messages, and automatic formatting—making it easier to write and spot mistakes.

Make It Faster and Stronger: We’ll boost the tool’s speed and ability to handle more users at once, so it stays smooth even as more people use it.

Simplify the Experience: We’ll polish the design and steps developers follow to build, test, and launch their smart contracts, cutting out confusion and hassle.

Why does this matter?

KuberIDE is already helping Cardano developers by taking away the headache of setting up a workspace. This proposal ensures it stays useful and grows with the community, making it easier for anyone, especially new developers to create Plutus smart contracts. It’s about saving time and letting developers focus on what they do best: building great things for Cardano.

In short, we’re taking a tool that’s already working, keeping it reliable, and adding improvements to make Cardano development simpler and faster for everyone.

Is Plutus still relevant? Even though there are other smart contract languages for a lower level entrance on Cardano, we think that Plutus based on Haskell is still relevant and will stay relevant. Multiple smart contract languages give students, developers the freedom of choice to write their smart contracts.

What problem are we trying to solve?

Building and testing smart contracts - automated agreements that run on the Cardano blockchain can be tricky and slow, especially for people new to Cardano. Some of these smart contracts use a language called Plutus, and getting started with it is tough. New developers often struggle to set up their workspace, which wastes time and makes it harder to get things done.

Our tool, KuberIDE, fixed this by giving developers an easy, web-based workspace that works right in their browser - no complicated setup is needed. It’s been a big help, but here’s the catch: without continued updates and support, KuberIDE could fall out of step with Cardano’s changes and what developers need today. This proposal aims to keep it useful and relevant.

In short, we’re addressing the challenge of making Plutus smart contract development simpler and faster for Cardano developers, especially beginners while ensuring our solution doesn’t get left behind as the network grows.

What will this proposal do, and who will it help?

This proposal is about keeping KuberIDE - a web-based tool for Cardano developers running strong and making it even better. KuberIDE lets developers create, check, and test Plutus smart contracts right in their browser, without needing to install complicated software. With this project, we’ll improve its speed, ability to grow, and ease of use, ensuring it stays valuable for the Cardano community.

How does this help the community?

Easier for Developers: It removes the hassle of setting up a workspace, so developers - especially beginners can jump in and start building faster.

*Quicker Testing and Ideas: * Developers can try out and test their Plutus smart contracts more quickly, speeding up the process of creating new apps for Cardano.

Great for Learning and Events: With no setup required, KuberIDE is perfect for teaching newbies or powering hackathons, helping more people get involved.

Keeps the Tool Reliable: We’ll make sure it stays up-to-date and works well as Cardano grows, so developers can count on it long-term.

Value to Cardano: This benefits new and current Plutus developers by saving them time and effort, which means more high-quality apps get built faster. It also welcomes more people into the Cardano community, through education and events - growing our network. The return on investment is a stronger, more active developer base, which makes Cardano more useful and attractive to everyone.

Deliverables

• Updated and optimized compiler engine for KuberIDE
• Enhanced in-browser code editor with better feedback and usability
• Improved system responsiveness and UI
• Regular releases and issue resolutions tracked via GitHub
• Developer support via Github and Discord

Definition of Done

• Updated KuberIDE instance live and publicly accessible
• Documented improvements with release notes
• Code performance improvements validated through internal benchmarks
• Final deliverables published on GitHub and community channels

Maintenance and support 100000 ADA or 50000 USD

Team: 2 core developers Duration: 12 months

Dquadrant website

The Kuber Team by Dquadrant has already developed and maintained KuberIDE from the ground up. We’ve worked on numerous Cardano-focused projects including:

• Cardano Mempool Explorer (Catalyst-funded)
• Autonomous Agent Testing (Catalyst-funded)
• GovTool Testing (uses Kuber API)
• Participation in hard fork readiness testing (Vasil, Chang)

We are deeply experienced in Haskell, Plutus, frontend/backend development, and infrastructure operations on Cardano.

How will we keep this tool working and useful ?

The main point of this proposal is to make sure KuberIDE, our web-based tool for Cardano developers stays reliable, fast, and easy to use.

After we finish the upgrades, here’s how we’ll take care of it:

Keep the Core Tool Up to Date: We’ll improve the part that turns code into smart contracts (the Plutus compiler) by:

• Making it faster so developers don’t wait as long.
• Updating it to match new versions as Cardano grows.
• Making error messages clearer so problems are easier to fix.

Upgrade the Writing Space:

• We’ll enhance the browser-based editor where developers type their code by:
• Showing instant feedback on mistakes as they type.
• Adding better color-coding and word suggestions for Cardano’s coding languages (Plutus and Haskell).
• Including simple tools to catch errors and tidy up the code.

Make It Faster and Stronger: We’ll boost the tool’s performance by:

• Speeding up the behind-the-scenes processes.
• Ensuring it works smoothly even when lots of people use it at once.

Simplify the Experience: We’ll polish how developers use the tool by:

• Making it easier to build, test, and launch smart contracts.
• Improving messages about errors or progress so they’re easy to understand.
• Helping new developers get started with a smoother first experience.

Fix Problems and Keep It Running:

We’ll stay on top of care by:

• Fixing bugs reported by users on GitHub (a site for sharing code) or the community.
• Testing the tool regularly to catch issues before they cause trouble.
• Keeping it online and stable so developers can always rely on it.

In short, we’ll actively maintain KuberIDE by making it faster, simpler, and more dependable ensuring it’s a tool Cardano developers can count on over time.

We have a formal endorsement from a Wims/Coxygen Global who is currently training a group of students (~ 50) in Africa relying on the capabilities of KuberIDE.

Further we know that an employee of IOG created a video about KuberIDE using it for certain occasions to write and test certain smart contracts quickly.

We don’t have any formal endorsements from groups like a Technical Working Group or CIP discussions yet, but KuberIDE - the tool we’re improving has already proven its worth in the Cardano community. Here’s how it’s been supported and used:

Real-World Use: KuberIDE has been a go-to tool in workshops, hackathons and internal Cardano projects. It helps developers create Plutus smart contracts on the blockchain faster and easier. You can check it out live at https://kuberide.com. Its use in these settings shows it’s valuable to real people working on Cardano.

Community Value: This proposal isn’t starting from scratch, it’s about keeping KuberIDE growing to meet what developers need as Cardano changes. Its track record shows it’s already helping, and we want to make it even better.

Built by a Trusted Team: The Kuber team from Dquadrant is behind this project. We’ve got a strong history with Cardano, including:

• Building Mempool Explorer to track transactions.
• Creating Cardano Autonomous Agent Testing for fair governance testing.
• Supporting big upgrades like the Vasil and Chang hard forks.
• Testing GovTool and the Constitutional Voting Tool to keep Cardano running smoothly.

Our work has made Cardano stronger, and KuberIDE is one of our successes.

Why This Matters: KuberIDE is already in action, helping developers learn and build. The Kuber team’s from Dquadrant achievements show we’re a reliable party that delivers for Cardano. This proposal builds on that trust and use, showing community support through real results.

What makes this special? This tool is one-of-a-kind for Plutus developers, giving them an advantage and making our network stronger. We’re confident that many students can be onboarded with this tool (like the example of Wims/Coxygen Global in Africa) and easily become productive in Plutus smart contract development.

In short, this is money well spent, it’s an investment in a unique tool that saves time, cuts costs, and supports Cardano’s growth.

What does this proposal need to get started and finished?

This project relies only on things we already have and control, no outside help is required.

Here’s what it depends on:

Our Own Tools: The proposal builds on KuberIDE, a tool we created and maintained ourselves. This includes the hosted Plutus compiler, the part that turns code into working smart contracts on Cardano. Since we manage it all internally, we don’t need anything from other groups or companies.

No External Needs: There are no dependencies outside our team, no special software or support from other people. Everything we need is already in place.

What’s Left to Do:

• To start, we just need the funding to kick things off.
• To finish, our team will handle the updates and improvements to KuberIDE - like making it faster and easier to use - using the tools and systems we’ve already built. It’s all up to us to get it done.

In short, this proposal stands on its own. It depends on our existing work and team effort, nothing more.