Key Points

References

Key Concepts

Project Management 

1. Deliverable definition
2. Team - editors, reviewers
3. Project Plan - work break down
4. assignment
5. deliverables w owners
6. simple weekly timeline w status
7. Checkpoint meeting weekly
8. Review meetings as needed
9. Publish all work in Teams ( what channel ? )

Report Contents and Scope

Review Questions to answer

1. what functional features are delivered in each environment?
2. what is open-source ?  how would that be supported?
3. what is licensed ? what type of support levels are available?
4. what operational features are provided compared to each of the supported native platforms?
5. what level of architecture, product planning can we expect with the vendor? the community?
6. what are keys for us in assessment if there is a value add?
7.  

Work Tasks

Like we learned with existing DLT reviews, we need to:

1. set research investment and decision gateways for this process
2. id ALL the functional, non-functional use cases in our current production solutions
3. id any new critical requirements not met in current solutions that are a priority based on regulations, compliance, business value, risk
4. review the candidate DLT solutions and their runtimes and integrations in detail 
5. map to a candidate DLT platform and environment to see what platform provides and what we need to provide
6. determine any delivery partners needed for the platform
7. determine long-term support for any external services, products that we integrate
8. design E2E deployment and operational support needs for the solution
9. forecast viability, growth, risks of the external product or platform: community, costs, risks, quality, support etc
10. perform the right evaluations:  POT, POC, POV

Why DAML?

https://daml.com/why-daml

The open source Daml smart contract language, described in more detail below under “Daml Smart Contracts,” forms the core of the Daml application stack. The language is a purpose-built Domain Specific Language (DSL) designed to encode the shared business logic of the application. It provides developers primitives to safely and succinctly describe core concerns like data types, privacy, and authorization rules without concerning themselves with the ultimate deployment target. In terms of the virtual shared ledger, it expresses who may write what events, and to whom they are distributed.

Daml abstracts the event sourcing model employed by blockchains and distributed ledgers. Event sourcing means that the current state of the system can be computed from the log of past events. Instead of keeping a global event log, Daml provides each stakeholder a consistent view on a virtual shared event log, called the virtual shared ledger, while distributing data on a strict need-to-know basis under the hood. This creates a system in which each participant has a consistent view of the (virtual) global system state, consisting of exactly the data they are entitled to. The virtual shared ledger is described in Daml’s Ledger Model and implemented in the Daml smart contract language and associated Ledger API.

The Ledger API is the primary API to interact with Daml smart contracts and the virtual shared ledger. It is a high-performance reactive gRPC-based streaming API. It allows applications to subscribe to events that they are permissioned to view, get their current state, or submit commands to write new events. As such, the Ledger API and smart contracts are the primary mechanisms for abstracting away concrete blockchains or databases to instead develop against a virtual shared ledger. Any node in a network that exposes Daml’s Ledger API—and thus gives access to the shared ledgers—is called a participant node as it allows participation in the network.

To enable an infrastructure like a blockchain or database to run Daml applications, it needs a Daml Driver that allows a matching participant node to connect into the network. Daml Drivers do not store any data and are typically deployed per node of the underlying blockchain or database. There are already numerous drivers, both open source and commercial, available in the Daml ecosystem, with more under development. See https://daml.com for an overview.

The deployed Daml smart contracts as well as everything on top of the Ledger API are considered part of a Daml application. Daml Connect is a suite of tools that assists in the development of full-stack Daml applications. Daml Connect contains an SDK that includes an Integrated Development Environment (IDE) for smart contract development, a suite of runtime components, and integration libraries spanning all the way to user interfaces.

General Notes on DAML work

DAML
tri tested

function delta
perf delta

arch overview

if we would use it
where
why ( over options )

map daml to our scenarios

corda for insurance

gartner
low-code, no-code

who can learn quickly?

4GLs
DSL

Python for analytics w libs

Normal languages with full flexibility in a runtime

arch process docs >>
quickLook - 5WH w refs
ISR - review - map to a test case,
ARB - arch, runtime
ORB - operations mapping << what IS our ORM by soln type?

daml review

summary on the opportunity, concerns, recs

what
why
who
where
how
when

feedback - internal, external

should we investigate daml as an option
of app fit

insurance test in DEVX

IT or ET

recommendations

dtcc roadmap

next steps

estimate
vcrs

when
1 week model - use cases, references, tests, evals

DAML Presentation 2/24/22

https://www.youtube.com/watch?v=QftcQgTfkJ4

DAML Sample Bike Repair Tutorial

https://kctheservant.medium.com/fix-my-bike-use-daml-to-model-a-real-life-example-ec6b578b02fb

DAML repos 

DAML reviews 

DAML solutions 

Potential Value Opportunities

Potential Challenges

Candidate Solutions

DAML - language, tools, runtimes

can execute on Corda, Fabric, Besu

Step-by-step guide for Example

sample code block

Recommended Next Steps

Related articles