Bernhard crafts theory with practicality, dismantling common misperceptions about what tokens can and can't do.

Beyond Tokenization

Distributed ledgers and smart contracts are the next big step in the private and flexible digitization of assets and processes.

'Helvetica Neue', Helvetica, Arial, sans-serif

DAML Driven Blog

DAML Driven

<html>
 <head></head>
 <body>
  <p>Many industries are on the brink of the next technological revolution in record keeping. Ten years after Bitcoin made its splash, we’re seeing many inspired by some of the benefits promised by the technology outside of the money use case:</p> 
 </body>
</html>

https://hub.daml.com/hubfs/DAML-blogpost.png

<p>Many industries are on the brink of the next technological revolution in record keeping. Ten years after Bitcoin made its splash, we’re seeing many inspired by some of the benefits promised by the technology outside of the money use case:</p>


module_15571537756151858

module_1557431396199392

module_1563914750727231

DLint : Expert help writing DAML

DLint analyzes your code while you’re typing it, looking for issues and making suggestions on how you might care to improve it. It’s highly configurable (you can turn warnings off and on with granular scope control).

DAML Engineering Blog

Engineering Notes

<p>For developers of all skill levels, it’s a constant challenge to keep in mind the myriad of ways the code we write could be better. For DAML developers it’s not different. We wish to produce programs that are elegant, efficient, readable by others ... the list goes on. With each PR, we look to our code reviewers to advise us on (at least) the most obvious improvements we could make. This is especially true for DAML newcomers.<br><br>One of our main goals with DAML is to make developers extremely productive, and to make it easy for them to build high quality and secure code. The faster a developer gets feedback, the more productive they are. Relying on code review has an unfavorable feedback latency and getting full value can be "hit and miss". Wouldn't it be ideal if, while programming, you had an expert at your shoulder offering advice? <br><br>With the linting features we are integrating into the DAML IDE, the developer gets that advice as they type. DLint analyzes your code while you’re typing it, looking for issues and making suggestions on how you might care to improve it. It’s highly configurable (you can turn warnings off and on with granular scope control). The suggestions are easy for programmers of all levels to understand and where it makes sense, provides suggested code. Taking advantage of it is very easy and its use improves code quality!<br><br>The image below shows DLint in action. The IDE is warning that it found a block of duplicated code (suggesting an improved version would “factor out” the common block into a function).</p>
<p><img src="https://hub.daml.com/hubfs/main.png" alt="main" width="1051" style="width: 1051px;">Here’s another example of the sort of thing it can do. Given this function,</p>
<p><img src="https://hub.daml.com/hubfs/negate.png" alt="negate" width="1083" style="width: 1083px;">DLint provides the following suggestion:</p>
<p><img src="https://hub.daml.com/hubfs/foldr.png" alt="foldr" width="1084" style="width: 1084px;"></p>
<p>The suggestion here is that we replace our multi-equation recursive function with a one line version using the idiomatic standard library function foldr. <span><br></span></p>
<p>This is an engineering note, so now let’s get a little into how it's implemented.</p>
<p>DLint is achieved by the adaption and integration of <a href="https://ndmitchell.com/">Neil Mitchell</a>'s celebrated HLint package. HLint is a venerable program with over 15+ years of active development and HLint's use by the Haskell community is ubiquitous. The integration is made possible by the fact that we wrote the DAML IDE in Haskell and that the DAML compiler <a href="https://www.youtube.com/watch?v=mQulFrOp0Rg">uses the GHC stack "under the hood"</a>.</p>
<p>We do a lot of cool open source work at DA. Part of getting this functionality into the IDE means submitting lots of updates to upstream <a href="https://github.com/ndmitchell/hlint">hlint</a> (to use the <a href="http://hackage.haskell.org/package/ghc-lib-parser">ghc-lib-parser</a> package). Also, check out the <a href="https://github.com/digital-asset/ghcide">ghcide project</a> where we're contributing parts of this technology to the Haskell community! DAML itself is completely open source <a href="https://github.com/digital-asset/daml">here</a>.</p>
<p>We are super proud of how the DAML IDE is coming along. Try the new DLint features for yourself! You can download the DAML SDK <a href="https://docs.daml.com/getting-started/installation.html">here</a> and <a href="https://github.com/shayne-fletcher-da/lint-demo">this git repository</a> will give you a quickstart exploring some of DLint’s capabilities.</p>

<html>
 <head></head>
 <body>
  <p>For developers of all skill levels, it’s a constant challenge to keep in mind the myriad of ways the code we write could be better. For DAML developers it’s not different. We wish to produce programs that are elegant, efficient, readable by others ... the list goes on. With each PR, we look to our code reviewers to advise us on (at least) the most obvious improvements we could make. This is especially true for DAML newcomers.<br><br>One of our main goals with DAML is to make developers extremely productive, and to make it easy for them to build high quality and secure code. The faster a developer gets feedback, the more productive they are. Relying on code review has an unfavorable feedback latency and getting full value can be "hit and miss". Wouldn't it be ideal if, while programming, you had an expert at your shoulder offering advice? <br><br>With the linting features we are integrating into the DAML IDE, the developer gets that advice as they type. DLint analyzes your code while you’re typing it, looking for issues and making suggestions on how you might care to improve it. It’s highly configurable (you can turn warnings off and on with granular scope control). The suggestions are easy for programmers of all levels to understand and where it makes sense, provides suggested code. Taking advantage of it is very easy and its use improves code quality!<br><br>The image below shows DLint in action. The IDE is warning that it found a block of duplicated code (suggesting an improved version would “factor out” the common block into a function).</p> 
 </body>
</html>

<p>For developers of all skill levels, it’s a constant challenge to keep in mind the myriad of ways the code we write could be better. For DAML developers it’s not different. We wish to produce programs that are elegant, efficient, readable by others ... the list goes on. With each PR, we look to our code reviewers to advise us on (at least) the most obvious improvements we could make. This is especially true for DAML newcomers.<br><br>One of our main goals with DAML is to make developers extremely productive, and to make it easy for them to build high quality and secure code. The faster a developer gets feedback, the more productive they are. Relying on code review has an unfavorable feedback latency and getting full value can be "hit and miss". Wouldn't it be ideal if, while programming, you had an expert at your shoulder offering advice? <br><br>With the linting features we are integrating into the DAML IDE, the developer gets that advice as they type. DLint analyzes your code while you’re typing it, looking for issues and making suggestions on how you might care to improve it. It’s highly configurable (you can turn warnings off and on with granular scope control). The suggestions are easy for programmers of all levels to understand and where it makes sense, provides suggested code. Taking advantage of it is very easy and its use improves code quality!<br><br>The image below shows DLint in action. The IDE is warning that it found a block of duplicated code (suggesting an improved version would “factor out” the common block into a function).</p>


Release of DAML SDK 0.13.46

DAML SDK Release Notes

Release Notes

<h1>Sandbox</h1>
<ul>
<li>
<p>The sandbox uses a new payload format for authentication tokens (JWTs). The old format is<br>
deprecated, but still works.</p>
</li>
<li>
<p>Metrics are now namespaced by <code>"daml"</code> and their names have been standardized to snake_case.</p>
</li>
</ul>
<h1>DAML Studio</h1>
<ul>
<li>
<p>Scenarios with unserializable result types no longer crash the scenario service.</p>
</li>
<li>
<p>Fix a bug introduced in 0.13.43 that caused DAML studio to stop responding after code completions were requested.</p>
</li>
</ul>
<h1>DAML-LF</h1>
<ul>
<li>Prohibit contract IDs in contract keys completely. Previously, creating keys containing absolute (but not relative) contract IDs was allowed, but <code>lookupByKey</code> on such a key would crash.</li>
</ul>
<h1>DAML Compiler</h1>
<ul>
<li>Added a <code>--drop-orphan-instances</code> flag in <code>daml damlc docs</code>.</li>
<li>The modification times in a DAR are now fixed to a given value which makes the output of <code>daml build</code> deterministic in single-threaded mode (which is the default).</li>
</ul>
<h1>JSON API</h1>
<ul>
<li>The HTTP JSON API now uses the same payload format for authentication tokens as the sandbox. The<br>
old format is deprecated, but still works.</li>
</ul>
<h1>JSON API - Experimental</h1>
<ul>
<li>Support Exercise by Key. See issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="551469769" data-permission-text="Issue title is private" data-url="https://github.com/digital-asset/daml/issues/4099" data-hovercard-type="pull_request" data-hovercard-url="/digital-asset/daml/pull/4099/hovercard" href="https://github.com/digital-asset/daml/pull/4099">#4099</a> .</li>
<li>Response format in <code>searchForever</code> changed to be more like <code>exercise</code>. See issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="550905306" data-permission-text="Issue title is private" data-url="https://github.com/digital-asset/daml/issues/4072" data-hovercard-type="issue" data-hovercard-url="/digital-asset/daml/issues/4072/hovercard" href="https://github.com/digital-asset/daml/issues/4072">#4072</a> .</li>
<li>In 'search' endpoint arguments, %templates is now templateIds.<br>
Additionally, all contract query fields must occur under 'query'. See issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="522265757" data-permission-text="Issue title is private" data-url="https://github.com/digital-asset/daml/issues/3450" data-hovercard-type="issue" data-hovercard-url="/digital-asset/daml/issues/3450/hovercard" href="https://github.com/digital-asset/daml/issues/3450">#3450</a> .</li>
<li>WebSocket contract search at <code>/contracts/searchForever</code>. See issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="544291268" data-permission-text="Issue title is private" data-url="https://github.com/digital-asset/daml/issues/3936" data-hovercard-type="pull_request" data-hovercard-url="/digital-asset/daml/pull/3936/hovercard" href="https://github.com/digital-asset/daml/pull/3936">#3936</a> .</li>
</ul>
<h1>Indexer</h1>
<ul>
<li>Potentially fix a bug when recovering from failure.</li>
</ul>
<h1>DAML Standard Library</h1>
<ul>
<li>The <code>Template</code>, <code>Choice</code>, and <code>TemplateKey</code> typeclasses have been split up into many small typeclasses to improve forward compatibility of DAML models. <code>Template</code>, <code>Choice</code> and <code>TemplateKey</code> constraints can still be used as before.</li>
</ul>
<h1>Ledger API Server</h1>
<ul>
<li>Publish the resource management code as a library under <code>com.digitalasset:resources</code>.</li>
</ul>
<h1>Ledger API Authorization</h1>
<ul>
<li>Support EC256 and EC512 algorithms for JWT</li>
</ul>

Get your distributed app to market first

Productive

Innovative

Developer Driven

The platforms

by Blockchain Technology Partners