OpenLaw Development Update

Feb 2, 2018 · 2 min read

February 2, 2018

Hi everyone! We’re thrilled to kick off the first Development Update series for OpenLaw. At OpenLaw we’re all about transparency (our name, after all, is OpenLaw). In light of that, we’re going to be circulating a weekly Development Update for you to keep up with what is going on with our team and follow the exciting growth of our project. After a seemingly endless January, OpenLaw is excited to share some of the stirring work we’ve done over the last week:

  • Improved Microsoft Word Document Upload: We have greatly improved your ability to upload word documents onto the website. Openlaw can now translate the document’s format into markdown mode instantaneously.
  • Markup Language Upgrades: We’ve made improvements to our Markup Language and have written some robust documentation. The biggest change is the ability to embed electronic signatures in executed documents and being able to turn default values into expressions.
  • Better Error Handling: Our team has put in a lot of work to improve the readability of error messages and to handle edge cases in a smooth fashion.
  • Signature Improvement: We now use the standard Ethereum signature scheme to sign documents.
  • Tightening-up the Backend Infrastructure: We’ve been putting the final touches on a highly scalable, self-healing backend infrastructure.

As you can see, we’re hard at work building a new technology stack for the legal industry and commercial world. We’ve made great strides, but still have a ways to go. Stay tuned on our Medium page for more development updates.

Thank you to all those who have reached out about your experience with OpenLaw. We love hearing your input! If you haven’t (and would like to) get in touch with our team please reach out:

We would love to get you involved.

— The OpenLaw Team


Written by


A legal operating system for blockchains. By @awrigh01 and @bmalaus; a @ConsenSys spoke.