| Table of Contents |
|---|
Key Points
...
| Reference_description_with_linked_URLs_______________________ | Notes______________________________________________________________ |
|---|---|
| DAML notes gdoc *** | |
| DAML intro course enrolled | jm9.L1xxxt#yn11 |
| https://docs.daml.com/cheat-sheet/ | |
| https://daml.com/blog/engineering/public-blockchains-and-distributed-ledgers?utm_campaign=coschedule&utm_source=linkedin_company&utm_medium=Daml | |
| DAML-DigitalAssetSDK.pdf | |
| https://daml.com/ | |
| daml-notes.pdf | |
| daml-101blockchains.com-DAML- The Language For Smart Contracts.pdf | |
| https://medium.com/daml-driven/tagged/smart-contracts | DAML online syntax |
| https://kctheservant.medium.com/fix-my-bike-use-daml-to-model-a-real-life-example-ec6b578b02fb | DAML bike repair app example 2022 |
| https://kctheservant.medium.com/asset-modeling-in-daml-tutorial-7-deep-dive-part-1-8f38756b2473 | DAML bike repair app example 2021 |
| https://www.digitalasset.com/developers/learn | DAML learning path |
Key Concepts
Project Management
...
- set research investment and decision gateways for this process
- id ALL the functional, non-functional use cases in our current production solutions
- id any new critical requirements not met in current solutions that are a priority based on regulations, compliance, business value, risk
- review the candidate DLT solutions and their runtimes and integrations in detail
- map to a candidate DLT platform and environment to see what platform provides and what we need to provide
- determine any delivery partners needed for the platform
- determine long-term support for any external services, products that we integrate
- design E2E deployment and operational support needs for the solution
- forecast viability, growth, risks of the external product or platform: community, costs, risks, quality, support etc
- perform the right evaluations: POT, POC, POV
Learning Path
DAML learn
https://www.digitalasset.com/developers/learn
Daml Developer
Learn how to write Daml and build simple multi-party applications.
System Integration
Learn how to produce an application that depends on a Daml back-end for business logic and data persistence.
application-architect
System Architect
Learn about the different components and how they work together to produce a Daml solution
DAML basics certification ( free )
DAML Cheat Sheet Concepts
https://docs.daml.com/cheat-sheet/
https://github.com/digital-asset/daml-cheat-sheet
docs.daml.com--cheat-sheet-The Fast Track to DAML.pdf file
|
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.
DAML Concept Overview slides
daml-101blockchains.com-DAML- The Language For Smart Contracts link
daml-101blockchains.com-DAML- The Language For Smart Contracts.pdf file
|
DAML Getting Started Docs
https://docs.daml.com/getting-started/index.html
local install?
recommend ubuntu, Linux
MACOS ok
General Notes on DAML work
...
https://kctheservant.medium.com/fix-my-bike-use-daml-to-model-a-real-life-example-ec6b578b02fb
DAML repos
DAML reviews
DAML POC for trade capture
Perfect analysis and conclusions in my opinion.
Absolutely stays on the radar but does not yet meet the needs of a portable, easy to learn, performant low-code DLT platform solution wih solid support for the primary DLT platforms in use today for most use cases today.
IF I were evaluating DAML vs Java in the future on any ledger, I'd look at the Java side very differently ( JDK17 ) with custom extensions to simplify code complexity ( making Java more of an event-driven DSL ). I'm guessing that would significantly simplify the developer experience with a shorter learning curve for Java Ledger development, improve portability, performance and reduce significantly the Java code lines involved ( like Firefly does ).
Really think this analysis project was really well done by you and the team.
You got the right outside partner to provide the best possible evaluation, picked a valuable use case but correctly simplified scope and did a great job leveraging DEVX for a training environment.
DAML solutions
DAML 2.0 and Canton ledger service
DAML notes including DAML 2.0 overview
https://docs.google.com/document/d/112-MCDKhqz0-aQqjHXboVWsEO15ygtM5eU_ZzC5Svg4/edit#
Questions for 2.0
- support for extensions, customizations via policies, delegate services via interfaces, modularity
- open-source ? base version not enterprise HA
- performance ? no benchmarks
- GA version? yes
- integration with other ledgers? yes - Besu, Fabric, Corda ...
- integration concept? Canton ledger service provides a common model that is integrated by any supported driver
- integration driver currency with DAML releases? no formal timing commitments
- is the HA model useful? costly for license and runtime metering? easy to integrate, extend or customize? unknown
- can the metering service be used with the open-source model? unknown
Potential Value Opportunities
What DAML production solutions use open source DAML Canton version? volumes? performance?
What DAML production solutions use enterprise DAML Canton version? volumes? performance?
What DAML production solutions use DAML Hub Canton version? volumes? performance?
Other DAML projects
Australia Stock Exchange cancels DAML project
ASX-daml-project-cancelled-Chairman Apologizes After Writing Off 165 Million Blockchain Project.pdf url
ASX-daml-project-cancelled-Chairman Apologizes After Writing Off 165 Million Blockchain Project.pdf file
the project was facing a number of obstacles, including resistance from companies on the platform to use the shared ledger.
<< Lesson learned: engage key partners through out the solution life cycle, not at the test phase ( see Food Trust, TradeLens, TYS )
<< Lesson learned: let the partner council define the economic. governance, compliance, trust models that work, not just the applications and technologies for the use cases in scope
the Accenture report commissioned by ASX that noted “the absence of appropriate design artefacts, rigour, or inconsistent design discipline to model the expected behaviour within the constraints of the technology.”
<< Lesson learned: don't try to be revolutionary. Be evolutionary in the solution design - takes longer but has lower risks, more network buy in for success
Potential Challenges
Candidate Solutions
...