<?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 Andy Tom on Medium]]></title>
        <description><![CDATA[Stories by Andy Tom on Medium]]></description>
        <link>https://medium.com/@andycf?source=rss-e3b0d0b2eb9d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8woxTvBhVGSOM7IKSTB54A.jpeg</url>
            <title>Stories by Andy Tom on Medium</title>
            <link>https://medium.com/@andycf?source=rss-e3b0d0b2eb9d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 01:17:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andycf/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 Launch an Expo Managed App to Beta Testers in 2020]]></title>
            <link>https://codeburst.io/how-to-launch-an-expo-managed-app-to-beta-testers-in-2020-61b5121089c8?source=rss-e3b0d0b2eb9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/61b5121089c8</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Andy Tom]]></dc:creator>
            <pubDate>Sat, 22 Aug 2020 21:18:32 GMT</pubDate>
            <atom:updated>2020-08-22T21:18:32.356Z</atom:updated>
            <content:encoded><![CDATA[<h4>My experience launching an Expo Managed App to Apple’s TestFlight for user testing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bKduc9Q2QRvTeO1_" /><figcaption>Photo by <a href="https://unsplash.com/@spacex?utm_source=medium&amp;utm_medium=referral">SpaceX</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Expo is a platform for making native apps using languages that web-developers are familiar with (Javascript + React), streamlining the process and learning curve of launching an app.</p><p>In this article, you will learn how to launch an Expo managed app to TestFlight so users can start to experiment and test your app. Throughout the guide, I will attempt to give rough estimates of time and cost where appropriate.</p><h4>You will need:</h4><ul><li>An email.</li><li>A debit/credit card to pay for Apple Developer.</li><li>An apple computer, preferably macOS.</li></ul><h3>Let’s get started</h3><h4><strong>Register an Apple Developer Account</strong></h4><p>To distribute an app to iOS Apple Users, you will need to open a developer account and enroll in the <a href="https://developer.apple.com/programs/enroll/">Apple Developer Program</a>. Without enrolling in the Apple Developer Program, you will be able to access basic features such as downloading Xcode and associated tools, as well as access to forums, documentation, and guides on building on the iOS platform. However, you will not be able to access <em>AppConnect</em><strong> </strong>and<strong> </strong><em>TestFlight</em> which are required to distribute your app. At the time of writing, the cost for enrolling in the Apple Developer Program is $149 AUD/annually.</p><ol><li>Visit <a href="https://developer.apple.com/account">https://developer.apple.com/account</a> and sign in with an Apple ID, if you don’t have one yet, register one with the email that you want to associate your app with.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_FugxWDdhi2ITNNHE8iVGQ.png" /><figcaption>Apple Developer Dashboard when not enrolled in the developer program.</figcaption></figure><p>2. Enroll in the Developer Program by following the steps on <a href="https://developer.apple.com/programs/enroll/">https://developer.apple.com/programs/enroll</a>. You will need to enter your personal information, select your entity type (individual, business, not for profit, etc.) and pay the annual enrollment fee.</p><p>3. Return to <a href="https://developer.apple.com/account/">https://developer.apple.com/account</a> and wait roughly 10 minutes for Apple to process your payment and you should have additional access to <em>Program Resources.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/273/1*Louxrk65Dzy9m_mS8mo80Q.png" /></figure><h4><strong>Creating a bundle identifier</strong></h4><p>Once you have access to the full features of the Apple Developer Program, you will need to generate a bundle identifier for your Expo App.</p><ol><li>Revisit your developer dashboard and select <em>Certificates, Identifiers &amp; Profiles</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*w4xPbIyoI-BDzYG351lVRg.png" /></figure><p>2. You should be on the URL <a href="https://developer.apple.com/account/resources/certificates/list">https://developer.apple.com/account/resources/certificates/list</a> where you want to navigate to <em>Identifiers </em>on the sidebar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/210/1*uYICCVbAZhOIrmBffGeeIg.png" /></figure><p>3. Clicking on the blue add icon, you will then run through the flow to create a new identifier — select App IDs, press continue, and select the App box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXDugOC_P0c75s4t7ZckHg.png" /></figure><p>4. At this step, you will then register an App ID and will be able to configure the capabilities that your app can handle such as Apple Pay. For the purpose of this guide, we are going to leave these configurations for production.</p><p>5. When you are on the <em>Register an App ID </em>screen. Create an explicit bundle ID using Apple’s recommendations for a reverse-domain-name (com.&lt;YOUR-DOMAIN-NANE&gt;.&lt;YOUR-APP-NAME&gt; and press continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tlXsWDUGoIsidkhOLEOPQA.png" /></figure><p>6. Congratulations you have registered your first app with Apple.</p><p>Now let’s return to our Expo App Project.</p><h4><strong>Add an app icon</strong></h4><p>Before we run through the expo publish and build flow, we need to create an App Icon. The icon will need to be 1024px x 1024px in size. You can create this icon using your preferred design tool.</p><h4><strong>Configure your app.json</strong></h4><p>In an Expo Managed App, the app.json file is used to configure all the meta-data and settings for your app. If you need help setting up your app.json view their guide at <a href="https://docs.expo.io/workflow/configuration/">https://docs.expo.io/workflow/configuration/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*LmpTWxVBBwPTrD-vqe2JCw.png" /></figure><p>Attached above is the example of the app.json I have for my app. The main steps you have to configure are:</p><ol><li><em>icon</em> — add the path to the icon you created in <strong>Step C </strong>within your project (i.e ../../assets/icon.png)</li><li>Under <em>ios,</em> you want to configure your build number (the number you should manage and increment depending on the version of your app that you want to publish) and bundle identifier generated in <strong>Step B.</strong></li></ol><p>It is time to run through Expo’s Standalone Build Workflow.</p><h4><strong>Running Expo CLI commands to publish and build your app.</strong></h4><p>In the Expo Managed Workflow, Expo does most of the heavy lifting for you.</p><ol><li>If you haven’t already, you will need to install the Expo CLI</li></ol><p>Using NPM (node package manager):</p><pre>npm install -g expo-cli</pre><p>Check Expo CLI is successfully installed with:</p><pre>expo --version</pre><p>2. Once you have Expo CLI installed, you can then run their <em>build </em>command for ios within your app project root. You will then be prompted to log in to your Expo account if you have not logged in already.</p><pre>expo build:ios</pre><p>3. Follow the command line instructions, you will need to log in with the Apple ID that you used to enroll in the Developer Program in <strong>Step A.</strong></p><pre>$ expo build:ios<br>[16:44:37] Checking if current build exists...<br><br>[16:44:37] No currently active or previous builds for this project.<br>[16:44:37]<br>We need your Apple ID/password to manage certificates, keys<br>and provisioning profiles from your Apple Developer account.<br><br>Note: Expo does not keep your Apple ID or your Apple ID password.<br><br>? What&#39;s your Apple ID? xxx@yyy.zzz<br>? Password? [hidden]<br>✔ Authenticated with Apple Developer Portal successfully!<br>[16:44:46] You have 4 teams associated with your account<br>? Which team would you like to use? 3) ABCDEFGHIJ &quot;John Turtle&quot; (Individual)<br>✔ Ensured App ID exists on Apple Developer Portal!<br>[16:44:59] We do not have some credentials for you: Apple Distribution Certificate, Apple Push Notifications service key, Apple Provisioning Profile<br>? How would you like to upload your credentials? (Use arrow keys)<br>❯ Expo handles all credentials, you can still provide overrides<br>  I will provide all the credentials and files needed, Expo does limited validation</pre><p>4. In the steps, you will have the opportunity to configure credentials and certificates, but for your first build you may want to let Expo handle all of them for you.</p><p>5. Once you have inputted all your configurations, Expo will start to publish and build your app. This build may take a while depending on how busy Expo’s build machines are (see <a href="https://expo.io/turtle-status">https://expo.io/turtle-status</a>). The command line will also print out a URL that you can follow. Alternatively, visit your Expo account dashboard at <strong><em>https://expo.io/dashboard/&lt;YOUR-EXPO-ACCOUNT-SLUG&gt;/builds</em></strong> to view the status of your build.</p><p>7. Once the build has been completed, you will be able to visit your Expo Dashboard (example URL above) where you can then download the .IPA artifact of your app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BYJ-sSsCo-0WXzmzPM_1Ng.png" /></figure><p>8. You will need this .IPA file to publish your app to TestFlight and the Appstore.</p><p>Let’s go back to our Apple Developer Account.</p><h4><strong>Creating our app in App Store Connect</strong></h4><p>In this step, you will have to return to your Apple Developer dashboard and discover App Store Connect.</p><p>This is where you can manage your iOS app, add testers, and submit to the AppStore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/271/1*1uhlZ845y7O-jCQmMrQa9w.png" /><figcaption>Select App Store Connect</figcaption></figure><ol><li>By clicking the App Store Connect button on the Apple Developer Dashboard you should end up at the URL <a href="https://appstoreconnect.apple.com/apps">https://appstoreconnect.apple.com/apps</a>, press the blue + icon and select <em>New App </em>in the dropdown.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cyO0fNt4ekAIkfaP29m_Yg.png" /></figure><p>2. You will be prompted with a <em>New App </em>modal, this is where you can configure details about the app that you are able to create. In this step, the most important field is selecting the <em>Bundle ID </em>that you created in the earlier step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*kaJPVyfDF72AM5EwWQqofA.png" /></figure><p>After we have created the app in App Store Connect we are ready to upload our app.</p><h4><strong>Uploading our App to App-Connect</strong></h4><p>We will need to install a macOS application that is required to upload our .IPA to App Store Connect.</p><ol><li>Visit <a href="https://apps.apple.com/us/app/transporter/id1450874784?mt=12">https://apps.apple.com/us/app/transporter/id1450874784?mt=12</a> on the Mac App Store and download the application.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wTS1wqa_LVx-6xWvW_Vj5Q.png" /></figure><p>2. When <em>Transporter </em>has finished downloading, launch the application. You will then be prompted to log into your Apple ID, use the credentials of the Apple ID that you registered in the first step (“Register an Apple Developer Account”)</p><p>3. Click on the + icon which prompts a file explorer, locate your .IPA file that you have downloaded from your Expo dashboard and upload it.</p><p>4. Select <em>Deliver </em>on the app you want to upload and Apple will begin to upload the app to App Store Connect.</p><h4><strong>Viewing our app on App Connect and adding Beta Testers</strong></h4><p>After using the transporter to deliver the app to App-Connect, we need to wait for Apple to build our app as well as beta review it before our users can download the app on TestFlight.</p><ol><li>Return to <a href="https://appstoreconnect.apple.com/apps">https://appstoreconnect.apple.com/apps</a> and click on the app you have just uploaded. Here we can view the status of our app (Building, Testing) as well as configure our app details for when we want to publish to the AppStore.</li><li>For beta testing we only care about adding users to our iOS build, this is done through the TestFlight tab. In this panel, we can view the status of our iOS build (<em>Building or Testing)</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*D9PXBuDdhwX_wX7smXHPOA.png" /></figure><p>3. When our app has finished building (which took ~1.5 hours) the app will need to be reviewed by Apples Beta Review Team (which took ~1.5 days for me). Meanwhile, we can begin to add our beta testing users who will receive an email invite once the build has been approved.</p><p>4. Visit the left-hand navigation and click on + to add a new group of testers. Here I have made a group called <em>Beta Testers</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/219/1*OsU5yAq6jkO-3iHcx6F0EA.png" /></figure><p>5. Clicking into the group allows you to view an interface that lets you add the emails of the users to test your app.</p><p>At the finalization of this step, our app is now able to be downloaded on TestFlight by our users to test!</p><p>What if we need to publish new bug fixes and updates to our users?</p><h4><strong>Over-The-Air Updates from Expo</strong></h4><p>So you’ve finally completed this guide to launching your app to beta testers on TestFlight, now you’re probably wondering if you need to follow this guide every time you fix a bug or deploy a new feature on your app. Luckily, the answer is no. Expo provides a quick and easy way to do this through OTA updates.</p><p>To publish any changes to your users, all you need to do is run</p><pre>expo publish</pre><p>within your project directory.</p><p>After it has finished publishing, your users will need to download the update (automatically downloaded when a user exits the app and relaunches) to view the latest changes.</p><p>To configure how and when users receive updates, you can visit their comprehensive OTA guide here <a href="https://docs.expo.io/guides/configuring-ota-updates/">https://docs.expo.io/guides/configuring-ota-update</a>s which show creative ways to make the update seamless and non-blocking to your users.</p><h3>Wrapping up</h3><p>In this guide, you have learned how to launch an Expo-managed app on TestFlight. You should now also be able to easily publish changes to your app so that your users can receive and test following app iterations.</p><p>Happy testing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61b5121089c8" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/how-to-launch-an-expo-managed-app-to-beta-testers-in-2020-61b5121089c8">How to Launch an Expo Managed App to Beta Testers in 2020</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our hospitals are overrun. How we made a COVID-19 SMS Bot to help out.]]></title>
            <link>https://medium.com/@andycf/our-hospitals-are-overrun-how-we-made-a-covid-19-sms-bot-to-help-out-9f217b06bb0?source=rss-e3b0d0b2eb9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f217b06bb0</guid>
            <category><![CDATA[health]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Andy Tom]]></dc:creator>
            <pubDate>Sat, 04 Apr 2020 23:12:46 GMT</pubDate>
            <atom:updated>2020-04-04T23:12:46.305Z</atom:updated>
            <content:encoded><![CDATA[<h3>Our hospitals are overrun. How we made a COVID-19 bot to help out.</h3><h4>There are more ways to help out than we think.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KD-4sN42FTqzCPVn" /><figcaption>Photo by <a href="https://unsplash.com/@olegmagni?utm_source=medium&amp;utm_medium=referral">Oleg Magni</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>COVID-19 Prescreening SMS Bot</h3><p><em>Problem, Objective and Solution write up courtesy of </em><a href="https://medium.com/u/10e86cbdc19"><em>Oliver</em></a><em>.</em></p><h4>Problem:</h4><p>Existing health services are overwhelmed by inquiries (online and web inquiries, call centers, ER visits, in-person GP visits).</p><p>Many are false positives (A person may feel sick but do not have COVID-19).</p><p>This takes testing resources away from true positives (A person who feels sick and has COVID-19).</p><p>In British Columbia, Canada, it takes over 24 hours to receive a generic response from a human SMS operator. A chatbot is a practical application because this task is repetitive and follows a sequential set of rules, a chatbot is a practical application. It’s also applicable to all regions of the world.</p><h4>Objective:</h4><p>Inform concerned citizens at scale and reduce the burden on healthcare professionals.</p><h4>Proposed Solution (MVP):</h4><p>Supplement human-operated SMS with a chatbot, which follows the same self-assessment protocol. In Alberta, Canada, this is the current <a href="https://myhealth.alberta.ca/journey/covid-19/Pages/COVID-Self-Assessment.aspx">self-assessment tool (web-based)</a>. It’s the same across all provinces. With a few tweaks, this could be applied to NSW (where I reside).</p><p><em>The following section is for those interested in the technology and problems faced in our solution.</em></p><p><em>If you are not interested in this, please scroll to the end where you can find out how you can help fight COVID-19.</em></p><h4>Twilio Autopilot &amp; Functions</h4><p>Twilio is a software company that allows companies and individuals to leverage their APIs and tools to create different types of communication channels (messaging, video, bots) with ease.</p><p>Their product called Autopilot allows us to utilize NLP (natural language processing) to develop a robust chatbot. In our case this allows our bot to understand different variations of yes or no (y, yeh, yup, n, nah, nope) from the user input.</p><p>To create a flow inside Autopilot we create a <strong>task</strong> in JSON format that contains an array of Autopilots Actions:</p><ul><li>Say — bot replies or displays a message</li><li>Listen — bot listens for user input</li><li>Redirect — sends the user input to a URL or directs to a specified task</li></ul><p>To view the entire action list, visit the docs here:</p><p><a href="https://www.twilio.com/docs/autopilot/actions">Actions Overview</a></p><p>Below is a copy of one of the tasks we specified for our flow.</p><pre>{<br> &quot;actions&quot;: [<br>  {<br>   &quot;collect&quot;: {<br>    &quot;name&quot;: &quot;collect_critical&quot;,<br>    &quot;questions&quot;: [<br>     {<br>      &quot;question&quot;: &quot;Are you having severe difficult breathing or chest pain?&quot;,<br>      &quot;name&quot;: &quot;critical_question&quot;,<br>      &quot;type&quot;: &quot;Twilio.YES_NO&quot;<br>     }<br>    ],<br>    &quot;on_complete&quot;: {<br>     &quot;redirect&quot;: {<br>      &quot;method&quot;: &quot;POST&quot;,<br>      &quot;uri&quot;: &quot;<a href="https://licorice-gnat-6331.twil.io/critical_question">https://licorice-gnat-6331.twil.io/critical_question</a>&quot;<br>     }<br>    }<br>   }<br>  }<br> ]<br>}</pre><p>The bot reads the JSON and maps through the actions array and performs each valid action within the array until it reaches the end.</p><p>In our example, our first action displays a message “Are you having severe difficulty breathing or chest pain?” while waiting for a user input (which is expected to be in the type of Twilio.YES_NO — boolean).</p><p>When the user has submitted a valid input this response is then sent to our Twilio Function that handles the boolean logic.</p><pre>exports.handler = function(context, event, callback) {</pre><pre>// Retrieve and parse the entire memory tree which shows previous actions until this point<br>    let memoryTree = JSON.parse(event.Memory);</pre><pre>// Initialise the action array to pass onto the next task<br>    let actions = [];<br>    // Initialise the response object we are going to append to our actions array<br>    let response;</pre><pre>//Get the user input <br>    let result = memoryTree.twilio.collected_data.collect_critical.answers.critical_question.answer;</pre><pre>// The logic flow is handled here<br>    if(result === &quot;Yes&quot;){<br>        response = {<br>          &quot;redirect&quot;: {<br>            &quot;method&quot;: &quot;POST&quot;,<br>            &quot;uri&quot;: &quot;task://Call_811&quot;<br>          }<br>        };<br>        actions.push(response);<br>    } else {<br>        result = {<br>          &quot;redirect&quot;: {<br>            &quot;method&quot;: &quot;POST&quot;,<br>            &quot;uri&quot;: &quot;task://Moderate_Question&quot;<br>          }<br>        };<br>        actions.push(response);<br>    }</pre><pre>// We create the response object to be passed back <br>    let responseObject = {<br>        &quot;actions&quot;: actions<br>    };</pre><pre>callback(null, responseObject);<br>};</pre><p>This Task-Function flow is repeated for each COVID-19 prescreening question where they are either prompted with the advice to:</p><ul><li>Call 911 (Emergency Department)</li><li>Call 811 (Canada COVID-19 hotline)</li><li>Stay home/practice social distancing as testing is not required.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*kZSw5fzvpIJOOza_AonB2Q.png" /><figcaption>Example of flow on Twilio simulator</figcaption></figure><h4>How you can help</h4><p>I found <a href="https://helpwithcovid.com/">https://helpwithcovid.com</a> from a tweet on twitter while browsing amidst the COVID-19 panic. That is where I met Oliver Leung who had posted this project with the request for volunteers.</p><p>Helpwithcovid is a website based on San Francisco and supported by Y Combinator where individuals who have ideas on how to support essential services during this Coronavirus Pandemic post in hopes of finding volunteers to help.</p><p>The projects range from design/engineering to skills like funding/social giving. You can filter by skill or project type which lets you map your interest and skills to projects that you may be able to help in.</p><p>We would like to thank those in the front-line (nurses, doctors, surgeons, and healthcare service workers) who are doing their best to support the rest of society.</p><p>We also hope everyone stays safe and practices social distancing as we try to flatten the curve. Together we can overcome this obstacle.</p><p><a href="https://helpwithcovid.com/projects">All Projects</a></p><p><em>Final words: If you know any countries or local states that could utilize our SMS bot please reach out by emailing me or Oliver at andyteechenfang@gmail.com and emailoliver@gmail.com.</em></p><p><em>If you have any feedback and product improvements, please reach out.</em></p><p><em>This article was originally published on </em><a href="https://medium.com/u/4a8a924edf41"><em>How Hackers Start Their Afternoons</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f217b06bb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why does 8x need a token?]]></title>
            <link>https://medium.com/@andycf/why-does-8x-need-a-token-6bd72ce9cd31?source=rss-e3b0d0b2eb9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bd72ce9cd31</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Andy Tom]]></dc:creator>
            <pubDate>Tue, 07 Aug 2018 02:24:34 GMT</pubDate>
            <atom:updated>2019-08-08T10:38:40.151Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>“Why does 8x Protocol need a token/coin?”</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*CSgkUL9PNQr4gqHpf5xRRw.png" /></figure><p>This post is aimed to help our audience grasp a better understanding of the concepts behind 8x Protocol. I have attempted to write towards the wider audience by including clarifications and diagrams while also allowing those who are interested in understanding it more deeply to do so through links and code references.</p><blockquote><strong>Question to answer: “Why does 8x Protocol need a token/coin?”</strong></blockquote><p>In this article, I will be answering the common question above by taking a closer look into how the system operates as well as introducing some economics concepts that will be apparent in the 8x Protocol ecosystem.</p><p><em>Before we begin, I know some of you hate reading (despite browsing medium) so here:</em></p><p><strong>TLDR </strong>— The 8x Token is used to incentivise a fair economy for the 8x Repeaters (service node operators who process the subscription transactions), by fair economy I do not mean that they are rewarded in 8x Tokens but that the 8x Token is used to solve issues such as the claiming problem, to prevent service nodes acting in a malicious way and also to facilitate some common economics principles.</p><h4>The 8x Protocol Ecosystem</h4><p>To understand the context behind the 8x Token we must first clarify the parties involved in the 8x Protocol system:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*ZOKp3CDzaGCHh3QWGW6nDQ.png" /></figure><ul><li><strong>Subscription plan creators </strong>(generally but not limited to businesses and services) — subscriptions plans are made using function createPlan()and subscriptions are then made through function createSubscription()For a more basic understanding (without needing to understand the code), these users make plans that include important information such as the subscription price and also subscription time period (e.g month, years). For a more technical view, I have attached a code snippet for function createPlan()that references the parameters that need to be input for a plan creation.<strong><em>View complete contracts here: </em></strong><a href="https://github.com/8xprotocol">https://github.com/8xprotocol</a></li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8b0a2fc40d0898fb31edc58ede84429b/href">https://medium.com/media/8b0a2fc40d0898fb31edc58ede84429b/href</a></iframe><ul><li><strong>Subscription consumers </strong>(individuals who want to make repeating payments with cryptocurrencies) — “subscribers” interact with the subscription contracts through interfaces (front-end). The MVP for this will be launched as a web portal in which businesses will redirect or integrate into their payment process when consumers opt into subscription plans. <em>Note that consumers pay their subscriptions with the currency specified by the plan creator (</em><strong><em>not 8x tokens</em></strong><em>).</em></li></ul><p><strong>“If both subscription consumers and creators do not transact or interact with the 8x Token than what’s the use?”</strong></p><ul><li><strong>Service Node Operators</strong>(8x Repeaters) — this group is an integral part of the ecosystem, their role is to process scheduled transactions (by calling the smart contract at the time it is due) and earn a fee by doing so.</li></ul><p><strong>This introduces the 8x Token.</strong></p><h4>8x Token Utility</h4><p>Unlike most systems, the service node operators are not rewarded in 8x Tokens for processing a transaction. The reward amount is determined as a percentage set by the subscription creator and in the same currency set in the subscription plan.</p><p>In order for service nodes to be eligible to process a subscription transaction they are required to stake 8x Tokens (lock up a certain amount of 8x Tokens for processing rights) the staking of the tokens then also act as collateral in the event that the operators fails to process the transaction on time or performs a malicious action. In the event that they do fail to process the transaction on time, their staked tokens are slashed and given to the next 8x Repeater who successfully processes the missed transaction. Below is the code snippet that allows 8x Repeaters to catch out missed transactions, this concept introduces an interesting aspect to the game theory of the 8x Protocol economy.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0c8f6e52757ecaaa536b6dd987223159/href">https://medium.com/media/0c8f6e52757ecaaa536b6dd987223159/href</a></iframe><h4>The Claiming Problem (Risk &gt; Reward)</h4><p>However consider the scenario we have two individuals — Bob and Alice. They both have the opportunity to earn 5 Ethers, in attempting to do they both need to spend 2.5 Ethers* in fees. Now it is clear that they both have an equal (50%) chance of winning the prize of 5 ETH, let’s say Bob claims the prize and he is 2.5 ETH richer but Alice is now at a loss of 2.5ETH.</p><p><em>*Note: The transaction fees are not this expensive, this is just for example purposes.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*Pm6tKYclqVbUwt9VGzuSKA.png" /></figure><p>This is fair game as they cost of participating is equal to the amount they can earn, however as more participants — such as Paul and Lisa — join the contest, the probability of earning the prize becomes increasingly small. Economics state that at the point where an individuals’ risk is greater than the probability that an individual is going to be rewarded, an individual would not participate in the game and that is exactly what happens in the claiming of subscription contracts in 8x Protocol.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/559/1*nfreo3Zbuvdbsz_9Rcs3tg.png" /></figure><p>Alas, this introduces another important concept used in 8x Protocol called the <strong>multiplier</strong>. Referencing back to the economics of supply and demand, in this case:</p><ul><li><strong>Supply</strong> — amount of unlocked (not staked) 8x Tokens held by the 8x repeaters.</li><li><strong>Demand</strong> — amount of subscription contracts that are unclaimed on the market (not being processed by 8x Repeaters).</li></ul><blockquote>One important thing to note is that we did consider using Ethereum as a basis of setting the multiplier however both the monetary policy (inflation) and the uncertainty of Ethereum distribution among users would provide difficulty for figuring out the multiplier for the 8x Protocol system.</blockquote><p><strong>Scenario one — Supply &gt; Demand</strong></p><p>The claiming problem exist mainly in the scenario that supply is greater than demand (where there are more free tokens than there are subscriptions to process). This results in a large amount of individuals fighting for each subscription contract (this is commonly labeled as the <strong>“gas war”</strong>).</p><blockquote>Gas is the fee of performing operations on Ethereum — this fee can be increased by the user in order to further incentivise miners to accept the operation before they accept other parties, this usually results in individuals attempting to fight each other by paying exceedingly high fees in the “war”.</blockquote><p>To prevent the conflicts that occur during this scenario, a multiplier would be set in place that reduces the amount of individuals who are eligible to process the subscription contract (a multiplier of 10x will mean you need 10 tokens staked per $1 value of subscription contract).</p><p><strong>Simply put the higher the multiplier the less conflicts would occur due to the reduced amount of individuals that are able to process the subscription.</strong></p><p>The above statement and concept assumes that there will be never exist a scenario that individuals hold the same number of tokens. This is highly likely due to the historic distribution of currency amongst different economies which show that the distribution (power law distribution) of currency is never even (there exist a small percentage of individuals who hold the majority of the circulating supply).</p><p><strong>Scenario two — Supply &lt; Demand</strong></p><p>If the number of unlocked tokens is less than the amount of subscriptions waiting to be processed, a backlog of contracts begins to form. By reaching this point, the economy of 8x Protocol would be well developed, businesses would automatically start to incentivise the 8x Repeaters to process their transactions first by setting higher rewards for them to earn.</p><p>On the 8x Protocol side, the multiplier could also be set at a lower rate in order to free up tokens that were once staked (e.g setting the multiplier from 1x to 0.5x would free up 0.5 tokens per dollar value) and thus allow the freed-up tokens to be used to process other subscriptions in the backlog.</p><p><strong>Summary of the multiplier</strong></p><p>Apparent in both scenarios above, the introduction of the 8x Token multiplier is an essential part of the 8x Protocol economy. Readjusting the multiplier enables us to respond to the market in different ways in order to provide a fair and incentivised economy for the 8x Repeaters to operate in.</p><h4>Conclusion</h4><p>I hope through the detailed scenarios and examples above that I have successfully explained the reasoning behind the 8x Token. While reading this article, I assume that you would have a better understanding of how the 8x Repeaters operate and remain incentivised.</p><p>On the ending note, we are currently looking for MVP testers for the 8x Protocol both implementing it in their service/business or project and also for individuals to test the UX of our designs.</p><p>Please free feel to reach me at <strong>andy@8xprotocol.com </strong>or dropping by our telegram (link below) if you are interested in discussing this article or the request above.</p><p><strong><em>Co-written by </em></strong><a href="https://medium.com/u/d81b0c185c2a"><strong><em>Kevin Lu</em></strong></a><strong><em> (product at 8x).</em></strong></p><p><strong>—</strong></p><h4>8x Protocol — Recurring Stable Payments on the Blockchain</h4><p>8x is a protocol for facilitating recurring crypto payments without exposing consumers or businesses to the volatility of crypto currencies.</p><p>Website/Whitepaper: <a href="https://8xprotocol.com/">https://8xprotocol.com/</a><br>Twitter: <a href="https://twitter.com/8x_Protocol">https://twitter.com/8x_Protocol</a><br>Telegram Community: <a href="https://t.me/eightexprotocol">https://t.me/eightexprotocol</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bd72ce9cd31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Echo Chambers of Crypto.]]></title>
            <link>https://medium.com/hackernoon/the-echo-chambers-of-crypto-205c78e318b7?source=rss-e3b0d0b2eb9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/205c78e318b7</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[echo-chambers-of-crypto]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Andy Tom]]></dc:creator>
            <pubDate>Sun, 29 Jul 2018 09:26:01 GMT</pubDate>
            <atom:updated>2019-05-24T04:31:16.537Z</atom:updated>
            <content:encoded><![CDATA[<h4>The disconnect between audiences in crypto and its barriers to mass-adoption.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0kXq7Zq7iweDbWvC" /><figcaption>Photo by <a href="https://unsplash.com/@xusanfeng?utm_source=medium&amp;utm_medium=referral">Levi XU</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Mass-Adoption Buzz</h4><p>If you have encountered the <a href="https://hackernoon.com/tagged/cryptocurrency">cryptocurrency</a> space, it is likely you have heard individuals speak on the importance of cryptocurrency mass-adoption. Inside the many articles titled “X reasons why Y is going to be mass-adopted” there exist a common argument that the new <strong>decentralised,</strong> <strong>transparent and trustless</strong> system will be self-selling to the general population (deemed no-coiners).</p><p>However, one of the less argued barriers of mass-adoptions is simply this — <strong>on-boarding new crypto users is not self-propelling</strong>. What I mean by this is that the no-coiners and even seasoned coiners are expected to learn too many new concepts by themselves (see diagram about the different <strong>limbos).</strong></p><p>One of the main reasons for this, is the disconnect between the “players” (player groups shown in diagram) in the cryptocurrency space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*jB7zxVEO-F-LJgmVEVx_lA.png" /></figure><h4>Will great UI and UX exist in the decentralised world?</h4><p>We are all familiar with the great apps, platforms and websites in our current web 2.0. For example, <a href="http://time.com/3834978/babies-use-devices/">age groups of 2+</a> are able to easily pick up a device to browse the internet, play on apps or watch videos.</p><p>Now compare that to the learning curve experience by individuals who encounter cryptocurrencies.</p><p>Even an experienced stocks trader or a frequent digital payment user is unable to easily open an exchange account immediately (verification lengths) or:</p><ul><li>Understand the significance of public and private keys (and the importance to know the difference — hint; one you of them you shouldn’t share).</li><li>Identify their own address and then realise that their address is 34 characters.</li><li>Understand and realise the immutability of transferring funds to a wrong address (whether it be a typo or incompatible address — sending BTC to ETH address).</li><li>Understand transaction costs and block confirmation times (wait-times).</li></ul><p><strong>And this is just to buy your way into using the decentralised system.</strong></p><p>There should be an effort made by those who design and build the entry points (exchanges, over-the-counter markets, wallets, payment systems…) to understand the perspective of a no-coiner and provide great UI* and UX* in order to flatten the learning curve. This learning curve is depicted in <strong>Limbo (1) </strong>and if addressed, could potentially bridge the gap between the no-coiners and coiners. This bridge alone would spark enough movement for a “mass-adoption” of cryptocurrencies and <a href="https://hackernoon.com/tagged/blockchain">blockchain</a>.</p><p><strong>But let’s go deeper.</strong></p><p>Once an individual has bought their first token and has some experience in transacting, trading and using software wallets they may wonder“where to next?”. The very next step covers all the applications, use cases and platforms in the decentralised web.</p><p>Such examples are projects such as <a href="https://medium.com/u/f4d568271227">Augur</a>’s prediction market and financial products such as {Set} Protocol’s exchange-traded funds* where users may begin to start using tokens for the decentralised counterparts of the current systems.</p><p><strong>The learning curve just got steeper.</strong></p><p>We are now in <strong>Limbo 2,</strong> concepts and problems users are faced with include (Not specific to the projects mentioned above):</p><ul><li>What is a dAPP* and how do I even access dAPPS?</li><li>Installing external clients.</li><li>Downloading copies of the blockchain.</li><li>Opening new wallets (remembering more seed* phrases).</li><li>Calculating gas* fees.</li></ul><p>(Non-conclusive as some of these issues even I have steered away from).</p><p>When we had thought that <strong>Limbo (1) </strong>was already a major barrier to on-boarding a no-coiner into a coiner, on-boarding users of crypto in <strong>Limbo (2) </strong>just got harder.</p><p>Focusing on UI and UX for these platforms and apps would assist in propelling the active users of the decentralised web, this would require community managers and marketers in performing regular feedback loops with their community in order to better guide the vision of designers and developers.</p><p>In the current cryptocurrency space, there exist echo chambers both at the top and the bottom. No-coiners and the general population are presented with too little guidance and information, that they usually resort in labelling this system a scam. Meanwhile the curse of knowledge experienced by the leaders, developers and creators have resorted in them creating products that are catered to a niche technical crowd but unusable by many.</p><p><strong>If we can bridge the gap between the top and bottom chambers we may see a spark in “mass-adoption”.</strong></p><p>Article inspired from reading <a href="https://medium.com/u/b99672bf26df">Trevor Caldwell</a>’s article.</p><blockquote>“One of the challenges of getting involved in the world of cryptocurrency is how many new concepts you need to learn about”.</blockquote><p><a href="https://cryptocurrencyhub.io/i-bought-my-first-bitcoin-now-what-fdf7dc9ad150">I Bought My First Bitcoin! Now What?</a></p><p><em>Let me know what you think of this opinion. If you enjoyed it please support by clapping and sharing.</em></p><h4>Definitions (marked by *)</h4><p><strong>UI</strong> = User Interface (Colours, Visual Design, Layouts)</p><p><strong>UX </strong>= User Experience (Interaction Design, Information Architect, User Research)</p><p><strong>dAPP</strong> = Decentralised apps (Apps built on the Blockchain).</p><p><strong>Seed Phrase </strong>= The seed phrase is a set of words that allows you get access to funds of your wallet.</p><p><strong>Exchange Traded Funds (ETF)= </strong>An ETF is a type of investment fund that can be bought and sold on a securities exchange market.</p><p><strong>Gas = </strong>Gas is the way that fees are calculated.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=205c78e318b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/the-echo-chambers-of-crypto-205c78e318b7">The Echo Chambers of Crypto.</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The World Of Finance Is Being Rebuilt.]]></title>
            <link>https://medium.com/swlh/the-world-of-finance-is-being-rebuilt-81dbb49ffae1?source=rss-e3b0d0b2eb9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/81dbb49ffae1</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Andy Tom]]></dc:creator>
            <pubDate>Thu, 26 Jul 2018 04:15:58 GMT</pubDate>
            <atom:updated>2018-07-26T10:37:56.676Z</atom:updated>
            <content:encoded><![CDATA[<h4>The rise of decentralised finance on Ethereum.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Go6klVxgwPvw7Uq8" /><figcaption>Photo by <a href="https://unsplash.com/@timbatec?utm_source=medium&amp;utm_medium=referral">Pepi Stojanovski</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Out with the old.</h4><p>From instances such as the downfall of Mt. Gox and the occasional security breaches of centralised exchanges, centralisation in finance has been set in a negative light.</p><p>This has been impetus for projects to create infrastructures that steer away from centralisation. One of the major infrastructure plays has been the introduction of technology that allow for decentralised exchanges (DEX) and token swap methods.</p><p>However, the introduction of DEXs was not just a win exclusively for traders and investors but also for the future of finance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*i_tY4wbxrCN3zlP_bcWViQ.png" /></figure><h4>In with the new.</h4><p>On Ethereum, the creation of infrastructure has allowed for the developer community to build out decentralised counter-parts of our legacy system.</p><p>The current examples of this include:</p><ul><li>Making payments.</li><li>Buying insurance.</li><li>Creating loans and lending.</li><li>Creating markets and being able to wager on said markets.</li><li>Trading baskets of cryptocurrencies.</li><li>Buying derivatives.</li></ul><p>The user flow of decentralised finance would go something like this:</p><p><em>DEXs -&gt; Wallets -&gt; Financial applications/products.</em></p><p>This is just the beginning of the decentralised world of finance, with the correct infrastructure in place the decentralised counterparts of our current world can be established in web 3.0.</p><p>However, the success of decentralised finance relies on solving issues such as scalability and mass-adoption. It will be interesting to see how things may play out.</p><h4>8x Protocol — Recurring Stable Payments on the Blockchain</h4><p><em>The author is a team member for 8x Protocol, a protocol for facilitating recurring crypto payments without exposing consumers or businesses to the volatility of crypto currencies.</em></p><p>Website/Whitepaper: <a href="https://8xprotocol.com/">https://8xprotocol.com/</a><br>Twitter: <a href="https://twitter.com/8x_Protocol">https://twitter.com/8x_Protocol</a><br>Telegram Community: <a href="https://t.me/eightexprotocol">https://t.me/eightexprotocol</a></p><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqDjlKFwScoQYQ62DWEdig.png" /></a></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by 351,974+ people.</h4><h4>Subscribe to receive <a href="http://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouK9XR4xuNWtCes-TIUNAw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81dbb49ffae1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-world-of-finance-is-being-rebuilt-81dbb49ffae1">The World Of Finance Is Being Rebuilt.</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Opt-in or Opt-out?]]></title>
            <link>https://medium.com/swlh/opt-in-or-opt-out-7db2a247e72f?source=rss-e3b0d0b2eb9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7db2a247e72f</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Andy Tom]]></dc:creator>
            <pubDate>Thu, 12 Jul 2018 14:05:58 GMT</pubDate>
            <atom:updated>2019-08-08T10:34:37.201Z</atom:updated>
            <content:encoded><![CDATA[<h4>The issues and works currently faced by recurring cryptocurrency payments.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H2LtPMopVh7BwT15MCoWmQ.png" /></figure><p><em>Subscription Article: </em>“<a href="https://medium.com/8xprotocol/product-ownership-is-in-the-past-2c4dc5572f1f">Product ownership is in the past”</a></p><p>With the shift of consumer preferences from product ownership to accessibility combined with more businesses opting into blockchain there is no doubt that the subscription industry and cryptocurrency will intertwine.</p><p>This article will cover the current issues and workings towards allowing the subscription industry to thrive on the blockchain.</p><h4><strong>Native Ethereum restrictions.</strong></h4><p>Ethereum (cryptocurrency) in its innate form would not be ideal for supporting recurring payments on the blockchain.</p><p>One of the main restrictions of Ethereum would be its volatility. Users and services transacting Ether would be exposed to the volatility of their funds which would impose major issues with the subscription economy on the blockchain.</p><p>Another barrier that arises from using Ethereum stems from the underlying principles of the subscription model. Consumer’s opting into subscription services look for convenience in purchasing consistent products/services with as little capital as possible.</p><p>Using Ethereum as a recurring payment method would mean that the user/consumer will need to sign transactions every month with their private key (push basis). This action alone would detrimentally affect the subscription businesses retention rates adding more pain-points into their service.</p><p>These two points alone have caused for the Ethereum community to look into further solutions to this problem.</p><p><em>Now let’s talk about using ERC20 tokens as a solution.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PMC00Dlbji1S40Ql" /><figcaption>“A white neon in the shape of the dollar sign at night” by <a href="https://unsplash.com/@jimiburg?utm_source=medium&amp;utm_medium=referral">Jimi Filipovski</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>ERC20 as a recurring payment method.</h4><p><a href="https://www.investopedia.com/news/what-erc20-and-what-does-it-mean-ethereum/">ERC20</a> is the standard on the Ethereum Blockchain used for smart contracts for implementing tokens (such tokens such as Bancor and Qash). It defines how tokens are transacted between users and also how data is accessed.</p><p>To solve the volatility issue, users and businesses could resort to using stable-coins that are ERC20 compliant. In Ethereum’s widely used token standard — ERC20, there exist functions in which users can send tokens to other addresses/users.</p><p>Incorporating stable-coins such as <a href="https://medium.com/u/743224aba00c">MakerDAO</a>’s Dai* will address the issues of volatility however the ERC20 standard functions alone would require consumers to sign transactions each billing cycle to renew their services. Although this could be mediated through the use of an escrow — whereby users deposit an upfront payment ($X price of a subscription multiplied by the Y billing cycles), users would require larger capital which in term would reduce the accessibility of goods/services (an essential part of the subscription economy).</p><p>The use of the most basic ERC20 model would provide negative consumer experiences and present high churn rates to businesses and therefore would not be the best foundations for the subscription industry in Web 3.0.</p><p><em>Building from the concept of using ERC20 standard for basic payments, comes the introduction of the ERC948 discussion.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NyzPZz6Hr20SnU2q" /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>ERC948, the discussion of recurring payments.</strong></h4><p>The ERC948 EIP started by <a href="https://github.com/owocki">Kevin Owocki </a>is a proposal published on github on the a standard for recurring payments.</p><p>While the ERC948 protocol is still yet to reach final consensus, the current ideas presented in the discussion of the standards present viable parts to resolving recurring payments on the blockchain.</p><p>In the current consensus of ERC948 (6/07/2018), the standard is set to bring forth an agnostic smart contract that serves to allow applications to understand the concept of a recurring payment contract. This in turn would allow for a user to see that they are subscribed to a service.</p><p>In the discussion, one of alternatives I favor would be a standard of ERC948 that only governs the way subscription data is viewed/accessed. The use of ERC948 in its lightest form will ensure that services would need to revoke the authorisation provided if they were to modify the subscription data; such as pricing. This subscription standard would stand-by the essential value of putting the users first.</p><p>This opinion is accompanied by many more discussions about the types of standard functions to include such as: the type of data stored, status of subscriptions and user subscription lengths (for loyalty programs).</p><p>All of which are available on the EIP.</p><p><strong>We won’t know how the ERC-948 standard will turn out, but we do know that recurring payment standards will be an integral part of web 3.0.</strong></p><p><a href="https://github.com/ethereum/EIPs/issues/948">Recurring Subscription Models are a Good Thing and should be viable on Ethereum (Merit + Architecture ERC) · Issue #948 · ethereum/EIPs</a></p><p><strong><em>I would love to hear about what you think about the future of ERC948 and if you think there will be any alternatives to the ERC948 standard.</em></strong></p><p><strong><em>Special mentions go to the co-author </em></strong><a href="https://medium.com/u/d81b0c185c2a"><strong><em>Kevin Lu</em></strong></a><strong><em>.</em></strong></p><h4>8x Protocol — Recurring Stable Payments on the Blockchain</h4><p><em>The author is a team member for 8x Protocol, a protocol for facilitating recurring crypto payments without exposing consumers or businesses to the volatility of crypto currencies.</em></p><p>Website/Whitepaper: <a href="https://8xprotocol.com/">https://8xprotocol.com/</a><br>Twitter: <a href="https://twitter.com/8x_Protocol">https://twitter.com/8x_Protocol</a><br>Telegram Community: <a href="https://t.me/eightexprotocol">https://t.me/eightexprotocol</a></p><h4>*MakerDao</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ggeUbtTi1JsD1x4GUHxbbQ.png" /></figure><p>MakerDao’s Dai is a collateralised stable-coin, the team is focusing on solving volatility on the blockchain.</p><p>Website — <a href="https://makerdao.com/">https://makerdao.com/</a></p><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqDjlKFwScoQYQ62DWEdig.png" /></a></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by 343,876+ people.</h4><h4>Subscribe to receive <a href="http://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouK9XR4xuNWtCes-TIUNAw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7db2a247e72f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/opt-in-or-opt-out-7db2a247e72f">Opt-in or Opt-out?</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ethereum will be the pioneer platform for recurring cryptocurrency payments.]]></title>
            <link>https://medium.com/@andycf/ethereum-will-be-the-pioneer-platform-for-recurring-cryptocurrency-payments-b60d22715e78?source=rss-e3b0d0b2eb9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b60d22715e78</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[8xprotocol]]></category>
            <dc:creator><![CDATA[Andy Tom]]></dc:creator>
            <pubDate>Fri, 22 Jun 2018 05:40:24 GMT</pubDate>
            <atom:updated>2019-08-08T10:36:38.219Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_c05WhtXzZ_WuuEiuhc_lQ.png" /></figure><p>8x Protocol, the protocol for facilitating recurring cryptocurrency payments will be built on Ethereum.</p><p><strong>Here’s why.</strong></p><h4>Platform vs Platform</h4><p>Recently in the cryptocurrency space, there has been a major spotlight on new platforms that are labelled as the next <strong>“Ethereum Killer”</strong>. Most of said platforms boast higher TPS (transactions per second) and sell their platform as the scalable Ethereum.</p><p><strong>While it is impossible to predict the future of Web 3.0, Ethereum looks like it is here to stay.</strong></p><p><strong><em>Ethereum’s Trilemma</em></strong></p><p>As a reiteration from above, platforms are attempting to outshine Ethereum through their large TPS.</p><p><strong>But at what cost?</strong></p><p>One of the important concepts to understand is of Ethereum’s Trilemma. This is the idea that the platform (in its current state) can only choose two out of three of its essential features; scalability, security and decentralisation.</p><p>In order for platforms to out-perform Ethereum in its TPS, many of them have resorted to sacrificing the concept that Ethereum has protected; complete decentralisation. Methods of doing so include the implementation of restrictions on node locations (to minimise latency) and even cherry-picking node operators (setting a minimum node computing power).</p><p>Without complete decentralisation, platforms begin to portray the negative effects that arise from governing bodies and centralised organisations. This is evident in the <a href="https://cryptocoremedia.com/eos-stealing-eth-from/">problems</a> that surfaced in the main-net launch of <a href="https://eos.io/">EOS</a>. EOS is a dAPP (decentralised application) platform that raised $4 Billion in their ICO. Through their use of delegated proof of stake mechanism, the platform is able to achieve a high benchmark of TPS speeds.</p><p>However in their main net launch, token holders were able to witness the power of the EOS constitution and the 21 nominated <strong>“Block Producers (BP)” </strong>who were able to freeze token holder wallets. Although the BP’s did this to prevent fraudulent activity from occurring, the event has highlighted future <a href="https://www.coindesk.com/eos-locked-7-accounts-implications-everyone-crypto/">ramifications</a> that may arise where the issues will be upscaled by the amount of transactions operating on the platform.</p><blockquote>“The fact that EOS transactions are subject to ‘arbitration’ based on an unclear document of zero legal force means that EOS transactions lack finality.” — Emin Gun Sirer, professor at Cornell.</blockquote><p>While Ethereum does have its current issues of scalability, it has not sacrificed the concept of decentralisation (importance of this covered in next topic) and through the test of time, Ethereum has proven that their base one layer has provided substantial security to its users.</p><p>Ethereum’s dominance will be reaffirmed through the implementation of a practical scalablility solution. Notable examples of works are Ethereum’s hybrid POW/POS consensus algorithm — <a href="https://blockgeeks.com/guides/ethereum-casper/">Casper</a>. While Ethereum continues to provide a secure and decentralised platform for its users, the community will be here to stay.</p><p><strong>Leading on to my next topic…</strong></p><h4>Developers and Community</h4><p>One of 8x Protocol’s main vision is to develop a protocol on Ethereum’s Layer 2 that provides a solution to recurring cryptocurrency payments for dAPP developers.</p><p><strong>What better place to achieve this vision but by building with the </strong><a href="https://media.consensys.net/andrew-keys-ethereum-has-30-times-more-devs-than-the-next-blockchain-community-27980a5ddc09"><strong>largest </strong></a><strong>developer community in the blockchain space.</strong></p><p><strong><em>Network Advantages</em></strong></p><p>As a result of the extensive developer community, Ethereum host a range of out-of-box tools and frameworks for dAPP developers such as Truffle and Web3.js. Not only will this save time but also reduce the barrier to entry for budding developers and innovators. 8x Protocol aims to increase this accessibility by creating easy to use SDK (software development kits) to enable recurring crypto businesses to thrive.</p><p>Decentralisation is important, however for developers this is ever more crucial. Many developers thrive on the censorship freedom that the blockchain provides. Ethereum’s dAPP develops can value the certainty that a centralised body would not be granted authority over their work.</p><p>A final note would be to highlight the network effect of Ethereum, where the platform users are not only growing but growing at an accelerating speed. This alongside the positive acts of Ethereum’s influencers (including grants and incubators) provide reason to the staggering amount of projects and dAPPs currently built on Ethereum’s ERC20.</p><p><strong>This is why 8x Protocol will be built on the Ethereum platform.</strong></p><p>Read about our recent collaboration with MakerDAO (team behind DAI) <a href="https://medium.com/8xprotocol/8x-protocol-partners-with-makerdao-370b5b8532da">here.</a></p><p><strong><em>Special thanks to </em></strong><a href="https://medium.com/u/d81b0c185c2a"><strong><em>Kevin Lu</em></strong></a><strong><em> (product @ 8x) for co-authoring this article.</em></strong></p><h4>8x Protocol — Recurring Stable Payments on the Blockchain</h4><p>8x is a protocol for facilitating recurring crypto payments without exposing consumers or businesses to the volatility of crypto currencies.</p><p>Website/Whitepaper: <a href="https://8xprotocol.com/">https://8xprotocol.com/</a><br>Twitter: <a href="https://twitter.com/8x_Protocol">https://twitter.com/8x_Protocol</a><br>Telegram Community: <a href="https://t.me/eightexprotocol">https://t.me/eightexprotocol</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b60d22715e78" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>