Contract Keys #75 Milestone 1: Two dApp's develop with Contract Key functionality

Milestone 1: Two dApp's develop with Contract Key functionality

Objective: dApp development can begin before deployment on Dev/Test/MainNet to validate the contract key semantics and tooling.

Estimated Delivery: Month 2 after approval

Deliverables:

• The full tech stack functionality works for the dApp development end-to-end on workflow. The tech stack includes contract key support in:

Daml language and compiler Visual Studio Code IDE Canton Ledger gRPC and JSON API Daml engine * Daml Script

Acceptance criteria:

• At least two dApps develop and locally test dApps using contract keys with LocalNet or DevNet (if available).
• At least one dApp successfully demonstrates using contract keys with the:

Daml compiler creates DAR files where the main package makes use of contract keys and at least two of the new APIs: fetchNByKey, exerciseByKey, and queryNByKey. Visual Studio Code IDE parses the new keywords and provides auto-completion of the key words. * Daml Script use of queryNByKey and exerciseByKey.

• Successful demonstration of the Canton Ledger gRPC and JSON API with the Command type exerciseByKey. This also exercises the Daml engine.

| Milestone | Earliest delivery | CC | | ----- | :---: | ----- | | Milestone 1: Two dApp's develop with an early release of the Contract Key functionality | Month 2 | 3.875M |

_Originally posted by @pedrodneves in https://github.com/canton-foundation/canton-dev-fund/issues/75#issuecomment-4388388158_