<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Alacris - Medium]]></title>
        <description><![CDATA[Alacris is a Scalability Solution for All Blockchains - Medium]]></description>
        <link>https://medium.com/alacris?source=rss----f79445458e89---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Alacris - Medium</title>
            <link>https://medium.com/alacris?source=rss----f79445458e89---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:52:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/alacris" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Alacris Releases Alpha Version of Scaling Solution]]></title>
            <link>https://medium.com/alacris/alacris-releases-alpha-version-of-scaling-solution-519e4cbf50a3?source=rss----f79445458e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/519e4cbf50a3</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[fast]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[scaling]]></category>
            <dc:creator><![CDATA[Amy Lynch]]></dc:creator>
            <pubDate>Fri, 24 May 2019 16:10:01 GMT</pubDate>
            <atom:updated>2019-05-24T16:10:01.160Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pxdX_y_qGP6Tp5htyt8xMw.png" /></figure><p>Alacris announces the release of Legicash, a fast cryptocurrency payment scaling solution for Ethereum to alphanet. This represents a major milestone for the Operating System company addressing the cryptocurrency functionalities to attract users to blockchain by creating an end-to-end Distributed Application (DApp) development platform.</p><p>This alphanet version of Legicash is the first in a two-part release. Legicash demonstrates our <em>Mutual Knowledge Base (MKB), </em>which serves as a data availability network<em> </em>and Side Chain Scaling Solution, that provides the basis for fast confirmation of transactions on a side chain. <em>This is Alacris’ contribution to the problem of designing practical solutions that are so urgently needed for the crypto economy.</em></p><p>“By launching this to the open source community, we look forward to feedback and exciting projects forked from this codebase,” said Chris Swenor, Alacris CEO and Co-Founder. “Being a practical design that solves cryptocurrency challenges including speed and security, this is a really great start in generating ideas and partnerships. We expect to keep building on this and our next releases to fully realize our vision for an operating system that makes blockchain easy to use.”</p><p>The next Alacris alphanet release will be announced later this quarter, which will feature Alacrity, our Domain Specific Language (DSL). Both releases denote a major landmark for Alacris and its work toward blockchain adoption and will be the first release of project development. The scaling solution release represents Alacris’ work over the past year.</p><p>We invite you to try Legicash on Github and get more information about our alpha version and Alacris technology:</p><ul><li><a href="https://github.com/AlacrisIO/legicash-facts"><strong>Try Legicash on Github</strong></a></li><li><a href="https://medium.com/alacris/making-fast-cryptocurrency-transactions-practical-legicash-by-alacris-io-61d9fe093116"><strong>About Legicash:</strong> <strong>Making Fast Cryptocurrency Transactions Practical</strong></a></li><li><a href="https://alacris.io/tech-due-diligence.html"><strong>Alacris Tech Due Diligence</strong></a></li></ul><p>Or, go to<a href="https://hy.t.hubspotemail.net/e2t/c/*W2l3d_H2kmx2KW8XNy0m5RjYGs0/*W1TXfzc7bgC1XW7xhZ4c5NGyYb0/5/f18dQhb0J4T3WC1PV5HlQt6zJnkvN7Qtjn22mqXPW1T4LB24fNSkDW26QkGZ3ZSy7xW3T3jwV43njM_W4fKWwD43XxswW3JML-h3vd6mLN3T0nsDLG53rW3H6xvk2dyN84W58-qMK4fGC1KW2dMbQJ3R4SSxW3DQGFF2nT8K0W4t3tQn3HcXT3W3b2wwF3NW7_TW2YNn8r4twjcKW3ZFjGV2RJrXSW3j6VG92sTB7zW2FY7gT2y00dsW4fwG3g4kn5Q3W3VVBNp3XJ0ZhW1QrFCd1Q9_d9W3b3Kv74hy4dKW1V3K4D4rC23lW1Zq4t232gt0cW3R4Tym2dMdxMW2lh4yb2XZgmLVmSsdy4rdWQZN763YQzZy6J8VjXTKt7b5wpqW8-FTSP5KRTdmW72jkYW6D7lNvW8wn13s1G1WTdCm-X2mYfzf3Bq2gH03"> Alacris.io</a> for more information about our company!</p><p><em>Alacris is an Operating System for the blockchain founded by Chris Swenor (CEO) and Francois-Rene Rideau (Chief Architect). We provide formalized verification and bridges to layer 1 and layer 2 protocols. Our OS abstracts away all infrastructure concerns from the DApp developers so they can focus on building the applications. Developed by LegiLogic in 2018, Alacris is comprised of a 13-person team with a collective of decades of industry experience in engineering, research, and product development, communications, located in Boston, MA.</em></p><p>Have questions? Please feel free to reach out to our CEO/Co-Founder Chris Swenor at <a href="/service/mailto:Chris@alacris.io">Chris@alacris.io</a>.</p><p>Sincerely,</p><p>The Alacris Team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=519e4cbf50a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alacris/alacris-releases-alpha-version-of-scaling-solution-519e4cbf50a3">Alacris Releases Alpha Version of Scaling Solution</a> was originally published in <a href="https://medium.com/alacris">Alacris</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blockchain Operating System Tech Talk is live!]]></title>
            <link>https://medium.com/alacris/blockchain-operating-system-tech-talk-is-live-46191ee6ac90?source=rss----f79445458e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/46191ee6ac90</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[formal-verification]]></category>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Amy Lynch]]></dc:creator>
            <pubDate>Fri, 03 May 2019 17:08:56 GMT</pubDate>
            <atom:updated>2019-05-04T14:38:31.109Z</atom:updated>
            <content:encoded><![CDATA[<h3>Blockchain Operating System Tech Talk is Online!</h3><p>Were you unable to attend our live Tech Talk on April 11th? We have now posted our talks on YouTube. For easier viewing, we have divided our talks into four videos, one for each presenter and our Q&amp;A portion. Huge thank you to <a href="https://robinsonit.cc/">Robinson IT</a> for their media and editing services!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7yDby9YiHvs%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7yDby9YiHvs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7yDby9YiHvs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/aff6bf42d305e421138166be947ee5a7/href">https://medium.com/media/aff6bf42d305e421138166be947ee5a7/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhjmGQpyGSUE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhjmGQpyGSUE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhjmGQpyGSUE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/58a642086d4097044ab09e65575a3916/href">https://medium.com/media/58a642086d4097044ab09e65575a3916/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FqV34GuiqnNY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DqV34GuiqnNY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FqV34GuiqnNY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd3341374230b7f0a27d5f51d94b11b0/href">https://medium.com/media/dd3341374230b7f0a27d5f51d94b11b0/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FzQCZtJDJwDs%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DzQCZtJDJwDs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FzQCZtJDJwDs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e751c57f2540642227497c18827a1b78/href">https://medium.com/media/e751c57f2540642227497c18827a1b78/href</a></iframe><p>Like what you see? Please share our videos!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46191ee6ac90" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alacris/blockchain-operating-system-tech-talk-is-live-46191ee6ac90">Blockchain Operating System Tech Talk is live!</a> was originally published in <a href="https://medium.com/alacris">Alacris</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alacris is coming to Boston & NYC Blockchain Week!]]></title>
            <link>https://medium.com/alacris/alacris-is-coming-to-boston-nyc-blockchain-week-d330c9b24ed7?source=rss----f79445458e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/d330c9b24ed7</guid>
            <category><![CDATA[new-york-blockchain-week]]></category>
            <category><![CDATA[boston-blockchain-week]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Amy Lynch]]></dc:creator>
            <pubDate>Fri, 03 May 2019 16:52:00 GMT</pubDate>
            <atom:updated>2019-05-03T16:52:51.884Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*edi4-gHxvjwK4tOTNiRNiw.png" /></figure><p>Alacris will be at both Boston and NYC Blockchain weeks. Our participation at various events will be between Saturday, May 11th through Thursday, May 18th. If you are in the area, stop by and say “hi!’ or email us to meet up at chris@alacris.io, we would love to talk to you.</p><p>Looking to attend one of the events we will be at? Stop by or reserve your tickets for:</p><p><strong>Boston</strong></p><p>Sat-Sun, May 11–12, BuidlBoston:<br><a href="https://bit.ly/2IUmRMg?fbclid=IwAR1TOD35EhVFpVAgxvY_DNiYpUbGJgiQjbK9sIny1ovNEmK6sfPlcuH0o7c">http://bit.ly/2IUmRMg</a></p><p><strong>New York City</strong></p><p>Monday, May 13, NYC Blockchain Deep Tech Fireside Chat:<br><a href="https://bit.ly/2IUmSji?fbclid=IwAR3r0xByoXRuHzjOpjIynjLPAfxFidRva2aQ2lLeG8YLInpHJmMS02ruZEI">http://bit.ly/2IUmSji</a></p><p>Wednesday, May 15, Layer 2 Meetup, Blockchain NY Edition:<br><a href="https://l.facebook.com/l.php?u=https%3A%2F%2Fbit.ly%2F2JfaGt4%3Ffbclid%3DIwAR3Eyt4dElZSGd5BXv9-3BwrKKf0-WWNRe_RFXnLsA2duwWm_4G12w7pCdU&amp;h=AT1RNqVQf2OGnKMTYhtCNPV-VU-jzZY15b_ToAwK1VAhkiVBedjdhRDiHYXUiS5XmYh58ayH9yufsgTuBhEmkyL6j-p4-N7rR8nJMpU4nMnLyreLQ7MELQ5Yni5NbKOYAGhYCR-gFcDjtP1wvHCFdk71C5rbXspsdNT3YK8ZuNLx0rYx6cYpTqAoBuSdli2ycoLGASZQXRR_ipx8LOuZs3vSdjm35ghzlAis8RQq2d0bOPZ8yS3kp2FYGoYI9I9CmQSGdfrrFMd74SdBJtGmr4O_jYc1MyknUM2u23JOaeV_Pry6J4oN2Q5ZsX-HEbzX3TM-TDvh0k_GVC1ez6owQSCUKHXdnOstOB6UlqlplQe7fHWzlz_LtnEb2OIm0Y79xPX7RUueTK5ZS9f5ZXmqADj70bSajMvE8-xijrihKdthbP5s4VW20_E2SraNIQNte91hu0VzHklBd7ci4cbjtQ_dm72XgUhwYYoMapY0KNhR6NWmVzz6CPQN78HES_OkcBRh4tS4NzBsI0oaew_IeGGbRA3xWsr63AbrjF7HY5GhfVbYRpambhACoyBHJ7Y2jgZ-UAwIA_Wpo2qnTV9lChKTTNkCdr0x1H_sCX-EifNNhRiHj9JbGAkMiCVIfV1208OH">http://bit.ly/2JfaGt4</a></p><p>Thursday, May 16, Blockchain Startup Showcase:<br><a href="https://l.facebook.com/l.php?u=https%3A%2F%2Fbit.ly%2F2IYhprX%3Ffbclid%3DIwAR3HYGxJLPm_rQmlAdwVI_WxN-rMH9dmdkZLAf4gReF4bNfKiG_XQAmwrRA&amp;h=AT3HKbCkyhLM5ND4vO1PvobvFhrKLQZT5kkbSZdeZ7prKFGBnJy-HSZG2b8VbHcNh6Fivb3P-HEnjKUlznOg2PSavQWSd9-t5bdiMR8Gaxi0L7tXtQLR5aHefwjpUh6F5L8wtU4lFhMc3WVDIWphzs_ulRJBkq00UTcM-ALKqADRq7GMJLfLtIHyJLg-J0Ap-eabCnk4rGIxPtyF73B9riwIts2vZb9gbrKe7eXv5jY5oS6uQGAloSEcBpHlEKMwbaypAIdWkK4wVij-t49Prt86qHJN8fhLyU7P8Rmj6cz9K-r_88PgJ8wjCv8KUm44fC4PT4xNXOAAQmXFS3BYNUf1LfxueJZj5F0mRbCwwhS_yOBuyNhYbKfF5XGSwAHRAgucdiNgwNa6kgMTkNbz1Mw_VSuixNUxwGCVoqagGEg65_tzDC65W7UFpeamYjYu3UMWNJBzFECHJMSCJEnSQjnTSux5AZoPYsAz67qxn5MMLRUp2eMVK0Fjmr9VlZGmRRSe8tW19M5fJpsgbP53tvEpqs9HTdhzs0Xy2aOwdT9YQyqzK5Osy0aTUQfkfdHDkfVC80thgIzJs-pzUuL_KClxv42sX4uvXoFKlz3F5PNru61xnNU90Tn_Cf-OWNDJZpuk">http://bit.ly/2IYhprX</a></p><p>Thursday, May 16, The Future of Layer 2: NYC Edition<br><a href="https://l.facebook.com/l.php?u=https%3A%2F%2Fbit.ly%2F2IUmTUo%3Ffbclid%3DIwAR0qgqminsm4HY6STR61tfXN5ityVJlft2Pj8QOov7LLp17BMp4-EeGc3z0&amp;h=AT2M15OIys_Q226zvnhYGels5TnU8EpGbvUA15_GjE07S6iGN3HZgRLcWfd12EaJHpFxcRiOO7pSWKK65eA68dz1P4SFJH4nsRhHjnRDW_95561bJTk2mbxb-gDKuAyA8AgnDJZE0e6Nin9koBfdZbYocqVc2rwkuw7dbXCLWDkFhYFMg-DWCyPTWsrYqwon28zzRItj0STYMOWj5itp8JNO3VyqXlIT7h3ktK6xFsR_AtEmUAa7L0t2vTgY_OwQDuvOw8eEcN9Nn0767wKFiagM1bgsGD1E5bimgBwDtOdh9exPnJIUbOPKnzqoEwhMIBdTdacNKhBvpeSjk7iO_EjO9qdN6PwzTmm9J9QnG0yVjHIwnkIUrrTd5xrTY_tYWPVBFabobAL0E5hZTqCdoFYLUm4PsaCmyS5EEbD2hicOvUY7BoUFlNzH5my6tHr7qH3KvyGEq3kPNctR7DRewmpDfVOtVa6NPS0Zm4_3mP129yWoSAU98gv17GYWvyjBaz3HZRaShQWA-cdwcAZKtoyuuaWAoJw8M8zdjdk2OzdQeYbPr4ewhl6Wca7i0WeD7H4yn_ZzdqeGWTfROryftTN6kwJhfvBkCn7lBX0Qj_getmrcx1yqckgLLb_vzirYM1Xq">http://bit.ly/2IUmTUo</a></p><p>We would love to meet you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d330c9b24ed7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alacris/alacris-is-coming-to-boston-nyc-blockchain-week-d330c9b24ed7">Alacris is coming to Boston &amp; NYC Blockchain Week!</a> was originally published in <a href="https://medium.com/alacris">Alacris</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Composing Contracts without Special Provisions — using Blockchain History]]></title>
            <link>https://medium.com/alacris/composing-contracts-without-special-provisions-using-blockchain-history-9fcef0129518?source=rss----f79445458e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/9fcef0129518</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[composition]]></category>
            <category><![CDATA[alacris]]></category>
            <dc:creator><![CDATA[François-René Rideau]]></dc:creator>
            <pubDate>Fri, 26 Apr 2019 20:31:36 GMT</pubDate>
            <atom:updated>2019-05-03T12:42:16.371Z</atom:updated>
            <content:encoded><![CDATA[<h3>Composing Contracts without Special Provisions — using Blockchain History</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/1*SsG6YYKiJQVLixfsYWlVZA.jpeg" /></figure><p>One feature I sorely miss in most existing blockchains is the ability to verify the <em>history</em> of the blockchain from within its contract language. Why so? Because this feature when present enables easy composition of contracts, without the contracts being composed having to offer a dedicated API to facilitate such composition, such as the awkward “allowances” of ERC20 contracts.</p><p>Indeed, thanks to access to blockchain history, it is possible to compose not just contracts that weren’t designed to be composed, but even contracts involving other parties who are not directly involved in the larger composition — whether you don’t want to involve them, or they refuse to make your life easy. It is even possible to compose contracts in a private way where no one needs know the details of the composed contract except its direct participants.</p><p>Let’s assume that someone wrote some cool contract to manage interesting assets, say cute lizards that scale, <a href="https://medium.com/alacris/cryptoscalies-cute-lizards-at-scale-5ac34e6cc2af">Cryptoscalies</a>, and someone else wrote another cool contract so your Cryptoscalies can wear T-shirts. Now let’s assume I want to sign a sponsorship contract with you, whereby I will pay you so that your famous lizard Scaly Cardassian shall wear a “Vote for Borg” T-shirt for the next month. One issue, though: neither the Cryptoscalies contract, nor the T-shirt contract, have any provision that can facilitate any such arrangement. Some other obligations may even prevent you from relinquishing control of your Cryptoscalies, even temporarily, to a contract we might otherwise have written to implement the arrangement. How can we implement this sponsorship contract still?</p><p>With access to the history, we can write a contract with the following terms: “if an event is posted before the start of the month whereby your lizard dons the T-shirt, and no event is posted thereafter and until the end of the month, that causes the T-shirt to be removed or covered — then I shall pay you the convened sponsorship reward, which until then is escrowed in this composition contract.” I can imagine other conditions in a sponsorship contract, but let’s focus on how we would resolve any potential dispute on whether or not you did fulfill this part of our deal.</p><p>As long as we both agree on the outcome, we can simply sign a common settlement that assigns the escrowed funds to the deserving party. But what if we disagree? What if I somehow refuse to pay you though you did your part? Or, what if you demand payment even though you didn’t? How will the matter be resolved? How can a fair judge, automatically implemented by a “smart contract” on the blockchain consensus, adjudicate between our conflicting claims? Is there a way to resolve the issue without having to trust, pay and wait for a third party who’d act as arbiter?</p><p>All you have to do is prove to the consensus that you posted the T-shirt donning event before the beginning of the month, and didn’t post any contrary event until after the end of the month. Let’s assume that the blockchain gives access from each block to the entire event history as a Merkle trie, and gives direct access to a few hours worth of previous blocks from its contract scripting language. Then, to prove that your lizard did wear the T-shirt, you can tell the judge to look at a given recent block, and exhibit as evidence a Merkle proof that some transaction was posted that indeed represents the lizard wearing the T-shirt — with this evidence, you have a case, without it, you are thrown out of court. Now, proving that you did do something is easy, but you cannot so easily convince the judge that you did <em>not</em> post a contrary transaction whereby the lizard removes the T-shirt: for that, the judge would have to look back at each and every transaction between the donning of the T-shirt and the expiration date of the contract — and that definitely will not scale. What you can do, though, is challenge <em>me</em> to show any such transaction, if it exists as I claim it does. If I can show that indeed your lizard removed the T-shirt, by similarly exhibiting a recent block and a Merkle proof of inclusion from it, then you failed your contract and the judge will adjudicate in my favor. However, if I cannot provide such a counter-argument within my deadline, then the judge will adjudicate in your favor.</p><p>Using a field of mathematics known as <em>Game Semantics</em>, any formula quantified over the history of the blockchain can be transformed into such a “verification game,” and thereby be used in a contract. This enables the composition of arbitrary activities that were not otherwise designed to be composed.</p><p>Furthermore, these kinds of contracts can be kept private: the terms can be hidden from the public by only publishing a salted hash of these terms when initially signing the contract and escrowing collateral funds on the blockchain. Only in case of a dispute will the terms of the contracts have to be revealed. Actually, only one single clause of the contract has to be revealed, even though the contract can be very large and contain many clauses. The claimants can choose the simplest clause to argue, for instance the presence of brown M&amp;Ms in a contractually required bowl. Or they can pick whichever clause will maximize the damages they will be awarded, if the damages may vary with the clause.</p><p>To go one step further towards privacy, even the arguments themselves can be obscured using recursive zkSNARKs: all that bystanders would then see would be you and I sending O(1) proofs that remain impossible to decode by anyone not privy to our agreement. Yet all these bystanders, as well as the “judge” made of the “smart contract” and the blockchain consensus, will be able to check which one of us won this trial fairly and was adjudicated the escrowed funds. Actually, even the outcome of the trial can itself be kept private, using techniques pioneered by ZCash or MimbleWimble. All the public will then see is that some dispute happened, which was resolved according to objective justice, though no one but the parties involved will know either the topic of the dispute, or its conclusion.</p><p>And to achieve this composition of contracts, all we need from a blockchain is the ability to verify historical events — and of course, for suitable events to be emitted that we can reason about. To this end, we need the blockchain’s contract scripting language to give us access to recent block hash <em>and</em> we need each hash to commit to a trie of all past events. Interestingly, Ethereum only does the former. We can still achieve the latter, but to that end, <a href="https://github.com/amiller/ethereum-blockhashes">some contract</a> must maintain this trie and be called regularly to update it, and that’s a major hassle. If instead block miners maintained the trie, their cost at each block would only be logarithmic in the depth of the trie — just a few tens of hashes to carry — because nodes don’t need to remember the entire history to update these hashes, just the spine of the trie. As for remembering history, users will each be responsible for remembering the fragments of it that they care about.</p><p>Of course, the applications of this technology are not limited just to dressing cute lizards in T-shirts. They can be used to compose arbitrary contracts and create elaborate decentralized applications.</p><p>At <a href="https://alacris.io/">Alacris.io</a>, we are using the above technique among many others to build an operating system for decentralized applications. The applications we will enable will include atomic swaps between arbitrary financial products, elaborate financial contracts, scaling solutions based on side-chains, and much more. And we are hoping to convince blockchain implementers to actively support this history verification feature that will let us to compose decentralized applications in ways easier not harder than what Ethereum currently allows.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fcef0129518" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alacris/composing-contracts-without-special-provisions-using-blockchain-history-9fcef0129518">Composing Contracts without Special Provisions — using Blockchain History</a> was originally published in <a href="https://medium.com/alacris">Alacris</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Researcher in Programming Languages and Verification Joins Alacris]]></title>
            <link>https://medium.com/alacris/researcher-in-programming-languages-and-verification-in-application-to-cryptographic-protocol-9f6db9d681c?source=rss----f79445458e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/9f6db9d681c</guid>
            <category><![CDATA[cryptographic]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[formal-verification]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Amy Lynch]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 15:42:49 GMT</pubDate>
            <atom:updated>2019-04-24T15:51:47.841Z</atom:updated>
            <content:encoded><![CDATA[<h3>Researcher in Programming Languages and Verification in Application to Cryptographic Protocol Joins Alacris</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*UybliZIocrzHgMhqFI2IRg.png" /></figure><p>Alacris is honored to announce that Dr. Jay McCarthy, one of the leading researchers in programming languages and verification in application to cryptographic protocols, has joined our organization as Head of Research. He will be responsible for the direction of development of the Alacris Operating System’s Domain Specific Language, Alacrity, that will drive the projects’ flexible usable language.</p><p>Currently, McCarthy is also an associate professor at the University of Massachusetts Lowell, since 2015, where he has been teaching and researching, funded by the National Science Foundation, in areas of computer science, software design, architecture, protocols and theory of computation. He was also previously on the faculty at Vassar College and Brigham Young University. Much of his work directly correlates to the technology within the Alacris OS.</p><p>“There are many reasons I was interested in Alacris. Primarily in the mechanics like formal verification,” McCarthy said. “My world revolves around how to do this. I primarily look at the problem domains and where it is useful is not typically interfacing with people. It’s abstract and my previous involvement with Formal Verification is detached from what people deal with.”</p><p>His expertise spans beyond the classroom and labs, as a global author and presenter in industry respected publications, journals and conferences. McCarthy has an extensive background in computer science, mathematics and economics with Bachelors in all three from UMass Lowell and a P.h.D. from and Master’s in Computer Science from Brown University.</p><p>“Jay’s expertise and knowledge in the field will literally take years off of our roadmap in product development,” Alacris CEO/Co-Founder Chris Swenor said. “We have often said how hard it is to develop on blockchain and the mass amount of knowledge it takes; well, he is one of those few that has the exact knowledge and expertise needed and we are pleased he decided to work with us to make blockchain development easier for everyone else in the future.”</p><p>Outside of academia, McCarthy has also been a member of the PLT research group for the last 14 years as one of the main developers of the Racket programming language and holds a key role in the continued development of the Racket Web Server. He specializes in projects that include continuous integration systems, the Racket package system, the continuation-based Web server, and high-performance graphics runtimes.</p><p>McCarthy said he is also excited about the challenge of working in the environment of blockchain and its impact it will have on commerce and society.</p><p>“One of the main reasons is I really like the vision of blockchain. It will serve important dual purposes: reduce transaction costs and remove our reliance on untrustworthy people,” he said. “When we look at economic history we observe the decrease transaction costs as the main driver of economic well-being. Take the switch to the railroad from the horse to transport cross country. One might think goods get to their destination faster on trains, but that is not the case. In reality, trains were cheaper to run than horses were to maintain. This means trains lowered the transaction costs of the trade network. Removing intermediaries is another major way to reduce these costs; and in this case, good examples are financial markets and the insurance industry. We now understand that blockchain technology has the potential to drastically reduce transaction costs and release a flood of lower cost transactions” he said.</p><p>“This excited me about blockchain: reducing transaction costs and removing trust in people that untrustworthy. In 100 years we will talk about blockchain in the way that today we talk about the steam engine: it will change the way the economy works,” McCarthy said. “Alacris and the development of this technology are a great way to apply these tools.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f6db9d681c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alacris/researcher-in-programming-languages-and-verification-in-application-to-cryptographic-protocol-9f6db9d681c">Researcher in Programming Languages and Verification Joins Alacris</a> was originally published in <a href="https://medium.com/alacris">Alacris</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alacris & 1kx Join Efforts for Blockchain Solutions]]></title>
            <link>https://medium.com/alacris/alacris-1kx-join-efforts-for-blockchain-solutions-584822462c0b?source=rss----f79445458e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/584822462c0b</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[layer-2]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[developer-tools]]></category>
            <dc:creator><![CDATA[Amy Lynch]]></dc:creator>
            <pubDate>Fri, 29 Mar 2019 15:58:16 GMT</pubDate>
            <atom:updated>2019-03-29T15:58:01.438Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*nXkdE1aA4ks50GZZCZQh_Q.png" /></figure><p>Alacris, a Boston-based blockchain project created by LegiLogic, and 1kx, an early stage token fund, are joining to advance efforts in layer 2 solutions to work toward reducing the complexity of developing distributed applications using blockchain and thus create the opportunity for wider use of the technology.</p><p>Wide-spread use of blockchain technology is stalled due to issues with lack of scalability (both high latency and low throughput for transactions), lack of interoperability between blockchains and uncertainty regarding governance. However, even as these issues are being addressed by many ongoing projects, a larger problem continues to loom over the space: developing robust applications is too difficult for developers who are not experienced in all layers of blockchain security since even the smallest vulnerability can cause users to lose all their money.</p><p>LegiLogic and Alacris Co-Founders, Chris Swenor, CEO, and Francois-Rene Rideau, Chief Architect, are building an operating system Alacris, which is aiming to solve these issues.</p><p>“Just last month the COO of Algorand stated there are close to 30 million developers in the world and only around 200 thousand blockchain developers. This is because developing blockchain is hard and inefficient,” Swenor said. “We are building Alacris so the common developer doesn’t need to have 3 PhDs to be confident about building a decentralized app on the blockchain.”</p><p>Alacris recently raised close to $1 million in funding, through 1kx, Nervos Network and CMBI, and released a demonstration of a fast payment system. The Alacris Operating System goes beyond addressing scaling and interoperability like other Layer 2 protocols currently being built. The Alacris Operating System aims to make the development of robust decentralized applications accessible to a multitude of developers more than it currently is. Developers have the ability to pick “primitives,” which are software building blocks that deliver useful functionality and service, from a catalog sourced from Alacris’ own internal development, as well as from the broader community and partners. Using primitives, developers are able to utilize our Domain Specific Language and even choose which base-layer or blockchain platform they want to use. Through the compile process, the code is then automatically formally verified providing the developer NASA-level security without learning a new skill set.</p><p>“Having seen a lot of layer 2 projects, we saw few that were thinking beyond Ethereum to create an operating system on top of multiple layer 1 chains” 1kx Founder Lasse Clausen said. “Alacris offers this compelling vision of a layer 2 solution that could become the actual platform for developers to build decentralised applications on, and not the layer 1 chains.”</p><p>1kx was founded by Clausen and Christopher Heymann in pursuit of backing companies in the blockchain space with the mission to be founder friendly and a source of support with early-stage capital for tokenized projects.</p><p>“We’re excited about crypto economics because they enable new structures for large networks, potentially better than for-profit companies,” Clausen said. “As former startup entrepreneurs building a mobility network, we experienced first hand how traditional, VC backed startups really just aim for lock-in in order to extract as much rent as possible. We think an open source, tokenized network aligns incentives among stakeholders much better, making it more efficient and more scalable.”</p><p>Swenor said the partnership will allow Alacris to grow by hiring some of the best minds in the blockchain and crypto space but goes beyond just what the dollars can bring to the organization.</p><p>“This partnership allows us more clout within blockchain along with being able to leverage the years of experience Lasse and Christopher bring to the table, which is worth much more,” he said.</p><p>“At Alacris, we pride on our ability to envision and deliver solutions that are meaningful both from a business and a technical point of view,” Rideau said. “When we met Lasse, Christopher and their team, we were impressed by how they too could zoom in to exactly the issues that mattered both economically and technically. They stand out among other investors. We are excited to be working with them, and already grateful for all their feedback and guidance so far.”</p><p><em>Alacris is an Operating System for the blockchain. We provide formalized security, automatic fraud detection and recovery, as well as bridges to layer 1 and layer 2 protocols. Abstracting away all infrastructure concerns from the DApp developers so they can focus on building the applications. Developed by LegiLogic in 2018, Alacris is located in Boston. For more information, contact Amy Lynch, communications, at </em><a href="/service/mailto:amy@alacris.io"><em>amy@alacris.io</em></a><em> or call (956) 244–2879.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=584822462c0b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alacris/alacris-1kx-join-efforts-for-blockchain-solutions-584822462c0b">Alacris &amp; 1kx Join Efforts for Blockchain Solutions</a> was originally published in <a href="https://medium.com/alacris">Alacris</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Developing for the Blockchain is Hard Part 2: Computing Proper Collateral]]></title>
            <link>https://medium.com/alacris/why-developing-for-the-blockchain-is-hard-part-2-computing-proper-collateral-4014ca612e63?source=rss----f79445458e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/4014ca612e63</guid>
            <category><![CDATA[verification-game]]></category>
            <category><![CDATA[collateral-bond]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[François-René Rideau]]></dc:creator>
            <pubDate>Thu, 28 Mar 2019 21:07:36 GMT</pubDate>
            <atom:updated>2019-03-28T21:07:14.416Z</atom:updated>
            <content:encoded><![CDATA[<p>Many proposed blockchain solutions use verification games, whether informally as in TrueBit and Plasma, or formally as in <a href="https://alacris.io/">Alacris.io</a>. In these systems, an important challenge is for the contract to be able to assess whether participants are putting down sufficient collateral to accompany their claims; and this assessment crucially depends on having a good model for the price of gas.</p><h3>My Name is Bond, Collateral Bond</h3><p>In a system based on verification games, participants make <em>claims</em> that others may disprove if they are invalid. Each step of the verification game (or “smart lawsuit”) happens by invoking the “smart contract” on the blockchain with parameters detailing the claim (making a “smart legal argument”). If no one successfully counters the claim with a <em>counter-claim</em> within its <em>challenge period</em>, then the claim is considered validated. To punish those who make spurious claims and reward those that prove their claims invalid, participants who make a claim must accompany it with the deposit of a proper collateral. The claimant is <em>bonded</em> and the collateral is his <em>bond</em>, that will be released back to the claimant if the claim is validated, or to the counter-claimant if the claim is invalidated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*6CXCHa8UlBdYZ6oR" /><figcaption>Don’t misbehave or bounty hunters will come for you and collect your bond.</figcaption></figure><p>In the normal use pattern, an honest participant making a valid claim only ends up paying the price of making the claim, and pays nothing for proving it correct. It is the dishonest participants, making invalid claims or counter-claims, who end up paying by losing their collateral. This “bad guy pays” property makes verification games cheap and attractive. The downside is that the challenge period is a pain for users when it’s too long, and a security issue when it’s too short. However, there is also a crucial difficulty in <em>computing the proper collateral</em> to deposit: it must be small enough not to be an unbearable burden to the honest participants, but large enough to discourage the dishonest claimants and reward their counter-claimants, by covering any gas paid by the counter-claimant.</p><p>If there is no collateral, or if the collateral is too low, a bad actor could “troll” or “grief” an honest party with a large number of frivolous lawsuits. The honest defendant might have to spend a lot of money in gas for “smart court fees,” and might be pushed into making exploitable mistakes, revealing information that enables attacks (such as a DoS attacks based on location information), giving up in rage, or going bankrupt. Collateral amounts should be high enough to discourage bad behavior and to award honest participants damage reparations that cover all the cost of litigation: gas costs of getting the transactions in, operational costs of running and securing computers in redundant data centers, insurance cost to deal with the risk and volatility associated with other costs, moral cost of it all.</p><p>On the other hand, collateral amounts should be low enough that honest parties of modest means can afford to defend themselves — although one way around this problem is to allow them to sell their claims to a richer party who has time, money and computer resources enough to afford taking the litigation to its conclusion. Another solution would be borrowing funds to use as collateral, but it cannot be implemented purely on the blockchain. If bad actors could even temporarily cause the contract to require overly high collateral bonds, they could possibly prevent the other parties from defending themselves.</p><h3>Estimating the Gas Price</h3><p>The main thing that the bond must cover is “smart court fees” for the other party should the current claimant be the losing party. These fees are transaction fees required for the other party to publish their arguments on the blockchain.</p><p>In the case of Ethereum, the cost is proportional to the price of gas, which is not fixed in ETH, but floats depending on supply and demand and market manipulation by unsavory miners and transaction posters. Note, however, that the issue is not specific to Ethereum; it is an essential issue of any blockchain. A limited supply of transaction space is a necessary limitation of any public blockchain, because block verification is massively decentralized, which means that block data must fit in the limited network and cpu bandwidth of those who partake in the verification network. Given this limited supply, the economic value of gas (being a fixed fraction of that transaction space) will naturally vary with the demand, in a way that is largely independent from the value of the tokens themselves; therefore the only economically rational way to ration this supply is by letting the relative price of gas vs tokens float. A fixed price would cause artificial scarcity when it’s higher than the free market equilibrium, and long waiting lines when it’s lower.</p><p>Thus, transaction fees will float, and the structure of the contract can only tell you how much you have to pay compared to some floating base price. For the smart contract to ensure that claimants post sufficient fees to support their claim, it must therefore be able to compare those fees to some multiple of an appropriate estimate of the gas price or other base price.</p><p>It is therefore important for high-level verification-based contracts to be able to predict the price of gas in the near future, the next few hours or days, however long the longest smart lawsuit may take, which can be statically determined from the number of quantifier alternations in the contract clauses times the duration of one challenge period. The prediction does not have to be very accurate, but it must be a strict upper bound on the price of gas in that window, even accounting for unusual volatility in the market and deliberate market manipulation by some sizeable minority of accomplices among consensus miners.</p><p>One formula might consist in observing the price of gas over the last few days of fully confirmed transactions; in each block discard the 33% (by gas limit) most expensive transactions and keep the remaining high price; then discard the 33% (by block) most expensive of those prices, keep the remaining high price, but assume it may shoot up five times (or some other multiple of) the volatility observed among the prices not discarded; further multiply by eight, and use that as a gas price basis. The exact formula will have to be devised by someone with expertise in economic or actuarial modelling — the point being that the formula must reliably overestimate how much gas honest people may have to pay to defend themselves, yet not by such a large factor that it becomes unaffordable.</p><p>When using a short term contract that itself expires in a few days, the signatories can agree on the price prediction and include it as an explicit parameter during the creation of the contract. A limit to one complaint per participant, or per pair of participant, as applicable, can also put a cap on how much trouble a dishonest participant can wreak if the prediction becomes too low. But what about long term contracts that may manage assets over many weeks, months, or even years, while the gas price may vary wildly? Whatever formula is used will have to be quite elaborate, and will therefore be too expensive for the low-level contract to recompute every time it is invoked. Unless somehow the blockchain’s low-level contract VM itself supports predicting gas according to this exact same formula. Yet, like all computations, the formula for gas prediction can be verified using our usual interactive proof techniques, so updates to the gas price estimate can be made as claims against the contract, and could be included as part of other claims that are part of the distributed application’s regular operations.</p><h3>A Protocol to Maintain the Gas Price Estimate</h3><p>If the distributed application includes side-chains, the side-chain operators may update the price estimate, possibly in conjunction with updates to the state of their side-chain. If there are no privileged parties in the long-running contract to regularly maintain the contract state, then some protocol part of the distributed application may designate whose responsibility it is (e.g. each participant in turn in some order) to update the gas price basis next time the previously registered estimate falls out of some safety range, say below 4 times or over 16 times the current price prediction. In some contracts, is also possible that their own selfish interest in other participants not making spurious claims against them will be incentive enough for some participants to spontaneously make claims to maintain the gas price basis within a safe range. An invalid claim will be verified invalid and rejected, and the wrongful claimant will lose their collateral as well as their operator privilege, if any, which should be enough to incentivize the party that denounces them — as long as the last previously confirmed prediction is still a valid upper bound on the gas price.</p><p>A further improvement on the protocol may involve building a futures market for gas price. Insurers will offer insurance against rise of the gas price, possibly available for use in verification games only. Users who wish to protect themselves from gas price fluctuations can then avoid the volatility, at a small premium. The mechanism used by MakerDAO to provide a stable coin indexed on the dollar, the DAI, can also be used to provide future GAS at fixed price in either USD or ETH. Insurers can also leverage the “gas refund” mechanism of Ethereum to buy gas in advance, though these refunds can only cover half of the gas of any given transaction.</p><p>There is a lot of complexity involved in such a protocol; to track gas price requires carefully watching a full node on the blockchain validation network. Therefore only professionals should partake in the protocol. But, there could be a common verifiable approximate gas price prediction contract on the blockchain, the estimates of which are shared by all contracts that rely on the same formula, as a public service. As part of developing the Alacris Operating System, we will make it possible for all DApps to use the gas price estimates maintained by our DApps, as well as other verifiable oracles for data about Ethereum and other blockchains.</p><p><em>This article is the second in an ongoing series titled “Why Developing for the Blockchain is Hard.” Keep an eye out for our next article about DoS Attacks.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4014ca612e63" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alacris/why-developing-for-the-blockchain-is-hard-part-2-computing-proper-collateral-4014ca612e63">Why Developing for the Blockchain is Hard Part 2: Computing Proper Collateral</a> was originally published in <a href="https://medium.com/alacris">Alacris</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Employee Spotlight: Matt Audesse]]></title>
            <link>https://medium.com/alacris/employee-spotlight-matt-audesse-4742d8c68e33?source=rss----f79445458e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/4742d8c68e33</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[engineer]]></category>
            <category><![CDATA[boston]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Amy Lynch]]></dc:creator>
            <pubDate>Thu, 21 Mar 2019 15:20:35 GMT</pubDate>
            <atom:updated>2019-03-21T15:20:06.064Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9qBtDAh2ooYgny6mrki4yA.jpeg" /></figure><p><strong>Meet Matt<br>Position: Senior Engineer<br>Home: Bangor, Maine</strong></p><p>Creating solutions for Blockchain and figuring out mass adoption of the technology is not your typical 9 to 5 task, but we don’t have your typical engineers. Matt Audesse thrives on finding the solutions of the technical puzzles posed by blockchain projects.</p><p>“Alacris in particular has set very ambitious goals for itself and the capabilities we confer on services which leverage it. I find tackling difficult tasks — such as those facing us — in an elegant and clean way to be hugely gratifying,” he said. “Perhaps even more attractive to me is the fact that everyone here already understands and has embraced purely functional programming as an essential component of our strategy”</p><p>Atypical also applies to Matt’s educational and professional background. He studied international political science at The University of Maine and speaks Latin and German. His career also spans a wide variety of leadership and mentor positions and team compositions from his involvement with four start-ups, including Alacris, to creating software for fortune 500 companies, local insurance agencies, financial services and investment firms, and even building components that integrated with about 20 U.S. State Departments of Revenue.</p><p><strong>More about Matt:</strong></p><p>Who inspires you?</p><ul><li>Maynard Keenan is the first answer that comes to mind, for a number of reasons:</li><li>He has a way of rejecting categorization or falling in line with others’ expectations, and his lyrics tend to reward you for doing your own thinking as well.</li><li>When not performing he’s perfectly happy to “go dark”.</li><li>He’s known mostly for his music but, as David Lynch would put it, “he’s living the art life” and constantly has his hands in many other pursuits (e.g. winemaking).</li><li>I dig heavy tunes, but most such music leans toward the vapid side lyrically; Maynard’s an exception.</li><li>Longevity and nostalgia since I’ve been listening to his work for multiple decades now.</li></ul><p>Where is your favorite place in the world?</p><ul><li>The driver’s seat during a good road trip.</li></ul><p>What was the last book you read?</p><ul><li>“Disinformation” by Ion Mihai Pacepa.</li></ul><p>What is your favorite thing to do/ spend your time doing outside of work, i.e. do you have a hobby?</p><ul><li>I enjoy traveling and getting out into nature.</li></ul><p>If you had a motto, what would it be? It doesnʼt have to be original…</p><ul><li>Be careful what you get good at, because you’ll probably wind up doing a lot of it.</li></ul><p>Talent and skill not an issue, what other profession would you like to do?</p><ul><li>Maybe painter or author? I could lose a lot of time pondering this question.</li></ul><p>What gets you out of bed in the morning/ what keeps you passionate?</p><ul><li>Passionate isn’t a word I’d use to describe myself, but there’s something very compelling (and probably addictive) to solving technical puzzles like I get to do with code. I’m constantly trying to devise more beautiful and correct solutions for the software I write.</li></ul><p>What is the best meal you have ever eaten?</p><ul><li>I’ve had plenty of amazing food and find it hard to play favorites, so the best meal I’ve had lately is the bowl of pho I had for lunch.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4742d8c68e33" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alacris/employee-spotlight-matt-audesse-4742d8c68e33">Employee Spotlight: Matt Audesse</a> was originally published in <a href="https://medium.com/alacris">Alacris</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Developing for the Blockchain is Hard — Part 1: Posting Transactions]]></title>
            <link>https://medium.com/alacris/why-developing-for-the-blockchain-is-hard-part-1-posting-transactions-31b5db9b6122?source=rss----f79445458e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/31b5db9b6122</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[François-René Rideau]]></dc:creator>
            <pubDate>Thu, 14 Mar 2019 16:48:18 GMT</pubDate>
            <atom:updated>2019-03-14T16:48:33.822Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why Developing for the Blockchain is Hard — Part 1: Posting Transactions</h3><p>We at <a href="https://alacris.io/">Alacris.io</a> want application developers to be able to spend their time focusing on the high-level design of their applications, in terms of economic interactions between multiple parties. We want to save them from having to deal with the complexity of issues like posting a transaction.</p><p>Wait, some will say: Posting a transaction is complex? Isn’t there already a function to call for that? Well, yes and no. There is already a function that works well enough for the simple case of manual payments; but that function fails badly and is wholly unsuitable for use in the more elaborate cases that matter to a distributed application backed by a smart contract.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*k1OCQDARvFuJqeY1.jpg" /><figcaption>When the simplest device (a Turing Machine) is already extremely complex…</figcaption></figure><h3>Existing Functions to Post Transactions are Lacking</h3><p>Sure, you will find functions to create and post transactions in the Ethereum JSON-RPC API, or the equivalent libraries for Go, Javascript, Python, Rust or your favorite language. But calling one of these functions does not and cannot guarantee that the transaction will go through. What if your application crashes in the middle of the interaction? What if your Ethereum node client crashes? What if you are victim of a network outage? What if you fail to use a high enough GAS limit, or use a high enough GAS price? What if your transaction loses the race to another transaction that you posted, or to a transaction posted by someone else using the same contract? What if your transaction makes it into a block, but that block gets reversed by a heavier uncle? What if any of the above happens, not by an unfortunate accident, but out of a deliberate attack by an enemy?</p><p>In all these cases, the simple answer is “after ten, thirty or sixty minutes, check whether the transaction went through, and if not try again.” And as long as you’re just a human sending payment and you’re in no great hurry, that’s probably a good enough answer. All you need is for your “wallet” to warn you that the transaction failed, and to offer you to try again with updated parameters at the press of a button. The merchant or trading partner on the other side will usually wait patiently for the payment to go through before they do anything, anyway. And so the existing function is good enough to implement a wallet.</p><p>Now, to write an application that is not merely a payment wallet, you need more than that. In a typical “smart contract”, one or multiple parties each posts a large bond that they will stand to lose should they fail to post the transactions that they contractually promised to post within a tight deadline. Is your “post transaction” function good enough to use in such a smart contract? If it works 99% of the time, that means that every hundred times someone will lose their large bond. Is that good enough for you? If the function works 99.9999% of the time, it will still fail once in a million calls. If it is to be used a billion times a year, that is still quite a number of discontent users each losing a significant amount of money. And yet, 99.9999% “six nines” reliability is already considered not easy to achieve in practice. Can you actually make this function that reliable, or even better? How many nines of reliability can you afford to have? And how many can you not afford not to have? When your function eventually fails because the world conspires against you, then what? Remember that in writing the function, you are not just fighting accidental odds of failure: you’re fighting deliberate attempts to thwart you by bad actors who will sign a contract with you just so they can prevent you from posting your transaction and collect part of your bond as reparations. Even if they can’t collect reparations from making you fail, enemies and vandals may want to see you lose even when they can’t directly benefit; and elaborate gangsters might threaten to make you fail to hold your bond hostage, blackmail you and ransom you. Will your function remain as reliable as you need it to be in that adversarial environment?</p><h3>What a Proper Post Transaction API would do</h3><p>The existing “post transaction” function is not at all a functional API usable by distributed applications beside simple wallets. The entire purpose of a functional API is to make it possible to write automated programs that will call the API, let it do its magic, and not have to deal with the details below that level of abstraction. A proper “post transaction” function will ensure that the transaction WILL go through, despite all the potential issues within the control of the program: It will include a good algorithmic model to follow the progress of the transaction in the network. It will handle persistence of data so the application survives a crash. It will maintain multiple application replicas over multiple data centers so that the application cannot “just” be thwarted by an enemy doing a DDoS. If needed, it will route all relevant communications through virtual circuits and/or mix networks so that enemies cannot easily locate the contract-using machine and attack it. It will automatically recompute nonces to adjust to race conditions. It will use some informed model-based strategy to watch the network and dynamically adjust what gas price to use, so as to resist block-buying attacks by partaking in a suitable auction for transaction space (and block-buying attacks are not just theoretical attacks, but things that have actually happened in the past: consider the case of the Fomo3D contract: <a href="https://medium.com/coinmonks/how-the-winner-got-fomo3d-prize-a-detailed-explanation-b30a69b7813f">1</a>, <a href="https://medium.com/coinmonks/the-buy-a-block-attack-c0ce845475d7">2</a>, <a href="https://motherboard.vice.com/en_us/article/7xq38d/fomo3d-winner-clogged-ethereum-blockchain">3</a>). All in all, a proper “post transaction” function will patiently nurse a pool of desired transactions until each of them is eventually posted and confirmed on the blockchain, once and only once, in a suitable order.</p><p>What if some issues outside the control of the program still crop up and prevent the transaction from being posted? Then the “post transaction” function will send suitable alerts, before it is too late. The program calling the function has the option of handling some of these alerts; but ultimately, whatever alerts are left unhandled will reach some human watchman on call. It is the role of the Blockchain Operating System to take over at this point, as the application developer doesn’t even have access to the entire context necessary to handle these complex issues. Is the application deployed on a cell phone? The user to alert is the cell phone owner, using cell phone alerts. Is the application deployed on a redundant network spanning three data centers across different continents? The user to alert may be a professional System Reliability Engineer on call. Users may be using a proprietary alert system that just did not exist when the application was written, and yet the application will indirectly make use of it, because alerts are part of the abstraction offered by the Operating System, rather than features of the application itself. What alert mechanism is used will depend on the deployment configuration for the application. It is not the responsibility of the application developer, who not only cannot know all the existing deployment situations, but by definition cannot predict the deployment situations that will only be invented in the future. Letting the application developer access the details of the deployment and handle the emergency situations would actually be big security concern that goes against all good practices for software security.</p><p>Now, what when an application fails? The human on call will have to take it over from there. And unless you’re a large corporation or wealthy individual affording a software operations engineer as technical support, that human on call will be you. Then, a <em>great</em> functional API will make it easy for that human on call to assess the situation and take appropriate action:</p><ul><li>plugging some cable back before retrying, retrying using a backup network connection,</li><li>calling a friend who will post the transaction for him over a different network,</li><li>using different parameters with more gas or a higher gas price,</li><li>dropping the transaction and losing the bond because posting the transaction would cost more than the bond is worth after all,</li><li>still posting the transaction and losing more in gas than the transaction is worth, because the failure to post would reward the bad guys, or would cause a loss of trust and future business from other users,</li><li>use some alternate execution path or mitigation game foreseen in the smart contract,</li><li>accept a settlement offer from the other party, rather than have a smart judge rule against you, etc.</li></ul><p>Many failure and recovery modes are possible, and in general it is not the responsibility of the calling function to painfully handle recovery strategies that involve global state way beyond the scope of said function. Rather, the Blockchain Operating System shall automatically deduce these monitoring interactions from the regular structure of the calling program.</p><p>However, before he may take any action at all, the human must be able to understand what is going on, what transaction is being held up, what value is at stake. It is therefore essential that the Operating System offers to the human the ability to inspect the structure of the calling program. The User Interface should make it possible for the user to inspect the current state of the program being interrupted. This is the reason why the program usually cannot be written as “just” simple function calls in Python, Go, Javascript or any such “blub” language: the program has to be written in a suitable Domain Specific Language (DSL), compiled by a metaprogram that has access to the entire program structure, rather than merely to local calls (though the program could be built from a metaprogram written in a blub language, in the style of Google TensorFlow, or from a metaprogram targeting the blub language). Writing distributed applications in suitable DSL also means that these applications can be made modular, where common modules can be reused and composed into larger applications, when written properly. By contrast, writing these applications by hand into a procedural language would lead to all the abstractions leaking and making the resulting program unsuitable for modular composition.</p><h3>Towards a Blockchain Operating System</h3><p>In conclusion, something as deceptively simple-looking as “posting a transaction” justifies that distributed applications should not be written using existing APIs, or using any API whatsoever expressed as function calls in any existing language. Rather, it should be written in a Domain Specific Language designed for the purpose of writing such applications, running on top of a “Blockchain Operating System” that will not only provide robust abstraction and enforce security practices, but also help humans handle emergency situations, depending on their specific deployment configuration. And posting a transaction is only one of a multitude of aspects of a distributed application, each of which has to be handled properly. At Alacris, we believe that these aspects are better implemented well once by infrastructure specialists then shared between all applications, rather than implemented many times by each application developer stepping out of his regular role and possibly out of his skills. That is why we at <a href="https://alacris.io/">Alacris.io</a> are building a Blockchain Operating System, that will manage these aspects for the application developers.</p><p><em>This article is the first in an ongoing series titled “Why Blockchain is Hard.” A new article will be released every three weeks. Keep an eye out for our next article “Computing a Proper Collateral.”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31b5db9b6122" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alacris/why-developing-for-the-blockchain-is-hard-part-1-posting-transactions-31b5db9b6122">Why Developing for the Blockchain is Hard — Part 1: Posting Transactions</a> was originally published in <a href="https://medium.com/alacris">Alacris</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ETHDenver Day 2 & 3: Amy’s Perspective]]></title>
            <link>https://medium.com/alacris/ethdenver-day-2-3-amys-perspective-af24fd182565?source=rss----f79445458e89---4</link>
            <guid isPermaLink="false">https://medium.com/p/af24fd182565</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[ethdenver]]></category>
            <category><![CDATA[layer-2]]></category>
            <dc:creator><![CDATA[Amy Lynch]]></dc:creator>
            <pubDate>Tue, 26 Feb 2019 22:49:09 GMT</pubDate>
            <atom:updated>2019-02-26T22:49:09.645Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7hhGSAY-MGh7O8MIk9DPhw.jpeg" /></figure><p>Can you be in the present and the future all at the same time? Being at a hackathon is somewhat like that. Almost indescribable, but once you enter the Denver Sports Palace, you feel it. A building made up of about 6 open level “floors” winding where it almost seems like one melts into the other. Where you almost feel like you are always in the middle of the action. Panels, discussions and workshops that easily allowed audience members to flow in and out and easily take in the hackathon teams’ process as they develop innovation right in front of our very eyes; again very much in the present but seeing where the future is going.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w1ZvSla8ENhoP_cIgDWXGQ.jpeg" /><figcaption>Me and the Bufficorn!</figcaption></figure><p>It sounds unreal, but it was a weekend of great nuggets and takeaways from many perspectives of blockchain and cryptocurrency in its present and future states. As someone coming from communications and marketing, many of those topics particularly piqued my interest. Adding to the magic, with coffee from a local shop, Amethyst Coffee, which flavored their latte with marshmallows from “lucky charms”… yes there is such a thing and yes, it was delicious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c_id_aEmWN0blXW0g3g1lQ.jpeg" /><figcaption>See.. it was real! <a href="https://www.amethystcoffee.co/">https://www.amethystcoffee.co/</a></figcaption></figure><p>I spent most of my time Day 2 melting into a beanbag chair near the Bufficorn Stage taking in discussions about governance, digital security, social impact, which turned out to be a big part of this conference, finance and security.</p><p>However, the one I found most interesting from my perspective was a panel titled “The Next Million” featuring Emily Coleman (ShapeShift), Lily Liu (Earn.com), Nabil Naghdy (Status), and Marguerite deCourcelle (Coin Artist).</p><p>Emily started the conversation about bringing the next wave of users in with something near and dear to me, bringing in people to whom blockchain is a brand new subject.</p><p>“I know marketers that are very talented coming from different worlds, even from finance, and there is a little bit of a fear of, ‘do I belong there? Will I be accepted? Will I ever understand this?’ I was in hospitality and tourism industry before and I had those same fears but I also joined a company where our CEO and everyone who was around me was helping me. They didn’t make me feel like it wasn’t doable for me to get there,” she said.</p><p>“What I like is we use this term ‘inclusivity’ and bring people in, which is a big part of the ethos side of this industry. I was out at the food truck today and a guy came up to me and we were chatting and he’s in the medical field and he said ‘I’m trying to figure out how I get in (blockchain),’ and I brought the point up that you actually have background in things that could be very interesting and usable here and he said, ‘I didn’t really think about it that way,” Emily continued. “We should help people identify how they can be part of this ecosystem and bring their talents and that might not be technological.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AMbKSmIEHMrKrMWh_6W1Dw.jpeg" /><figcaption>ETHDenver Sponsors had some great swag, information and opportunities for all Bufficorns.</figcaption></figure><p>The other panelists also brought up great points of how we can change the narrative to be more relatable to help adoption of blockchain by those who will not necessarily be developing in the space, but using the technology.</p><p>“The narrative around privacy needs to be re-branded into digital security. Sometimes I feel like we should talk more to why this is important to hundreds of millions of people rather than talking technology, which is cool, but we need to talk about the other side of the conversation,” Lily said. “That narrative needs to be much simpler, and use cases need to be simpler, as well. I don’t think that censorship resistance is a narrative that will bring in anymore people beyond the appeal it is right now. Maybe we need to talk more about freedom and security rather than censorship and privacy. The later sounds like you have something to hide and freedom is more aspirational… Where as security and safety is something everyone can understand.”</p><p>Nabil also touched on the ole’ how you describe what you do for a living to people (I know I have a “fun” time with this one, too) and helping to shift that narrative to create a more telling view of what blockchain really is and can do.</p><p>“Blockchain is contributed to the cryptocurrency valuation for the vast majority of people. If I have family ask me what I do I say, ‘I work in cryptocurrency,’ and they say ‘Ahh..you work for bitcoin?’ and usually I concede ‘yeah, sure, fine.’ So that misconception of language, which comes back again to Blockchain vs. bitcoin, vs Ethereum. Maybe web3 is the answer but there is this misconception of this whole space that its about currency speculation and people making money and it’s more than that,” he said.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-D5oSjQBm8dxsizSBB7tA.jpeg" /><figcaption>On the Buidler’s Level judges make final decisions for the finalists that created projects over the weekend.</figcaption></figure><p>In fact, leading into Day 3 it was 120 projects that entered into the ETHDenver Hackathon. With a number focusing on social impact and social good as a focus of their projects. You can check out a list of Finalists and Bounty winners <a href="https://kauri.io/collection/5c69c8c39c73740001dab899/ethdenver-2019-finalists-and-winners">here</a>. Projects ranged from government task marketplaces, aimed at helping underprivileged citizens can fulfill government-specified bounties and get rewarded for their contributions in the form of welfare benefits (Wel-fair), to a sketch collaborative on the Ethereum blockchain using instruction to a real handmade 2d plotter to see everyone’s doodles (EthASketch).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iPOlZY6WDmDpsbIL2vUV7w.jpeg" /><figcaption>Finalist presentations to close out the conference.</figcaption></figure><p>The closing after party was nothing short of the entire culture of ETHDenver 2019 throughout its entirety: fun, eclectic, surreal and welcoming. Definitely one to not miss next year and of course mark your calendars for ETHBoston, Sept. 6–8.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJPbrbyBpJ7s%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJPbrbyBpJ7s&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJPbrbyBpJ7s%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/78cf3c8373545a91087a5315a2ba284b/href">https://medium.com/media/78cf3c8373545a91087a5315a2ba284b/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QtHAve8d_jiXs6cwc5W_Qg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*58cY7QIlGISjNcBI2WfmIQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af24fd182565" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alacris/ethdenver-day-2-3-amys-perspective-af24fd182565">ETHDenver Day 2 &amp; 3: Amy’s Perspective</a> was originally published in <a href="https://medium.com/alacris">Alacris</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>