Please describe your proposed solution.
Cardano Native Scripts have 6 primitives which can be composed together in a flat, nested and even finite recursive form. This allows to create quite simple "smart contracts", like a simple multi-sig option, a treasury account, an escrow, time locked contracts. These contracts don't require advanced knowledge of smart contracts and programing, because they rely on composing them through simple logic.
I have already built the transaction editor as a web application and it allows for collaborative transactions. This project aims to extend it to also collaborate in crafting a Native Script. That is the easy part. A complete backend infrastructure is required to store all those Native Scripts, because if you loose your script, you won't be able to unlock the funds from those addresses.
As a firm believer in privacy, I must offer multiple options, and the most private by construction is the one I can't make money from. What perverse incentives of our society, we can offer privacy as a service because you loose it when you engage the service provider. In the same way that the transaction editor works, what can take place on your computer alone, is private and free, I don't want to know about. The native script editor itself is free of charge, and saving your scripts in your computer too.
The moment you need me to backup your script, I'll keep you anonymous, no need of email or any form of ID, a simple payment will match your wallet and give you an account. Now you have two storage systems your PC and my server. Once in the server you can engage in collaborative work, and have other people partake in your script building and signing.
Associated to a native script is an address. Your wallet does not manage this address, because up until today we only have single-signature wallets. Thus the editor must help you manage your funds on the script addresses. For this, I'll rely on the KOIOS REST API to gather information and load balance your use, also because that is a distributed service you'll have better anonymity compared to using a single service.
How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?
Every tool available enhances the ecosystem. Native Scripts are under utilized in the ecosystem, and they can be incredibly helpful for single users and even more for creating simple DAOs. Plutus smart contracts are highly complex, but native scripts are only 6 primitives and the combining them, you don't need advanced degrees to read them and use them.
Alone as the script editor this is a wallet enhancement, which is part of the challenge goals. Incorporating the collaboration option for these scripts. Now it unlocks: DAOs treasury, escrows, shared custody, which would be DeFi and Governance Systems also part of the change. And why not Legal, we make our own contracts. Contracts should be easy, anyone needs to be able to set them up. After all, it is about human collaboration.
How do you intend to measure the success of your project?
A market has supply and demand, this project would have availability and usage. The first success is the features are there, what I have promised is delivered. The second success is from people using it, that takes more time and effort.
I can always measure traffic on my service, and track how much does it grow. There is the actual measurement on the blockchain itself on how many people move towards script addresses instead of single signatures. As we allow users to embrace new possibilities the richer the ecosystem.
Please describe your plans to share the outputs and results of your project?
This project is a web service, certainly in SaaS mode. It does contain certain service tiers. The free and most private one is the local service page application. It is the editor for scripts and local backup. The paid part of the service is once connected to my servers how to collaboratively share and edit those scripts with other parties.
Because build and they'll come does not work, I will accompany the development with YouTube video tutorials. As a developer I finally come to embrace the amount of effort it takes to popularize a tool. And that a big part of this project is educating people how to write their own native scripts to secure their assets.