<?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 Chlu Team on Medium]]></title>
        <description><![CDATA[Stories by Chlu Team on Medium]]></description>
        <link>https://medium.com/@ChluNetwork?source=rss-e951a4b238c7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Sd1jZ-7McWru2NO8jVRnEQ.png</url>
            <title>Stories by Chlu Team on Medium</title>
            <link>https://medium.com/@ChluNetwork?source=rss-e951a4b238c7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:31:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ChluNetwork/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[How to Fight Fake Reviews]]></title>
            <link>https://medium.com/chlunetwork/how-to-fight-fake-reviews-2ff82e643fa3?source=rss-e951a4b238c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ff82e643fa3</guid>
            <category><![CDATA[online-reputation]]></category>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[fake-reviews]]></category>
            <category><![CDATA[reputation-management]]></category>
            <dc:creator><![CDATA[Chlu Team]]></dc:creator>
            <pubDate>Tue, 10 Jul 2018 14:19:43 GMT</pubDate>
            <atom:updated>2018-07-10T14:21:15.163Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Fight Fake Reviews:</h3><h4>Saving your business from the epidemic of fake reviews online</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*o_dRtELskoeTTsQVYtiF5w.jpeg" /><figcaption><a href="http://dilbert.com/strip/2009-02-01">Dilbert by Scott Adams</a></figcaption></figure><h3>The problem of fake reviews</h3><p>Fake reviews are a <a href="https://www.newyorker.com/tech/elements/the-never-ending-war-on-fake-reviews">well known</a> and <a href="https://www.bbc.com/news/technology-43907695">global problem</a>. Reviews are highly manipulable. A reporter at Vice demonstrated just how much by using fake reviews to push his garden shed to the <a href="https://www.vice.com/en_us/article/434gqw/i-made-my-shed-the-top-rated-restaurant-on-tripadvisor">#1 rated restaurant in London </a>on TripAdvisor. As funny as the story is, it points out something very tragic — review sites can no longer be trusted.</p><p>It is estimated that as many as 1 in 5 reviews on Yelp are fake according to <a href="https://www.marketwatch.com/story/20-of-yelp-reviews-are-fake-2013-09-24">one study in 2013</a>. And this is <em>after</em> Yelp’s screening process which <a href="https://searchengineland.com/why-we-need-to-fight-fake-reviews-295005">rejects about 25%</a> of submitted reviews as likely fakes. TripAdvisor has also tried to implement safeguards against fake reviews, which helped them identify <a href="https://www.newyorker.com/tech/elements/the-never-ending-war-on-fake-reviews">60 review farms in 2015</a>. But type in “TripAdvisor Review” or “Yelp Review” in Facebook Search and 100s of groups will pop up offering fake reviews. And things are only going to get worse — researchers have developed software that can write <a href="https://www.businessinsider.de/researchers-teach-ai-neural-network-write-fake-reviews-fake-news-2017-8?r=UK&amp;IR=T">extremely believable fake reviews online</a>. These fake reviews are undetectable by review sites and considered “highly reliable” by readers, posing a <a href="http://people.cs.uchicago.edu/~ravenben/publications/pdf/crowdturf-ccs17.pdf">very real threat</a> to these review sites.</p><p>Amazon is also struggling with its <a href="https://www.buzzfeed.com/nicolenguyen/amazon-fake-review-problem?utm_term=.lx3ZmL8nG#.quzzdLqb0">fake review problem</a>. Experts estimate that between <a href="https://www.buzzfeed.com/nicolenguyen/amazon-fake-review-problem?utm_term=.enD6e4WRb#.emoPn9lA1">9%</a> to <a href="https://searchengineland.com/why-we-need-to-fight-fake-reviews-295005">40%</a> of reviews on Amazon are fake. Put your favorite product into <a href="https://www.fakespot.com/">Fakespot</a> to see just how bad the problem is. When Hillary Clinton published her memoir of the 2016 US presidential election, hundreds of users took to Amazon to leave reviews. Within 24 hours, there were over 1500 reviews of the book — and only <a href="https://qz.com/1076357/hillary-clintons-what-happened-amazon-just-deleted-over-900-reviews-of-hillary-clintons-new-book/">338 were from users with verified purchases</a>. After 48 hours, <a href="https://www.theguardian.com/books/2017/sep/14/amazon-redacts-one-star-reviews-of-hillary-clintons-what-happened">only 581 reviews remained</a>. Amazon just deleted over 900 reviews it considered to be fake. But can they be trusted to be the judge? After the incident Amazon now requires its users to <a href="https://www.amazon.com/gp/help/customer/display.html?nodeId=201929730">purchase $50 worth of products </a>before leaving reviews, but this doesn’t guarantee the reviewer actually bought the product.</p><h3>Why real reviews matter</h3><p>It’s no surprise this problem exists, <a href="https://medium.com/chlunetwork/freelancers-take-back-your-reputation-cf226ef09ee1">reviews are extremely important</a> for the reputation and revenue of your business. There are strong incentives for competitors (and even you) to manipulate reviews to an advantage. But what happens when everyone tries to game the system? It becomes useless. <strong>If consumers no longer trust reviews — they definitely won’t trust your business.</strong></p><blockquote>“It may be tempting to justify a boost in ratings with a few made-up reviews when you’re convinced everyone else is doing it. But the negative impact on your business far outweighs the temporary lift you might experience.” (<a href="https://searchengineland.com/why-we-need-to-fight-fake-reviews-295005">Young</a>)</blockquote><p>Businesses like restaurants and hotels are most at risk because they rely on sites that are highly manipulatable. Yet, these businesses stand to lose the most from a negative review. A 1% increase in online customer rating for hotels <a href="https://www.tandfonline.com/doi/abs/10.1080/02642069.2010.529436">increases sales per room up to 2.68%</a> whereas negative reviews can <a href="https://asu.pure.elsevier.com/en/publications/the-impact-of-online-user-reviews-on-hotel-room-sales">decrease sales by 2.8%</a>. For restaurants, a 1-star increase in Yelp rating leads to a <a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1928601">5–9% increase in revenue</a>. Ultimately, a customer’s purchase decision depends on perceived value and trust. When these review sites can no longer promise real, valid reviews; <a href="https://www.sciencedirect.com/science/article/pii/S026151771400209X">this trust breaks down</a>.</p><h3>How to fix the system</h3><p>Help fight fake reviews! A few key steps you can take as a business:</p><h4>1. Use a reputation system that ties your ratings and reviews to a real transaction</h4><p>When ratings and reviews are tied to a purchase, the potential for fake reviews decreases significantly. This is a huge step towards preventing bots from writing reviews and to block attacks from competitors.</p><h4>2. Take ownership of your reputation data</h4><p>If you take ownership of your data then you gain the power to protect it, and control exactly where it is published. This means you can push review sites to improve their standards to prevent fake reviews — and do a much better job at guarding your reputation.</p><h4>3. Use several marketplaces</h4><p>The more marketplaces you offer your services on, the more opportunity you have to be seen! You grow your potential customer base with more exposure, and you have opportunity to get many more reviews.</p><p>At <a href="https://chlu.io/">Chlu</a>, fighting fake reviews is part of our mission. We solve the problem by verifying each review with a purchase. We use <a href="https://ipfs.io/">IPFS</a> (a peer-to-peer, distributed file system) to store the rating and review with a reference to a transaction made on any* blockchain to provide a <strong>proof of payment</strong>. When Chlu ensures verified reviews have a real transaction that is independently verifiable on the blockchain — this prevents fakes from users who never made a purchase. <em>*We are starting with an integration for Bitcoin and Lightning Network payments.</em></p><p>Chlu also gives you ownership of your reputation — and that gives you the ability to take it to any marketplace you choose! We leverage <a href="https://w3c-ccg.github.io/did-spec/">DID</a>s (decentralized identifiers) together with <a href="https://ipfs.io/">IPFS</a> to tie your reputation data to your digital identity and make it portable. Reputation online is broken. Chlu’s solution helps users to finally own and control their validated reputation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ff82e643fa3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chlunetwork/how-to-fight-fake-reviews-2ff82e643fa3">How to Fight Fake Reviews</a> was originally published in <a href="https://medium.com/chlunetwork">Chlu Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Freelancers: Take Back Your Reputation]]></title>
            <link>https://medium.com/chlunetwork/freelancers-take-back-your-reputation-cf226ef09ee1?source=rss-e951a4b238c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf226ef09ee1</guid>
            <category><![CDATA[data-portability]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[gig-economy]]></category>
            <category><![CDATA[ipfs]]></category>
            <category><![CDATA[online-reputation]]></category>
            <dc:creator><![CDATA[Chlu Team]]></dc:creator>
            <pubDate>Tue, 19 Jun 2018 16:11:44 GMT</pubDate>
            <atom:updated>2018-06-19T18:52:15.636Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why data portability is crucial in a Gig Economy</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MMr2LUduZDQEY_CSIYLPQw.jpeg" /></figure><h3>It’s a Freelancer’s World</h3><p>The world is moving towards a <a href="https://www.oreilly.com/iot/free/serving-workers-gig-economy.csp">Gig Economy</a>. According to a <a href="https://s3.amazonaws.com/fuwt-prod-storage/content/FreelancingInAmericaReport-2017.pdf">study by the Freelancers Union in 2017</a>, Freelancers make up 36% of the US workforce. By 2020, this number will increase to 40%, and by 2027 the majority of the US workforce will freelance. As we move towards the Gig Economy — reputation becomes even more valuable.</p><blockquote>“Freelance workforce growth is accelerating and has outpaced overall U.S. workforce growth by 3x since 2014.” (<a href="https://www.slideshare.net/kleinerperkins/internet-trends-report-2018-99574140">Internet Trends Report</a>)</blockquote><p>According to a <a href="https://www.payoneer.com/downloads/freelancer-income-report-2018.pdf">global study by Payoneer</a>, freelancers typically take on 3+ different projects each year. The number of projects and companies quickly adds up — making a resume pretty unhelpful in the search for the next gig. The study also found <strong>75% of freelancers find work on online marketplaces</strong>. Trust becomes even more abstracted as the potential hiring pool becomes a vast, global network. As a result, ratings and reviews of past work — which are a proxy for trust — have become instrumental in the hiring process.</p><h3>Reputation as a Proxy for Trust</h3><p>As marketplaces for goods and services moved online, so did the reviews of their products. The business models of web 2.0 quickly grew from providing the product/service (cars and hotels) to providing the network and the <a href="http://www.mobilelifecentre.org/sites/default/files/Airbnb%20Submitted%20Camera.pdf">facilitation of trust</a> through financial assurance and reputation. These marketplaces became a gateway to further social exchange and interpersonal interaction.</p><p>But, while large companies like Google have built a brand around trust, <strong>small businesses and freelancers fight harder</strong> to earn the confidence of consumers. Ratings and reviews are most important for the long-tail, and thus SMEs and individuals diligently work to maintain good reputations online. (<a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=2&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwikroaGh93bAhVOY1AKHctcDVQQFgg2MAE&amp;url=http%3A%2F%2Fblog.mikezhang.com%2Ffiles%2Fgamereviews.pdf&amp;usg=AOvVaw0fBUx0zfsQE8k-NGc2GRNz">Zhu, Zhang</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aEFylLvRZE1RzbTzZL58hw.png" /></figure><p>Trust is an essential part of a functioning economy. If actors do not trust each other, goods and services will not be bought or sold. This becomes even more relevant online amongst complete strangers. If Alice doesn’t know Bob, she has no personal way to establish trust that he will deliver the t-shirt she paid him for. This is where a history of ratings and reviews comes in. So, Alice doesn’t have to know Bob to trust his service. Instead, she trusts the history of ratings and reviews to make a judgment on Bob’s reputation, value, and then on a purchase.</p><p>There is a proven relationship between trust and the intention to purchase online.* The influence of trust is significant and positive.** <strong>Consumer’s perceived trust </strong><a href="https://www.sciencedirect.com/science/article/pii/S026151771400209X"><strong>directly impacts purchase intention</strong></a><strong>.</strong> It reduces the non-monetary cost and raises the perceived value. Reviews display this trust, and thus, are a tool for online users to evaluate and purchase a product or service online. Globally, <a href="https://www.sciencedirect.com/science/article/pii/S0167923614002097?via%3Dihub">83%</a> of online shoppers consider reviews important before making purchase decisions.</p><p>As a result, reviews impact the <a href="http://journals.sagepub.com/doi/abs/10.1177/014920630102700304">price</a> a business can charge. A higher rating also increases <a href="https://www.tandfonline.com/doi/abs/10.1080/02642069.2010.529436">sales</a>. <strong>Reviews directly increase </strong><a href="https://www.researchgate.net/publication/264982883_The_business_value_of_online_consumer_reviews_and_management_response_to_hotel_performance"><strong>financial performance</strong></a> and <a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1928601">revenue</a>. Reputation online is critical for businesses. Freelancers <a href="https://www.payoneer.com/downloads/freelancer-income-report-2018.pdf">depend on their online reputation</a> to find work. Yet, the reputation in one marketplace <strong>does not carry over to another marketplace</strong>. This is why data portability is crucial for freelancers online.</p><h3>Data Ownership &amp; Portability</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kWETqwEvA5995a1II1_y8w.jpeg" /><figcaption>Image via <a href="https://www.economist.com/leaders/2017/05/06/the-worlds-most-valuable-resource-is-no-longer-oil-but-data">The Economist</a></figcaption></figure><p>These marketplaces capitalize on the user data they silo, preventing users from moving to competing marketplaces by restricting the access of ratings and reviews to their marketplace alone.</p><p>We are now moving into web 3.0, and things are about to change. New technology has enabled financial assurance structures for users without the need for a middleman. Users no longer have to trust a central service such as AirBnB to make sure they get paid; blockchain and smart contracts can accomplish this. You can do this right now on <a href="https://ethereum.org/">Ethereum</a> — or make it even easier by using <a href="https://aragon.one/">Aragon</a>.</p><p>The major innovation is in projects that take this a step further and <a href="https://blog.bigchaindb.com/blockchains-for-big-data-from-data-audit-trails-to-a-universal-data-exchange-cf9956ec58ea">decentralize what was once a silo</a> — with the core belief that the <strong>user should own their own data</strong>. Data no longer needs to be centrally held. This allows users control over their information, more privacy, and enhanced security.</p><p>The nation of Estonia is a good working example of this. A core tenet of the Estonian system is that <a href="https://www.newyorker.com/magazine/2017/12/18/estonia-the-digital-republic">an individual owns all recorded information about them</a>. The government’s data platform links individual servers through encrypted pathways — decentralizing its storage and letting the information live locally. This reduces the chance of Equifax-level security failures, and gives users control over that information when they request it.</p><h3>Taking Back Reputation</h3><p>We are making great progress towards taking back reputation as a society. But reputation data remains silo’d and out of the control of freelancers. <a href="https://ec.europa.eu/commission/priorities/justice-and-fundamental-rights/data-protection/2018-reform-eu-data-protection-rules_en">GDPR</a> has been a huge step towards ensuring users own the rights to their reputation data, forcing marketplaces to give the data back to the true owner: the businesses. Yet, we are still some ways away from truly decentralized and portable reputation — the most critical aspect of data for business success online.</p><p>At <a href="https://chlu.io/">Chlu</a>, we are providing a solve for both reputation data ownership and portability. We will leverage GDPR <a href="https://gdpr-info.eu/recitals/no-63/">data access rights</a> and <a href="https://www.i-scoop.eu/gdprarticle/gdpr-article-20-right-data-portability/">data portability</a> rights to give freelancers control of their reputation — to choose when, and with which marketplace, to share their data. We believe the data belongs to the freelancer, so they should control it. The <a href="https://www.ft.com/content/a72f7e56-3724-11e8-8b98-2f31af407cc8">lack of data portability</a> is a <a href="https://medium.com/doteveryone/exploring-portable-ratings-for-gig-workers-5632fd9b262e">well documented problem</a> for the gig economy. Allowing users to own their data will open up new doors to freelancers.</p><blockquote>“If Uber drivers want to change platforms and start delivering packages for Instacart, they have to start from scratch to build up a good reputation on the new site — even though they are using skills that are valuable to both sites.” <a href="https://www.wired.com/story/how-to-fix-ratings-in-the-gig-economy/">Wired</a></blockquote><p>Independent experts, commissioned by the UK, <a href="https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/627671/good-work-taylor-review-modern-working-practices-rg.pdf"><strong>recommend the portability of ratings and reviews</strong></a> to support the modern competitive digital economy. They find that with data portability, freelancers will be able to list their services on as many marketplaces as they choose, which will result in increased economic activity and also in fairer competition between platforms. With a stronger, persistent reputation, freelancers will have access to more work at better rates — increasing their financial performance.</p><p>In fact, the portability problem was one of the driving forces behind the creation of Chlu. Through our own difficulties in hiring software developers, we were able to experience first-hand how valuable transferable reputation is for freelancers. We felt that the individual should own their reputation, and be able to take it with them to any marketplace they choose. That is why we started Chlu, and <strong>leverage </strong><a href="https://w3c-ccg.github.io/did-spec/"><strong>DID</strong></a><strong>s (decentralized identifiers) and </strong><a href="https://ipfs.io/"><strong>IPFS</strong></a><strong> (a peer-to-peer, distributed file system)</strong> to store your data and tie it to your digital identity. With Chlu, users own and control their reputation.</p><p>Another important part of reputation is validity — an integral part of our solution at Chlu. Stay tuned for our next blog post where we will cover the problem of fake reviews and how businesses can fight this.</p><h4>Additional Citations</h4><p>*Chiu, Huang, &amp; Hui, 2010; Gefen et al., 2003; Grazioli &amp; Jarvenpaa, 2000; Jarvenpaa et al., 2000; Kim et al., 2008, 2012</p><p>** Bigne, Sanz, Ruiz, &amp; Aldas, 2010; Escobar-Rodríguez &amp; Carvajal-Trujillo, 2014; Kamarulzaman, 2007; Kim et al., 2009, 2011; Sanz-Blas, Ruiz-Mafe, &amp; Perez Perez, 2014; Wen, 2009, 2010</p><p>Thanks to: <a href="https://medium.com/u/66d75dada4fb">Ha Duong</a>, <a href="https://medium.com/u/98b293335bf6">Ricardo Sequerra Amram</a> for the feedback &amp; source contributions!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf226ef09ee1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chlunetwork/freelancers-take-back-your-reputation-cf226ef09ee1">Freelancers: Take Back Your Reputation</a> was originally published in <a href="https://medium.com/chlunetwork">Chlu Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bitcoin Lightning Network Tutorial — How to integrate Lightning to a crypto project]]></title>
            <link>https://medium.com/chlunetwork/bitcoin-lightning-network-tutorial-how-to-integrate-lightning-to-a-crypto-project-f48743c8644a?source=rss-e951a4b238c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f48743c8644a</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[lightning-network]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Chlu Team]]></dc:creator>
            <pubDate>Fri, 01 Jun 2018 18:05:07 GMT</pubDate>
            <atom:updated>2018-06-01T21:48:55.271Z</atom:updated>
            <content:encoded><![CDATA[<p>The Chlu team has been working closely with our friends at the MIT Digital Currency Initiative (DCI) for some time. We were honored to be invited recently by the DCI to a two day hackathon at MIT and Fidelity Labs, focused on the latest advancements in Layer 2 technology.</p><p>For those who are not aware, Layer 2 technologies focus on scaling blockchains by removing the requirement to immediately “commit” each transaction to Layer 1 blockchains. Blockchains have a fixed block size which, while necessary, constrains how much data they can fit in each block which in turn limits the transaction throughput. Thus we get the much cited ~7 transactions per second that bitcoin’s blockchain can process at peak versus the ~ 45,000 transactions per second that Visa’s network can process at peak. Layer 2 technologies are an effort to address this crucial scaling problem.</p><p>The first day of the conference focused on presentations and Q&amp;A from Layer 2 experts. The core of the discussions were around the Lightning Network (LN) which is the Layer 2 technology aimed at scaling bitcoin, but Raiden was also discussed. Research from <a href="https://lightning.engineering/">Lightning Labs</a> was presented by Conner Fromknecht and Elizabeth Stark, from <a href="https://blockstream.com/">Blockstream</a> by Andrew Poelstra, and from MIT’s <a href="https://dci.mit.edu/">DCI</a> by Neha Narula and Tadge Dryja (who described a novel approach to create “invisible smart contracts” using <a href="https://www.youtube.com/watch?v=c4slzFdykpc">Discreet Log Contracts</a> built on top of <a href="https://github.com/mit-dci/lit">LIT</a>). Other Layer 2 innovations were also presented from Sharon Goldberg &amp; Ethan Heilman of <a href="https://www.commonwealthcrypto.com/">CommonWealth Crypto</a>, Sami Makela of <a href="https://truebit.io/">TrueBit</a>, Lefteris Karapetsas of <a href="https://raiden.network/">Raiden</a>, Evan Schwartz of <a href="https://interledger.org/">Interledger</a> and Alex Bosworth of <a href="https://yalls.org/">Yalls</a> and <a href="http://www.submarineswaps.org/">submarineswaps</a>.</p><p>The second day was a hackathon focused on Layer 2. There were around 8 participating teams, one of which was <a href="https://chlu.io/">Chlu</a>. Our project for the hackathon was to investigate how we can provide a proof of payment while using Lightning Network transactions, enabling verified ratings and reviews to support the <a href="https://github.com/ChluNetwork/chlu-protocol">Chlu protocol</a>.</p><p>The rest of this article describes our efforts during the hackathon and concludes with our learnings and future work. Hopefully our write up helps the reader leverage Lightning payments in their crypto projects.</p><h3>The Hackathon — Approach</h3><p>Support for Lightning payments as part of the Chlu protocol is complex because transactions are private between the lightning channel participants and only the channel opening transaction and the final channel settlement/closing transaction need to be written to the blockchain. Thus, we don’t have the same proof of payment that we do when directly using blockchains.</p><p>We initially investigated building a LN <a href="https://www.coindesk.com/laolu-building-watchtower-fight-bitcoin-lightning-fraud/">Watchtower</a> as a potential solution, however a discussion with the original Lightning Network paper co-author Tadge Dryja convinced us this was not the right approach. Interestingly, this is because watchtowers implementations need to preserve the privacy of nodes they are helping, which is contrary to what we would want to do, i.e. to know the public key identifiers of the nodes involved in the transaction.</p><p>We decided to focus on two things in the 8 hour hackathon: first on integrating Lightning support into our Chlu demo hot wallet, and second, to investigate using LN participant signatures plus <a href="https://opentimestamps.org/">Open Timestamps</a> for the LN proof of payment/Chlu protocol.</p><p>The following outlines the approach we took to the first task: how to add Lightning payment support to an existing crypto wallet, in our case the Chlu demo hot wallet.</p><h3>Step 1: Setting up Lightning Nodes</h3><p>Bitcoind is the Bitcoin Core implementation of the bitcoin blockchain. <a href="https://github.com/lightningnetwork/lnd">lnd</a> is the Lightning implementation from Lightning Labs. To make a LN payment a user has to setup a lightning node that in turn talks to bitcoind. Once lnd and bitcoind are setup, a lightning node needs to open a channel to another lightning node. Opening a channel is effectively committing bitcoins into the lightning channel. Below we describe the LN Node infrastructure. We followed the <a href="https://dev.lightning.community/tutorial/">tutorial</a> from the lnd pages to help us with the setup.</p><h4>Step 1.1 — Create EC2 Instances with LND &amp; Bitcoind</h4><p>We setup three EC2 nodes each with bitcoind running and synchronised with the bitcoin testnet blockchain, and with lnd installed. <a href="https://github.com/alexbosworth">Alex Bosworth</a> pointed us to how lnd can run with bitcoind. He posted an excellent <a href="https://gist.github.com/alexbosworth/f4dc09951b0c648bc49f77faa9be1c27">gist</a> to help us out. We decided to run three separate LN instances for experimentation however this is essentially not required and the lnd tutorial explains how to set up different lightning nodes on the same host talking to the same bitcoind.</p><h4>Step 1.2 — Create a Lightning Wallet on each EC2 Instance</h4><p>We use lnd and lncli to create a new wallets (alice, bob and carol) on the three EC2 instance. You can use lncli create to create a new wallet for you that is not shared with the local bitcoind . Once a lightning wallet is created, the public key is used as the identifier for the lightning node.</p><p>This was an interesting detail for us to know as in the long run Chlu wants to enable lightning payments for end users without relying on the a dedicated lightning node that is online all the time. This is to avoid user’s private keys being sent to a server running a custodial wallet, and this is a vision that a lot of teams are working towards including the efforts by the <a href="https://vertcoin.org/">Vertcoin</a> team building LitBox.</p><h4>Step 1.3 — Fund theLightning Wallets</h4><p>We funded the new wallets using bitcoin test faucet at <a href="https://testnet.manu.backend.hamburg/faucet">https://testnet.manu.backend.hamburg/faucet</a>.</p><p>Our three nodes are now identifiable from their public key hash. We can see their identity by running lncli getinfo .</p><p>Alice (027bda)</p><pre>027bda4485e6be6238df4e14666a721e04aea485d5717ebdd43235a46ce3e16dce@34.196.116.222:9735</pre><p>Bob (03a488)</p><pre>03a488dd9f3e19956c58ee78967b098111fe5e37fa94d57abf3e4018e039c9b0af@52.91.162.42:9735</pre><p>Carol (03f105)</p><pre>03f1055ab2be1da3fe6225f99f1405f54bc2fc8c564f3401b249d97dc4e82efabf@54.90.73.105:9735</pre><h4>Step 1.4 Connect our lightning nodes</h4><p>We next created a P2P network connection between the nodes.</p><p>From Alice’s node we ran lncli connect 03a488..@xxx:yy to connect to Bob’s lightning node, and then from Bob’s node we run lncli connect 03f105..@xxx:yy</p><p>Once the connection is setup we can see that Bob is in Alice’s list of peers by running lncli listpeers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/865/0*wtxc9FlWAhOriCAR." /><figcaption>Alice’s peers include Bob (03a488)</figcaption></figure><h4>Step 1.5 Create Lightning Channels</h4><p>The next step is to create channels between our nodes. But first we explain what a channel is. A channel is best defined on <a href="https://lightning.network/">https://lightning.network/</a> as:</p><blockquote>Two participants create a ledger entry on the blockchain which requires both participants to sign off on any spending of funds. Both parties create transactions which refund the ledger entry to their individual allocation, but do not broadcast them to the blockchain. They can update their individual allocations for the ledger entry by creating many transactions spending from the current ledger entry output. Only the most recent version is valid, which is enforced by blockchain-parsable smart-contract scripting. This entry can be closed out at any time by either party without any trust or custodianship by broadcasting the most recent version to the blockchain.</blockquote><h4>Create a channel between our lightning nodes</h4><p>To open a channel we need to keep a few things in mind</p><ol><li>How much capacity we want in the channel? The capacity of the channel determines what is the maximum size of payment that can be made through a channel, and if this channel is routing payments through it, the capacity will influence if the payment can go across the channel.</li><li>The capacity of a channel is not the same in both the directions, in fact, a channel can send up to a certain amount and receive a different amount. The amounts depend on the balance of the channel. Each node maintains a local balance and a remote balance — which tracks the amount of bitcoin committed to the channel by the two parties.</li><li>The screenshot below shows the channel between Bob and Carol. There is the capacity at 1,000,000 and local balance and remote balance are set to 499,819 and 500,000. This is because we created the channel with local amount set to 1,000,000 and pushed 500,000 to the remote balance. The difference went as the fee for publishing the channel creation (funding transaction) to the bitcoin testnet.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*kbw7dslddbT5tz6Mwowb7Q.png" /><figcaption>Active channel between Alice and Bob as viewed on Alice’s node (299,819 and 200,000 Satoshi)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*yd2W4cDtbB3Lne90-fTyqg.png" /><figcaption>Our active channel between Bob and Carol as viewed from Bob’s node (499,819 and 500,000 Satoshi)</figcaption></figure><p>Our channel balances at the end of our setup were as follows:</p><p>Alice to Bob: 299,819</p><p>Bob to Alice: 200,000</p><p>Bob to Carol: 499,819</p><p>Carol to Bob: 500,000</p><h3>Step 2 — Making LN Payments</h3><p>With our channels setup, we are now ready to send payments from Alice to Bob and once that worked, from Alice to Carol — finally getting to that “network” in Lightning Network.</p><h4>Step 2.1 : Make a Single Hop Payment</h4><p>To request a payment, a node has to create an “invoice”, which is defined as by <a href="https://github.com/lightningnetwork/lightning-rfc/blob/master/11-payment-encoding.md">lightning protocol</a> as</p><blockquote>A simple, extendable QR-code-ready protocol for requesting payments over Lightning.</blockquote><p>So to make a payment from Alice to Bob, the following steps need to happen:</p><ol><li>Bob creates an invoice using lncli addinvoice --amt=100000 to create a payment invoice of 100,000 Satoshi. Note that the invoice does not identify the public key that should make the payment. This allows lightning supporting checkouts to show the invoice as a QR code or a link.</li><li>Bob sends the invoice to Alice using any means available — be it a checkout button or a QR code to pay using a lightning enabled wallet.</li><li>Bob pays the invoice by using lncli sendpayment --pay_req=&lt;INVOICE&gt;</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*LrKsnBYHmg2qLo85TwE1WA.png" /><figcaption>Alice pays Bob 100,000 Satoshi. New balance: 199,819 and 300,000</figcaption></figure><p><strong>Note that for a direct payment between two lightning nodes, there was no fees, zero, nada, zilch, niente.</strong></p><p>After the payment from Alice to Bob our new balances are</p><p>Alice to Bob: 299,819</p><p>Bob to Alice: 200,000</p><p>Bob to Carol: 499,819</p><p>Carol to Bob: 500,000</p><h4>Step 2.2 Making Multi-hop Payments</h4><p>Now comes the fun part of making payments over the network, with payments routed through intermediaries.</p><p>Lightning network routes payments over channels. lnd uses provides an onion routing implementation to preserve privacy of the sending and receiving nodes.</p><p>We wanted to try and make a multi-hop payment from Alice to Carol to take the routing sub-system for a drive, and it turned out to be a fun experience because we kept running into the dreaded UnknownNextPeer error.</p><p>We learnt that most likely this is caused by the lack of txindex support in our bitcoind. We restarted our bitcoind with -reindex and -txindex flags. Once transaction indexing had finished we tried making a multi-hop payment by going through the following steps:</p><ol><li>Carol creates an invoice, just as Bob created one in the single-hop payment approach. lncli addinvoice --amt=10000</li><li>Carol sends the invoice to Alice</li><li>Alices executes sendpayment by running lncli sendpayment --pay_req=&lt;INVOICE&gt;</li></ol><p>At this point we still ran into UnknownNextPeer issue, so we decided to close all channels that were not created by us and were automatically created by lnd’s autopilot feature. Once we closed all the channels and tried the multi-hop payment it went through without any problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e4qrTUJeZhZlDfx7aq1iRw.png" /><figcaption>Multi-hop payment from Alice to Carol</figcaption></figure><p>Once back from the hackathon, we reported our experience with the problems while sending a multi-hop payment as an <a href="https://github.com/lightningnetwork/lnd/issues/1304">issue</a> on lnd’s repo.</p><h3>Step 3 — Integrate Lightning with Chlu Wallet</h3><p>At this point we had multihop LN payments working from the command line between our LN channels on our 3 EC2 instances. However, our first goal of the day was enable Lightning payments from our demo Chlu bitcoin web wallet which also provides an implementation of the Chlu protocol.</p><h4>Step 3.1 — Run LN-Service on our EC2 LN Node</h4><p><a href="https://github.com/alexbosworth/ln-service">ln-service</a> is an excellent wrapper around LND written by Alex Bosworth, exposing many of the command line equivalents via a REST api. While not production ready, it was perfect for a quick integration between our EC2 LN Nodes and our Chlu web wallet. We setup ln-service on our lightning node for Alice and given it exposed a REST api, it was trivial to integrate with our Chlu web wallet.</p><h4>Step 3.2 — Make a payment to another LN wallet</h4><p>We decided to try to make an LN payment from our Chlu web wallet to another LN web wallet, thus testing a full payment over multiple hops. HTLC.me, also developed by Alex, allows you to simply create a LN web wallet and fund it, which we did. Thus we had our Chlu LN web wallet and our HTLC.me LN web wallet and were ready to go.</p><p>With our ln-service setup on our LN node for Alice, and our Chlu wallet changed to make http calls to the service for sending a lightning payment, we then generated an invoice from our htlc.me wallet and were successfully able to send a multi-hop payment to our wallet on htlc.me. This also worked because we had multiple channels open from the ln node running ln-service, these channels were opened by the autopilot mode.</p><p>The following screenshot show our web wallet that uses our reference implementation of the Chlu protocol written in javascript. The first screenshot shows a payment being made using bitcoin blockchain and op_return, while the second one shows the use of LN.</p><h3>Achievements</h3><ol><li>We were able to make direct &amp; multihop payments between ln nodes</li><li>We successfully deployed ln-service that provides an easier API to talk the lnd gRPC.</li><li>We were able to enable lightning payments from our Chlu wallet</li></ol><h3>Next Steps</h3><p>While it was great to be able to integrate LN payments into our Chlu web wallet and our first hackathon goal was a resounding success, questions remain about how to really provide consumer wallets in production with this approach. Could spawning docker instances running lnd daemons be a good approach? How can that scale for a wallet provider and what about trustlessness?</p><p>For the second goal of enabling proof of payment for lightning payments, discussions with Alex and Tadge pointed to using DIDs signatures and OpenTimeStamp to save the reference to the proof of payments for future verification of reviews. That topic will be the subject of a future article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f48743c8644a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chlunetwork/bitcoin-lightning-network-tutorial-how-to-integrate-lightning-to-a-crypto-project-f48743c8644a">Bitcoin Lightning Network Tutorial — How to integrate Lightning to a crypto project</a> was originally published in <a href="https://medium.com/chlunetwork">Chlu Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is wrong with current reputation systems?]]></title>
            <link>https://medium.com/chlunetwork/what-is-wrong-with-current-reputation-systems-7955596b35df?source=rss-e951a4b238c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7955596b35df</guid>
            <category><![CDATA[trustless]]></category>
            <category><![CDATA[decentralized]]></category>
            <category><![CDATA[reputation]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[chlu]]></category>
            <dc:creator><![CDATA[Chlu Team]]></dc:creator>
            <pubDate>Fri, 28 Jul 2017 18:14:54 GMT</pubDate>
            <atom:updated>2017-07-28T18:29:55.270Z</atom:updated>
            <content:encoded><![CDATA[<p>Reputation has been at the center of how we make socioeconomic decisions for millennia. Reviews from our peers are central to how we make purchasing decisions — and yet, we don’t really have a good model for establishing the trust needed to have friction free engagement.</p><p>The value of reputation is now a well-established concept when it comes to online transactions. From hiring a cleaner to choosing a restaurant to eCommerce, reviews are invaluable when making a decision. By 2020, global eCommerce will be a <a href="https://www.emarketer.com/Article/Worldwide-Retail-Ecommerce-Sales-Will-Reach-1915-Trillion-This-Year/1014369">4 trillion dollar industry</a>, and <a href="https://econsultancy.com/blog/9366-ecommerce-consumer-reviews-why-you-need-them-and-how-to-use-them/">around 61%</a> of these customers read reviews before deciding whether or not to buy.</p><p>Some marketplaces have been successful at creating a proxy for this trust that over time establishes reputation. However, online reputation management is deeply flawed in a couple of key ways.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LEs41ln49KZppNjKiO6iFg.png" /><figcaption>The current flawed reputation systems</figcaption></figure><h3><strong>1. Your reputation isn’t portable</strong></h3><p>Marketplaces such as Amazon, eBay, and UpWork have created their own reviews and ratings systems to allow vendors to establish their reputation over time. Unfortunately, all of these solutions are <em>walled gardens — </em>managed ecosystems that are locked and closed. The reputation is non-transferable externally. Your reputation on eBay is meaningless on Amazon.</p><p>In an ideal world, <em>you</em> should own your data — not the marketplace.</p><p>There is huge value in having an established reputation that is portable across all ecosystems. No single organization should be a gatekeeper that must be trusted with a vendor’s reputation data. The future is <strong>trustless</strong>!</p><h3><strong>2. It is easy to cheat and game the current systems</strong></h3><p>From established players like TrustPilot to new entrants like Feefo, the problem is evident: the current systems are prone to being gamed. It is clear why — there are substantial incentives to cheat the system. Going from a 3-star rating to a 5-star rating gets a business <a href="https://www.brightlocal.com/learn/review-search-click-through-study/">25% more clicks</a> from Google Local Pack. The importance of ratings cannot be overstated.</p><p>While players like TrustedShops, Reevoo, and of course even Amazon themselves are trying to find solutions, fake reviews abound. Nearly <a href="http://people.hbs.edu/mluca/fakeittillyoumakeit.pdf">1 out of 5 reviews is marked as fake</a> by Yelp’s algorithm. Even with a solution like TrustedShops where <em>proof of purchase </em>is necessary to leave a review, the reality is that ownership of the data in the purchasing chain is broken several times along the way.</p><p>Google even uses a long list of independent vendors that provide inputs to establish their seller ratings, and still it appears that approximately 15–35% of these are still fake.</p><p>How can this problem be solved? A universal platform based on real-world payments makes gaming the system far more difficult and costly. <strong>Decentralized</strong> ownership of the data coupled with required proof of purchase can eliminate fake and deceptive reviews.</p><h3><strong>The need for a universal, open, free-to-use reputation is clear</strong></h3><p><em>“An aggregated online reputation having a real-world value holds enormous potential for sectors where trust is fractured: banking; e-commerce, where value is exponentially increased by knowing who someone really is; peer-to-peer marketplaces, where a high degree of trust is required between strangers; and where a traditional approach based on disjointed information sources is currently inefficient, such as recruiting.” —</em><a href="http://www.wired.co.uk/article/welcome-to-the-new-reputation-economy"><em> </em>Wired</a></p><p>Many businesses have tackled this problem over the last five years, and none have truly succeeded.</p><h4>That is why we are introducing <strong>Chlu </strong>— the world’s first truly open reputation platform.</h4><p>The future of reputation is decentralized.</p><p>Stay tuned…</p><p>-The <a href="https://medium.com/u/e951a4b238c7">Chlu Team</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7955596b35df" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chlunetwork/what-is-wrong-with-current-reputation-systems-7955596b35df">What is wrong with current reputation systems?</a> was originally published in <a href="https://medium.com/chlunetwork">Chlu Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to the Chlu blog]]></title>
            <link>https://medium.com/chlunetwork/welcome-to-the-chlu-blog-c186c4192b47?source=rss-e951a4b238c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c186c4192b47</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[chlu]]></category>
            <category><![CDATA[reputation]]></category>
            <dc:creator><![CDATA[Chlu Team]]></dc:creator>
            <pubDate>Wed, 26 Jul 2017 13:20:51 GMT</pubDate>
            <atom:updated>2017-07-26T13:20:51.468Z</atom:updated>
            <content:encoded><![CDATA[<p>Follow us here to get updates and announcements as we launch the world’s first truly open reputation platform. The <a href="https://medium.com/u/e951a4b238c7">Chlu Team</a> is excited to finally show you what we have been working on.</p><p>Stay tuned!</p><p>-Team Chlu</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c186c4192b47" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chlunetwork/welcome-to-the-chlu-blog-c186c4192b47">Welcome to the Chlu blog</a> was originally published in <a href="https://medium.com/chlunetwork">Chlu Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>