This proposal aims to create a smart contract template and the necessary documentation for it, make it freely available to the community, and use it as an example in the Plutus Project Based Learning.

The proposing team behind this project are all core members of the Gimbalabs project, an initiative with a proven track record, that's been contributing greatly to creating resources and spreading knowledge in the Cardano community for over a year now.

Gimbalabs will also be hosting the sessions where this smart contract template will be used as an example and teaching tool, to instruct others about Plutus and Cardano smart contracts. As such I assess this to be a very impactful proposal for the Cardano developer community in the near and medium future.

Considering all this and the very low budget requested by this proposal of $3000 it represents an incredible value proposition for the Cardano Treasury.

Definitely, this proposal is needed for the other ongoing proposals submitted by the proposer. In my opinion, this is the core of the main product (scheduling dApp). Another positive thing, this is also part of Plutus community learning which will bring lots of positive impact on Cardano's development.

I like that this smart contract will be built for all to use. I find it important to create a project that will attract more people to using the Cardano blockchain. I know that lots of builders would appreciate an escrow smart contract to help them build their daaps. It is also nice that the smart contract will be used for a variety of use-cases.

This proposal is about creating an escrow smart contract for dapps that will allow a trustless peer to peer transactions. The proposers have also expressed the desire of creating documents for the project and making it open source. I think the proposers have done a great job explaining the purpose of this project and how it adds value to the cardano ecosystem. I have to recognize that the cardano network needs a set of tools that will make it easy for developers to build dapps. That leads me to think that maybe this proposal is more suitable for the open source challenge. I recommend the proposers to think about that too. Other than that , this proposal is a great initiative and I support it.

They plan on creating a sophisticated escrow smart contract with documentation that could be used by other applications which aligns with the challenge setting. It will help in building high quality dapps on Cardano therefore bringing value to the ecosystem. It's main goal is to provide this product for free to other developers and to be used by them. This goal aligns with the challenge in the sense of building more Dapps on Cardano. This product is able to scale as it is open source and the public can help this evolve over time.

This proposal, despite having been briefly explained, seems to me to be very promising, well meeting what we are looking for in this challenge. The idea is to create a smart contract, using our Plutus language, which will serve as a caution, many also have the relationship and specifics of how this contract would be used). The objective that is both parties imply in the contract on the basis of “exchange value, in a way without trust and schemes”. In other words, the proponent intends to create an alternative for people who are still not so sure about carrying out transactions on the Cardano blockchain, due to the fact that it is a totally new process for most, of which it is not fully understood how it works, unlike anything that has already been done outside the cryptographic world. In fact, each blockchain works its own, so it's fair to say that an expanding Cardano ecosystem is still so involved with a bit of prejudice and estimation of its own on the part of the parties; or even the parties may not trust each other, wanting to run a test before actually doing what they want. As I said, it's interesting how the author created a hypothetical situation (with Alice and Bob), where we can see how the technology he intends to understand would work. In the part “a predefined “funds release window”, in case one of the parties does not withdraw its funds that would incur in proposals for the commitment assumed by the other party to deliver in the agreed time and values, etc etc”, the proposer explicit the use cases that this technology can provide. Overall, this project would help people build software on Cardano more securely, which would contribute to the adoption of our blockchain. That is, the objectives of the challenge will be proposed directly contemplated, probably the number of transactions will increase as more people would trust to do this; New members to our environment, increasing the number of Ada and CNFTs in circulation, also investment in other Dapps, new active members to our community can also increase. In short, I think the idea is very pertinent and could generate great results for our ecosystem, in line with what we are looking for in the challenge.

Although KPIs and metrics can be relatively easily deduced and extrapolated from other parts of the proposal I still would've liked to see them more specifically included in the auditability section. As a result, I have subtracted one point from my score for this section of the proposal.

The definition of success is very well written and it creates a concise picture of what the community can expect on the successful completion of this project.

Recommendations for a more complete auditability section and getting a maximum score:

• accurately describe, easily verifiable and trackable, metrics and KPIs that will allow for effortless monitoring of the project’s implementation progress.
• define milestones that describe clearly the expected progress markers.

As stated in the other related proposals, the proposer and his team need to add some channels for public communication besides GitHub or GitLab. By having more channels, communities are aware and can contribute some help like running the product on testnets. The development phases of this project should also be added as part of the roadmap.

I think that this proposal is auditable based on the roadmap and milestones to deliver the project. They have promised a well documented escrow smart contract that other developers can use in their dapps, in two months. That is a short time and we’ll be able to track the results easily. I think that this is a great project and it should be great for the community if well executed.

There was a good amount of information given in this proposal. I like that it was short and concise and got straight to the point. They are requesting such a small amount of funds that will likely be used to increase the amount of users/money by a lot. Especially taking note of the various use-cases of this smart contract. I think that the roadmap is written nicely. I would continue to add onto the roadmap as the time progresses or try to make it as detailed and concise as possible. If that is already done, it looks good.

The suggested auductability for process monitoring is quite superficial. They say that they will be guided by the activities and milestones of the roadmap and that they will run a test on the testnet network, before officially releasing the product. We don't know important things, such as, for example, whether the work routine of the developer who will work on the project will be monitored, how it will be monitored, what he has to deliver per week, how many hours he needs to work, how all this information can be measured and made known to all members of the Cardano community. In terms of partial success, how would it be measured and reported to all of us? Does the bidder intend to share the github repository or build a roadmap at the end of each project month? Talking about both tasks and goals? Unfortunately, I think it was too shallow how this part of the project would be monitored. Finally, when it comes to the end results, success is very well defined by obtaining “a well-documented example of a Smart Escrow Agreement that others can use in their own projects”. But I think that, like the auditability of the process, this part was very shallow. How can we define metrics that demonstrate the success of this project in a verifiable and reliable way? How to perceive the impacts of the idea for the Cardano ecosystem? Has this new technology actually contributed to more transactions being minted on our blockchain, more people choosing to work with Cardano over other blockchains? Has the number of active members somehow grown from this project? And has the satisfaction of the parties increased, the level of trust increased on both sides? I believe that it would be necessary for the proponent to collect this data, both quantitative and qualitative, so that we could better understand the consequences of this project for Cardano. Therefore, unfortunately, I found the proposal not very auditable based on what was stated, being this part of a good reformulation (deepening).

They provided a roadmap of 2 months, with milestones for each month. Making it easy to track the progress of this project. The only KPIs they have is that their product can reach a real world application and that it is able to be an example for other people to learn from. No mention of measuring its usage is mentioned. Since they will use this product in Gimbalabs to teach other people it will already be used as an example and hopefully as a real product by some of the students. It would help to measure it's usage somehow and keeping track of it. That way the community can see the performance of this product. Having good quality applications on Cardano especially when it involves smart contracts is a must. They see this problem and they solve it by creating a good example of an escrow smart contract and making it open source with proper documentation.