Detailed Plan

Basic idea is to upload legal document (if necessary), and allow for simplified description of smart contracts that can later be read by conventional contract analyst in English.
That means that our basic "code templates" will be used to generate English text that describes contract behaviour and provides transparency.

In order to provide a conventional record, we would also include PDF of intended contract, if there is a conventional legal contract with "terms of use".

Together with payments in ADA and clear descriptions, such smart contracts would allow to move bureaucracy entire onto ADA blockchain, together with document flows.

It would also let users analyze smart contracts behind each document by using English description of the policy.

We request a see funding for developing a compiler that provides both English and Plutus description of each contract, and an MVP interface that allows to manage smart contract together with filled PDF forms with data.

Future user experience will be that of uploading a conventional Word document, choosing smart contract template, and deploying a smart contract application on Cardano from SaaS application.
This would allow an easy migration of national bureaucracies to digital domain, along with smart contract that prescribe their application.

1. Compiler

• at this stage, we will formalize input syntax and validate it with a focus

group including developer, an accounting specialist, an economist,

and a blockchain lawyer

• basic operations on ada and fungible tokens

• basic preconditions, postconditions and invariants on the values of

the tokens, and block time

• escape to reference any low-level conditions in lower-level smart con-

tract languages

2. IDE showing live execution trace

• at this stage, we will combine the compiler with a Plutus interpreter

to provide a live execution trace for test operation traces

• we will also provide IDE support for our language, including in-editor

rendering of the contract description, and operation trace

3. Advanced conditions and operations:

• fungible tickets

• voting tickets

• other features as suggested by the community

4. Tutorials based on existing contract library with common nation-specific documents

• we will port contracts from the open source Ethereum smart contract library to our notation

• we will validate their execution in the IDE

• establish community support forum

Deliverables:

* Smart contract translator that compiler to Plutus for execution - 30k$

* Smart contract translator to Plutus: advanced features - 20k$

* Smart contract translator that compiles to English document for contract analyst - 10k$

* Web server to fill in the data for the contract, and use its smart contracts - 20k$

* IPFS server for holding the attachment data - 3k$

* smart contract example: two phase commit (Escrow) for two-party contract - 5k$

* smart contract example: atomic swap for multi-party contract - 10k$

* smart contract example: submitter-reviewer-approver - 5k$

* smart contract example: paid application for the government service - 4k$

* smart contract example: delivery of the NFT - 3k$

* smart contract example: refinanced purchase - 6k$

* user forum - 3k$

Keywords: document workflow system, low code for smart contracts, open source contract templates

Success after 3, 6, 12 months:

1. After 3 months we hope to provide MVP for the compiler and implement at least one example contract.
2. After 6-9 months we hope to have a working IDE with the compiler.
3. After 12 months we aim to build the community using the new smart contract platform.