<?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 Gulden on Medium]]></title>
        <description><![CDATA[Stories by Gulden on Medium]]></description>
        <link>https://medium.com/@gulden?source=rss-d5a05e1ca811------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Yy4R56E2K04q1TfZgCjvfg.png</url>
            <title>Stories by Gulden on Medium</title>
            <link>https://medium.com/@gulden?source=rss-d5a05e1ca811------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 00:36:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gulden/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[NFT’s op de Gulden blockchain]]></title>
            <link>https://gulden.medium.com/nfts-op-de-gulden-blockchain-ec3be07e5086?source=rss-d5a05e1ca811------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec3be07e5086</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[gulden]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Gulden]]></dc:creator>
            <pubDate>Wed, 10 Mar 2021 15:37:21 GMT</pubDate>
            <atom:updated>2021-03-10T15:37:21.504Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r7YgDJN_1nsme8AKfN2DIA.png" /></figure><h3><strong>Wat is een NFT (Non-Fungible Token)</strong></h3><p><strong>A</strong><br>Je verzamelt smurfen… Er komt een gelimiteerde smurf uit, 10 stuks. Heel exclusief dus. Bij deze smurf zit een certificaat. Op het certificaat staat welke van de 10 je hebt. Je koopt nr. 2 van 10. Andere mensen willen deze ook wel hebben, dus bieden je geld ervoor.</p><p>Dit lijkt me heel duidelijk en nu wordt het interessant… Want dit is een NFT:</p><p><strong>B</strong><br>Je verzamelt digitale smurfen. Er komt een digitale smurf uit, onbeperkt aantal. Iedereen kan de smurf bekijken/opslaan/delen. Er komen naast de digitale smurf 10 digitale certificaten uit. Op het certificaat staat een verwijzing naar de digitale smurf, een link bijvoorbeeld. Daarnaast staat op het certificaat welke van de 10 je hebt. Je koopt nr. 2 van 10.</p><p>Het digitale certificaat is de NFT.</p><p>Bij A. is de waarde gebaseerd op hoeveel smurfen er zijn. Bij B. is de waarde gebaseerd op hoeveel certificaten er zijn. Dat is natuurlijk heel erg vreemd… alhoewel. Waarom is dat certificaat dan zoveel waard, als het niet meer om het item gaat waar het certificaat naar verwijst. Het item is namelijk niet schaars. Iedereen kan de digitale smurf hebben. Daarvoor moeten we kijken naar waar het certificaat vandaan komt… namelijk van de uitgever van de digitale smurf. De bron.</p><p>Stel er komt een digitale smurf uit en een willekeurig iemand hangt daar een digitaal certificaat aan. Er zal niemand zijn die daar voor wil betalen. Echter, als de uitgever van de digitale smurf het certificaat uitbrengt willen mensen er wel voor betalen.</p><p>Stel jij geeft een digitaal certificaat uit van een tweet geplaatst door de oprichter van Twitter… Zou iemand daar geld voor over hebben? Waarschijnlijk niet. Maar stel de oprichter van Twitter geeft een digitaal certificaat uit voor een door hem geplaatste tweet…</p><p>Wat is het verschil? Simpel, de waarde ontstaat bij de bron. Het enige wat relevant is, is wie het certificaat uit geeft.</p><p>Stel je koopt een boek in de winkel, iedereen kan dat boek kopen. Het wordt onbeperkt uitgegeven. Maar nu geeft de schrijver een boekpresentatie. Na afloop staat er een rij bij de schrijver, mensen hebben het boek in handen en willen iets van de schrijver. Wat willen ze? Een handtekening in het boek… En nu opeens is jouw boek gelimiteerd. De schrijver heeft namelijk een handtekening erin gezet. Is het boek nu anders? Is de inhoud anders? Nee. Het is hetzelfde boek wat iedereen heeft, maar die van jou heeft een handtekening erin.</p><p>Het lijkt op wat een NFT is, maar bij een NFT zet de schrijver de handtekening op een apart blaadje, niet eens in jouw boek. Dus jouw boek blijft hetzelfde boek wat alle andere mensen hebben. Maar jij hebt het aparte blaadje met de handtekening.</p><p>En waarom is dat blaadje dan wat waard? Omdat de handtekening van de schrijver is. En dat blaadje kan je doorverkopen. Zonder boek.</p><h3><strong>Wat gaat Gulden doen?</strong></h3><p>Gulden gaat terug naar de essentie van de NFT, waardoor het voor iedereen makkelijk te begrijpen zal zijn en vooral makkelijk te gebruiken. Zowel het creëren als het verhandelen. Wij gaan dit op een manier toepassen die uniek is, maar tegelijk ongelooflijk logisch. De kracht zit in de simpliciteit ervan. Daarnaast is er gekozen voor deze ontwikkeling, omdat er een heel groot marketing onderdeel in zit. We hebben natuurlijk jaren gewerkt aan de techniek en nu is het tijd voor marketing. Bij dit project raken we beide vlakken. Niet eens zozeer vanwege de “NFT hype”, maar doordat het onderdeel promotie er al automatisch in zit. Dat zal natuurlijk een stuk duidelijker worden zodra we meer bekend maken over deze toepassing.</p><p>Gulden is door de jaren ontwikkeld met het oog op dit soort ontwikkelingen, zonder dat we wisten wat die ontwikkelingen zouden zijn. Onder de motorkap zijn het transacties, is het blockchain. Dat betekent dat Gulden hier absoluut perfect voor is, dat de manier waarop wij het gaan implementeren ongelooflijk efficient is. Het is alsof onze blockchain maatwerk zijn voor iets waar we de maten nog niet van wisten. Wat betekent dat concreet:</p><p><strong>Fase 1 — Duur: 2 maanden</strong><br>De ontwikkeling aan de Gulden Core.</p><p><strong>Fase 2 — Duur: 1.5 maand (start tegelijk met Core ontwikkeling)</strong><br>Het UI gedeelte van de Gulden app. De “NFT” functionaliteit zal worden geïntroduceerd in de Gulden LITE app, maar ook in een nieuwe specifiek hiervoor ontwikkelde applicatie. Deze applicatie plaatst Gulden op de achtergrond en de “NFT” functionaliteit op de voorgrond.</p><p><strong>Fase 3 — Duur 3 maanden (start tegelijk met Core ontwikkeling)</strong><br>Ontwikkeling van de decentrale handelsmarkt voor de Gulden “NFT’s”. Vergelijkbaar met een DEX, maar efficiënter en specifiek gericht op het verhandelen van “NFT’s” in de apps. Deze handelsmarkt zal decentraal zijn waar nodig en centraal waar dat voor efficiëntie kan zorgen. Een hybride vorm dus.</p><p>De ontwikkeling start na Witness Sync (binnenkort testen) en zal dus in totaal zo’n 3 maanden in beslag nemen. Zodra Fase 1 en 2 klaar zijn kan er al grootschalig worden getest.</p><p>In overleg met de GAB is besloten dat dit project na Witness Sync de hoogste prioriteit krijgt ivm de ontwikkelingen in de markt en de kracht van het concept. Dat is ook de reden dat we nog niet veel bekend maken over wat het nu precies zal zijn. Zodra we al ver in de ontwikkeling zijn zal dat wel gebeuren.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec3be07e5086" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NFTs on the Gulden blockchain]]></title>
            <link>https://gulden.medium.com/nfts-on-the-gulden-blockchain-4569aa4061d9?source=rss-d5a05e1ca811------2</link>
            <guid isPermaLink="false">https://medium.com/p/4569aa4061d9</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[gulden]]></category>
            <dc:creator><![CDATA[Gulden]]></dc:creator>
            <pubDate>Wed, 10 Mar 2021 15:37:17 GMT</pubDate>
            <atom:updated>2021-03-10T15:37:17.284Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r7YgDJN_1nsme8AKfN2DIA.png" /></figure><h3><strong>What is a NFT (Non-Fungible Token)</strong></h3><p><strong>A</strong><br>You collect smurfs… A limited edition smurf comes out, 10 pieces. Very exclusive. With this smurf comes a certificate. The certificate says which of the 10 you have. You buy no. 2 of 10. Other people want this one too, so you offer money for it.</p><p>This seems very clear to me and now it gets interesting… Because this is a NFT:</p><p><strong>B</strong><br>You collect digital smurfs. A digital smurf comes out, unlimited number. Anyone can view/save/share the smurf. 10 digital certificates come out in addition to the digital smurf. On the certificate there is a reference to the digital smurf, a link for example. In addition, the certificate says which of the 10 you have. You buy no. 2 of 10.</p><p>The digital certificate is the NFT.</p><p>With A., the value is based on how many smurfs there are. With B., the value is based on how many certificates there are. This is, of course, very strange… though. So why is that certificate worth so much, if it is no longer about the item the certificate refers to. After all, the item is not scarce. Anyone can have the digital smurf. For that, we need to look at where the certificate comes from… namely, from the publisher of the digital smurf. The source.</p><p>Suppose a digital smurf comes out and some random person attaches a digital certificate to it. There won’t be anyone who wants to pay for that. However, if the publisher of the digital smurf issues the certificate, people do want to pay for it.</p><p>Suppose you issue a digital certificate of a tweet posted by the founder of Twitter… Would anyone be willing to pay money for that? Probably not. But suppose the founder of Twitter issues a digital certificate for a tweet posted by him….</p><p>What’s the difference? Simple, the value arises at the source. The only thing relevant is who issues the certificate.</p><p>Suppose you buy a book in the store, anyone can buy that book. It is issued without limitation. But now the author gives a book presentation. Afterwards there is a queue at the writer’s desk, people have the book in their hands and want something from the writer. What do they want? A signature in the book… And now suddenly your book is limited. Because the writer has put a signature in it. Is the book different now? Is the content different? No. It’s the same book that everybody has, but yours has a signature in it.</p><p>It’s similar to what a NFT is, but with a NFT, the writer puts the signature on a separate piece of paper, not even in your book. So your book remains the same book that everyone else has. But you have the separate piece of paper with the signature.</p><p>So why is that signed piece of paper worth anything? Because the signature is from the author. And you can resell that signed piece of paper. Without a book.</p><h3><strong>What will Gulden do?</strong></h3><p>Gulden goes back to the essence of the NFT, which will make it easy to understand for everyone and especially easy to use. Both creating and trading. We are going to apply this in a way that is unique, but at the same time incredibly logical. The power lies in its simplicity. In addition, this development was chosen because it has a very large marketing component. Of course, we’ve been working on the technology for years and now it’s time for marketing. With this project we hit both. Not even so much because of the “NFT hype”, but because the promotion component is already automatically included. Of course, that will become a lot clearer once we announce more about this application.</p><p>Gulden has been developed over the years with this kind of development in mind, without us knowing what those developments would be. Under the hood it is transactions, it is blockchain. That means that Gulden is absolutely perfect for this, that the way we are going to implement it is incredibly efficient. It’s like our blockchain is tailor made for something we didn’t know the sizes of yet. What does that mean specifically:</p><p><strong>Phase 1 — Duration: 2 months</strong><br>The development on the Gulden Core.</p><p><strong>Phase 2 — Duration: 1.5 months (starts simultaneously with Core development)</strong><br>The UI part of the Gulden app. The “NFT” functionality will be introduced in the Gulden LITE app, but also in a new application developed specifically for this purpose. This application will place Gulden in the background and the “NFT” functionality in the foreground.</p><p><strong>Phase 3 — Duration 3 months (starts simultaneously with Core development)</strong><br>Development of the decentralized trading market for the Gulden “NFTs”. Similar to a DEX, but more efficient and specifically aimed at trading “NFTs” in the apps. This trading market will be decentralized where needed and centralized where it can provide efficiency. In other words, a hybrid form.</p><p>Development will start after Witness Sync (testing next week), so it will take about 3 months in total. As soon as Phase 1 and 2 are ready, large-scale testing can already take place.</p><p>In consultation with the GAB it was decided that this project will have the highest priority after Witness Sync because of the developments in the market and the strength of the concept. That is also the reason why we are not yet announcing much about what it will be exactly. Once we are well into the development that will happen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4569aa4061d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gulden Monthly Recap February 2021]]></title>
            <link>https://gulden.medium.com/gulden-monthly-recap-february-2021-347c5e731ab5?source=rss-d5a05e1ca811------2</link>
            <guid isPermaLink="false">https://medium.com/p/347c5e731ab5</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[altcoins]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[gulden]]></category>
            <dc:creator><![CDATA[Gulden]]></dc:creator>
            <pubDate>Mon, 01 Mar 2021 16:56:52 GMT</pubDate>
            <atom:updated>2021-03-01T16:56:52.306Z</atom:updated>
            <content:encoded><![CDATA[<p>A lot has happened during the past month. If you want to be up to date about anything Gulden related, this blog-post is here for you.</p><p><strong>Gulden LITE</strong></p><p>Blazing fast ‘LITE’ Gulden wallets have been developed for beginners interested in buying and owning Gulden.</p><p>Gulden LITE is the fast minimized wallet without witness and mining functionality. This is a great development for mass adoption of Gulden. We are very proud that people can now create new desktop wallet and have it completely synchronized in under a minute. The LITE wallet can work next to a full desktop version of Gulden. But keep in mind not to use any old recovery sentence in the LITE wallets, because they are not designed for this.</p><p>Download the LITE wallet at <a href="https://gulden.com/download">Gulden.com/download</a></p><p>Another few facts that might have your attention: We’re also working on the option to sell Gulden straight in the Gulden wallets. We are very excited on these developments as they contribute to more users of the Gulden wallets.</p><p><strong>Gulden on Clubhouse</strong></p><p>A few members of the Gulden Community started hosting weekly live Clushouse sessions, with great results. The sessions are called Gulden Café and Crypto Café. The first event there were 12 listeners and during the last sessions over 40 people were listening or discussing anything related to Gulden or other cryptocurrencies. The events are momentarily held in Dutch language, but soon also English events can be organised.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yQ5lHWZZh1499-Cc.png" /></figure><p>Every yet to be held event will be available at <a href="https://guldenadvisoryboard.com/room">guldenadvisoryboard.com/room</a><br>Keep in mind the current conversations are held in Dutch. In the future there will be also English held events!</p><p>Don’t have a invite to Clubhouse yet? Reach out on our community Slack: <a href="https://guldencom.slack.com/">Guldencom.slack.com</a></p><p><strong>Fast growing political party Code Oranje started giving away Gulden as part of their member recruitment campaign.</strong></p><p>Quoted from the website of Code Oranje: “We value nostalgia, with a view to the modern world.”</p><p>All new members of the political movement will receive 150 Gulden. Read all about it on the official website of <a href="http://wijzijncodeoranje.nl/2021/02/14/ledenwerfactie-code-oranje-geeft-leden-150-gulden">Code Oranje</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i5QmEQZOasT7SR3r.jpeg" /></figure><p><strong>Gulden based Crowdfunding platform Gulden.Social has been given a new name, website and look.</strong></p><p>The new website is <a href="https://guldenkickstart.com/">guldenkickstart.com</a></p><p>A new crowdfund campaign has been recently launched for developing a WooCommerce Plugin so that web shop owners can add Gulden as a payment option. Look it up here: <a href="https://wcplugin.guldenkickstart.com/">https://wcplugin.guldenkickstart.com/</a></p><p>The latest completed campaign of €2500,- was for the full wrapping of the van of Robby Stofbergen, who has recently stated to make a career switch to be able to work full-time on the promotion and adoption of the Gulden project. He has launched a website where he will keep people informed about his Gulden adventure, including video blogs: <a href="http://robbygulden.nl/">RobbyGulden.nl</a></p><p><strong>Buying Gulden directly in the Gulden app</strong></p><p>Blockhut has been working hard to make it possible to buy Gulden easily straight out of the Gulden wallets. This option is now available on ALL wallets, including the full desktop and mobile versions. This is another great development towards further adoption of Gulden.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a28BG1midHuQNAS1.png" /></figure><p><strong>The Dutch Bitcoin</strong></p><p>Gulden has received a nickname of The Dutch Bitcoin. Or in Dutch “De Nederlandse Bitcoin”. Two new websites went live as a marketing instrument: <a href="https://dutchbitcoin.com/">https://DutchBitcoin.com</a> &amp; <a href="https://nederlandsebitcoin.nl/">https://NederlandseBitcoin.nl</a></p><p><strong>The Gulden Bus</strong></p><p>Gulden ambassador Robby Stofbergen now drives around in one big Gulden van! Robby will be promoting Gulden in The Netherlands as part of his career switch. He will be touring in this amazing looking fully wrapped Van!</p><p>Visit his website for more info (website is in Dutch): <a href="https://robbygulden.nl/">RobbyGulden.nl</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uEmk23TTuRcKmUAm.jpeg" /></figure><p><strong>Medium posts</strong></p><p>Pensionado and crypto-lover Aat de Kwaasteniet has released several great medium articles in both Dutch and English. An example of this <a href="https://medium.com/@aat.de.kwaasteniet/cryptos-ranked-by-number-of-nodes-feb-2021-f5044d3e721f">here</a>.</p><p>Read all other of Aat’s Medium posts <a href="https://medium.com/@aat.de.kwaasteniet">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xTNZJ81M_jNSELdw.jpeg" /></figure><p><strong>Rijk.nl</strong></p><p>A new Gulden related website has been launched which shows the top 100 richest Gulden addresses. Are you one of them? Look it up here: <a href="https://rijk.nl/">Rijk.nl</a></p><p><strong>Plan B</strong></p><p>Another new website has been launched by Danny, a Gulden community member to provide an interesting solution to the self-employed who’s careers have been struck heavily by the Covid pandemic. You can read this plan on <a href="https://www.reddezzp.nl/">www.reddezzp.nl</a> (in Dutch).</p><p><strong>Gulden Meme Competition</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z-ojpWiduJjyJwJN.jpeg" /></figure><p>There was a meme competition held by the Gulden community, there were over 40 submissions. You can view them all at: <a href="https://twitter.com/BitcoinNL/status/1359427736285175810?s=20">twitter.com/BitcoinNL/status/1359427736285175810?s=20</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t5MVDnCXEA9-so-D.jpeg" /></figure><p><strong>Gulden.Cafe</strong></p><p>There are new stories from Gulden users available at <a href="https://gulden.cafe/">Gulden.Cafe!</a></p><p><strong>Gulden Newsletter</strong></p><p>Last but not least: Many newsletters have already been send out to over 3500 Gulden followers. The response rate is over 80%, which is a great sign of interest in Gulden. If you haven’t signed up for the newsletter yet, you can sign up here: <a href="https://gulden.com/news">Gulden.com/news</a></p><p><strong>Gulden Medium</strong></p><p>Subscribe to our Medium channel to be notified when there is another Monthly Recap available.</p><p>Follow Gulden on <a href="https://twitter.com/Gulden">Twitter</a> or <a href="https://www.facebook.com/gulden">Facebook</a>. See you next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=347c5e731ab5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Een Gulden toekomst]]></title>
            <link>https://gulden.medium.com/een-gulden-toekomst-17510d5eff96?source=rss-d5a05e1ca811------2</link>
            <guid isPermaLink="false">https://medium.com/p/17510d5eff96</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Gulden]]></dc:creator>
            <pubDate>Fri, 15 May 2020 12:15:54 GMT</pubDate>
            <atom:updated>2020-05-15T12:17:10.538Z</atom:updated>
            <content:encoded><![CDATA[<p>Bron: <a href="https://guldenadvisoryboard.com/een-gulden-toekomst/">https://guldenadvisoryboard.com/een-gulden-toekomst/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LrDRKKjmOgJe3aJ5a15tPg.png" /></figure><p>Na zoveel jaar crypto weten we één ding zeker, de crypto wereld ondergaat continu veranderingen welke niet te voorspellen zijn. De volgende verandering dient zich nu aan, en dat is een hele grote. Nocks is voor ons een belangrijke partner geweest. En aan dit waardevolle partnerschap komt nu een einde. Nocks heeft zojuist aangekondigd de exchange te sluiten en de software over te dragen aan een nog nader te noemen derde partij. We wensen vanuit Gulden het Nocksteam veel succes in de toekomst en bedanken hun voor de mooie samenwerking.</p><p>Vanuit Gulden denken we graag pro-actief en kijken we vooruit. De toekomst voorspellen kunnen we natuurlijk niet, maar de ontwikkelingen hebben we wel in eigen hand. We zullen keuzes moeten maken welke misschien voor nu nog niet relevant zijn, maar die wel belangrijk zijn voor de toekomst. Gulden heeft vele uitdagingen gekend en is deze nooit uit de weg gegaan; ook nu niet. De missie van Gulden gaat vanzelfsprekend door.</p><p>Nadat de Witness ontwikkeling steeds meer voltooiing naderde, zijn we binnen de GAB gaan nadenken over vervolgontwikkelingen. Witness brengt ons nog meer onafhankelijkheid en decentraliteit dan crypto in de basis al doet. Daarom wilden we die weg vervolgen op andere vlakken. Minder afhankelijkheid van externe partijen en een nog stevigere basis, ook wat betreft infrastructuur rondom Gulden. Dit willen we op de volgende manieren bereiken:</p><p>We zijn een exchange aan het ontwikkelen en niet zomaar één… Een decentrale in-wallet exchange (DEX). Deze ontwikkeling is besproken in de GAB-vergadering van 16 april jl. en er is unaniem besloten door de GAB om deze ontwikkeling hogere prioriteit te geven. Door het statement van Nocks is het ook nu een stuk actueler. Gulden gekoppeld aan een Euro stablecoin (op de Gulden chain) en andere crypto. Uiteraard zal deze exchange zeer gebruiksvriendelijk werken, want dat verwachten onze gebruikers. Dat is ook waar Gulden voor staat!</p><p>We gaan op zoek naar nieuwe partners op het gebied van Exchange functionaliteit. Ook op gebied van koop/verkoop Gulden integratie, zoals we op dit moment gewend zijn (in–app kopen of via website Gulden.com). Vanzelfsprekend is de nieuwe partij waar het Nocks team aan de slag gaat, ook een potentiële partner en staan wij open voor eenzelfde mooie samenwerking.</p><p>We gaan vanuit Centure een KYC account functionaliteit opzetten. Dit zorgt ervoor dat we gebruikers beter van nieuws kunnen voorzien, maar ook om voorbereid te zijn op wetgeving en functionaliteiten waarbij KYC een vereiste is. Daarnaast geeft dit ons ook de kans om een hele mooie functionaliteit toe te voegen aan Gulden: het versturen naar echte personen en niet enkel ingewikkelde adressen. Denk aan verzenden naar bijv. e-mail.</p><p>De komende tijd zullen wij jullie op de hoogte houden over deze ontwikkelingen. Wat betreft ontwikkelingstijd is het onze intentie om deze functionaliteiten dit jaar al werkend te hebben.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17510d5eff96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A post launch look at SIGMA]]></title>
            <link>https://gulden.medium.com/a-post-launch-look-at-sigma-28d2b1b5940f?source=rss-d5a05e1ca811------2</link>
            <guid isPermaLink="false">https://medium.com/p/28d2b1b5940f</guid>
            <category><![CDATA[gulden]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[proof-of-work]]></category>
            <dc:creator><![CDATA[Gulden]]></dc:creator>
            <pubDate>Thu, 07 Nov 2019 17:07:50 GMT</pubDate>
            <atom:updated>2019-11-07T17:07:50.591Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://medium.com/@MacLeod_MJ_za">Malcolm MacLeod</a></p><p>For those who don’t already know about Gulden; Gulden uses a unique consensus algorithm which we call PoW² that combines traditional “proof of work” mining with a secondary system of “witnesses” to greatly enhance security. To be a witness coin holders must lock substantial funds up for a lengthy period of time (up to three years). More information on this system: <a href="https://medium.com/@MacLeod_MJ_za/pow%C2%B2-explored-a-post-launch-look-at-some-of-the-security-implications-2773fc11e50c?source=your_stories_page---------------------------">article on security implications</a>, <a href="https://medium.com/@MacLeod_MJ_za/beginners-guide-to-witnessing-11253afd645d?source=your_stories_page---------------------------">basic guide to being a witness</a>, <a href="https://gulden.com/en#technology">simple graphical high level overview</a>, <a href="https://medium.com/@Gulden/pow%C2%B2-frequently-asked-questions-643d69bc20d2?source=---------14------------------">some FAQS</a>, <a href="https://github.com/Gulden/gulden-official/raw/master/technical_documentation/Gulden_PoW2.pdf">detailed paper</a> .</p><p>On October 16th we activated SIGMA our new hash algorithm at the centre of the “proof of work” portion of our blockchain consensus. The reasons behind the design of and change to SIGMA were numerous but a non exhaustive list of some of the major reasons were as follows:</p><ol><li>Lack of decentralisation — A single pool was frequently finding more than 50% of the blocks, with almost all blocks split between only several pools.</li><li>Long block times — It had started to become extremely common to see blocks taking 20 minutes or more to come in instead of the target of 2.5 minutes. To the extent that sometimes only 500 blocks were found in a day instead of the expected 576. Erratic block times like this presents usability issues for our users as well as having potential security implications.</li><li>High barrier to entry — It was expensive/impractical for potential new users to get involved in mining. This was a waste of a potential way to grow our user base and interest in the coin.</li><li>Shrinking hash rate — Our Scrypt hash rate was shrinking over time meaning that security was slowly diminishing. While it was not at a point where it was problematic it also was not ideal going forward.</li><li>Toxic mining community — We have found over the years (with some exceptions of course) that the community of people who own scrypt mining hardware and run Scrypt mining pools is very small, shows zero actual interest in the coins they mine at the best of times, and is outright toxic a lot of the time. It seemed it would be in the best interests of the coin to lose these miners and to attract instead fresh people in their place.</li></ol><h3>A look into performance so far</h3><p>We are now three weeks past the switch over, so how are things going? Obviously a lot will still change as things mature, so we are watching with interest, but we are far enough past the initial activation that we already have some data that we can start to look at.</p><p>For those in a rush jump ahead to the end a short summary (tl;dr) of the article.</p><h3>Decentralisation</h3><p>Under Scrypt the majority of blocks were being found by only one or two pools. With it not being uncommon for a single pool to be controlling 50% or more of blocks. The below screenshot (July 2019) nicely demonstrates this.<br>This is not good at all, however to be clear this is not a Gulden specific problem, in fact as bad as the below screenshot is, the majority of PoW coins are in an even worse position…<br>It is also worth noting that for Gulden a single miner having 50% of the hash is a lot less of a problem than for a regular coin, the reason being that each block still requires a witness from our large and diverse pool of witnesses (834 accounts and growing).</p><figure><img alt="Previous (July 2019) mining distribution under Scrypt — Courtesy Dactual.com" src="https://cdn-images-1.medium.com/max/609/0*EBqu-o2H8hcC0V9g.png" /><figcaption><a href="http://dactua.com/">Previous (July 2019) mining distribution under Scrypt — Courtesy Dactual.com</a></figcaption></figure><p>A week after SIGMA activation, some screenshots of the same chart but with SIGMA data started doing the rounds. The chart shows a completely different picture with the daily blocks shared out between over 200 different miners the absolute largest of which controlling only 4% of the blocks.<br>This represents an almost ideal situation that every blockchain should be striving to achieve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/0*s5_R7g49Q2Ohj000" /><figcaption><a href="https://www.dactual.com/minedby.php">Gulden; Mining distribution a week after activation — Courtesy Dactual.com</a></figcaption></figure><p>Three weeks in things have changed a little bit. The largest miner is now larger at around 16% but still a reasonably healthy size. The four largest miners controlling only 25% of the blocks between them. The remaining 75% of blocks keep an almost ideal distribution shared out amongst hundreds of miners.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/608/0*Mt8LIXCTLpg8bR4i.png" /><figcaption><a href="https://www.dactual.com/minedby.php">Gulden; Current mining distribution — Courtesy Dactual.com</a></figcaption></figure><p>Of interest is that the largest miner has peaked at a higher percentage (around 20%) and then declined, and that this has happened more than once. This potentially indicates that the larger miners are not finding the profits they are hoping for.</p><p>For an ordinary blockchain there are various factors that push towards centralisation, greedy mining being one. However Gulden is immune to this and this may be playing a role in the above effect.</p><p>It is still early days so we will be watching with interest how things progress.</p><h3>Block times</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/0*NWqCWPBkm24cI6gw.png" /></figure><p>Before SIGMA activation our block times were not looking great. Our block target is 150 seconds a block but we were seeing daily averages as high as 170. Post activation things are looking quite a bit better with the average around 147 — while we are still slightly off the target there are some technical reasons for this (that are not the fault of SIGMA itself) and we have good reason to believe that once we activate phase 4 of witnessing we will be able to achieve even more optimal block timings.</p><p>However although when people look at blockchain projects they tend to focus on the ‘average’ (mean) block time, this is actually not the most useful measurement to be looking at. Of far greater interest is the median, the minimum and the maximum. We have a built in command in Gulden `dumpblockgaps` that anyone can use to look at this sort of information.</p><p>For Gulden if I grab a random day in the past (e.g. 4 months ago) we see the following stats for the day:</p><ul><li>max: 2158s (The longest block for that day took 36 minutes)</li><li>min: 1s (The quickest block took only 1 second)</li><li>mean (average): 162s (On average blocks took 162 seconds to find)</li><li>median: 56s (Half of the blocks for the day took less than 56 seconds to find, the other half more)</li></ul><p>While the average looks ‘reasonable’ in reality what we have is bursts of extremely quick blocks (half the blocks coming in at under a minute, a good portion of them likely in seconds) — Followed by some extremely long blocks, the longest of which was 36 minutes. <br>These bursts and then stalls mean that users have to wait a long time for a confirmation, and in general it makes the experience of those using our blockchain not great.</p><p>Perhaps more remarkable is that as bad as the above sounds these numbers are actually ‘good’, in that they have historically been a lot worse in the past for Gulden and that for most competing projects today those numbers are much worse <strong>right now</strong>. It took a lot of work from the Gulden team to get the median as high as 56s/60s and to keep most of the longer blocks below 40 minutes…</p><p>So how do these numbers look post SIGMA? The stats for the previous day:</p><ul><li>max: 785s (The longest block for the day took 13 minutes)</li><li>min: 1s (The quickest block took only 1 second)</li><li>mean (average): 148s (On average blocks took 148 seconds to find)</li><li>median: 100s (Half of the blocks for the day took less than 100 seconds to find, the other half more)</li></ul><p>While still not perfect this represents a massive improvement, the higher median means that blocks are coming in at more regular intervals, with less fast blocks and less stalls. The longest stall is13 minutes (only 5x longer than block target) which is the longest any user would have had to wait.</p><p>Things are running much smoother, the even better news is that we can still improve on this further, phase4 brings some further improvements in this regard (with the witness timestamps being used for more reliable difficulty adjustment). Our difficulty algorithm Delta has also not yet been adjusted at all for SIGMA (it was finely tuned for Scrypt over the years) and with some minor tweaks its reasonable to expect it to do better.</p><p>I am therefore extremely pleased with these results.</p><h3>Barrier to entry/New mining community</h3><p>The barrier to entry has quite clearly being lowered for now. With Scrypt to start mining Gulden an ‘investment’ in specialist hardware was required — while currently right now anyone with a reasonably new laptop or desktop machine can download the wallet, run it and expect to eventually find a block.</p><p>Granted they may find only 1 block a day, or a block every 2 days or similar, nobody should be under any illusion that they will become millionaires from mining Gulden… However this was never the point, the point was always that anybody who wants to try mining should at least be able to do so, and in this SIGMA is a wild success.</p><p>I would previously describe the bulk of our mining community as highly toxic. While there are one or two exceptions for the most part there was zero overlap between those who mined Gulden and those who used Gulden, with the miners mostly dealing only with pools and likely many of them not even knowing anything about Gulden.<br>We would never hear from most miners/pools unless it was to complain about something, threaten us about developments we were making or so on, we have had very little positive interaction with or contributions from the Scrypt mining community over the years; #mining on our slack was a ghost town.</p><p>In contrast since launching Gulden #mining on our slack has been far more active than ever more, dozens of different miners have reached out to assist me in various ways whether that be assistance with testing. A minor code bug fix from one miner, questions about how they could help support the development team in future and so on.<br>Our new miners also contribute to the network in a positive way, with new nodes/peers popping up all over the show, our entire network is looking much healthier than it has in quite some time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j3546m10gxSo5L1s.png" /><figcaption><a href="https://www.dactual.com/nodemaps.php">Map of Gulden nodes (last 24 hours) — courtesy Dactual.com</a></figcaption></figure><p>If we look at <a href="https://docs.google.com/document/d/1_7mwZD7ORzKn81cVqfoYaqwibbIWfmhrCffh7LmNmdY/edit">some user generated statistics on mining</a> we see that over the course of a week we had some 433 different miners. Some of these miners will carry on mining, others will learn about witnessing and decide that witnessing is more suitable for them while others may just have been curious and after mining a block or two may instead decide to just buy some Gulden and become regular users.</p><p>For every miner that leaves other new miners will likely take their place, transforming mining into not just a way to keep the network secure but also a much needed method of bringing in new people/blood/interest to the project. This effect can already be seen in the increase in network witnesses/witness weight since SIGMA activation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/829/0*duhuJyTKF-DuSFAQ.png" /><figcaption><a href="https://www.dactual.com/witnessweight.php">Gulden network witness weight — Courtesy Dactual.com</a></figcaption></figure><h3>Shrinking hash rate</h3><p>Under SIGMA the previous Scrypt hash rate is of course no longer relevant. We have started again from zero (so to speak) with the hash rate of the new algorithm, and we are still in the early days.<br>Still, so far the hash rate is in a healthy upward trend — which is what we should expect to see.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/0*ti6d5fwdCIKGr8OX.png" /><figcaption><a href="https://www.dactual.com/hashrate.php">Gulden SIGMA network hash rate Oct 23 — Nov 08; Courtesy Dactual.com</a></figcaption></figure><h3>Impact on coin security</h3><p>The above all sounds good, but has it come at the cost of security? If so that would likely not be good.</p><p>Before the swap over our Scrypt network hash rate was in the region of 150gh/s. Although in reality this would have fluctuated a lot over the course of the day (pools switching away for higher difficulty blocks and coming back to quickly mine easier ones). An attacker only needs to succeed when the chain is at its weakest, not on average so in reality our ‘security’ was likely only 50gh/s maybe even less. Regardless lets work on 100 gh/s.</p><p>An antminer L3+ achieves around 0.5 gh/s of Scrypt hashing power, using 880W of energy and can be purchased for around $209. For 100 gh/s it would be necessary to purchase 200 of these $41800. (Total energy usage 176kW) However the Litecoin network had a peak of 500 Th/s and is now at only 180 Th/s there is therefore over 320 Th/s or more of ‘idle’ hardware out there that can be rented cheaply, bought second hand cheaply, or which a potential attacker might already own and just use for an attack.</p><p>To rent 100 gh/s of Scrypt hash rate is as little as $270 a day or $11.25 an hour, so our Scrypt miners were providing as little as $11.25 (or even lower potentially) in terms of network security…</p><p>Thankfully because of PoW² our effective security is/was much higher than this, otherwise like most other PoW coins we would effectively have no security. As I‘ve covered this in a prior article I’m not going to go into details on the amplified security here.</p><p>So how does SIGMA fair? Our network hash rate currently sits between 1.4 gh/s and 2 gh/s but lets work on 1.4 gh/s.</p><p>A relatively high end computer — AMD thread ripper 2950x, is able to achieve a constant hash rate of 12 Mh/s at about 340W energy usage. The purchase price of such a machine is around $1200. It would be necessary to purchase around 116 of them for a total of $139000 or around 4x the price of the Scrypt hardware. (And around 39.4 kW) Like with Scrypt cheaper second hand options theoretically exist on the market.<br>How about rental? Pricing rental for SIGMA is a bit more difficult as there is a much wider variety of conventional computer rental out there, many of them with tough/strict rules on number of instances and many of which may kick you off for mining at any moment. Still a fair indicative price can be had.<br>A roughly equivalent machine to the TR2950x can be rented from Scaleway for $0.66 per hour or $76.56 per hour for 1.4 gh/s.</p><p>So where does all of this leave us?</p><p>Currently SIGMA is relatively new, word of it is still spreading and our hash rate still growing. Our SIGMA miners are consuming 22% of the energy that our Scrypt miners were and yet are providing up to 7x the base security (rental prices) or 4x the base security (equipment purchase prices). And the hash rate is still climbing…</p><p>After considering this amplified base, the large multiplier in security that witnessing brings, and the growth in witness accounts since SIGMA has launched our network is already more secure under SIGMA than it has ever been before.</p><pre>Attack cost 3 confirms under current SIGMA conditions:We now have over 90&#39;000&#39;000 NLG locked up in witness accounts, with a total weight of 903&#39;582&#39;015.</pre><pre>To create a single witness account that holds 1% of the  network weight an attacker would need to lock up 865’000 NLG ($6610) for a period of 1 months — this would give him a 1% chance of  witnessing any block he mines.</pre><pre>An attacker would require at least 3 such accounts ($19830) in order to attempt to attack 3 confirms.</pre><pre>Additionally the attacker would need additional funds with which to perform the double spend, it is a reasonable assumption that he is not going to lock up $19830 to try perform a double spend for substantially less - given the risks that a double spend has in terms of lowering the value of his locked funds.<br>Therefore we can assume at least an additional $20000 in coins required for the double spend.</pre><pre>If he were to acquire 100x the network  hash rate (140 gh/s), at a rental cost of ($7656), he could mine roughly 100 blocks for every 1 the main network mines, as he would have a 1% chance of being the selected  witness for each of these blocks this would give him a reasonable but not guaranteed chance of both mining and witnessing three blocks before the main network.</pre><pre>The above assumes that acquiring over 5&#39;190&#39;000 NLG in order to attempt to stage this attack does not push up the price of the coin - in reality it is almost certain it will. An increase in the coin price means that the attacker would need to spend even more acquiring the Gulden as well as that the network hash rate will increase require more expenditure on mining as well.</pre><pre><a href="https://medium.com/@Gulden/pow%C2%B2-explored-a-post-launch-look-at-some-of-the-security-implications-933d8054380d">The attacker additionally faces various other difficulties in terms of ensuring none of this accounts are in cool down for the attack - and that such an attack is potentially detectable.</a></pre><pre>This puts the attack cost at well over $50&#39;000 at a minimum, likely more and for only 3 confirms, for each additional confirm more witness accounts are required and the attack becomes exponentially more expensive.</pre><p>In terms of other ways to attack the network SIGMA also comes out shining, the increased decentralisation makes us more secure against a ‘bribery’ based attack than even the most high market cap coins out there. We also have increased resilience against transaction censorship as a result.</p><p>The final concern might be that SIGMA itself has some kind of exploitable flaw, or that someone might be able to obtain a secret GPU or ASIC — thankfully witnessing acts to limit the damage they could do in this event. Additionally all the signs so far are that everything is working 100% correctly.</p><p>Our post-nonce distribution appears perfectly random, if there were any exploitable flaws in the algorithm we would expect to see non-random patterns start to emerge:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/837/0*1oWtwaSMWrIlY-mY.png" /><figcaption><a href="https://www.dactual.com/noncedistribution.php">Gulden post-nonce distribution — Courtesy Dactual.com</a></figcaption></figure><p>Our pre-nonce distribution is simultaneously both random but also biased toward lower numbers, as expected. If a different type of miner GPU/ASIC were to emerge we would expect to start to see different patterns here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/837/0*aYEG0pHRwwf_M8Cq.png" /><figcaption><a href="https://www.dactual.com/noncedistribution.php">Gulden pre-nonce distribution — Courtesy Dactual.com</a></figcaption></figure><p>In short everything appears to be working as designed, a very reassuring sign!</p><h3>Summary (tl;dr)</h3><p>With SIGMA we set out to achieve numerous different objectives/improvements. So far it has exceeded our wildest expectations.</p><ul><li>Network security has already increased, despite reduced energy consumption.</li><li>Block times, and therefore overall coin usability are massively improved. With expectation of further improvements still once phase4 activates.</li><li>Active installs/nodes/users on the network are massively up.</li><li>A more positive mining community has emerged.</li><li>Our community is invigorated and more alive again with new users coming in and old users having more to be positive about.</li><li>An increase in witness accounts has also been observed.</li></ul><p>With SIGMA and PoW² complementing one another we have one of (if not the) most decentralised blockchain projects. We are not held hostage by a small group of miners who get to dictate every development decision. We have fast and predictable block times that won’t confuse regular users.</p><p>All in all I’m incredibly happy with the results so far, there is of course room for improvement and the roll out of Phase4 will bring yet more improvements in terms of block times.</p><p>We still have many further ideas for keeping mining decentralised going forward, and have many adjustments up our sleeves that can easily be made should feasible ASICs or GPU miners emerge and become dominant — we are therefore highly confident that we can keep things in a healthy space like this going forward.</p><p>Since joining Gulden the team has worked tirelessly to achieve a blockchain that is secure, has stable predictable block intervals, is robust and scalable. We have always maintained that these are the bare minimum requirements to have a feasible product and that only with this in place does it make sense to build more user visible products and really push for adoption — without constantly worrying about users having bad experiences due to chain issues.<br>It has been a long and hard road but I believe that SIGMA combined with our previous work (PoW², Unity and others) puts us within grasp of this goal.</p><p>The final piece of the puzzle is the new transaction format and witnessing improvements that phase4 brings, and these too are not far off.<br>While all this work has been crucial and difficult it is not very user visible — with these major items out the way we can focus on less difficult faster to develop but more user visible and just as important items and really push things forward.</p><p>2020 is going to be really exciting, I am very excited for what the future has in store.</p><p>Source: <a href="https://medium.com/@MacLeod_MJ_za/a-post-launch-look-at-sigma-performance-70794d835b8c">https://medium.com/@MacLeod_MJ_za/a-post-launch-look-at-sigma-performance-70794d835b8c</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28d2b1b5940f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SIGMA is here]]></title>
            <link>https://gulden.medium.com/sigma-is-here-c33724e6de5d?source=rss-d5a05e1ca811------2</link>
            <guid isPermaLink="false">https://medium.com/p/c33724e6de5d</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[gulden]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Gulden]]></dc:creator>
            <pubDate>Tue, 01 Oct 2019 18:27:01 GMT</pubDate>
            <atom:updated>2019-10-08T12:40:40.434Z</atom:updated>
            <content:encoded><![CDATA[<p>by <a href="https://medium.com/@MacLeod_MJ_za">Malcolm MacLeod</a> — Gulden Lead Developer</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MveFSXC31-dms2jXChmuhQ.png" /></figure><p>It has once again been a busy few months for the development team, with work split up amongst multiple different projects all of which are challenging in their own right and even more so when all going on simultaneously.</p><h3><strong>Unity/iOS</strong></h3><p>Earlier in the year we saw the release of our first “unity” based wallet for Android; since then a lot of work has gone into further improving the “unity” backend and implementing a new iOS app on top of it.<br>With a lot of great work from both Rits and Willem this is now a reality, and all of our wallets now run on mostly the same backend codebase while still retaining native user interfaces.<br>Thanks to the shared code a lot of these improvements filter back into our Android and Desktop wallets as well and in the longterm this will mean a better experience for everybody.</p><p>While obviously the initial releases occasionally see some regressions in functionality and performance this only improves over time and with the iOS wallets are still seeing frequent updates since the initial release things will only continue to get better.<br> <br>While a shared backend may not sound that impressive it is actually a huge accomplishment and will have huge benefits for us going forward in terms of being able to put out more frequent features/updates faster, with less work and with more consistent quality.<br> It also makes it easier to keep things running on a day to day basis.</p><h3><strong>Phase 4</strong></h3><p>Development of Phase 4 has been ongoing and substantial progress has been made. The ‘<a href="https://github.com/Gulden/gulden-official/tree/2.2_development">2.2_development</a>’ branch is now <a href="https://github.com/Gulden/gulden-official/compare/master@%7B12month%7D...2.2_development">1437 commits ahead</a> of ‘master’ and growing daily.<br>While we are very near ready for testing and then release, something we are very eager for, we are not quite there yet.<br> <br>It is important to understand that while we call this ‘Phase 4’ and indeed the ‘PoW2 Phase 4’ changes this branch contains are the main highlight, the 2.2 branch also represents a lot of other ‘less prominent’ work fixing a huge variety of little performance niggles and other issues with the coin and codebase.<br> <br>A decentralised project like Gulden is like a living entity that needs constant and ongoing development not because new features are always needed but because without this development everything slowly starts to get slower, work slightly less well and eventually break. Left alone without maintenance software quickly becomes unusable.</p><p>This update is therefore crucial for the coin, not just for the fancy new features, which of course we are all anxious for, but for a far more important reason, to provide new and existing users with a smooth experience.<br> <br>Most of the ‘fancy new features’ of course are also designed around chain stability and ultimately usability. PoW2 for instance is a project of necessity not something done purely to be flashy or appealing…<br> <br>As important as ‘Phase 4’ is in this regard, over the last months frequent chain stalls have become more and more of an issue for our userbase. Dealing with these stalls further started to noticeably impact my time and energy making it difficult to work on what I wanted to work on, and as such out of necessity another project long on our roadmap frustratingly had to come first and take priority, and that project is SIGMA. Ideally this would have come after Phase 4 but necessity has dictated otherwise.</p><h3><strong>SIGMA</strong></h3><p>In late August we announced SIGMA, our new proof of work algorithm which will replace Scrypt.</p><p>(More on SIGMA here <a href="https://medium.com/@Gulden/an-introduction-to-sigma-the-new-cpu-friendly-algorithm-for-gulden-5cee3a2ad62d">https://medium.com/@Gulden/an-introduction-to-sigma-the-new-cpu-friendly-algorithm-for-gulden-5cee3a2ad62d</a><a href="https://medium.com/@Gulden/an-introduction-to-sigma-the-new-cpu-friendly-algorithm-for-gulden-5cee3a2ad62d)">)</a><br> <br>The algorithm is designed to be ASIC/GPU resistant and also to be updateable in future with minimal work in such a way that any progress on GPU/ASIC implementations can be stopped in their tracks.</p><p>This represents a new era for Gulden where mining should be a ‘level playing field’ and that we will do everything in our capabilities to keep in that way. Note this does not necessarily mean that you are going to get rich overnight mining with your ten year old computer, or that someone elses newer far more expensive computer will not be faster at mining than yours.<br>It does however mean that for the same expenditure on power most people should get roughly the same output without anyone being able to gain a massive advantage via certain hardware, that the best hardware to mine with is likely usually going to be hardware you already own, and that those with cheap/free energy or hobbyists are able to have a shot at mining.<br>While nothing can stop people spending huge amounts of money trying to build larger setups its unlikely to be hugely profitable for them…</p><p>Since then we have been working tirelessly on it, along with some community members who have been extremely helpful in testing performance on a wide array of machines, and things are looking really good.<br> <br>It has been a really huge effort to get here this quickly, but today 1 October, only about a month later we are ready for release.</p><p>SIGMA has been set to activate on 16 October and is ready to be released in a phased manner. We will notify exchanges and similar first about the update so that they have plenty of time to do it.<br>Initial releases for regular users who need to upgrade in a hurry (e.g. will be away on the 16th) or early adopters will become available over the coming days — with beta builds already available for the testers.<br>There are still various minor improvements to be done (including a pretty mining user interface) which will take place over the coming week, so for those who are not in a rush it is better to wait for the follow up releases which will come out between now and the 16th instead of rushing to upgrade to this first version.</p><p>SIGMA wallet software will be available tomorrow in the afternoon (2 October) at Gulden.com.</p><h3><strong>Going forward</strong></h3><p>This year has been a busy one and has flown past far faster than I would have liked, and of course no matter how much we achieve we always wish we had achieved more. That said this has been a massive year for Gulden in terms of development with lots of large and important updates coming out.</p><p>We are not done yet however, the remainder of the year will see us doing further minor improvements on SIGMA, the iOS and Android wallets, and finally pushing to try and get Phase 4 out.</p><p>We are hopeful that we can get it out in the last quarter of the year and will be pushing for exactly this with everything that we have.<br>However it is not going to be easy, there are effectively only 2 ‘working months’ left in the year, with various people generally being unavailable during various parts of December, and there are a huge amount of other day to day things with running Gulden that come up.<br>Sometimes despite our best efforts things take longer than expected as a result, in the event we don’t manage to get ‘Phase 4’ out by end November it will then be something to look forward to very early in 2020.<br> <br>In 2020 we have lots of big plans as well, we expect with both SIGMA and “Phase 4” active our chain will be operating very smoothly and with lots of problems solved, this will free us up to finally work on various more ‘user visible’ projects as opposed to focusing simply on keeping things running, and we have quite a few of these projects lined up. We expect 2020 to be a great and exciting year.</p><h3><strong>Funding</strong></h3><p>While I am very greatful/privileged to work on Gulden and enjoy the work we are doing, I do have to pay the bills and earn a market related salary I cannot work for free.<br><br>Running a project like this is a full time job in itself and requires planning to prevent things like running out of money long before it actually happens. Paying the salaries of several developers as well as all sorts of other behind the scenes costs related to development (theres more than you might expect) is not cheap.<br>Rijk has done a great job of doing this, running the project and keeping us funded to get this far, but nothing lasts forever, funding needs to be sustainable in the long term and in discussion with GAB a new model to ensure we are funded well into the future in a sustainable way has been agreed upon.<br> <br>Without this funding it is not possible to keep doing the work we do, so I do hope that the funding model will be accepted graciously by the community and that I can look forward to many more years of working on the project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c33724e6de5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An introduction to SIGMA the new ‘CPU friendly’ algorithm for Gulden]]></title>
            <link>https://gulden.medium.com/an-introduction-to-sigma-the-new-cpu-friendly-algorithm-for-gulden-5cee3a2ad62d?source=rss-d5a05e1ca811------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cee3a2ad62d</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[gulden]]></category>
            <dc:creator><![CDATA[Gulden]]></dc:creator>
            <pubDate>Tue, 20 Aug 2019 06:08:17 GMT</pubDate>
            <atom:updated>2019-08-20T06:08:17.433Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://medium.com/@MacLeod_MJ_za?source=post_page-----9395b2db9357----------------------">Malcolm MacLeod</a></p><p>We will soon be entering public testing of our new ‘CPU friendly’ PoW algorithm. This article will give a high level overview of how it works; however before doing so first a discussion about how we arrived here and why we think a ‘CPU friendly’ algorithm is the way forward for Gulden is necessary.</p><p>Generally when the topic of ‘ASIC resistance’ or ‘CPU friendly’ PoW algorithms comes up people tend to immediately be separated into two camps.</p><ol><li>Those whose eyes begin to roll back in their heads as they explain that any algorithm that can execute on a CPU can also have an ASIC constructed for it. That even if this were not the case ASIC resistance is undesirable because ASICs are the only true way to gain resistance to attack via botnet and so on…</li><li>Those who swear that ASICs are the devil, that they lead to centralisation, push the common man out of crypto and should be fought at all costs. Quite often the people in the second group are oblivious too or choose to ignore the many failings or previous ‘ASIC resistant’ algorithms that have since had ASICs constructed for them.</li></ol><p>In the past I would have fallen into group 1 as a less extreme member, probably a lot less sarcastic as many other people in this group, but in it nonetheless — after all, the facts on the surface do seem to be on this side of the argument. And indeed in the past I have advised against such algorithms for Gulden.<br>Therefore it is reasonable that I should offer an explanation for why we now pursue an ‘ASIC resistant’ algorithm.</p><p>The reality of course is that, as usual, both extremes are always wrong to some degree and reality is a lot more complex and usually lies somewhere in the middle. The arguments around this are complex and I will not address absolutely everything, for the sake of brevity, but will try to lay out my thoughts on some parts of this argument. Understand that just because I don’t address some specific point here does not mean I am not aware of it nor that I don’t have opinions on it…</p><p>There are several things that I shall address, however I will get the largest of them out of the way first as it impacts most the others.</p><p><strong>Witnessing</strong> — With the introduction of our <a href="https://medium.com/@MacLeod_MJ_za/pow%C2%B2-explored-a-post-launch-look-at-some-of-the-security-implications-2773fc11e50c">witnessing system</a> the rules for Gulden have forever changed in various ways, things that previously were ‘gospel’, ‘fact’ or ‘common sense’ for regular PoW are not the case with witnessing in place and therefore absolutely everything should be reevaluated under the new rule set throwing old assumptions aside.</p><p>I in fact remain as convinced as ever that a ‘CPU friendly’ algorithm for a PoW only coin would be a mistake, and so it is not really my view that has changed but rather the question itself that has changed from “Does a CPU friendly algorithm make sense for a PoW coin?” to “Does a CPU friendly algorithm make sense for a PoW² coin?”. It turns out that the answer to these questions is different.</p><p><strong>CPU friendly mining helps attract new users</strong> — It is undeniable that several of the larger alternative cryptocurrencies are ones that have started with “ASIC resistant” mining; while these algorithms may have eventually failed it seems likely that the period during which they worked has allowed for more people to become interested in the currency.</p><p>Over the years at Gulden we have had to watch as streams of new people have appeared to ask about how they can mine, only to leave in disappointment when they find out that specialist hardware is required. If only a fraction of these people can instead be attracted to us than this is certainly appealing.</p><p>ASIC mining has over the years attracted very few users to our community, while creating a lot of work for the developers. A lot of it undesirable work for instance helping track down and attempt to support various mining pools to upgrade at every major update, mining pools that have at times been toxic toward both the coin and the developers.</p><p>This is of course not a technical reason — so should not override technical concerns but the importance of this should not be understated regardless.</p><p><strong>An ASIC can be made for any algorithm</strong> — As a basic surface statement this is indeed true, however the devil is in the details. The real and closely related questions are “Can an ASIC be made that is massively more energy efficient?” and “Can an ASIC be made that is profitable enough that the extra expense to produce one is worthwhile?”<br>The answer to these is a lot less clear cut, and over the last few years a lot more research has gone into this. Blockchains are not the only area of computer science where this question is important — its also very important for password hashing, where the PHC was held to try make better algorithms for this.<br>Based on these algorithms and continued development it appears reasonable to believe that though ASICs may always have an advantage, the advantages can be drastically diminished, potentially to the point that the production costs of small batches of ASICs will simply not be competitive cost wise against CPUs that continue to be made in far larger batches.<br>Particularly for a low ‘market cap’ coin like Gulden it seems a reasonable assumption that with some clever choices we can hold off ASICs for the foreseeable future. Should we reach a point where ASICs become worthwhile to manufacture we can always at that point adapt further new developments or switch to an ASIC friendly algorithm.</p><p><strong>ASIC resistance is undesirable because ASICs provide security that CPUs cannot<br></strong>This is a complex situation, the main claims are usually:</p><ol><li>Having much more efficient ASICs renders a blockchain immune to botnets/government/well funded corporations; while a CPU only coin would be vulnerable to them.</li><li>The up front costs of purchasing ASICs act as an additional deterrent to attackers.</li></ol><p>There is some truth behind these sort of claims, a CPU only PoW coin is indeed quite vulnerable to botnets, a huge amount of expensive ASICs does indeed represent an additional expense for a would be attacker. It is not inconceivable that an advanced botnet could hijack ASICs as well but it is certainly a lot less likely/realistic than a CPU based botnet.</p><p>In the case of Gulden the importance of PoW is diminished with witnesses providing a huge part of the network security, this greatly diminishes the threat a botnet could pose. An attacker with a botnet would also require a vast amount of coins locked in witnessing to stage an attack. It is true that a botnet could still come to dominate mining for a time but while not ideal this would not diminish security and may even enhance it.</p><p>Further certain types of ASIC resistance (large memory usage for instance) can also act as a form of botnet resistance, as most devices forming botnets tend to not have enough memory capability to participate in such networks.</p><p>For a very high value blockchain there is a strong/reasonable argument that instead of ‘ASIC resistance’ it is better instead to have a very simple algorithm for which ASICs are as cheap to manufacture as possible. It is not worth going too much further in depth into this line of argument as Gulden is not currently anywhere near a ‘market cap’ where this is a reality — for lower value coins things are quite clearly flipped around.</p><p><strong>Actual security comes from energy expenditure and not the type of hardware</strong></p><p>Ultimately relying on the up front expense of hardware, which the <strong>‘</strong>ASICs provide security<strong>’</strong> argument relies on; to secure a blockchain can be seen as a type of ‘security by obscurity’ which is not really a good idea.</p><p>The real security measure of a PoW blockchain is how many watts of energy are protecting it; and this will ultimately end up being roughly the same regardless of the hardware type that is expending the energy. A balance should/will always roughly be obtained where watts expended matches energy prices such that mining is still marginally profitable…</p><p>There is a reasonable argument and one I strongly believe in that a CPU only coin can, in certain theoretical conditions, if the right balance is obtained actually attract more watts to protect it than an ASIC one could, the reason for this is ‘edge cases’.</p><p>With the rise of renewable energy there are people who have solar PV on their rooftop which at times produce excess energy that is not utilised, and computers in their house that are at times idle. I myself am in this exact situation. For these people the costs of purchasing an ASIC to expend this energy is not worthwhile, but if they can have their existing computer mine with that energy when it would otherwise be idle, then it is essentially free.<br>There are also people with remote servers hosted elsewhere that they pay the same price for monthly whether the servers are mostly idle or at full usage .<br>For others there is an attraction to mining even if they are doing it at a loss in present value, as they see value in the future or just find it fun to mine.<br>For all of these groups of people as well as various other groups the costs of an ASIC are prohibitive but mining with a CPU entirely feasible, and so it is entirely possible that a CPU only coin is capable of achieving more energy protection than would otherwise be possible, provided the right balance can be found such that it taps into these groups.</p><p><strong>ASIC resistance is as much about intent as it is about the algorithm</strong></p><p>The argument here is that if the developers of a blockchain announce the intent to keep a coin ‘ASIC resistant’ than this alone acts as a deterrent of sorts to manufacturers. The reason for this is that ASIC development is an expensive investment and takes a long time to make that money back; if there is the possibility that after spending vast resources developing ASICs that the developers of a coin may just change the algorithm, then this is obviously a huge risk factor for ASIC developers to consider.</p><p>The problem with this for most blockchains is that to change the algorithm requires a fork, and a fork is controlled by miners, and if the majority of miners are ASIC developers then … well you get the picture there are likely to be problems. This was definitely a large factor keeping Gulden on scrypt in the past.</p><p>Witnessing again changes things here. Any change in consensus requires a majority of both witnesses and miners to agree in order to become the dominant chain <em>however</em> the witnesses are the far more important part of this equation. Gulden ASIC miners do not hold the power to block updates as they do for pure PoW based blockchains and so as the Gulden developers we have the ability to not only express our future intentions here but also the ability to follow through on them without hassle as long as the changes are agreeable with the community.<br>And this is of course exactly what we intend to do — SIGMA is much more than just an algorithm change but an expression of intent that we can and do intend to make whatever changes necessary to keep CPU miners competitive for the foreseeable future.</p><h3>Development of a new algorithm</h3><p>In the search of a new algorithm I have read through numerous literature. I have read through the entire archives of the the <a href="https://password-hashing.net/">PHC (Password Hashing Competition)</a>, I have read through forum/github/mailing lists of various other coins that have developed or are developing interesting new techniques and read the problems they have encountered, the pros/cons of their approaches and so forth.</p><p>One of the key aspects that emerges is that any successful algorithm must have a large memory footprint as well as large memory bandwidth utilisation.</p><p>Algorithms like Argon2 are great at this, unfortunately the huge problem is that to have Argon2 use e.g. 4gb of memory for miners means that all verifying nodes would also need to use 4gb of memory and this is not really feasible. So the naive approach of simply using Argon2 with large memory requirements is not feasible.</p><p>Ideally an asymmetrical algorithm is required instead (lots of memory to mine but small amount of memory to verify) — Merkle Tree Proofs (also based on Argon2) is an interesting example of this however we view the large proof size that must accompany each header under this scheme to be unacceptable.</p><p>Another common thread that emerged is that while the problem we face for blockchain PoW shares some similarities to password hashing (<a href="https://password-hashing.net/">PHC</a>) there are also differences. The <a href="https://password-hashing.net/">PHC</a> was very concerned with side channel attacks for instance, which is a non-issue for our specific use case. Using specific instructions like AES-NI is problematic for <a href="https://password-hashing.net/">password hashing</a> as they don’t want to limit hardware compatibility, while with Gulden we have a bit more control over that. So while we should learn from <a href="https://password-hashing.net/">PHC</a> we should not take the results of it as the best that we can achieve.</p><p>I have discussed various ideas surrounding ASIC resistance with other programmers, and finally I have also discussed (briefly) with Bill Cox (a very active member of the <a href="https://password-hashing.net/">PHC</a>) an idea that he offered to me unexpectedly when I was asking him a question about a different algorithm of his own.</p><p>The final algorithm that I have come up is entirely mine in terms of design and implementation; but it would be wrong to claim it is entirely mine in concept. It lends heavily from the idea presented by Bill and also from various other ideas picked up based on other peoples work.</p><p>This is probably a good thing — I’m far more confident in an idea that others who have also put a lot of thought into have come up with and with which I agree after applying a lot of thought of my own. This is far preferable to an idea of my own with no independent thought from elsewhere.</p><p>A golden rule of programming is ‘Never roll your own cryptography’ and this extends as well to hash functions. Cryptography and hash functions should be developed by experts in this field.</p><p>While the algorithm itself is unique I have taken great care to properly select existing algorithms that fit the above description for all aspects of it, and merely combine them in a unique way. With great consideration for using the algorithms exactly as they are specified.</p><p>In doing so I feel I have stuck to this golden rule and stuck within my strengths (applying existing cryptographic algorithms) and avoided an area out of my expertise (creating new cryptographic algorithms) — as such I am confident that this algorithm works as intended.</p><h3>SIGMA (Semi Iterated Global Memory Argon)</h3><p><em>The high level functioning of SIGMA is as follows from a mining perspective:</em></p><ol><li>A miner assembles a valid block header.</li><li>The full 32 bit nonce of the header is set to zero.</li><li>Using repeated <em>expensive</em> hashing of the header, a large quantity of memory is filled up in smaller chunks based on the largest memory size we are willing to tolerate for an individual hash.</li><li>The nonce is now treated as two separate halves that together total 32 bits, the ‘pre-nonce’ and the ’post-nonce’.</li><li>The miner alters the pre-nonce, and performs an <em>expensive</em><strong> </strong>hash on the modified header.</li><li>The <em>expensive</em> hash from 5 is taken as the seed for a PRNG (Pseudo Random Number Generator) from which the miner sequentially generates 2^post-nonce-size sets of N random numbers. (65536 if post-nonce is 16 bits)</li><li>As each set of N numbers is generated the miner sets the post-nonce to the current index and uses the set values as an index to a chunk of the global memory (which we treat as the same number of chunks as sets for this purpose).</li><li>For each N in the set a chunk of global memory is hashed (along with the expensive hash and the modified header) using one of a selection of <em>fast</em> hash algorithms (also determined by the PRNG) and compared against the difficulty target.</li><li>If a set of N values is found for which all the resulting <em>fast</em> hashes are lower than the difficulty target then a valid block has been found.</li><li>The miner repeats 5–8 until a valid block is found</li><li>If the miner exhausts the pre-nonce without success he updates the block data and starts again from step 1.</li></ol><p>The upfront costs to generate the global memory array are expensive, the costs of each pre-nonce hash is expensive. The multiple post-nonce hashes that can be generated per pre-nonce hash are very cheap and fast, but to be able to generate them the miner must have all of the memory from the first step.<br>For N=2 and a post-nonce that is 16 bits a miner who attempts to ‘cheat’ and mine with half the memory, would be able to perform only 16384 out of 65536 cheap hashes for every expensive hash; he would have to perform 4x the amount of expensive hashing to mine at the same speed. For N=4 only 4096 out of 65536.</p><p>A miner who attempted to skip the global generation entirely would have to constantly perform expensive hashes for every fast hash attempt which would drastically slow mining down.<br>It is therefore impractical to design a mining ASIC that uses less memory or to mine using less memory.<br>The iterative PRNG step with random selection of fast hash algorithm complicates attempts to make the fast hashing parallel and introduces depth and branching that will make GPU implementations less practical and ASIC implementations more expensive.</p><p><em>From a verification perspective the client needs to do as follows:</em></p><ol><li>The client receives a new header with nonce values already set.</li><li>The client generates a single expensive hash for the header with pre-nonce.</li><li>The client generates the PRNG set of N indices for the header with the post-nonce.</li><li>The client performs another single expensive hash to generate the single required chunk of global memory.</li><li>The client performs a single fast hash for the global chunk of memory.</li><li>The client validates that the fast hash meets the difficulty target, if not the header can be discarded as invalid without any further work.</li><li>Otherwise the client then re-uses the memory from (4) and performs another expensive hash and another fast hash to validate the second fast hash, and again checks it for validity.</li><li>This continues for all N until the entire set is validated</li></ol><p>Notes:</p><ul><li>The memory requirement of validation is constant, if the expensive hash is 16mb then validation can be done with roughly 16mb.</li><li>Validation is reasonably fast and allows to prevent DoS attacks, with invalid headers detectable with only 2 slow and 1 fast hashing operation.</li><li>Light clients on low power hardware can further reduce resource usage by opting to selectively/randomly validate only some of the hashes in the set and still be reasonably sure that they are not being sent down a path of false headers, effectively using less resources to validate than a malicious attacker would have to use to generate the string of false headers.</li></ul><p><em>Gulden specific implementation details:</em></p><ul><li>Initially we aim to require a 4gb global memory buffer — it is likely we will increase this to 8gb in the forseeable future.</li><li>For the expensive hashing we will use a modified Argon2d (argon2d_echo) with 16mb for the memory parameter; the reason for the deviation from plain argon is to prevent the re-use of any general purpose Argon ASICs that are manufactured.</li><li>The modification is that Echo is used in place of Blake for the initial and final phases in argon (Argon2 is designed to accommodate changes like this) while the bulk of the algorithm remains unchanged. The second change is to use it as a memory filler (to fill large amounts of memory) instead of only as a hash function (small memory output) — again this is completely within the design of Argon2 and not an invasive change.<br>Echo is chosen for its heavy usage of AES (which most common CPUs have hardware acceleration for).</li><li>The PRNG is again AES based and designed to not allow for jumps. This is important to force post-nonce calculations to be (partially) sequential instead of paralleled complicating things for GPU implementations.</li><li>We have selected N=2 for now for the fast hashes; that is two fast hashes to be performed for every attempt. It is entirely possible that we will increase this in future.</li><li>We have also selected two fast hash algorithms, from which the random hash selection for the fast hashes can pick. Echo and Shavite both chosen for their similar performance and heavy usage of AES (which most common CPUs have hardware acceleration for).<br>It is quite possible if not likely that we may add additional algorithms here in future.</li></ul><p>The choice of Argon2d instead of Argon2i or Argon2id is deliberate; in this use case side channel resistance is not at all important or desirable and therefore Argon2d is the best choice.</p><p>Argon2d is carefully designed to reduce the advantages GPUs and ASICs may have over CPUs; as the winner of the <a href="https://password-hashing.net/">PHC</a> it is well suited and evaluated for this task.</p><p>The heavy reliance on AES is deliberate as modern CPUs have very well developed hardware acceleration for this, that have had a lot of development put into them by manufacturers. There has been extensive work and multiple studies comparing AES-NI instruction performance vs GPUs and ASICs for pure AES computation; attempting to speed AES up on GPUs etc. and the results have been very favourable for CPUs — with the AES instructions mixed with other branching and instructions we expect an extra advantage for CPUs as a result.</p><p>Older CPUs; low end CPUs from before 2012 or high end CPUs from before 2009 that do not have AES specific instructions can still benefit from other hardware accelerated instructions, and are still expected to perform reasonably, albeit not as well as CPUs who do have the instructions. Meeting the memory requirements remains the dominant factor in terms of performance.</p><p>The lower (4gb memory size) is chosen for now to be as inclusive as possible for initial launch, so that more miners can be available — as the quantity of miners on the network grows we will increase this memory size requirement over time to increase GPU/ASIC resistance.</p><p>There are various other aspects that can be tweaked in various ways to change GPU/ASIC behaviour (and completely break any ASICs that rely on specific behaviours) and over time we may consider these in more detail once we see the algorithm perform in the wild.</p><p>For more detailed specifics refer to the source code which will soon be made public.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cee3a2ad62d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Phase 4, Android & iOS Development Update]]></title>
            <link>https://gulden.medium.com/phase-4-android-ios-development-update-2222678ae8b?source=rss-d5a05e1ca811------2</link>
            <guid isPermaLink="false">https://medium.com/p/2222678ae8b</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[gulden]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Gulden]]></dc:creator>
            <pubDate>Tue, 28 May 2019 09:09:28 GMT</pubDate>
            <atom:updated>2019-05-28T09:09:28.182Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IH13G03juYTLa0lhCmGGrA.png" /></figure><p><strong>In March we released our new Android app utilizing the new unified backend. While the development team has been very busy since then, on the outside things might seem a bit quiet and people might be wondering what we have been doing, so here is a quick update.</strong></p><h3><strong>Android</strong></h3><p>The new Android app exceeded our expectations on launch, performing better than expected for version 1.0 of a completely new app. However even with this being the case, with so many different android versions and devices out there in the wild, there are always going to be some things that appear only after release.</p><p>And so part of the team has been monitoring Google Play for any issues that present themselves, as well as listening to various feedback from reviews and has put out multiple releases to improve on what we already have.</p><p>We are now 2 months post release and the app we have on the store is really doing great now, it is far more stable than the old app as well as similar competing apps on the store. At this point we can take most of the development focus off Android temporarily — however don’t worry there will still be periodic new releases with plenty more improvements to come.</p><p>We can however use your help.</p><p>Although we believe the vast majority of our users are happy with the new app, if you aren’t please let us know why so we can improve… A small but vocal minority of users have given us negative reviews over things that our out of our control e.g. forgetting their own passwords. Due to the way that the Play store will give a larger weighting to recent reviews going forward these few reviews can have a very negative impact for us and chase away future prospective users.</p><p>So we ask that all users who appreciate this app take a moment to do something positive for the project and to give us a fair rating on the play store, even if you have done so in the past the fact that it is an updated rating is important and will be good for Gulden as a whole. If you are feeling particularly generous an honest review to go with it is even better.</p><h3><strong>Node.js/Electron</strong></h3><p>Last month the core team also quietly put out another exciting development. As it is not really user facing at this point we didn’t make a large fuss of it at the time, but it is there for the more technically inclined to tinker with.</p><p>A prototype “proof of concept” electron app using the unified backend.</p><p>The primary purpose of developing this was to enable the core team to better test the unified backend going forward, allowing us to develop with it on the desktop without having to use mobile devices or emulators.</p><p>However this also presents interesting opportunities in terms of being able to develop other new applications using Electron in future, potentially support additional new platforms more rapidly, for third parties to write apps (not necessarily wallet apps) that make use of it and so on. It also makes Gulden more accessible to the large and growing number of node.js developers out there. So we are very excited by this development.</p><p>The speed and ease at which we were able to get a proof of concept up and running also showcases the power that having a unified backend brings to the table.</p><h3><strong>iOS</strong></h3><p>In the meantime the iOS team has been hard at work porting the iOS app onto the unified backend as well, and have been making great progress.</p><p>The current iOS app is already great and we won’t release the new app until it is as good or better than the old one, so it may take a bit longer, but we are well on the way to completion in the coming month(s).</p><h3><strong>Phase 4 witnessing</strong></h3><p>With the iOS team rapidly making progress, and Android now running smoothly, the core team have shifted their full attention onto Phase 4.</p><p>The bulk of the work for Phase 4 is already completed, including our brand new transaction format ‘SegSig”. However with a completely new transaction format it brings we cannot be too careful with testing, we are therefore hard at work on unit tests and functional tests to ensure everything is properly covered. There are various edge cases in the code that need some improvements, manual programmer testing and code review.</p><p>Once a new iOS build is released, we hope to have the Phase 4 betas ready shortly thereafter, we will then be able to do a (hopefully short) beta test of Phase 4 across Desktop/Android/iOS simultaneously before releasing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2222678ae8b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gulden for Android (Unity)]]></title>
            <link>https://gulden.medium.com/gulden-for-android-unity-f1a6d26a7141?source=rss-d5a05e1ca811------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1a6d26a7141</guid>
            <category><![CDATA[gulden]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Gulden]]></dc:creator>
            <pubDate>Wed, 27 Mar 2019 16:53:40 GMT</pubDate>
            <atom:updated>2019-03-27T18:03:43.219Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The Gulden development team is extremely pleased to announce the release of our new Android app.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vN5RrMv7a_591m5DE_J2yg.png" /></figure><p>The new app is a massive improvement over the previous one, and features: Much faster initial network synchronization and recovery from phrase/link; enhanced address privacy; lower battery consumption; reduced bandwidth usage; along with dozens of other drastic improvements.</p><p>However, as exciting as the release of the app itself is. For us, this is a milestone not just because of the great new app but also because it is the first of our apps to utilize our <a href="https://gulden.com/#technology">new unified backend (codenamed Unity)</a> that we have been working very hard on ever since the community selected it as our priority project last year.</p><p>Not just an update this is a completely new app written 100% fresh from the ground up and not based on any prior code or project. Its design takes into account the experiences and lessons learned from the old app but leaving all the old baggage behind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dhk2GjiPCpaBhCr4DEcCWg.png" /></figure><p>It is almost entirely written in Kotlin, taking advantage of better and more modern libraries and development practices for Android.</p><p>The new app is written (measured using the CLOC tool) in only roughly 4840 lines of Kotlin and 146 lines of Java on the frontend and despite this managed to replace and surpass in functionality the old app which had over 15076 lines of Java on the frontend and an additional 79855 lines of Java on the backend.</p><p>The backend is written in C++17 and the codebase is shared with the desktop, and in future iOS wallets; it enjoys better unit testing coverage as well as increased developer scrutiny than the old library as a result and will also be easier to keep updated.</p><p>Compared to its predecessor the new app has only 5% of the code to maintain and keep updated, this is a massive improvement. The core code will see increased focus and attention as it is used more, and features from each will be more readily available to one another allowing for new opportunities to improve both.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QJ3dLk3EXJhiyMoDHyyNXQ.png" /></figure><p>The end result is a codebase that is much cleaner, leaner, faster, and with fewer bugs. Most importantly it means that we can roll out future developments much faster than we have in the past, implementing them in only one backend and language, instead of multiple backends across every platform we support.</p><p>This also paves the way for opportunities to support new platforms in the future, with a much faster turn around time and lower upfront effort.</p><p>While this is a hugely exciting step for us, it is only the first release for the Android app. It will, no doubt, continue to see further work, improvements, and updates on a frequent basis.</p><h3><em>Staged rollout</em></h3><p>We have a large quantity of Android users and we want the upgrade experience to be as smooth as possible for everybody, due to this the new app will not be immediately available to all users upon release but will become gradually available over the course of the coming days.</p><p>The new app will be made randomly available to a small percentage of users at first, we will monitor play store statistics and reports as these users upgrade and once they have upgraded without incident we will increase the rollout coverage to a larger group until all users are upgraded.</p><p>Users of the existing wallet will have to perform a simple upgrade process when they first launch the new app, which should take a few minutes or slightly more depending on the age of the wallet and how many transactions it contains. Please contact <a href="https://gulden.com/#support">support</a> in the unlikely event you run into any issues, we want to make our apps the best they can possibly be and we can only do this with your feedback.</p><p><a href="https://gulden.com/download"><em>Gulden.com/download</em></a></p><h3>The road ahead</h3><p>Going forward we will now be able to put out android releases much more frequently, which should be a massive improvement for our user base.</p><p>Our main focus will now shift to moving the iOS app onto the unified backed, as well as Desktop builds incorporating the same. In doing so the Desktop and Android clients will benefit from any backend improvements made during iOS development and vice-versa.</p><p>The Android work has paved the way, and doing the same for iOS and Desktop will, therefore, be substantially less work. A lot of which has already been done in parallel during the Android development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NyiTSKxVAIs_tFz5KTL5rg.png" /></figure><p>Once all our apps are using the same shared unified backend, we will be pushing to release “Phase 4” of witnessing, as soon as possible.</p><p>Most of the code for this is already complete, having been developed and tested along with the rest of the witnessing codebase in previous years.</p><p>There are some final tweaks necessary and testing to perform, particularly mobile compatibility. With all mobile apps on Unity, ensuring they are compatible will be easier to achieve, and with less effort than would have been necessary when all codebases were separate.</p><p>Following the launch of “Phase 4”, the team has a list of exciting developments that we are yearning to get started on.</p><p>These will be smaller, in terms of work, than the recent massive projects we have undertaken, yet just as if not more exciting in terms of user-facing impact.</p><p>With a stable solid unified code base to build on, development will be much easier than it would have been, without this difficult but necessary groundwork.</p><p>2019 is shaping up to be a very interesting year for the project.</p><p><a href="https://gulden.com/download"><em>Gulden.com/download</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1a6d26a7141" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview: “Er zou een keurmerk voor cryptovaluta moeten komen”]]></title>
            <link>https://gulden.medium.com/interview-er-zou-een-keurmerk-voor-cryptovaluta-moeten-komen-aecbe8ab4ea4?source=rss-d5a05e1ca811------2</link>
            <guid isPermaLink="false">https://medium.com/p/aecbe8ab4ea4</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[proof-of-stake]]></category>
            <category><![CDATA[proof-of-work]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Gulden]]></dc:creator>
            <pubDate>Fri, 22 Mar 2019 09:06:33 GMT</pubDate>
            <atom:updated>2019-03-22T09:06:33.138Z</atom:updated>
            <content:encoded><![CDATA[<p>Door <a href="https://blockchainrealisten.nl/author/lykledevries/">Lykle de Vries</a> | 21 maart 2019</p><p><strong>In 2017, op het hoogtepunt van de blockchain-hype, maakten we een serie interviews met Nederlandse experts onder het motto “Op zoek naar de schat”. We probeerden te achterhalen wat nou de werkelijke toegevoegde waarde van blockchain was. Dit jaar maken we een nieuwe serie, met mensen die daadwerkelijk met Blockchain aan de slag zijn gegaan en iets tot stand hebben gebracht. Wat zijn ze tegengekomen? Wat viel er mee, wat viel er tegen? Is de blockchain-hype voorbij, en is dat terecht? In dit interview spreken we met Rijk Plasman, initiatiefnemer van de Nederlandse cryptocurrency Gulden.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IH7L0GkjLBdrtGyS2wTf4A.png" /></figure><h3>Rijk Plasman</h3><p>De timing van ons interview met Rijk Plasman van <a href="https://gulden.com/nl">Gulden.com</a> had niet veel beter gekund. Net een dag eerder had GeenStijl bekend gemaakt voortaan donaties in Gulden te accepteren. (Met de typische GeenStijl-kop: “<a href="https://www.geenstijl.nl/5146795/piekenkermis/">GeenStijl voert de Gulden weer in!</a>”)</p><p>Leuke publiciteit natuurlijk, maar er zit wel degelijk een verhaal achter. Voor een shockblog als GeenStijl is het niet ondenkbaar dat het ooit belangrijk zou kunnen worden om anonieme, oncensureerbare <em>funding</em> te ontvangen. En dat kan, met Gulden.</p><p>We spraken met Rijk over de geschiedenis van Gulden, over de ambities en over het zelf ontwikkelde consensus-mechanisme POW2. Een van de opmerkelijkste uitspraken uit het interview: “Er zou een keurmerk voor cryptovaluta moeten komen.” Want hoewel de meeste projecten open source zijn, zijn er maar weinig mensen die echt de kwaliteit van de code kunnen beoordelen. Een keurmerk zou gebruikers kunnen overtuigen om een cryptomunt te vertrouwen, ook als ze zelf onvoldoende kennis hebben om de werking helemaal te begrijpen.</p><p>Fundamentalisten zullen gruwen van zo’n pleidooi voor een <em>trusted third party</em>, maar het is tekenend voor het pragmatisme van Gulden. Gewoon iets bouwen dat werkt en gebruikt wordt. Er is iets voor te zeggen, denken we.</p><p><em>Dit artikel is oorspronkelijk verschenen op </em><a href="https://blockchainrealisten.nl/blog/er-zou-een-keurmerk-voor-cryptovaluta-moeten-komen/"><em>https://blockchainrealisten.nl/blog/er-zou-een-keurmerk-voor-cryptovaluta-moeten-komen/</em></a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F325609620%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F325609620&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F769398290_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/59f7af83746f380c26fa1fed09dbe4f4/href">https://medium.com/media/59f7af83746f380c26fa1fed09dbe4f4/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6Pg2ZfjHRmY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6Pg2ZfjHRmY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6Pg2ZfjHRmY%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/f22aa9936244ecec5ea81e0cbbd7a412/href">https://medium.com/media/f22aa9936244ecec5ea81e0cbbd7a412/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aecbe8ab4ea4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>