September 17, 2020 Software Open Access

Coblenz, Michael; Aldrich, Jonathan; Myers, Brad A.; Sunshine, Joshua

MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nmm##2200000uu#4500</leader>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">typestate</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">linear types</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">ownership</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">assets</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">permissions</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">blockchain</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">smart contracts</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">empirical studies of programmers</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">empirical studies of programming languages</subfield>
  </datafield>
  <controlfield tag="005">20200918122359.0</controlfield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Additional funding sources:

NSA award H9823018D0008
NSF award CCF1901033
USAF award FA8702-15-D-0002
IBM
Ripple</subfield>
  </datafield>
  <controlfield tag="001">4035150</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Carnegie Mellon University</subfield>
    <subfield code="0">(orcid)0000-0003-0631-5591</subfield>
    <subfield code="a">Aldrich, Jonathan</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Carnegie Mellon University</subfield>
    <subfield code="0">(orcid)0000-0002-4769-0219</subfield>
    <subfield code="a">Myers, Brad A.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Carnegie Mellon University</subfield>
    <subfield code="0">(orcid)0000-0002-9672-5297</subfield>
    <subfield code="a">Sunshine, Joshua</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">61472139</subfield>
    <subfield code="z">md5:855166962a9a1c4f9f9ed1406ae23875</subfield>
    <subfield code="u">https://zenodo.org/record/4035150/files/Obsidian-evaluation-OOPSLA-2020.zip</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2020-09-17</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">software</subfield>
    <subfield code="p">user-empirical-software-engineering</subfield>
    <subfield code="o">oai:zenodo.org:4035150</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Carnegie Mellon University</subfield>
    <subfield code="0">(orcid)0000-0002-9369-4069</subfield>
    <subfield code="a">Coblenz, Michael</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Can Advanced Type Systems Be Usable? An Empirical Study of Ownership, Assets, and Typestate in Obsidian (Artifact)</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-empirical-software-engineering</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">1423054</subfield>
    <subfield code="a">TWC: Small: Empirical Evaluation of the Usability and Security Implications of Application Programming Interface Design</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">http://www.opensource.org/licenses/bsd-license.php</subfield>
    <subfield code="a">BSD licenses (New and Simplified)</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;&lt;strong&gt;Abstract&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Some blockchain programs (smart contracts) have included serious security vulnerabilities. Obsidian is a new typestate-oriented programming language that uses a strong type system to rule out some of these vulnerabilities. Although Obsidian was designed to promote &lt;em&gt;usability&lt;/em&gt;&amp;nbsp;to make it as easy as possible to write programs, strong type systems can cause a language to be difficult to use. In particular, ownership, typestate, and assets, which Obsidian uses to provide safety guarantees, have not seen broad adoption together in popular languages and result in significant usability challenges. We performed an empirical study with 20 participants comparing Obsidian to Solidity, which is the language most commonly used for writing smart contracts today. We observed that Obsidian participants were able to successfully complete more of the programming tasks than the Solidity participants. We also found that asset-related bugs, which Obsidian detects at compile time, were commonly accidentally inserted by the Solidity participants.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Artifact&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The artifact supports replication of the experiment described in the paper. For instructions regarding how to use the artifact, please see the included artifact evaluation guide.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.4035149</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.4035150</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">software</subfield>
  </datafield>
</record>