<?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[Stories by Aleksandra Skrzypczak on Medium]]></title>
        <description><![CDATA[Stories by Aleksandra Skrzypczak on Medium]]></description>
        <link>https://medium.com/@Skrzypczak?source=rss-32f833fb6dfb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dn6PG_ft4TK7KIApbZRQhw.jpeg</url>
            <title>Stories by Aleksandra Skrzypczak on Medium</title>
            <link>https://medium.com/@Skrzypczak?source=rss-32f833fb6dfb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 14:34:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Skrzypczak/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Brass Golem Beta 0.16.1]]></title>
            <link>https://medium.com/golem-project/brass-golem-beta-0-16-1-e9910308b620?source=rss-32f833fb6dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9910308b620</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[golem]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[golem-project]]></category>
            <dc:creator><![CDATA[Aleksandra Skrzypczak]]></dc:creator>
            <pubDate>Thu, 28 Jun 2018 15:38:10 GMT</pubDate>
            <atom:updated>2018-06-28T15:38:10.840Z</atom:updated>
            <content:encoded><![CDATA[<p>The new patch release of Brass Golem Beta 0.16.1 is available. This version contains some minor bugfixes, optimizations and a payment system refactor.</p><p>Thanks to the consistent feedback from our users on UX issues we’ve introduced some fixtures in GUI.</p><p>Additionally, in this release we are introducing the payment refactor, which allows to eliminate the unlikely but possible scenario of not sending funds properly. Transactions are re-broadcasted anytime they go “missing” from the tx pool, and this re-broadcasting stops only after they are confirmed by the required number of blocks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kae5p6GAv14FQz6Hf80d3Q.jpeg" /><figcaption>Muhammed Tanrikulu and Adam Wierzbicki working on GUI</figcaption></figure><p>As per usual, we encourage you to follow our project’s progress on the Golem <a href="https://trello.com/b/YL1qZ2pZ/brass-kanban">Kanban</a>, download and test this latest release.</p><p><strong>We are thankful for you comments and feedback, and we encourage you to continue doing so, as our software development is an ongoing process and users help make it better and more efficient.</strong></p><p>For more details and troubleshooting, please visit the <a href="https://github.com/golemfactory/golem">official GitHub repository</a>.</p><h3>Upgrading to Brass Golem Beta 0.16.1</h3><p>You can find detailed information here:</p><ul><li><strong>macOS</strong></li></ul><pre>brew update<br>brew upgrade golem<br>brew cask upgrade golem</pre><pre>sudo chown root:wheel $(brew<strong> </strong>--prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve<strong><br></strong>sudo chmod u+s $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve</pre><ul><li><strong>Ubuntu<br></strong>Download the installation script from <a href="https://raw.githubusercontent.com/golemfactory/golem/develop/Installer/Installer_Linux/install.sh">here</a>. In terminal, run <br>chmod +x install.sh &amp;&amp; ./install.sh.</li><li><strong>Windows<br></strong>Download and execute the installer from <a href="https://github.com/golemfactory/golem/releases/download/0.16.1/golem-0.16.1-windows.exe">here</a>.</li></ul><p>If you encounter any errors please let us know in the testers channel at <a href="https://chat.golem.network/home">chat.golem.network</a> or write an email to contact@golem.network .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9910308b620" width="1" height="1" alt=""><hr><p><a href="https://medium.com/golem-project/brass-golem-beta-0-16-1-e9910308b620">Brass Golem Beta 0.16.1</a> was originally published in <a href="https://medium.com/golem-project">The Golem Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brass Golem Beta 0.16.0]]></title>
            <link>https://medium.com/golem-project/brass-golem-beta-0-16-0-7ed7ee2341b0?source=rss-32f833fb6dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ed7ee2341b0</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[golem]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[golem-project]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Aleksandra Skrzypczak]]></dc:creator>
            <pubDate>Wed, 06 Jun 2018 16:28:57 GMT</pubDate>
            <atom:updated>2018-06-06T16:33:44.373Z</atom:updated>
            <content:encoded><![CDATA[<p>We are happy to announce the new release of Golem Brass Beta 0.16.0.</p><p><strong>Important! This version introduces changes to the Golem protocol and uses different cryptographic methods for signing and serializing messages so it’s not compatible with the previous Golem versions. Nodes running 0.16.0 would be able to only compute tasks from nodes that are running this updated version.</strong></p><p>Brass Beta 0.16.0 improves the general performance of the network, and additionally, of the entire application. Moreover, it also introduces new interesting features for requestors:</p><ul><li>Requestors can now define the minimal performance of the providers’ machines. For example, this can be used to ensure their task will be computed only on machines that are stronger than their own ones.</li><li>Requestors can now set a different number of samples per pixel than the one that is set by default in the scene, from within the Golem interface.</li></ul><p><em>To be noted, the testnet version of 0.16.0 will feature our Concent service enabled by default. However, not all use-cases for it will be enabled.</em></p><p><strong>Please update your Golem version to this latest one, to ensure you will be using the network at its full capacities to date.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hYb9THKAC9kSDYY3RidVoQ.jpeg" /><figcaption>Adam Wierzbicki working on message encryption</figcaption></figure><p>As per usual, we encourage you to follow our project’s progress on the Golem <a href="https://trello.com/b/YL1qZ2pZ/brass-kanban">Kanban</a>, download and test this latest release.</p><p><strong>Most importantly, we would like to remark that your feedback matters, as it plays a key part for us to continue improving Golem.</strong></p><p>For more details and troubleshooting, please visit the <a href="https://github.com/golemfactory/golem">official GitHub repository</a>.</p><p>More detailed changelog:</p><h4>Core</h4><ul><li>Different, optimized cryptographic methods for message signing and serializing</li><li>New additional settings for choosing providers based on their performance</li><li>Updated Terms of Use</li><li>Possibility to define the number of samples per pixel in Blender scenes</li><li>Improved verification metrics for comparing images</li><li>More friendly CLI options results, eg. “golemcli res show” or “golemcli task subtasks”</li><li>Modified runtime environment configurations</li><li>GNT is converted to GNTB as soon as possible: in previous versions, GNT was automatically converted to GNTB when it was necessary, Ie. when a user was trying to add a new task. From now on, we’ll be doing the conversion earlier, right when we have enough ETH to cover the gas price.</li><li>Bugfixes &amp; optimizations</li></ul><h4>Electron</h4><ul><li>Minimal performance setting added</li><li>Lock Fund information added</li><li>New Footer</li><li>Malicious Node blocking system implemented</li><li>Terms and privacy policy updated</li><li>Bugfixes, UI &amp; UX improvements</li></ul><h4>Concent</h4><ul><li>Concent enabled by default on Testnet</li><li>React to ForceSubtaskResults</li><li>React to SubtaksResultSettled</li><li>React to AckSubtaskResultVerify</li></ul><h3>Upgrading to Brass Golem Beta 0.16.0</h3><p>You can find detailed information here:</p><ul><li><strong>macOS</strong></li></ul><pre>brew update<br>brew upgrade golem<br>brew cask upgrade golem</pre><pre>sudo chown root:wheel $(brew<strong> </strong>--prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve<strong><br></strong>sudo chmod u+s $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve</pre><ul><li><strong>Ubuntu<br></strong>Download the installation script from <a href="https://raw.githubusercontent.com/golemfactory/golem/develop/Installer/Installer_Linux/install.sh">here</a>. In terminal, run <br>chmod +x install.sh &amp;&amp; ./install.sh.</li><li><strong>Windows<br></strong>Download and execute the installer from <a href="https://github.com/golemfactory/golem/releases/download/0.16.0/golem-0.16.0-windows.exe">here</a>.</li></ul><p>If you encounter any errors please let us know in the testers channel at <a href="https://chat.golem.network/home">chat.golem.network</a> or write an email to contact@golem.network.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ed7ee2341b0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/golem-project/brass-golem-beta-0-16-0-7ed7ee2341b0">Brass Golem Beta 0.16.0</a> was originally published in <a href="https://medium.com/golem-project">The Golem Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brass Golem Beta 0.15.1]]></title>
            <link>https://medium.com/golem-project/brass-golem-beta-0-15-1-7f43a7e3f5f5?source=rss-32f833fb6dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f43a7e3f5f5</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[golem]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[golem-project]]></category>
            <dc:creator><![CDATA[Aleksandra Skrzypczak]]></dc:creator>
            <pubDate>Tue, 24 Apr 2018 13:07:58 GMT</pubDate>
            <atom:updated>2018-04-24T16:24:03.659Z</atom:updated>
            <content:encoded><![CDATA[<p>We are happy to announce the new release of Golem 0.15.1.</p><p>This release adds as a feature, the possibility to restart a single subtask after the whole task hits deadline.</p><p>This functionality may be useful if a user is not satisfied with a small part of the rendered image and wants to repeat this particular computation with a different provider.</p><p>We have also lowered eth gas cost and predicted gas amount needed estimations, and included fixes to several errors with diverse severity on this new release.</p><p><strong>We strongly recommend updating your Golem version to the newer one.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ZeTpXLTY2uCS7BgDOdtCA.jpeg" /></figure><p>As usual, we encourage you to follow the progress of our project on Golem <a href="https://trello.com/b/YL1qZ2pZ/brass-kanban">Kanban</a>, download and test this latest release</p><p>Most importantly we would like to remark that your feedback matters, as it plays a key part for us to continue improving Golem.</p><p>For more details and troubleshooting, please visit the <a href="https://github.com/golemfactory/golem">official GitHub repository</a>.</p><p>More detailed changelog:</p><h4>Core</h4><ul><li>Possibility to restart single subtask after task deadline</li><li>Less restrictive eth for gas usage estimation</li><li>RPC call that displays number of subtask that is going to be used by Golem for given scene parameters</li><li>Changes and fixes in golemcli tasks show</li><li>Checks that task id and subtask id were generated by requestor</li><li>Fixed task persistence</li><li>Sync payment processor on startup</li><li>Task duration computation changed</li><li>Send RemoveTask message after task is finished</li><li>Additional logs for funds locks</li></ul><h4><strong>Electron</strong></h4><ul><li>Switch added on the GUI to opt out of being a provider</li><li>Port warnings added on footer status bar</li><li>Header style on preview screen fixed (for Windows users)</li><li>Copying subtask id is possible on preview screen</li><li>Estimation logic implemented for computed tasks in task list</li><li>Maximum balance validation implemented on withdraw form</li><li>Golem sync status message added into footer status bar</li><li>Insufficient balance warning while restarting task</li><li>UX updates and responsiveness</li></ul><h3>Upgrading to Brass Golem Beta 0.15.1</h3><p>You can find detailed information here:</p><ul><li><strong>macOS</strong></li></ul><pre>brew update<br>brew upgrade golem<br>brew cask upgrade golem</pre><pre>sudo chown root:wheel $(brew<strong> </strong>--prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve<strong><br></strong>sudo chmod u+s $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve</pre><ul><li><strong>Ubuntu<br></strong>Download the installation script from <a href="https://raw.githubusercontent.com/golemfactory/golem/develop/Installer/Installer_Linux/install.sh">here</a>. In terminal, run <br>chmod +x install.sh &amp;&amp; ./install.sh.</li><li><strong>Windows<br></strong>Download and execute the installer from <a href="https://github.com/golemfactory/golem/releases/download/0.15.1/golem-0.15.1-windows.exe">here</a>.</li></ul><p>If you encounter any errors please let us know on testers channel at <a href="https://chat.golem.network/home">chat.golem.network</a> or write an email to contact@golem.network.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f43a7e3f5f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/golem-project/brass-golem-beta-0-15-1-7f43a7e3f5f5">Brass Golem Beta 0.15.1</a> was originally published in <a href="https://medium.com/golem-project">The Golem Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brass Golem Alpha2 0.14.0]]></title>
            <link>https://medium.com/golem-project/brass-golem-alpha2-0-14-0-182db913ed3e?source=rss-32f833fb6dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/182db913ed3e</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[golem-project]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[dapps]]></category>
            <dc:creator><![CDATA[Aleksandra Skrzypczak]]></dc:creator>
            <pubDate>Tue, 27 Mar 2018 13:31:55 GMT</pubDate>
            <atom:updated>2018-03-27T13:31:55.477Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CEbkBCqKSKEMrurf1TqWQA.jpeg" /></figure><p>We are very pleased to announce the new release of Golem 0.14.0. This release adds password management for unlocking Golem accounts and several other features that will be needed for the upcoming switch to mainnet. Also worth mentioning, are the updates in the GUI.</p><p>As usual, we encourage you to follow the progress of our project on the Golem <a href="https://trello.com/b/YL1qZ2pZ/brass-kanban">Kanban</a>, download and test this latest release, as well as provide us with feedback, so that we can keep improving Golem. For more details and troubleshooting, please visit the <a href="https://github.com/golemfactory/golem">official GitHub repository</a>.</p><p>More detailed changelog:</p><h4>Core</h4><ul><li>Password is now required to unlock Golem service</li><li>Term-of-use added (temporarily disabled)</li><li>Websocket encryption</li><li>(Anti-sybil) Key difficulty checks added to task session</li><li>— mainnet flag added</li><li>Blender verification is now called sequentially</li><li>Better address management in HyperG</li><li>Decrease reputation when requestor is not paying for computation</li><li>Lock funds after requesting task</li><li>Sentry integration added</li><li>Bugfixes and optimizations</li></ul><p>Concent:</p><ul><li>— concent flag added</li><li>support for ForceReportComputedTaskResponse, ForceSubtaskResults, ForceSubtaskResulstsRejection, ForceGetTaskResult, ForceGetTaskResultFailed</li><li>FileTransferToken improvements</li></ul><h4>Electron</h4><ul><li>Wallet implementation</li><li>Password protection implementation</li><li>Secure websocket connection activated</li><li>New onboarding elements and navigations</li><li>Terms of Usage added</li><li>Task Settings screen updated</li><li>More information tooltips about sections</li><li>Critical warnings</li><li>Design updates &amp; UX improvements</li></ul><h3>Upgrading to Brass Golem Alpha2 0.14.0</h3><p>You can the find detailed information here:</p><ul><li><strong>macOS</strong></li></ul><pre>brew update<br>brew upgrade golem<br>brew cask upgrade golem</pre><pre>sudo chown root:wheel $(brew<strong> </strong>--prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve<strong><br></strong>sudo chmod u+s $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve</pre><ul><li><strong>Ubuntu<br></strong>Download the installation script from <a href="https://raw.githubusercontent.com/golemfactory/golem/develop/Installer/Installer_Linux/install.sh">here</a>. In terminal, run <br>chmod +x install.sh &amp;&amp; ./install.sh.</li><li><strong>Windows<br></strong>Download and execute the installer from <a href="https://github.com/golemfactory/golem/releases/download/0.14.0/golem-0.14.0-windows.exe">here</a>.</li></ul><p>If you encounter any errors please let us know on testers channel at <a href="https://chat.golem.network/home">chat.golem.network</a> or write an email to contact@golem.network.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=182db913ed3e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/golem-project/brass-golem-alpha2-0-14-0-182db913ed3e">Brass Golem Alpha2 0.14.0</a> was originally published in <a href="https://medium.com/golem-project">The Golem Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brass Golem Alpha2 0.13.0]]></title>
            <link>https://medium.com/golem-project/brass-golem-alpha2-0-13-0-10f502a558ee?source=rss-32f833fb6dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/10f502a558ee</guid>
            <category><![CDATA[golem]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[golem-project]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Aleksandra Skrzypczak]]></dc:creator>
            <pubDate>Wed, 14 Mar 2018 11:05:52 GMT</pubDate>
            <atom:updated>2018-03-14T11:05:52.229Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*IhN9pPFSWwFWBa4TBGBLqw.jpeg" /><figcaption>Rubber duck debugging is commonly used by Golem devs.</figcaption></figure><p>We are happy to announce the new release of Golem 0.13.0. This releases supports new version of Golem payment contracts and contains several protocol improvements. And general bugfixing.</p><p>As usual we encourage you to follow the progress of our project on Golem <a href="https://trello.com/b/YL1qZ2pZ/brass-kanban">Kanban</a>, download and test the newest release, as well as provide us with feedback, so that we can keep improving Golem. For more details and troubleshooting, please visit the <a href="https://github.com/golemfactory/golem">official GitHub repository</a>.</p><p>More detailed changelog:</p><h4><strong>Core</strong></h4><ul><li>New version of contracts connected with golem</li><li>Blender version updated to 2.79</li><li>Only task owner can now broadcast task cancellation to the network</li><li>Increased key difficulty built up in public key</li><li>Key difficulty is now also checked in task session</li><li>Simplified subtask definition sent to provider</li><li>Modification in hello message handling</li><li>Additional subtask status “verifying”added</li><li>Address list generation refactored</li><li>Tuned verification function</li><li>Information about user caps displayed in logs</li><li>Warning about desynchronized clock is displayed in log</li></ul><p>Concent:</p><ul><li>Support for TransferRateFailure to request Concent’s forced download</li><li>ForceReportComputeTask message is properly handled</li></ul><h4>Electron</h4><ul><li>Minimum application size re-defined</li><li>Multiple instance problem fixed on Windows</li><li>Application log path changed as the default golem log path</li><li>GUI version information added</li><li>RPC communication fixes and improvements</li><li>UX Fixes</li><li>Minor design updates</li></ul><h3>Upgrading to Brass Golem Alpha2 0.13.0</h3><p>You can find detailed information here:</p><ul><li><strong>macOS</strong></li></ul><pre>brew update<br>brew upgrade golem<br>brew cask upgrade golem</pre><pre>sudo chown root:wheel $(brew<strong> </strong>--prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve<strong><br></strong>sudo chmod u+s $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve</pre><ul><li><strong>Ubuntu<br></strong>Download the installation script from <a href="https://raw.githubusercontent.com/golemfactory/golem/develop/Installer/Installer_Linux/install.sh">here</a>. In terminal, run <br>chmod +x install.sh &amp;&amp; ./install.sh.</li><li><strong>Windows<br></strong>Download and execute the installer from <a href="https://github.com/golemfactory/golem/releases/download/0.13.0/golem-0.13.0-windows.exe">here</a>.</li></ul><p>If you encounter any errors please let us know on testers channel at <a href="https://chat.golem.network/home">chat.golem.network</a> or write an email to contact@golem.network.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10f502a558ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/golem-project/brass-golem-alpha2-0-13-0-10f502a558ee">Brass Golem Alpha2 0.13.0</a> was originally published in <a href="https://medium.com/golem-project">The Golem Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brass Golem Alpha2 0.10.0]]></title>
            <link>https://medium.com/golem-project/brass-golem-alpha2-0-10-0-d397ea605f00?source=rss-32f833fb6dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d397ea605f00</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[golem]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[bras]]></category>
            <dc:creator><![CDATA[Aleksandra Skrzypczak]]></dc:creator>
            <pubDate>Wed, 20 Dec 2017 14:22:15 GMT</pubDate>
            <atom:updated>2017-12-20T18:59:03.772Z</atom:updated>
            <content:encoded><![CDATA[<p>We are pleased to announce the next major release which contains a few long-awaited features and protocol optimizations.</p><p>With this new version users can observe their incomes displayed in the GUI and check how many test GNT they have earned for each subtask by sharing their machine’s computing power.</p><p>Tasks persistance is turned on by default, so restarting Golem will not require restarting all computations that someone has requested.</p><p>Improvements in the protocol should make Golem network more scalable and find other nodes quicker.</p><p>As usual, we encourage you to test our upgraded Alpha2 version and provide us with feedback. For more details and troubleshooting, please visit <a href="https://github.com/golemfactory/golem">the official GitHub repository</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OqSMzq5aX9iruIburqZ-cw.jpeg" /><figcaption>Blender<a href="https://svn.blender.org/svnroot/bf-blender/trunk/lib/benchmarks/cycles/barbershop_interior/"> barbershop_interior</a> benchmark rendered with Golem</figcaption></figure><h3><strong>Changelog</strong></h3><h4>Tasks</h4><ul><li>Task persistence implemented. Tasks are revived after Golem is restarted.</li></ul><h4>Protocol</h4><ul><li>Handshake protocol is improved.</li><li>Golem messages are moved to external module and refactored.</li><li>Task-related messages are saved for Concent service.</li><li>Additional message for communication with Concent are added.</li><li>Bootstrap choosing mechanism is improved.</li><li>Additional bootstrap nodes with lighter protocol (implemented in Golang) are added to Golem network.</li></ul><h4>Payments</h4><ul><li>Incomes are now properly matched with proper tasks and displayed in GUI.</li></ul><h4>Computations</h4><ul><li>Docker recovery mechanism improved.</li><li>Old computation related data are now regularly cleaned.</li></ul><h4>Electron (GUI)</h4><ul><li>Major dependencies are upgraded for security and performance reasons.</li><li>Application size is reduced approx. 10 percent.</li><li>Input validation behaviours are improved.</li><li>Reported and known issues are solved.</li></ul><h3><strong>Upgrading to Golem Alpha2 0.10.0</strong></h3><ul><li><strong>macOS</strong></li></ul><pre>brew tap caskroom/cask<br>brew upgrade golem<br>brew cask install golem</pre><pre>sudo chown root:wheel $(brew<strong> --</strong>prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve<strong><br></strong>sudo chmod u+s $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve</pre><ul><li><strong>Ubuntu<br></strong>Download the installation script from <a href="https://raw.githubusercontent.com/golemfactory/golem/develop/Installer/Installer_Linux/install.sh">here</a>. In terminal, run <br>chmod +x install.sh &amp;&amp; ./install.sh.</li><li><strong>Windows<br></strong>Download and execute the installer from <a href="https://github.com/golemfactory/golem/releases/download/0.10.0/Golem_win_0.10.0.exe">here</a>.</li></ul><p>If you encounter any errors please let us know on testers channel at <a href="https://chat.golem.network/home">chat.golem.network</a> or write an email to tech@golem.network.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d397ea605f00" width="1" height="1" alt=""><hr><p><a href="https://medium.com/golem-project/brass-golem-alpha2-0-10-0-d397ea605f00">Brass Golem Alpha2 0.10.0</a> was originally published in <a href="https://medium.com/golem-project">The Golem Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Golem Crowdfunding — Summary]]></title>
            <link>https://medium.com/golem-project/the-golem-crowdfunding-summary-8a3504375aa7?source=rss-32f833fb6dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a3504375aa7</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[crowdfunding]]></category>
            <dc:creator><![CDATA[Aleksandra Skrzypczak]]></dc:creator>
            <pubDate>Thu, 24 Nov 2016 18:15:42 GMT</pubDate>
            <atom:updated>2016-11-25T10:33:54.361Z</atom:updated>
            <content:encoded><![CDATA[<p>On November 11, while the rest of our nation was celebrating National Independence Day in Poland, the entire Golem team was at their computers, hard at work.</p><p>After weeks of planning, chatting with bloggers, communicating with the community, and coding, we were finally ready to launch the Golem crowdfunding event and really see if our mission resonated with the people we’re building it for.</p><p>Everyone was nervous. The question of whether or not we would even it our minimum was being discusses, beside cautious hopes that we’d hit our maximum in the first day.</p><p>This is a short recap of how we prepared, how it went down, and what we’ll be doing next.</p><h3>Preparation</h3><p>Our main principle was simple: full transparency. Publish early, answer questions, take feedback into account.</p><p>Following that, we had three main things to prepare:</p><ol><li>Whitepaper and Communications</li></ol><p>We published our draft version of the Golem whitepaper early, wrote <a href="https://blog.golemproject.net/the-economics-of-the-golem-network-token-d64c1a50b1d5">blogpost</a> explaining the design elements and economics of the Golem Network Token, and tried to communicate our plans, visions and <a href="https://blog.golemproject.net/why-no-fee-45a9496b033e">ideas</a> to the community as clearly as possible. We wanted it to be clear that the whole amount of collected ETH would be used following the budget plan in the whitepaper and that the GNT that was assigned to the Golem Factory would be used to finance the project until Iron Golem was live.</p><p>After listening to <a href="https://www.reddit.com/r/ethereum/comments/58ndzx/golem_crowdfunding_whitepaper_release_candidate/">community feedback</a> on the draft, we iterated the whitepaper to address thoughts &amp; concerns, and published the release version.</p><p>2. Smart contract</p><p>Writing a token contract itself should be simple — <a href="https://blog.golemproject.net/gnt-crowdfunding-contract-in-pictures-d6b5a2e69150">it wasn’t</a>.</p><p>Keeping in mind problems with The DAO, we decided to keep contract as simple as possible, having only necessary features and an additional migration mechanism that will allow us to add new features in the future.</p><p>At the community’s request, we put a timelock on developers’ tokens.</p><p>The token contract was intensively tested with unittest, and via test scenarios on Morden (testnet) and mainnet. There were also two external audits run by Jordi Baylina and <a href="https://medium.com/zeppelin-blog/golem-network-token-gnt-audit-edfa4a45bc32">Zeppelin</a>.</p><p>3. User instruction</p><p>We wanted the process of obtaining GNT to be as easy and as safe as possible. To this end we…</p><ul><li>Added additional data to the contract as a safety measure to protect users from sending ETH directly from exchanges that don’t support smart contracts.</li><li>Created two separate guides. The first one for current desktop clients (Mist / EthereWallet / Parity) and the second one for the best “light wallet” available in Ethereum — <a href="https://www.myetherwallet.com/">MyEtherWallet</a>. We tested the instructions with non-technical users who didn’t have experience with Ethereum to make sure that the provided guides were easily understandable.</li></ul><p>We’ve heard that some users may have problems with syncing desktop wallets. It’s still a time-consuming process that requires a good bandwidth, high uptime, and a lot of a disk space.</p><p>Therefore we recommended MyEtherWallet (MEW) as a preferred solution for non-experienced users. Usually it works like charm, is secure and easy to use.</p><h3>Crowdfunding</h3><p>We published the contract code around 18 hours before the crowdfunding block. MyEtherWallet developers added an autofill for the contract address to make the process easier for users, doubled the size of their nodes and increased the gas price to ensure the transactions get mined. The MetaMask team also contacted us to run some test with golem contract.</p><p>We had a full 3-weeks schedule of 4-hour shifts to make sure there would always be at least one team member monitoring progress, answering user questions, solving problems, etc… but everyone wanted to be there to see the countdown timer to start hit zero.</p><p>We prepared a “control room” in our conference room with a golem website displayed on a huge monitor and sit around it with laptops waiting for the starting block and listening to <a href="https://www.youtube.com/watch?v=9jK-NcRmVcw">“The Final Countdown”</a>. Team members from London to Thailand to Taipei were live with us.</p><p>In the first minute, the minimum cap was reached. We watched it happen &amp; keep climbing with a mix of joy, amazement, and disbelief.</p><p>Then the problems started.</p><p>The slack and reddit post got flooded with comments about MEW ot working. Our simple, read-only, site become heavily overloaded too. We realized that the attention to our crowdfunding must be unintentially DDoSing our site and MEW’s servers. We <a href="https://www.reddit.com/r/ethereum/comments/5e3alw/massive_myetherwalletcom_update_better_uris_the/">found out</a> later from Taylor that the main problem was in the number of json requests (200/s) which simply couldn’t be processed by parity working on the MEW backend.</p><p>29 minutes into the crowdfunding, the max cap was reached. We’d succeded at the level of our most optimistic hopes.</p><p>It probably would have finished sooner if MEW hadn’t been flooded with all the requests (due to the contract construction additional transactions were required to exactly match the cap). We ran finalize functions from our control room, creating additional tokens for Golem Factory and the team and enabling users to transfer their token.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uCV6iIZRfwILc7Su." /><figcaption><em>“Control room”, first minutes after the crowdfunding started</em></figcaption></figure><h3>…and it’s gone</h3><p>We honestly did not expect that the crowdfunding would end so quickly, so we want to say sorry to all users that wanted to take part and didn’t succeeded. We should have known better, but things like that are really hard to predict.</p><p>Some people accuse MEW of not being prepared, which is unfair (and wrong). Tayvano and kvhnuk are doing amazing job for the community, delivering their great software for free, based only on donations. They also <a href="https://www.reddit.com/r/ethereum/comments/5cf7qd/golem_ico_and_myetherwallet/d9w10s9/">prepared themselves</a> really carefully, and couldn’t have predicted the record number of people interested in the crowdfunding event.</p><p>It was our mis-step to point to a centralized solution as a recommended method, and we should have prepared more backup plans in our guides. Once again, we want to apologize the MEW team and all the users who didn’t manage to buy tokens during the crowdfunding.</p><p>Still — if it wasn’t for MEW, there would definitely be other issues. Maybe our site would crash (which it did, for short periods), maybe miners would stop processing transaction on time or just process only those with skyrocketed gas price.</p><p>When demand exceeds supply, there will be people who cannot get access to the thing in demand. With crowdfunding, it’s difficult to find the right spot between fairness, simplicity, and safety.</p><p>If you still want to own some GNT, you can purchase it from other users. We believe that token value should come from the value in the application and from Golem app itself, not from speculation. That’s the main reason why we haven’t decide to ask exchanges for adding tokens to their portfolio. But we never planned to hinder token transfers and we don’t mind exchanges integrating GNT.</p><p>EtherDelta prepared a GNT wrapper that allows <a href="https://www.reddit.com/r/ethereum/comments/5cs2n4/erc20compliant_wrapper_token_for_gnt_will_enable/">trading GNT</a>. A few users implemented their own smart contracts for selling GNT with a set price. GNT can be also traded on <a href="https://twitter.com/gparalikidis/status/798129796509237248">Liqui exchange</a> and <a href="https://twitter.com/yunbicom/status/798915836920492032">Yunbi</a>.</p><h3>Thank you</h3><p>We would like to thank all the people who took part in the crowdfunding, and express our gratitude to all of you who made it possible and supported us in our preparations with advice and motivation.</p><p>Especially we would like to thank:</p><ul><li>Taylor Van Orden &amp; MEW team for doing an amazing job with their light wallet, their involvement and all-nighters before the crowdfunding and preparation of great <a href="https://www.reddit.com/r/ethereum/comments/5e3alw/massive_myetherwalletcom_update_better_uris_the/">post-crowdfunding analyses</a>.</li><li>Patricio Worthalter from Milliwatt &amp; his team for being a huge and important part of our testnet from the very beginning.</li><li>Ksenya Bellman from World Crypto Network for hosting an youtube AMA with Golem team twice.</li><li>Jordi Baylina and Zeppelin (Manuel Aráoz and Demian Brener) for running audits.</li><li>Aaron Davis &amp; Metamask team for doing great job with their software and running the Metamask tests with our contract.</li><li>The Ethereum developers for creating the platform with which all of this is possible. And the whole Ethereum community for support, great advice, and warm reception during three devcons.</li><li>Chris Remus for great <a href="https://hackernoon.com/heres-how-i-m-participating-in-golem-s-crowdfunding-process-part-1-56eaeada392d">medium </a>posts about preparation to participate in golem crowdfunding.</li><li>Daniel Zakrisson for preparing a great crowdfunding <a href="https://medium.com/@danielzakrisson/the-crowdsale-analyst-preliminary-thoughts-9c764a13a9d2">preeliminary analysis</a> and the <a href="https://keepingstock.net/the-crowdsale-analyst-golem-final-thoughts-eaf65d80d472">final thoughts</a> and also Jake Lanor for critical but also <a href="https://medium.com/@jakelanor/considerations-against-the-golem-crowdsale-758c9f5008be">insightful analysis</a> .</li><li>Our slack community for high quality responses and communication during pre-crowdfunding phase</li></ul><h3>Future plans</h3><p>We’ve been a bit quiet recently because we are really busy with preparing a detailed work plan, organizing a workflow, recruitment, and governance of the Golem Factory. We still want to keep transparency rule so we will keep you posted with our development plans and new implemented features. We would like to slightly limit the time we spend on slack, so we encourage users to use our <a href="https://www.reddit.com/r/GolemProject/">reddit</a> as the preferable communication channel.</p><p>We still want to encourage you to join our <a href="https://github.com/imapp-pl/golem">testnet</a>. <a href="https://github.com/imapp-pl/golem/wiki/Command-Line">Console interface</a> is now available.</p><p>We also want to welcome a new scientist in our team, laureate of “TOP500 Innovators” program at the University of California, Berkley, Grzegorz Borowik Ph. D. He’s an optimization expert, author and co-author of over 80 publications. We really hope that he’ll help use with creation of efficient algorithms for Golem.</p><h3>Join our team</h3><p>We’re still looking for brilliant developers ready to learn new technologies and create Golem with us. If you have experience with any of the technologies that we’re using and if you want to create golem computer with us — send us an email to <a href="/service/mailto:contact@golemproject.net">contact@golemproject.net.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a3504375aa7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/golem-project/the-golem-crowdfunding-summary-8a3504375aa7">The Golem Crowdfunding — Summary</a> was originally published in <a href="https://medium.com/golem-project">The Golem Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Golem architecture]]></title>
            <link>https://medium.com/golem-project/golem-architecture-bfd75faa8ecc?source=rss-32f833fb6dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfd75faa8ecc</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ipfs]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Aleksandra Skrzypczak]]></dc:creator>
            <pubDate>Tue, 07 Jun 2016 15:36:32 GMT</pubDate>
            <atom:updated>2016-06-07T15:37:32.513Z</atom:updated>
            <content:encoded><![CDATA[<p>So, how exactly does Golem work? To get an idea, let’s go through the computing task process.</p><p>Everything begins when a requestor needs to compute a task using the Golem network. It may be a CGI artist who has just finished working on an animation and wants to render it in high quality or a data scientist who wants to train her machine learning algorithm.</p><p>If the requestor’s task belongs to a class already implemented in Golem, she may use one of the task templates from the task collection. <strong>The task template </strong>contains the full computational logic. It has the source code that should be run, knows how to split the task into subtasks that are sent to different nodes, how to verify results and put them together as the final result. Right now, the task collection is just a set of available <strong>task templates </strong>(Blender and Luxrender rendering in Brass Golem), but later on it will transform into Golem Shop, where users will be able to add and download new use cases.</p><p>If the user’s task is something more specific, which isn’t available in the <strong>task collection,</strong> she would have to write her own code using the <strong>task definition framework. </strong>In Brass and Clay Golem, only the closed task collection will be available (effectively limiting the use cases to those preprogrammed by us). The task definition framework will be introduced in Stone Golem. It is a generic template providing public interface which allows users to create new types of tasks by implementing their own task templates. These can be stored locally and be used exclusively by the creator or they can be submitted to Golem Shop.</p><p>Once the requestor chooses the task template and defines a new task, it is added to the <strong>task manager</strong>, which<strong> </strong>keeps track of all tasks that have been requested from this node. Then information about the new tasks<strong> </strong>is broadcasted to<strong> </strong>the Golem network.</p><p>The provider’s<strong> transaction system </strong>collects all broadcasted offers and chooses the best ones. It checks the reputation of each node in the <strong>reputation system </strong>and rejects offers from nodes with poor reputation. Then, the provider’s Golem connects with the requestor’s node and submits an offer with a price and information about the machine’s capabilities (performance, available cores, etc.). The requestor’s transaction system checks the provider’s reputation and rejects offers from providers with poor reputation. If the task manager decides that there’s a subtask fitting one of the submitted offers, then a list of resources that should be downloaded via <a href="https://ipfs.io/"><strong>IPFS</strong></a><strong> </strong>is sent to the provider.</p><p>After all resources are pulled into the provider’s machine, the <strong>task computer </strong>(on the provider’s machine) can finally start computing.</p><p><strong>The task computer</strong> is responsible for running and managing the computation. It can start a <a href="https://www.docker.com/"><strong>Docker</strong></a><strong> </strong>container, where the proper source code will be executed, it also checks for errors or timeouts. In the future, it may run on a Virtual Machine (slow but secure) or run the code directly on the host machine (quick but insecure). Of course, the second option will only be used in a very specific scenario and providers will only run code from well-checked, secure tasks from the task collection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/807/1*b6_nogTIJJpPHrJRmOo4LA.png" /></figure><p>Once the computation is finished, its results and logs are sent back to the requestor via the IPFS network. The task manager passes them to the task template for verification. It can be different for every task type. The most popular one is based on redundancy. Some subtasks may be sent to more than one node (the requestor may decide how often and to how many) and their results will be compared. In some cases, it won’t be necessary because verification will be simple — if the task itself is Proof of Work of some kind. Another requestor may be able to compute a random, smaller part of the task and compare it with the result. For example, in the case of rendering it is possible to render some pixels locally and compare their colour with those from the received image. Sometimes a combination of all these method may work.</p><p>When the result passes the verification stage, a new due payment is notified to the <strong>payment system</strong>, which<strong> </strong>sends the right amount of ethers to the <a href="https://www.ethereum.org/"><strong>Ethereum</strong></a> contract. Check our previous post to see how it’s implemented and why we’ve decided to use <a href="https://blog.golemproject.net/why-ethereum-b398df34df9b#.o6l7tbitd">Ethereum</a>. Simultaneously, the provider’s reputation level rises in the requestor’s reputation system (and decreases if the result doesn’t pass the verification). The reputation decline will be lower if the provider sends information about errors during the computation or doesn’t send results at all (in most cases, this would be due to technical problems) and much higher if the result is wrong.</p><p>The provider’s payment system monitors the Ethereum blockchain and timeliness of payment. If it’s late the requestor’s reputation gets significantly lower. The reputation system keeps track of all positive and negative interactions with other nodes and uses it to compute a local rank. There are two separate rankings: one for providers and another for requestors. The system exchanges information about these ranks using a differential gossiping algorithm, causing the reputation vector converge to a real global value. The implementation of an efficient reputation system is not easy, but constitutes one of the most important challenges within the project. In the future, we plan to add yet another mechanism to it — a sort of synchronization with some form of Ethereum-based reputation systems, depending on their actual development within the Ethereum ecosystem.</p><p>Of course this is just the tip of the iceberg and a glimpse of typical workflow within Golem. In the future, we’ll provide detailed descriptions of other systems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfd75faa8ecc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/golem-project/golem-architecture-bfd75faa8ecc">Golem architecture</a> was originally published in <a href="https://medium.com/golem-project">The Golem Project</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>