<?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 Stefan Andrei on Medium]]></title>
        <description><![CDATA[Stories by Stefan Andrei on Medium]]></description>
        <link>https://medium.com/@andreistefanciprian?source=rss-512e3bbbb0c4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*FX4ssmlOly2TjWS5.</url>
            <title>Stories by Stefan Andrei on Medium</title>
            <link>https://medium.com/@andreistefanciprian?source=rss-512e3bbbb0c4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:54:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andreistefanciprian/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 build a Jenkins pipeline for Terraforming AWS resources]]></title>
            <link>https://medium.com/@andreistefanciprian/how-to-build-a-jenkins-pipeline-for-terraforming-aws-resources-956bf1262457?source=rss-512e3bbbb0c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/956bf1262457</guid>
            <category><![CDATA[jenkins-pipeline]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[jenkinsfile]]></category>
            <dc:creator><![CDATA[Stefan Andrei]]></dc:creator>
            <pubDate>Sun, 31 May 2020 20:59:19 GMT</pubDate>
            <atom:updated>2020-06-01T07:39:58.865Z</atom:updated>
            <content:encoded><![CDATA[<h3>Overview</h3><p>This is a tutorial for how to build a Jenkins pipeline that builds AWS resources with terraform.</p><h3>Prerequisites</h3><p>Spin off Jenkins docker container with a named volume to preserve configuration and pipeline jobs for future use:</p><pre>docker run -p 8080:8080 -d -v jenkins_home_centos:/var/jenkins_home — name jenkins jenkins/jenkins:lts-centos</pre><p>Clone git repository with the code:</p><p><a href="https://github.com/andreistefanciprian/terraform-jenkins-pipeline.git">https://github.com/andreistefanciprian/terraform-jenkins-pipeline.git</a></p><p>Have aws s3 bucket for terraform backend and dynamodb table for terraform state lock management:</p><pre>cd prerequisites</pre><pre>terraform init --var-file=&quot;../terraform.tfvars&quot;</pre><pre>terraform plan --var-file=&quot;../terraform.tfvars&quot; -out terraform.tfplan</pre><pre>terraform apply &quot;terraform.tfplan&quot;</pre><p>For the step above to work, AWS access key and access secret key should be stored in a terraform.tfvars.</p><p>There is a sample with the contents of this file in the main directory of the repository.</p><p>Once s3 bucket and dynamodb table are built, the names of these resources will be shown in the terraform output.</p><p>Take these names and populate the related fields in the backend section of the terraform code inside the main.tf files in both static and infra directories.</p><h3>What are we building?</h3><p>The terraform code is building a VPC and an EC2 instance. The VPC resources are built in the static terraform state and the S3 instance resource is built in the infra terraform state.</p><p>Since we have two terraform states, I think we should have separate pipelines for each terraform state.</p><h3>How to configure Jenkins</h3><p>Access Jenkins at <a href="http://localhost:8080/">http://localhost:8080/</a> and go through the steps below.</p><p>Get Jenkins password from docker container logs:</p><pre>docker container logs jenkins<br>...</pre><pre>An admin user has been created and a password generated.</pre><pre>Please use the following password to proceed to installation:</pre><pre>b270d85bf9bc4f5897eeeda8fc295e96</pre><p>Paste the password in the Unlock Jenkins page and press Continue:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*ZaF0xuJtPit8wwEThZYXpQ.png" /></figure><p>On the next page, choose Install suggested plugins:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*f7bbTsn-yeLyeKll7z_TOA.png" /></figure><p>Create a user and password to access Jenkins:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*pk3ZMNMmJT_kZ5-tsviuCA.png" /></figure><p>Install terraform plugin. Go to Manage Jenkins&gt;Manage Plugins, choose Available tab and search for terraform. Select terraform plugin and press Install without restart button.</p><p>Configure terraform tool. Go to Manage Jenkins&gt;Global Tool Configuration and fill in this information. The name you choose for the terraform tool, will be also used inside the Jenkins file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/1*gHAyA6rdDPd9tpcfGh7HFQ.png" /></figure><p>Add AWS credentials. Go to Credentials&gt;global&gt;Add credentials:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/1*EQhHoeqN3yzdVExvSgb4BA.png" /></figure><p>Create aws_secret_key (Secret text type):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AbePfoqobckMqd7TjOIZDg.png" /></figure><p>Create aws_access_key (Secret text type):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*lA20AhvwOmzhVPf7EvoeAQ.png" /></figure><p>Both AWS keys have been created and credentials page should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*d7Ua40dP09_zGWEdTArDGw.png" /></figure><p>Create github developer token to be used by Jenkins to access repository.In your github.com account, go to Settings&gt;Developer Settings&gt;Personal access tokens and generate token. Select repo and admin:repo_hook when selecting token scopes. Once token in generated, take the token secret and add it to Jenkins.</p><p>Add git credentials to Jenkins(Username with password type). The token is pasted in the password field below. This credential will be used for cloning the repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*hmV9kVfQdRJRs57PUSmN4Q.png" /></figure><p>Add git token to Jenkins (Secret text type):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*XE8RwoKi7QZePaj8r6Rixg.png" /></figure><p>Add github.com configuration in Manage Jenkins&gt;Configure System. Choose githook credentials and check ‘Manage hooks’ checkbox:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*WHe9xuR-zSXMWRqzObInRw.png" /></figure><h3>Create Jenkins pipelines</h3><ol><li>Create pipeline for building AWS resources in the static state/folder.</li></ol><p>Go to main Jenkins page and click ‘Create new’ button. Pick a name for your jenkins pipeline and choose Pipeline:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*Unrmf8keLEu7XrCPcEnrqQ.png" /></figure><p>For the Pipeline definition, choose ‘Pipeline script from SCM’, add github repo link, choose git credentials and specify Jenkinsfile.static as the Jenkinsfile we’re gonna be using for running this pipeline:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*OwJjUAdiDQxk31HE_H7esA.png" /></figure><p>Once pipeline is created, click ‘Build now’ and notice how the pipeline starts executing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yiIF4x_LQvcuNyQdfWPStw.png" /></figure><p>Here’s the Jenkinsfile code for the static pipeline:</p><h4><a href="https://github.com/andreistefanciprian/terraform-jenkins-pipeline/blob/master/Jenkinsfile.static">https://github.com/andreistefanciprian/terraform-jenkins-pipeline/blob/master/Jenkinsfile.static</a></h4><p>Follow the same steps to build pipelines for building AWS instance in infra state or destroy resources. All Jenkins files provided in the github repo.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=956bf1262457" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From ZERO Kubernetes knowledge to getting both CKA and CKAD certifications.]]></title>
            <link>https://medium.com/@andreistefanciprian/from-zero-kubernetes-knowledge-to-getting-both-cka-and-ckad-certifications-c70ba503d6e0?source=rss-512e3bbbb0c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c70ba503d6e0</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[tehnology]]></category>
            <dc:creator><![CDATA[Stefan Andrei]]></dc:creator>
            <pubDate>Wed, 08 Jan 2020 22:26:09 GMT</pubDate>
            <atom:updated>2020-05-05T06:05:11.162Z</atom:updated>
            <content:encoded><![CDATA[<h3>From ZERO Kubernetes knowledge to getting both CKA and CKAD certifications</h3><p>I started my Kubernetes journey in June 2019 with the <a href="https://www.udemy.com/share/101WlGBkYTd1xVQng=/">Docker Mastery</a> course from udemy.com. Prior to this I had a small amount of experience with Docker but no knowledge of Kubernetes or how it works — just the understanding that it is the tool of the future.</p><p>With some spare time on my hands after my work contract came to an end in October and the understanding that Kubernetes is the way forward if you want to easily automate infrastructure in the cloud or if you want to keep working in the DevOps space, I embarked on the learning path of this sometimes complex tool. My initial target was to gain an understanding of how the tool works and maybe automate some apps using Terraform, GCP and Kubernetes afterwards. Just to get my hands dirty a little bit before I start looking for a new contract. But once I started learning, I was hooked.</p><p>My interest then turned towards determination to learn as much about Kubernetes as possible. And so it snowballed from one course to another, a few books and loads of labs in between, in this order …</p><ul><li><a href="https://acloud.guru/learn/gke-beginner-to-pro">GKE: beginner to pro</a> from <a href="http://acloudguru.com/">acloudguru.com</a> (very good if you’re into GCP cloud)</li><li><a href="https://www.coursera.org/specializations/architecting-google-kubernetes-engine">Architecting with Google Kubernetes Engine Specialization</a> from Coursera (very well organised with loads of <a href="https://www.qwiklabs.com/catalog?keywords=kubernetes">qwiklabs</a>)</li><li>Read <a href="https://www.amazon.co.uk/Kubernetes-Running-Dive-Future-Infrastructure/dp/1492046531">Kubernetes: Up and Running: Dive Into the Future of Infrastructure</a> while on a few long flights</li><li>Then read <a href="https://www.amazon.co.uk/Kubernetes-Book-Version-November-2018-ebook/dp/B072TS9ZQZ/ref=sr_1_2?keywords=kubernetes&amp;qid=1578461570&amp;sr=8-2">The Kubernetes book</a> which it was a good refresh of everything I’ve learned prior</li></ul><p>Then I decided to follow a more structured way of learning about this amazing technology and started to look into the <a href="https://www.cncf.io/certification/ckad/">Certified Kubernetes Application Developer (CKAD)</a> curriculum to see if it was for me. And it was. So continued my learning journey with the followings:</p><ul><li><a href="https://linuxacademy.com/cp/modules/view/id/305?redirect_uri=https://app.linuxacademy.com/search?query=cka">CKAD</a> from Linux Academy + did all the labs a few times and read all the <a href="https://kubernetes.io/docs/setup/">kubernetes.io</a> reference pages for each lesson</li><li>And went through all this <a href="https://medium.com/bb-tutorials-and-thoughts/practice-enough-with-these-questions-for-the-ckad-exam-2f42d1228552">150 practical CKAD questions</a> list a few times</li></ul><p>After going through all this I recently passed the CKAD performance based exam on my first attempt. I must admit, I didn’t have time to finish all of the challenges. You have two hours to finish 24 problems and you really need to have a lot of practice with the kubectl command and know the yaml files for all Kubernetes resources, in and out. Loads of practice is the key to pass this exam.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O22eFqMjWo8gwB_J5K2JXA.jpeg" /></figure><p>After passing this exam and a bit of holidaying I’ve decided it’s time to start learning a bit more about Kubernetes. So I’ve set a new goal of learning and passing the <a href="https://www.cncf.io/certification/cka/">Certified Kubernetes Administrator</a> exam.</p><p>My steps in doing so:</p><ul><li>Finished <a href="https://linuxacademy.com/cp/modules/view/id/327?redirect_uri=https://app.linuxacademy.com/search?query=ck">CKA</a> from Linux Academy and did all the labs twice but felt it wasn’t enough which I was right. I’ve also read all the related <a href="https://kubernetes.io/docs/setup/">kubernetes.io</a> reference pages for each lesson</li><li>Did the labs in <a href="https://linuxacademy.com/cp/modules/view/id/371">Learn Kubernetes by doing</a> from Linux Academy. I don’t recommend doing all the labs there as some of the labs are on RedHat which is not required for this exam.</li><li>Did <a href="https://linuxacademy.com/cp/modules/view/id/221">Kubernetes the hard way</a> from Linux Academy only once and payed for it during the exam. I recommend doing this a few times in order to grasp the inner workings of how to setup and debug a Kubernetes cluster.</li><li>I’ve also started to read the <a href="https://www.amazon.com/Kubernetes-Action-Marko-Luksa/dp/1617293725">Kubernetes in Action</a> book which is probably the best book on this subject. But haven’t finish it yet.</li></ul><p>After going through CKAD and all the CKA courses above I’ve passed the CKA certification. You get 3 hours to solve 24 challenges. Finished the first 18–20 questions in less than 2 hours and the cluster debug problems took the rest of it.</p><p><strong>I am now very excited to embark on the next stage of my career using Kubernetes.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rx0PO20OVpzUA2dWkaBPRg.jpeg" /></figure><h3>CKA Tips</h3><ul><li>Do Kubernetes the hard way a few times and don’t copy and paste everything. Try to understand how every service is built and the relation between all components. This is mandatory because you’ll get 3–4 scenarios during the CKA exam, all about debugging a broken cluster (node not ready, or even worse, missing components, etc).</li><li>Practice etcd backup and recovery with certs.</li><li>Build, debug and rebuild clusters with kubeadm utility. Many articles online say you won’t get to build a cluster during the exam but it’s not true.</li><li>Build a few static pods.</li><li>Play with node and tolerations.</li><li>Play with affinity and anti-affinity.</li><li>Use jsonpath, sort-by, custom-columns.</li><li>Do RBAC from command line.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c70ba503d6e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First NEO decentralized exchange, Switcheo Networks, aims to compete head-to-head with popular…]]></title>
            <link>https://medium.com/@andreistefanciprian/first-neo-decentralized-exchange-switcheo-networks-aims-to-compete-head-to-head-with-popular-fce8c57c977c?source=rss-512e3bbbb0c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/fce8c57c977c</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ico]]></category>
            <dc:creator><![CDATA[Stefan Andrei]]></dc:creator>
            <pubDate>Sun, 18 Mar 2018 12:21:38 GMT</pubDate>
            <atom:updated>2018-03-19T16:46:56.686Z</atom:updated>
            <content:encoded><![CDATA[<h3>First NEO decentralized exchange, Switcheo Networks, aims to compete head-to-head with popular centralized exchanges like Binance and Kucoin</h3><h3>Who is Switcheo Network?</h3><p>Switcheo (SWH) is a Decentralized Exchange to be built on top of multiple popular blockchains to facilitate the exchange of digital assets. It will first be launched on the NEO blockchain and will include digital assets such as <a href="https://neoguide.io/nep-5-tokens-2/">NEP-5 tokens</a> (e.g. RPX, QLC) and future NEP-X tokens, and NEO’s system assets such as NEO and GAS. Switcheo aims to achieve a network of DEX with cross-chain swapping capabilities between multiple popular blockchains such as QTUM (QRC20) and Ethereum (ERC20), with more research being done for upcoming blockchains like Stellar.</p><p>The Switcheo journey began in Nov’17, when they participated and won in the first <a href="https://cityofzion.io/dapps/1">NEO dApp competition</a> hosted by CoZ.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IrVEP7j1s0rwzWA1ht3FrA.jpeg" /><figcaption><a href="https://medium.com/switcheo/a-taste-of-the-new-switcheo-exchange-7ad5deec6a39">A taste of the Switcheo Exchange</a></figcaption></figure><h3>Problems with centralized exchanges</h3><h4>1. Security</h4><p>An immediate disadvantage when using a centralized exchange is the security risks arising from the centralization of funds. As all funds sent in by users for trading are stored and secured by the exchange, the funds are prone to a single point of failure. For example, the exchange servers could be breached by attackers, or the exchange’s wallet private keys could be lost, resulting in a loss of funds.</p><p>These failures are completely out of the control of the individual user, regardless of how secure their passwords are, and they have to trust that the centralized exchange have done what is necessary to secure their funds. There have been major breaches of users’ trust, evidenced in past exchange hacks which have amounted to billions of dollars in value lost over the last few years. A prime example of this would be the USD 500 million lost in the recent <a href="http://fortune.com/2018/01/31/coincheck-hack-how/">Coincheck breach</a>.</p><p>Decentralized exchanges solve this problem by letting the blockchain and the user handle the security of funds from start to end. A DEX is therefore as secure as its smart contract, and most existing DEXs have been running for a long time with no core breaches (e.g. EtherDelta).</p><h4>2. Control of funds</h4><p>When users deposit their funds into a centralized exchange, their funds are under the control of the exchange. The exchange has the private keys of the wallets. The exchange may be able to <a href="http://bitcoinist.com/coinbase-missing-funds-legal-action/">withhold funds from users</a> or <a href="https://en.wikipedia.org/wiki/Bitfinex_hack">remove funds from users’ accounts</a> at any time. In general, a user has to trust that a centralized exchange will always act in good faith for the user. This is in contrast to cryptocurrency’s spirit of decentralization and trustlessness.</p><p>When trading on DEXs, the user is in control of his wallet’s private key.</p><h4>3. Ease of Transfer</h4><p>Users may also be unable to withdraw assets in small numbers from centralized exchanges, or it may not be viable to withdraw often due to high withdrawal fees. Furthermore, a high number of confirmations are typically required when depositing funds. These issues make trading on centralized exchange a hassle.</p><p>These problems are solved when trading on DEXs because users can buy or sell tokens directly from their wallet, without additional transfers.</p><h4>4. Immediate Listing</h4><p>A big issue with the acquisition of tokens of an early stage blockchain startup is finding exchanges that list the wanted tokens. On the other hand, users who have purchased tokens during an Initial Coin Offering (ICO) also have to wait for the token to be listed on an exchange before being able to sell it. This leaves many users stuck with the token even though they may no longer want it. With the increasing popularity of projects developed on the NEO Blockchain, Switcheo will strategically start trading NEP-5 Token contracts for the NEO Blockchain first, before moving on to QRC20 Tokens (QTUM). Using the dynamic call functionality of the NEO blockchain, users will be able to list and buy tokens the moment they are available for transfer on the blockchain.</p><h4>5. Exchange Fees</h4><p>While centralized exchanges like Binance and Gate.io charge exorbitant rates for withdrawals for small amounts of cryptocurrencies, there will be no withdrawal fee for Switcheo’s smart contract. Users will only pay the standard network fees, and not be charged additional amounts should they decide to withdraw their balance. The maker and taker fee for Switcheo is capped at 0.5%, and is guaranteed by the smart contract.</p><h3>Problems with existing DEXs</h3><p>While a DEX has clear advantages over a centralized exchange in the security &amp; control of funds, ease of transfer, immediate token listing, and lower fees, Switcheo’s true priority is to overcome the shortfalls of existing DEXs:</p><ul><li>User Experience (almost identical to traditional exchanges that users are comfortable with)</li><li>Smart Contract Security (bug bounty campaign and external audits)</li><li>KYC/AML Requirements (implementation of D-KYC whitelists so that users can trade in compliance with the relevant legislations)</li><li>Low Exchange Volume (they plan on overcoming this with state-of-the-art ease-of-use platform, such that using Switcheo’s user experience is preferred even to popular centralized exchanges)</li></ul><h3>Public Sale and Listing</h3><p>They just finished the public sale on the 17th of March after a first round sale started on the 16th of March where participants had their spot reserved for 24 hours.</p><p>Listing of the SWH token is planned for the upcoming days. Tokens will be listed on the <a href="https://switcheo.exchange/">Switcheo’s Exchange</a> as a base pair while trading on the Switcheo DEX.</p><h3><a href="https://switcheo.network/index.html#team">Team and Advisors</a></h3><p>Roger Lim (advisor) — one of the most significant advisors and investors out of China. He is a partner of <a href="http://www.ngc.fund/">NEO Global Capital</a>, an investment fund strategically affiliated with NEO.</p><p>Ivan Poon (blockchain developer) — he’s the leader of the four people team. Has quite an impressive experience as <a href="https://github.com/RavenXce">developer</a> and entrepreneur.</p><h3><a href="https://switcheo.network/index.html#roadmap">Roadmap</a></h3><ul><li>Q1 2018 — Launch of Switcheo DEX for NEO, GAS &amp; NEP-5</li><li>Q2 2018 — Launch of QRC20 trading</li><li>Q3 2018 — Launch of ERC20 trading</li><li>Q4 2018 — Cross-swap feature using SWH and Wanchain</li><li>2019 — Launch of trading for top 5 chains</li></ul><h3>Useful Links</h3><p><a href="https://switcheo.exchange/">Exchange Website</a>, <a href="https://switcheo.network/switcheo_whitepaper_v1.0.pdf">Whitepaper</a>, <a href="https://twitter.com/switcheonetwork">Twitter</a>, <a href="https://medium.com/@switcheo">Blog</a>, <a href="https://t.me/switcheo">Telegram</a>,</p><h3>Resources used for writing this article</h3><p><a href="https://switcheo.network/switcheo_whitepaper_v1.0.pdf">Switcheo Network’s Whitepaper</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fce8c57c977c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MAINFRAME is creating a new layer of the internet where privacy and freedom are first class…]]></title>
            <link>https://medium.com/@andreistefanciprian/mainframe-a-fully-decentralized-messaging-platform-1cff43dbfe15?source=rss-512e3bbbb0c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cff43dbfe15</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ico]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[messaging]]></category>
            <dc:creator><![CDATA[Stefan Andrei]]></dc:creator>
            <pubDate>Thu, 15 Mar 2018 20:34:34 GMT</pubDate>
            <atom:updated>2018-03-18T03:51:31.314Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong><em>MAINFRAME is creating a new layer of the internet where privacy and freedom are first class citizens</em></strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V2IVY2aFbMX-b8ftyinkkw.jpeg" /></figure><p>Everyone knows that online private conversations aren’t at all private.</p><p><strong>Whatsapp, Gmail, Slack and other messaging service providers are in control of our data. They market our private data and even share it with governments and secret service agencies that are spying on it’s citizens on the pretext of counterterrorism</strong> (remember the Edward Snowden leaked documents about mass surveillance programs?). Like this is not enough, these centralized services also get hacked from time to time, and our data gets into the hands of hackers (<a href="http://www.wired.co.uk/article/hacks-data-breaches-2017">That Yahoo data breach actually hit three billion</a>).</p><p>Well, with the help of Decentralized Ledger Technologies we can now stop relying on these “trusted third-party” providers and start building a peer to peer decentralized network that provides secure messaging services that are censorship and surveillance resistance.</p><p>In other words we can have:</p><ul><li><strong>Peer to peer architecture</strong> (all data services that applications rely on are distributed in redundant fragments throughout the network. This eliminates the need to rely on or manage your own infrastructure, and makes it extremely difficult for would-be censors to deny access. Nobody can shutdown the network, not even it’s creator)</li><li><strong>One to one and one to many encryption</strong> (no outside party, whether government, corporate, or rogue hacker, will have access to your messages or media)</li><li><strong>Dark Routing</strong> (the content can’t be followed hence you can’t see who is communicating with whom)</li><li><strong>Incentivization</strong> (the token economy incentivizes each node to provide bandwidth for packet relay and storage, data services, file storage and be fair; bad actors are avoided since each node’s creditworthiness is constantly tracked)</li><li><strong>Interoperability</strong> (the protocol will be available to any app, network, or blockchain that requires truly private communication services. SDKs and other tools for interoperability will be deployed based on community needs.)</li></ul><h3>The company that undertook this task is called <a href="https://twitter.com/Mainframe_HQ">MAINFRAME</a> and they have been working on building messaging protocols for about five years now.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/383/1*mwxx1N3L8RsI1p9jPXlV3g.png" /></figure><blockquote><strong>Their aim is to create a new layer of the internet where privacy and freedom are first class citizens.</strong></blockquote><blockquote><strong>They are working on correcting the weaknesses in the current messaging protocols and services that are susceptible to centralized control, surveillance, and manipulation.</strong></blockquote><p>They are headquartered in London with a few remote developers. Among the investors are some interesting technology entrepreneurs. Check them out at <a href="https://mainframe.com/team">https://mainframe.com/team</a></p><p><strong>They already have a first application built on the MAINFRAME network. It’s a fully decentralized workplace messaging tool called </strong><a href="https://mainframe.com/onyx"><strong>Onyx</strong></a><strong>.</strong> A very similar tool to Slack but an upgrade from the downtime, security vulnerabilities, or centralized architecture of traditional messengers. All major platforms are supported (even mobile).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TKsGPlN1z6Pnn28zC1af4A.png" /></figure><p><strong>Here is a nice presentation of the MAINFRAME network by the team itself:</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeaQyE8m9pKk%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeaQyE8m9pKk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FeaQyE8m9pKk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a99121d08bc4ecf22fd4dc5ac04af702/href">https://medium.com/media/a99121d08bc4ecf22fd4dc5ac04af702/href</a></iframe><p><strong>Interested readers can take a closer look at the following links:</strong></p><p><a href="https://blog.mainframe.com/introducing-the-mainframe-crowdsale-9a73ea7ae9d4">Crowdsale details</a>, <a href="https://mainframe.docsend.com/view/j39qpui">Whitepaper</a>, <a href="https://t.me/MainframeCommunity">Telegram</a>, <a href="https://twitter.com/Mainframe_HQ">Twitter</a>, <a href="https://blog.mainframe.com/mainframe-token-generation-event-ad775f509871">Token Metrics</a></p><p>Stay private! #MainframeForFreedom</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cff43dbfe15" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>