Please describe your proposed solution.
Cardano's Smart Contracts are inherently passive. They act as validators of submitted transactions rather than actors that build transactions themselves.This calls for off-chain components that build, submit and process transactions locked in a Smart Contract.
Take as an example the MuesliSwap order book contract. Users lock in the contract their intention to trade at a certain price. Off-chain components, so-called “matchmakers”, continuously scan the ledger for open orders that appear as UTxOs on the blockchain. The overall performance and decentralization level of the protocol depends on presence, performance and diversity of these matchmakers. To the user, higher presence of matchmakers appears as faster throughput of the protocol.
We want to develop tutorials, publish sample code and instruct the community in building their own tools to interact with Smart Contracts in general. This can start at the specific example of the MuesliSwap protocol but may be extended to various other protocols that encourage third party participation. We have seen singleton members of the community come forward and develop their own tools already but are yet to see any publication of this work. As sample code is worth money – it is essentially the code of another Miner on top of the Cardano Ecosystem – open-source development needs to be funded, preferably by the community itself.
In addition, we want to see externally audited basic tools that are a solid foundation to build on top of. After all, not only smart contracts need to be audited. As the protocols rely on the performance and availability of off-chain components we want to make sure these components are resilient.
Please describe how your proposed solution will address the Challenge that you have submitted it in.
The ecosystem features many abstract libraries for building tools on Cardano, yet lacks hands-on examples and tutorials for actually building off-chain code. This is a paradox since the off-chain part is one of the strengths of Cardano, agnostic to the programming language and with a well-specified API.
We want to change this and enrich the Ecosystem for developers with hands-on tooling and tutorials for starting to build fully working DApps with off-chain tooling.
What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?
We have already developed a diverse range of off-chain tools and thus do expect that building tutorials and publishing new tools will not be a technical problem.
We will not encounter any budget problems as any extra costs will be covered by the MuesliSwap team. As we have a big development team, we will also not encounter risks like development staff leaving.