<?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 BORING PROTOCOL on Medium]]></title>
        <description><![CDATA[Stories by BORING PROTOCOL on Medium]]></description>
        <link>https://medium.com/@boringprotocol?source=rss-802e6d9f9ee4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Di2B3HImhOkKEhzBIAHclw.png</url>
            <title>Stories by BORING PROTOCOL on Medium</title>
            <link>https://medium.com/@boringprotocol?source=rss-802e6d9f9ee4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:36:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@boringprotocol/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[Cloud Providers on the Boring Network]]></title>
            <link>https://medium.com/@boringprotocol/cloud-providers-on-the-boring-network-54df3e377c3?source=rss-802e6d9f9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/54df3e377c3</guid>
            <category><![CDATA[crypto-mining]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[dvpn]]></category>
            <dc:creator><![CDATA[BORING PROTOCOL]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 17:02:20 GMT</pubDate>
            <atom:updated>2023-01-25T17:02:20.022Z</atom:updated>
            <content:encoded><![CDATA[<p>We support the creation of provider peers on any VPS. In this post, we have a user-contributed walk-through of how to run a Cloud Provider on AWS specifically. Thanks to <strong>luckyracer9999</strong> in the #boredroom for sharing!</p><p>First, create a new Cloud Provider Peer in the Motherbored interface in the <a href="https://motherbored.app/">motherbored.app</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gv323AhoxVVNno8WbHphog.png" /><figcaption>Add Cloud Provider in <a href="https://motherbored.app/">motherbored.app</a></figcaption></figure><p><strong>Follow the set-up flow:</strong></p><ul><li>Change the country dropdown to match the region from which your node will run.</li><li>Click “Save Changes”</li><li>Click “boring.env” to download the boring.env file</li></ul><p>A known issue to check before proceeding:</p><blockquote>Check if boring.env file does not have spaces between the ‘=‘ sign and remove them (ex: BORING_NAME= redacted-zipper-3885 is wrong because it has a space next to the ‘=‘ sign).</blockquote><h3>Go to the AWS Console</h3><h4>Create a new VPC</h4><ul><li>VPC only</li><li>Chose a name for the VPC</li><li>Chose an IPV4 CIDR block (e.g., 10.80.0.0/16)</li><li>Chose “No IPv6 CIDR block”</li><li>Click “Create VPC”</li></ul><h4>Create a new Subnet to the previous VPC</h4><ul><li>Create Subnet</li><li>Chose the VPC previously created</li><li>Chose a Subnet name</li><li>Chose a Subnet IPv4 CIDR block (e.g., 10.80.1.0/24)</li><li>Click “Create Subnet”</li></ul><h4>Create a new Internet Gateway</h4><ul><li>Create an internet gateway</li><li>Chose a name</li><li>Click “Create internet gateway”</li></ul><h4>Attach the internet gateway to the VPC</h4><ul><li>Go to the Internet Gateway page</li><li>Click on the previously create gateway -&gt; Actions -&gt; Attach to VPC</li><li>Chose the previously created VPC</li><li>Click “Attach internet gateway”</li></ul><h4>Change Route Table of VPC</h4><ul><li>Go to Route Tables in the left menu</li><li>Click the Route Table created by AWS associated with the previously created VPC</li><li>Go to the tab “Routes”</li><li>Add a new Route:<br>- Destination: 0.0.0.0/0 Target: The previously created Internet Gateway<br>- Go to the tab “Subnet Associations”<br>- Click “Edit Subnet Associations” in “Explicit Subnet Associations”<br>- Pick the subnet you previously created<br>- “Save Associations”</li></ul><h4>Create the security group for the EC2 instance</h4><ul><li>Go to Security Groups in the left menu</li><li>Chose a name</li><li>Chose a description</li><li>Chose a VPC<br>Inbound rules:<br>- SSH port from your IP only!<br>Outbound rules:<br>- Type: All traffic // Destination: Anywhere IPv4</li><li>Click “Create security group”</li></ul><h4>Create a new EC2 instance</h4><ul><li>Click “Launch instance”</li><li>Choose a name</li><li>Choose an Amazon Machine Image — ami-0dae3a932d090b3de works, “Canonical, Ubuntu, 22.04 LTS, amd64 jammy image build on 2023–01–15”, with Architecture: x86)</li><li>Choose an instance type</li><li>Choose a key-pair (if none is created, create one and save the downloaded file in a secure place on your computer)</li></ul><p>In your computer, you need to change the permission in the .pem file with the command:</p><pre>chmod 400 BORING_KEY.pem</pre><h4>Network Settings</h4><ul><li>Choose the VPC you created</li><li>Choose the Subnet you created</li><li>Enable “Auto-assign public IP”</li><li>Select the Security Group you created</li></ul><p>Leave the rest unchanged and click “Launch instance”</p><h4>Connect to the EC2 instance:</h4><pre>ssh -i PATH_TO_KEY_PEM_FILE ubuntu@PUBLIC_IPV4_ADDRESS</pre><p>Add the contents of the boring.env file you downloaded in Step#1 into boring.env file inside the EC2</p><pre>sudo vi /boot/boring.env </pre><p>Past the content inside this file, save it, and close vi.</p><h4>Install Boring</h4><pre>wget https://s3.us-east-2.amazonaws.com/boringfiles.dank.earth/install.sh<br>chmod +x install.sh<br>sudo ./install.sh</pre><p>Check if boring service is running (you should see Active: active in green)</p><pre>systemctl status boring.service</pre><p>Check the logs of the service if something is not right</p><pre>journalctl -u boring.service</pre><h4>Activate the node in motherbored.app</h4><p>Go to the Cloud Provider node in your wallet<br>Click “Activate”</p><p>You should see “Great news. Successfully activated!”</p><p>Thanks again to <strong>luckyracer9999</strong> for the AWS walk-through.</p><p>If you have another VPS in mind that you would like to use, please take a look at the more generalized Cloud Provider set-up doc at <a href="https://docs.motherbored.app/docs/motherbored-basics/add-motherbored-cloud-provider">https://docs.motherbored.app/docs/motherbored-basics/add-motherbored-cloud-provider</a></p><p>Come to <a href="https://discord.gg/gJt4X8qnJz">the #boredroom</a> for help from other users who are working on a variety of set-ups.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54df3e377c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[V1/V2 and Boperator NFT drop]]></title>
            <link>https://medium.com/@boringprotocol/v1-v2-and-boperator-nft-drop-ed17608cf7f0?source=rss-802e6d9f9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed17608cf7f0</guid>
            <dc:creator><![CDATA[BORING PROTOCOL]]></dc:creator>
            <pubDate>Thu, 27 Oct 2022 16:24:20 GMT</pubDate>
            <atom:updated>2022-10-27T20:52:33.287Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*XkKrK8s73W9pAsbs9eOcSg.png" /></figure><p>We’re back again with another exciting update!</p><p><strong>The minting for our utility NFT will begin Friday, Oct 28th at 10am CST</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*Pw4Ru4w86q-o8mBfkKStFQ.gif" /><figcaption>Boperator VX NFT</figcaption></figure><p><strong>Our NFTs function as a software license allowing Boring Protocol node operators to activate purchased nodes and software (SD) from our store.</strong></p><p><strong>Each node requires one Boperator NFT held in the wallet.</strong> If you have two nodes, you will need to mint and hold two NFTs. The system periodically verifies the owner has the required number of NFTs to operate their nodes and, if necessary, removes the worst-performing nodes from the network in the event not enough NFTs are present in the user’s wallet.</p><p>Friday, Oct 28th at 10 am CST (barring the unforeseen), we will release the directive and URL for all V1/V2 &amp; Boperator VX NFT software license claims as NFTs. <strong>Hardware purchasers must use the email they used when ordering and a Solana Wallet to claim their NFTs.</strong></p><p>Again, as these NFTs operate as software licenses, they must be kept in the wallet to receive platform rewards multipliers. <strong>Boperator NFTs must be kept in a wallet attached to your node to keep it active on the network.</strong> From Friday forward, new node operators will need to download the free updated software from <a href="http://www.motherboard.app/">www.motherboard.app</a> and mint their Boperator NFT to activate newly purchased nodes.</p><p><strong><em>NOTE:</em></strong><em> NFT license activations will NOT be immediately enforced! Do not feel a need to rush through this process. We will give everyone plenty of time to get their NFTs minted and set up in their wallets.</em></p><p>We will not sell any of the Boperator NFTs for DIY nodes — who download FREE firmware — until after the mobile application is live and the economics of the $BOP token is in full swing.</p><p>Thanks for your continued support.</p><p>Boring Protocol</p><p>Come visit us in Discord: <a href="https://discord.gg/gJt4X8qnJz">https://discord.gg/gJt4X8qnJz</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed17608cf7f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Up, Up and Away]]></title>
            <link>https://medium.com/@boringprotocol/up-up-and-away-9505b60638b2?source=rss-802e6d9f9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/9505b60638b2</guid>
            <dc:creator><![CDATA[BORING PROTOCOL]]></dc:creator>
            <pubDate>Thu, 13 Oct 2022 19:19:53 GMT</pubDate>
            <atom:updated>2022-10-13T19:24:52.068Z</atom:updated>
            <content:encoded><![CDATA[<p>Helium Network’s Potential Adoption of Boring Protocol subDAO</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*uRxFbYfEjJApiJM-YsHXsQ.png" /></figure><p>The web3 space has been treacherous the last few months. Not only has the bear market been slowly chopping away at the capital, but the slew of hacks and controversies have been slowly chopping away at morale and trust in the space. Fortunately, we are a privacy company at our core, and this environment only strengthens our resolve and demonstrates the importance of our mission.</p><p>Over the past few months, we have been working on becoming a Helium subDAO. As a dVPN service, we provide an obfuscation layer for decentralized network traffic. Joining Helium is a win-win scenario for Boring Protocol and the Helium Network. Their network, as it stands, has thousands of active nodes, and their newly introduced <a href="https://www.helium.com/5G">mobile 5G network</a> and their <a href="https://www.coindesk.com/markets/2022/09/20/nova-labs-says-t-mobile-to-cover-5g-dead-spots-in-helium-network/">partnership with T-Mobile</a> bode well for their continued growth and adoption. However, the implementation of this network presents a security risk for its users.</p><p>The following is a quote from Helium’s <a href="https://docs.helium.com/blockchain/proof-of-coverage/">documentation</a>; the emphasis added is our own. “Helium’s Network runs on a consensus algorithm called Proof-of-Coverage. Proof-of-Coverage takes advantage of the unique, undeniable properties of radio frequency (RF) to produce meaningful proofs to the Helium Network and its participants. Specifically, PoC relies on the following characteristics:”</p><ol><li>RF has limited physical propagation and, therefore, distance;</li><li>The strength of a received RF signal is inversely proportional to the square of the distance from the transmitter; and</li><li>RF travels at the speed of light with (effectively) no latency</li></ol><p>As you can see, Proof-of-Coverage utilizes the key property of radio frequencies — that they move at the speed of light — to broadcast real-time proof that the node is running as intended. For the security of the network, this is amazing. The network can keep track of all nodes and their real-time coverage instantly. As great as a consensus algorithm of this type is for a decentralized mobile provider, if your consensus algorithm broadcasts your node/phone’s live location — without lag — then you’re simply creating a large-scale tracking service. While some users will have no issue with this, it creates a real security threat.</p><p>The question becomes, how do you resolve the issue of providing sybil and spoofing resistance but also protecting your user base’s physical security? Simple, you add an obfuscation layer.</p><p>Enter: Boring Protocol.</p><p>As it stands, our proposal for Boring to become a Helium subDAO has been accepted for discussion. We are discussing the tech and economics of the two networks and the correct implementation of Boring as a subDAO with the Helium Foundation. As of <a href="https://medium.com/helium-foundation/hip-70-helium-core-team-proposes-to-migrate-to-solana-e7ea23a042e7">HIP-70</a>, Helium will be transitioning to the Solana Network for its L1. Consequently, we already have a head start and there should be minimal backward compatibility issues for our current holders. Our goal is to honor the holders of BOP and the users of our hardware in this merger so you can rest assured that the interests of our community will be taken care of.</p><p>This next phase of Boring Protocol will add thousands of users to our network and provide value to both communities. We firmly believe this will be a great step forward for our customers.</p><p>Thanks for your continued support.</p><p>Boring Protocol</p><p>Come visit us in Discord: <a href="https://discord.gg/gJt4X8qnJz">https://discord.gg/gJt4X8qnJz</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9505b60638b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ok, This is War]]></title>
            <link>https://medium.com/@boringprotocol/ok-this-is-war-734e1042a808?source=rss-802e6d9f9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/734e1042a808</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[war]]></category>
            <category><![CDATA[vpn]]></category>
            <dc:creator><![CDATA[BORING PROTOCOL]]></dc:creator>
            <pubDate>Wed, 17 Aug 2022 00:10:43 GMT</pubDate>
            <atom:updated>2022-08-17T00:10:43.364Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B1-oT-aZ21bY2q6IEtfrIA.png" /></figure><p>We’re asking all Boring supporters to come to the front lines with us. We have weathered the bear market thus far and while we’re dead set on emerging victorious on the other end we want your help to make it a guaranteed victory in Q4.</p><h3>The best thing you can do to push this project forward and help us break out sooner than later:</h3><p><strong>Become an Affiliate</strong>. It’s <a href="https://affiliates.boringprotocol.io/boringprotocol/register">a simple sign-up process</a> and you’ll get a special link you can use to earn commissions for every sale you refer to our store. Share this link far and wide. Twitter is always a great place to start but maybe you have some reach on other platforms. Try it.</p><p>We want you to help us wrap up the Motherbored V2 sale <em>now</em> so we can throw more coal into the steam engine. Revenue generated from these nodes sales is coal. Our steam engine is moving steady but we’d like to see it at full speed. I know you do too.</p><p>We are largely a bootstrapped company and our model for success is heavily dependent on this sale closing successfully. The sooner it does the sooner we can make big moves.</p><p>We will reward every soldier handsomely and will work with any individuals who have interesting ideas about how to wrap this sale.</p><p><a href="https://affiliates.boringprotocol.io/boringprotocol/register">Click here</a> to become and Affiliate and go procure the coal. The effort requires your service.</p><p>This is war.</p><p>Boring Protocol</p><p>Discount Code: <a href="https://store.motherbored.limited/discount/SOLANASUMMER?redirect=%2Fproducts%2Fboring-protocol-mbv2">SOLANASUMMER</a>. It gets a person 20% off all Motherbored V2 purchases.</p><p>Come visit us in Discord: <a href="https://discord.gg/gJt4X8qnJz">https://discord.gg/gJt4X8qnJz</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=734e1042a808" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Basis and Core]]></title>
            <link>https://medium.com/@boringprotocol/in-this-article-we-intend-to-discuss-how-the-privacy-mechanics-of-the-boring-protocol-settlement-fc50c1475976?source=rss-802e6d9f9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc50c1475976</guid>
            <dc:creator><![CDATA[BORING PROTOCOL]]></dc:creator>
            <pubDate>Wed, 11 May 2022 15:12:10 GMT</pubDate>
            <atom:updated>2022-05-12T05:17:55.653Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-7NUO2hGEKpJT_JXdmYtw.jpeg" /></figure><p>In this article, we intend to discuss how the privacy mechanics of the Boring Protocol Settlement layer accomplishes such, while also fitting into some parameters of the market for VPNs.</p><p>In our system, there is a grand need to separate the client from the operator within the economic model in order to reduce the risk of tracking the client’s traffic to the node it is accessing.</p><p>While it could be said that this problem requires a meticulous amount of thought and concern overall the solution we are proposing is actually quite simple.</p><p>At the heart of this protocol is a root settlement structure that acts as an escrow account for the entire network. The root settlement receives commands from both clients and operators to balance clients’ usage funding and payouts to operators. The contract monitors the data consumed from the perspective of the client and deducts from their usage funding, the necessary token value. Opposite of this the operator is monitored for data consumed through their node(s) and their escrow balance is credited to the corresponding values.</p><p>In order to maintain the obfuscation, the only transactions outside of the contract written to the Solana chain are the funding that the client transacts to access network utilization and the operator’s settlement function when they withdraw from the root settlement escrow. This mechanism will also reduce the transactional load and overall transactional fees of the network and its participants.</p><p>From the dVPN users’ perspective, a contract-operated wallet receives the entirety of a client’s usage funds they allocate. This funding is a proposed amount given to the user that estimates their cost based on the quality of the node they select and its subsequent “ask” or cost for the bandwidth consumed. This balance remains in this wallet until actions of data consumption or disconnection from the network by the user (at this point a client has the ability to settle their unused balance back to their non-custodial wallet) take place.</p><p>As the funds enter the wallet and the user connects to the network, our protocol begins counting data consumed by the client from the perspective of the client. This protocol also monitors and reports the amount of data that is consumed from the perspective of each node operated on the network in order to pay out to these nodes for their service. Each of these measurements is to be used to settle the transaction.</p><p>As the root settlement tracks consumption of data from the perspective of clients and providers individually and does not place a direct deduction of client balance to that of its payout of the operator; it is reasonable to determine that multiple equal value payouts occur in each epoch would provide a layer of obfuscation.</p><p>It is arguable that transactional totals could be used to trace who is transacting with who. However, because the transactions are not directly between clients and node operators there is no way to concretely determine that these totals one user is definitively connected through another user.</p><p>If all users connected to the network are exchanging $bop at different rates directly the ability to track which client is paying which operator becomes easily distinguishable. For our system to work we have to implement some controls to keep all clients paying similar amounts per the data they are consuming. This also keeps market participants competitive and in line with the scale of the network and the global market for data consumption rates.</p><p>In any free market, these kinds of regulations can impede the user experience and the success of the market as a whole. However, regulation in the most minimally invasive approach can be beneficial to the market.</p><p>For this proposal, we are implementing a slide rule of acceptable terms in the cost of data consumed. This slide rule is not permanent and will need some form of future governance outside of the core team.</p><p>Given the research of market data consumption rates the core team proposes a slide rule scale of $.03-$.2 cents USD per GB (in increments of whole &amp; half cents).</p><p>For instance, according to <a href="https://aws.amazon.com/blogs/aws/aws-data-transfer-prices-reduced/">Amazon AWS</a> users pay $.15 per GB for outbound transfer at the top of the scale of anything less than 10TB total consumption per month down to $.08 per GB for anything over 150 TB total per month.</p><p>In 2021 the average US household was measured to use 435 GB per month according to <a href="https://www.cnet.com/google-amp/news/how-to-manage-your-home-internet-plans-data-cap/">CNET</a></p><p>For reference, 31% of US consumers polled were said to use a VPN once per week and another 36% said they used a VPN daily or nearly every day. According to <a href="https://www.cloudwards.net/vpn-statistics/">Cloudwards</a></p><p>Using some inference we can say that not all household internet traffic is 100% through a VPN service, though it should be.</p><p>Now, if we also infer that on the lowest level a VPN customer uses a VPN service once per week or 4 out of 28 days in a month span we can assume that the average low-level VPN user consumes 62 GB of data through a VPN per Month. That’s 435GB(avg monthly data consumption)/28days (4weeks) = ~ 15.5GB daily</p><p>15.5GB Daily * 4 (total number of days 31% of users access internet via VPN) = 62 GB</p><p>At this rate of consumption, a low-level VPN user would pay between $1.84-$12.40 per month to utilize the Boring Protocol dVPN when applying our slide rule scale. Bear in mind this is only a single client being serviced by a node and while we will have hard figures very soon early tests reveal potential to service as many as or more than 24 customers daily from a single, average bandwidth limited node. This would present the possibility of $44.16 to $297~ of profitability per node/monthly.</p><p>Now, inversely the user which consumes all of their traffic via VPN could pay between $13.05 &amp; $87 a month for their usage given the slide rule scale. $87/month for bandwidth is a tough pill to swallow for any power user and it may be that we can implement some form of a subscription-based model for such users.</p><p>On average access to VPNs cost users $10/Month in the traditional VPN market which is subscription-based and riddled with negatives in privacy aspects and user experience. The cost of that $10 a month may include having your banking data stored on centralized servers, breached or it may mean having your traffic logged and given over to those who choose to exploit it. However, the understanding is that these services for the most part provide unlimited data consumption for any given period. It is also understood that not all users of these traditional VPN services consume 100% of their total internet data under the umbrella of these VPNs.</p><p>For a MotherBored operator to provide an average MBPS connection to 6–8 individuals at a time (considering time zones of user sets) and break a single day into 3, 8 hour periods provides an estimate of 24 customers serviced via a single node operator and $240/month in profit given the same cost basis that a typical VPN charges @ $10 month. Comparing this to the initial cost of ~$400 to set up and run a node (not including ISP costs) that ROI is incredibly manageable.</p><p>Tests on the network have already shown and will continue to display the possibilities with regard to profitability. This is assuming the network can harness that amount of consumer traffic. This is simply projected profitability for the bandwidth market and does not include the platform incentive model. With the release of the Public Beta and launch of the consumer facing web application (mobile optimized), we will begin allowing free client access to the dVPN for a short period to allow new users to flock in and facilitate further projections and network usage.</p><p>It is important to note that these figures require some degree of inference which does not make them concrete indicators of models. It is also notable that these are residential consumer figures we are exploring and not enterprise or business consumers whose data consumption rates are higher at an average rate of 498 GB monthly according to <a href="https://bluebirdnetwork.com/how-is-data-being-used-by-businesses-today">BlueBird Network</a>.</p><p>In order for the Boring Protocol to be competitive to the traditional VPN subscription model, we must apply some controls or the balance of usership on the network will suffer. If the cost to clients is too great they will possibly access competitors’ VPNs for cheaper if they are not keen to the unique value proposition of a truly decentralized VPN service. If the cost to clients is not great enough the operators of nodes will not be profitable enough to wish to continue providing their services.</p><p>For this and for the aspect of privacy at the settlement layer we believe the slide rule pricing scale for the bandwidth market and an escrow with non-automatic payouts to <a href="https://store.motherbored.limited/products/boring-protocol-mbv2">MotherBored</a> node operators to be the initial solution. The exact parameters are to be determined with the testing of current network participants. As we are given data to analyze in this aspect we will reach evolutions of perfecting the slide rule scale to provide profitability to node operators, and competitive pricing to clients and still allow for a robust degree of free-market economics.</p><p>The higher cost operators may have more efficient connections and therefore be able to provide these more costly connections to less frequent users of VPNs but perhaps more of them at one given period of time. The lower cost operators may have slightly less robust connections but be able to provide access to web browsers that use VPNs more frequently.</p><p>These sets of balances are something we believe is paramount to the success of the network and they do not exist without some degree of community accepted regulation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc50c1475976" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Collaboration]]></title>
            <link>https://medium.com/@boringprotocol/collaboration-20155a1b75b8?source=rss-802e6d9f9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/20155a1b75b8</guid>
            <category><![CDATA[dvpn]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[BORING PROTOCOL]]></dc:creator>
            <pubDate>Fri, 29 Apr 2022 17:44:16 GMT</pubDate>
            <atom:updated>2022-04-29T17:44:16.064Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bfbQeLrlZIe6WFWK_jTC-g.png" /></figure><p>The projects that come and go within the Crypto realm are often defined by a single thing. Their commitment to the community that supports them. Our continued commitment to the participants in our product is something we have we have repeatedly pushed to exemplify. While that may seem like a one way street it is most certainly not. Our community has ensured that we gain the connections needed within our industry to continue to grow and build. Some community participants have become members of our core team and some have led us to fantastic developments and partnerships. One thing is for sure. We can rely on our community and we intend to reciprocate such.</p><p>In the early hours of Boring we were met with an immense opportunity to gather seed investment from interested parties in the Solana ecosystem. As we explored this we set about finding a legal structure partner. That partner, Sky Vision Capital, became a partner we could heavily rely on for consult and entity formation. It was apparent very early that they supported what we were building and wanted to facilitate our growth by helping us move forward in a way that ensured the long term success of the project. We cannot thank them enough for their efforts throughout this first year.</p><p>As we set up our entity and delivered some legal documentation we continued to explore the early seed investors interested and began to develop a strategy for determining who we would accept as backers from a financial and advisory perspective. Many funds wanted to change the tokenomics to better serve their interests and less of the communities. This was, in some ways, by design that we airdropped a fair portion of the token to our early community. 25% of the total supply to be exact.</p><p>The funds that didn’t like this, especially at the low valuation at the time, were immediately outed as having less of our vision or passion for a truly decentralized VPN and more vision for their pockets. Don’t get this wrong. Funds are meant for making money by taking early risk. But as our founder was bootstrapping early development with his own funds, it was important that his perspective as a community member within crypto for the last 7 years was not discounted. Not necessarily with a chip on his shoulder, but rather a keen eye for BS non financial value adds that some of these funds boast.</p><p>We separated the funds true to the nature of cryptocurrency from those who only saw the financial opportunity. It’s idealistic but that is what Boring is at its core. Pushing for some semblance of fairness in an increasingly digital world. As the Decentralized financial revolution presses ever onward access to information in a decentralized way is equally as important.</p><p>Through our efforts to raise outside capital we have made many amazing friends and partners. Doing so while bootstrapping early development allowed us to pick and choose who we wanted involved and truly vet them as participants. Did they share our vision? What was their record with other investments? Were they able to accept our reasoning behind some of the things we did which appeared entirely opposite the traditional path of projects?</p><p>Not many funds inside what is considered Tier One passed the test. But the great ones did and though not all of them ended up backing us we have excellent working relationships with them. Some participate in the open market of our token and yet others are now V1 Motherbored operators.</p><p>It’s been tricky to say the least. Having a financial runway is incredibly important to any project. Especially the ones who are frugal and smart with said funding. But the most important thing to gain is the knowledge and relationship that these partners have brought to the table. Their connections within our industry cannot be given a value and their experience isn’t something money can buy.</p><p>That said we have brought and continue to bring the most valuable assets in financial backing and industry know how to Team Boring Protocol.</p><ul><li><a href="https://www.skyvisioncapital.com/"><strong>Sky Vision Capital</strong></a> is a Venture Capital Fund that is dedicated to incubating and investing in founders of tomorrow, today.</li><li><a href="https://0xventures.org/"><strong>0xVentures</strong></a> is a small DAO operated fund with various long term investments in the space and their consistent eagerness to advise and explore with us has been incredibly fruitful. They are users and creators first and like us they deeply care about blockchain and its communities.</li><li><a href="https://www.bigbrain.holdings/"><strong>Big Brain Holdings</strong></a> is a well known name within the Solana Ecosystem. They are a crypto-exclusive fund with matching values to that of our project.</li><li><a href="https://www.gonarwhalventures.com/"><strong>Narwhal Ventures</strong></a> is a family operated fund with numerous successful ventures backed including Helium and funds such as MultiCoin capital. The fund supports “Unicorns of Different Kinds”</li><li><a href="https://www.alameda-research.com/"><strong>Alameda Research</strong></a> is a market making and advisory market strategy partner for Boring.</li><li><a href="https://jumpcrypto.com/"><strong>Jump Crypto</strong></a> is a liquidity provider, market maker and exchange listing advisor for our project.</li></ul><p>We are happy to have these names and faces behind our project and incredibly appreciative of the value they have brought to our pursuit. Our partners, much like you, are our family. But this isn’t all we have. Over the last year we have partnered with numerous other projects for promotion and strategy. <strong>Including partners within the </strong><a href="https://www.raspberrypi.org/"><strong>Raspberry Pi Foundation</strong></a><strong> which have helped us secure hardware materials for the V2 and beyond</strong>.</p><p>We also have research and development partners at <a href="https://dignifiedme.com/">DignifiedME Technologies</a> to develop our own proprietary hardware device for the future of Boring. This small but knowledgeable firm has been instrumental in finding ways around the global supply shortages in regards to processing chips necessary for our Motherbored devices.</p><p>Our ever expanding network of advisors and partners will see Boring Protocol through to become the privacy web3 building block that the internet so desperately requires.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20155a1b75b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[V1 Customer Rewards and NFT Drop]]></title>
            <link>https://medium.com/@boringprotocol/v1-customer-rewards-and-nft-drop-8ba683f342f3?source=rss-802e6d9f9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ba683f342f3</guid>
            <category><![CDATA[dvpn]]></category>
            <category><![CDATA[vpn]]></category>
            <dc:creator><![CDATA[BORING PROTOCOL]]></dc:creator>
            <pubDate>Tue, 19 Apr 2022 15:56:28 GMT</pubDate>
            <atom:updated>2022-04-25T05:21:09.977Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JsLDjAYRLx6xxY-hOBuXYw.png" /></figure><p>As Q1 comes to a close, we are happy to announce that all Motherbored V1 nodes have <em>been shipped</em> as of April 15th, 2022.</p><p><a href="https://www.youtube.com/boringprotocol">Follow this link</a> to an unboxing, and see what you can expect when yours arrives.</p><p>All V1 Node Operators will have received a tracking number via email; and access to the <strong>Boredroom </strong>in <a href="https://discord.gg/boringprotocol">our official Discord</a> awaits you, should you wish to participate.</p><p><em>Simply join and request someone from our Moderator team give you the “Executive” role.</em></p><p>Additionally, you will receive a Proof of Ownership Limited NFT: A run of 1000 NFTs created solely for early adopters (Including V1 buyers). Ownership of this NFT will entitle you to lifetime access to better reward rates as a provider, access to beta programs, and in C<em>ryptonese</em>, OG status. The NFT’s will be transferable should you wish to sell yours on the open market. Inversely, you may be able to buy one this way, should an early adopter decide to part ways with theirs. <strong>Last, and certainly not least, this NFT allows Motherbored V1 Provider nodes increased mining rewards (1.5x).</strong></p><h3>What comes in the box?</h3><p>A Motherbored V1 Node and a USB charging cable.</p><h3>What will I need to get up and running?</h3><ol><li>You will need to source your own ethernet cable and have access to your Internet Router.</li><li>Next, visit the <a href="https://docs.boringprotocol.io/">start-up guide</a> in our official documentation to get your Node up and running!</li></ol><p>As always, all V1 Customer have the choice to troubleshoot and speak directly with the core team in the Boredroom if you have any difficulties or would like to provide feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ba683f342f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Note From The Founder]]></title>
            <link>https://medium.com/@boringprotocol/a-note-from-the-founder-ff17f5a257e4?source=rss-802e6d9f9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff17f5a257e4</guid>
            <dc:creator><![CDATA[BORING PROTOCOL]]></dc:creator>
            <pubDate>Mon, 28 Mar 2022 15:32:53 GMT</pubDate>
            <atom:updated>2022-04-25T05:17:19.908Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KrYgEfm0CEwEkFQCyplFoA.png" /></figure><p>The legal ramifications of operating a dVPN node are something we at Boring Protocol have spent a great deal of time and effort researching.</p><p>This article and many others that will follow will address these concerns and provide you with the tools and education to protect yourself and the strength of the network as a whole.</p><p>Many have come to us to ask what happens in the event someone accesses illicit content or conducts illegal activities from the exit node a MotherBored Operator manages.</p><p>There are numerous ways we set out to protect node operators in this case. While these kinds of “nefarious” activities are in the <em>vast minority</em>, it’s important to us to protect those acting in good faith to the network even so. A secure and private network does not mean we should give up our undeniable humanity to be kind to one another and provide access to a free internet. The trade offs begin when a central authority, for instance, the Boring Protocol core team decides to intervene and determine what users can and cannot access. We cannot and will not do this. To begin to do this is that “slippery slope” we fight so hard against and have pledged to never enter into.</p><p>One proposal for Node Operators is that they be furnished with a program that logs only the data/content they access from their console as opposed to what comes across their IP from the network. We will not keep logs of dVPN subscribers/clients at Boring, so if a Node Operator was to log their <em>own</em> activity it may be helpful should questions arise from authoritative bodies. This is a concept and is not currently implemented into the features of the existing protocol nor is it planned for. It is for us, as a community, to discuss and find ways of creating solutions, if they can be justified.</p><p>Truth be told. Right now, your IP could be hacked and content accessed through it. In this case and many others it’s important to arm yourselves with the knowledge of how to proceed to protect yourself in that situation and reduce the likelihood of it happening again. If we are to provide this community with these tools it is only responsible for you to employ them.</p><p>In being committed to this pursuit of privacy &amp; security we will constantly be evolving and educating ourselves to grow stronger in this way. We have added a few “recommended reading” links below for you to explore to further understand your right and responsibility to protect yourself. The privacy infrastructure of the web is kinetic. As new threats present themselves we will adapt to thwart them. Equally important is the forward thinking perspective our team takes to see these potential new threats long before they happen.</p><p>We are also considering a proposal program to allow network participants to vote on Operator facing features such as individual node operator settings to censor certain URLs. This allows the client to access these URLs but not through node operators that have them blocked. This is one decentralized solution we may be able to offer for this specific security threat. But it is a question for each network user to answer for themselves.</p><p>Another thing Boring would like to do outside of features, tools, and education is to use some of the transaction fees between operators and clients to fund a treasury to be used in further strengthening the legal standing our network participants have. This could include legal representation should the need arise and the community approve of such. If all else fails we want our community strong and knowledgeable to help one another against these potential threats.</p><p>As with anything, know your rights. <strong>Now let’s Bore a private path through the internet!</strong></p><p>Come see us on <a href="https://discord.gg/Ejaf6DHuns">Discord</a> and <a href="https://twitter.com/BoringProtocol">Twitter</a> and feel free to ask any questions in the comments.</p><p>Also, you may like to join the waitlist for the upcoming <strong>product releases</strong>… Do so by <a href="https://boringprotocol.io/">visiting our website</a>.</p><p>The aforementioned recommended reading:</p><ul><li><a href="https://urbangeekz.com/2017/03/hacked-off-when-someone-uses-your-ip-for-illegal-activity/">https://urbangeekz.com/2017/03/hacked-off-when-someone-uses-your-ip-for-illegal-activity/</a></li><li><a href="https://nordvpn.com/blog/what-can-someone-do-with-your-ip-address/">https://nordvpn.com/blog/what-can-someone-do-with-your-ip-address/</a></li><li><a href="https://www.hg.org/legal-articles/what-is-your-liability-if-someone-hacks-your-pc-and-uses-information-for-criminal-purposes-36527">https://www.hg.org/legal-articles/what-is-your-liability-if-someone-hacks-your-pc-and-uses-information-for-criminal-purposes-36527</a></li><li><a href="https://digitalcommons.law.uw.edu/cgi/viewcontent.cgi?article=1012&amp;context=techclinic">https://digitalcommons.law.uw.edu/cgi/viewcontent.cgi?article=1012&amp;context=techclinic</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff17f5a257e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Boring Protocol: On Privacy]]></title>
            <link>https://medium.com/@boringprotocol/boring-protocol-on-privacy-41dbb200bcdd?source=rss-802e6d9f9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/41dbb200bcdd</guid>
            <category><![CDATA[solana-blockchain]]></category>
            <category><![CDATA[vpn]]></category>
            <category><![CDATA[vpn-service]]></category>
            <category><![CDATA[solana-network]]></category>
            <category><![CDATA[vpn-service-providers]]></category>
            <dc:creator><![CDATA[BORING PROTOCOL]]></dc:creator>
            <pubDate>Tue, 25 Jan 2022 01:35:20 GMT</pubDate>
            <atom:updated>2022-04-25T05:12:07.882Z</atom:updated>
            <content:encoded><![CDATA[<p>A decentralized VPN on Solana.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VHt15n305QC43Rf1hjULwA.png" /></figure><p>In order to understand Boring Protocol’s support for privacy, it is absolutely vital that you know how it compares to a regular VPN and Tor. You InfoSec analysts, and persons capable of understanding how commercial VPNs work, should read on. Everyone else, there is plenty of information for you in here too so stick around.</p><p>Let’s run through a short list of important questions to consider, so that we can start to see a premise, and understand what problems we are solving and how different concerns are met. Here we go:</p><ol><li>Is Boring allowing end points to control what can and cannot go through their node?</li><li>How does the protocol ensures that a response wasn’t forged along the way?</li><li>Is this closer to a general VPN provider or to Tor in terms of nodes?</li><li>Will my traffic pass on to one node and exit there? Or will you have entry-relay-exit nodes?</li><li>How many Nodes can you run in close proximity?</li><li>Who can see the customer IPs? Are there any relays? Who exits the traffic? <em>(using one node as entry AND exit == malice and abuse</em>.)</li><li>Will BOP use an entry-relay-exit model similar to Tor? Or it’s going to be more like most dVPNS where you just connect to one node directly?</li><li>What about malicious providers? Can someone who runs the node intercept ongoing traffic within the node?</li></ol><p>With the exception of questions 1 and 2, all the others are basically the same question so let’s get those out of the way first:</p><p><strong>Is Boring allowing end points to control what can and can’t go thorough their node?</strong></p><p>No.</p><p><strong>How does the protocol ensures that a response wasn’t forged along the way?</strong></p><p>Traffic that goes through the VPN is encrypted. A third party attacker along the way will not have the encryption keys, and therefore cannot decrypt the traffic. Without decrypting it, it’s not feasible to forge traffic. Even if it was, all forged traffic would just be ignored by the peers since it would not be encrypted with a valid encryption key.</p><p><strong>Ok, now let’s dive in deeper.</strong></p><p>Can someone who runs the node intercept ongoing traffic within the node?<br>On the exit node, yes, they can. But that’s not an issue with our protocol, that’s just the way the internet works and the same is valid for all VPNs, distributed or not, as well as non-VPN traffic.</p><p>Suppose you are using TOR, considered one of the most secure dVPNs, say you access your Gmail using TOR, after the traffic goes through TOR, it will reach an exit node, after that, traffic will go to exit node’s provider (ISP). Suppose the exit node’s ISP is in Germany and the Google server you are trying to reach is in the USA. Your traffic needs to go across the Atlantic ocean, and there are thousands of paths it could use to reach the USA, including crossing the Pacific instead of the transatlantic submarine cables that may be damaged or overloaded. So, your traffic could be intercepted not only at the exit node but at any of hop along the way of these thousands of possible paths your traffic could go through.</p><p>The Internet’s answer for this problem of interception is SSL/TLS end-to-end encryption (like in HTTPS, FTPS, SFTP, IMAPS, etc). End-to-end encryption means your e-mail content, for example, is encrypted inside Google’s server before leaving it, and can only be decrypted by your browser. If someone tries to intercept your traffic, that will render the SSL/TLS certificate invalid, that’s why you kids should never ignore that invalid certificate warning you see sometimes, it could mean a real attack. Without tampering with the certificate, attackers will not be able to decrypt your traffic and/or change it, as they don’t have the private keys for that certificate.</p><p>If you are not using SSL/TLS you are screwed any way, your traffic can be intercepted and forged at any point along the way. A VPN can help a bit with that but only to some extent, like hiding your traffic from your ISP and maybe your neighbors, but after the exit node it’s all in the open, and that’s is true for any VPN, centralized or distributed, onion based or not.</p><p>That being said, considering the common case nowadays where basically all applications do use SSL/TLS, when we talk about the VPN based attacks, VPNs protect the <em>routing</em> information along the way, that means your e-mails are secure, we (wearing the attacker’s hat now) cannot read or forge your e-mails, we cannot see who you are sending e-mails to, who you are receiving e-mails from, etc. If we intercept the traffic, <em>all</em> we <em>can</em> see is that you are talking to Google’s servers, but we can’t know <em>what</em> is being communicated with Google. We can have a rough idea (far from exact) about how much information you exchange with Google (is it a few kb’s of traffic or many gigabytes?). Basically, the information that can leak from VPNs are origin IPs (source), destination IPs (servers) and amount and frequency of traffic exchanged.</p><p>As you can see, the main concern of the VPN is <em>overall</em> privacy: which IPs are talking to which servers and how frequent or how much.</p><p>Back to our Gmail example: it’s not very interesting to know that you are talking to Google, as many people do, but as an attacker — even if I cannot read/forge the traffic — it may be interesting to know that you are talking to [redacted] servers, or that you have traffic everyday with [redacted] servers, or with some servers from the government of [redacted].</p><p>That’s the main issue with centralized VPNs, they will know every server you are talking to and you have to trust that they will not log this data and not share/sell it.</p><p>With dVPNs, you spread this risk across many exit nodes, even if some malicious nodes do keep logs of that data, each one will only have access to a very small fractions of a traffic from many different users, due to the dVPNs natural rotation of peers, which is usually of little to no value to attackers.</p><p>With all that in mind, some protocols, like TOR, go to great lengths to create additional anonymity for it’s users, mostly by creating randomized multi-hop traffic paths of varying length and frequently changing across its network of relay nodes. That indeed improves the user’s privacy but at great costs of performance, which is an acceptable trade off for TOR’s goals of increased privacy.</p><p>The other extreme from TOR is single node dVPNS. Those single node dVPNs usually delivers the best performance, at the cost of less user privacy. The main issue with single node dVPNs is that malicious exit nodes have access to both traffic destination <em>and</em> source, so a single hope will know your IP <em>and</em> the servers your are connecting to.</p><p>Boring Protocol is somewhat in between, in general we lean more towards the performance side of the equation (Netflix is for example usable) but <strong>we do not allow single nodes</strong> either (entry nodes will never be the same as exit nodes). This way, no single node has access to both source <em>and</em> destination.</p><p>Entry nodes can see your IP (no way around that, as the connection needs to start somewhere) but not your traffic destination, intermediate nodes can’t see either, exit nodes can see the destination (no way around that either, as they must send the traffic to the correct destination) but can’t see the source IPs.</p><p>In our first public version, all the entry and relay nodes are operated by us directly, and the Motherbored boxes can operate as either consumers or providers (exit nodes). Since entry and relay nodes must be different from exit nodes, we are multi-hop in nature (not single node), but the number of intermediate relay hops is fixed at one for the moment.</p><p>We could have varying length multi-hop capabilities added for future versions if we find it useful.</p><p>We have a <a href="https://boringprotocol.io/">waitlist for the Motherbored V2</a> if you’d like to be notified when pre-orders begin. Meanwhile, Motherbored V1 has started shipping</p><h3>BORING PROTOCOL on Twitter: &quot;MotherBored V1 is now shipping. Please be patient as we will be sending these out as the QA process is completed on each individual unit. pic.twitter.com/zyman2Ars8 / Twitter&quot;</h3><p>MotherBored V1 is now shipping. Please be patient as we will be sending these out as the QA process is completed on each individual unit. pic.twitter.com/zyman2Ars8</p><p>We’d love to hear from you in the comments. Please let us know your thoughts. You can always reach out to us on <a href="https://discord.gg/Ejaf6DHuns">Discord</a> and <a href="https://twitter.com/BoringProtocol">Twitter</a>.</p><p>Stay tuned for out next post coming very soon where we will be outlining all the benefits our Motherbored V1 users can expect in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41dbb200bcdd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Q1 holds in store for Boring Protocol.]]></title>
            <link>https://medium.com/@boringprotocol/what-q1-holds-in-store-for-boring-protocol-e27fde4fb11f?source=rss-802e6d9f9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e27fde4fb11f</guid>
            <category><![CDATA[vpn-service-providers]]></category>
            <category><![CDATA[solana-blockchain]]></category>
            <category><![CDATA[dvpn]]></category>
            <category><![CDATA[solana-network]]></category>
            <category><![CDATA[bandwidth-networks]]></category>
            <dc:creator><![CDATA[BORING PROTOCOL]]></dc:creator>
            <pubDate>Thu, 30 Dec 2021 18:31:41 GMT</pubDate>
            <atom:updated>2022-04-25T05:23:04.544Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Update: We’ve just </em><a href="https://docs.boringprotocol.io/bop/information/boring-protocol"><em>published documentation</em></a><em> that we will be updating frequently as we move through this first quarter.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FFi5AN7VmPplqeWrQEvvbQ.png" /></figure><p>Our first priority is the V1 Network Beta launch and you can be assured we are doing our best to get this out without any further delay. We are very grateful for your patience and will be <a href="https://twitter.com/BoringProtocol">sending out updates</a> on the progress frequently as we come nearer to shipping.</p><p><em>More information on the software development to come in a later post.</em></p><p>New exchange listings are being applied for and much work has been done under the hood to ensure our token data is distributed most accurately throughout the ecosystem. In addition to token data, our general appearance is getting some polish and we’ve also done a major overhaul on our White-paper and documentation which will be published early in January.</p><p>We will be starting a big marketing push that will follow shipment of V1. We have set an ambitious goal of producing 10,000 units for the first batch of V2 Motherboreds. We are confident we can meet this goal and have prepared for an ongoing production to bring our total of V2 sales to 100,000 units by the end of the year (2022).</p><p>The process of hand making the first batch of 500 for V1 has been a very valuable learning experience. Our strategy from the beginning was to have our hands on the creation of the product during every step of the process. From 3d printing the boxes, to mounting the PCB and sourcing components; we’ve done all this by hand and piece by piece.</p><figure><img alt="Boring Protocol MotherBored" src="https://cdn-images-1.medium.com/max/800/1*Iy9hJYYj9M21WTCRRPJCKA.png" /><figcaption>MotherBored node being tested in an unfinished case. December 2021</figcaption></figure><p>We are currently installing the software on each Motherbored and hand packaging each unit. This has been a long process and each unit feels almost unique. We expect to ship each unit from Texas this month and are sure that we’ve got a truly great release. This tedious process has prepared us to execute a large scale production in V2 in the coming months and we invite you <a href="https://boringprotocol.io/">join our waitlist</a> for that. We don’t have a date set for pre-orders as we will be focusing on the network launch and V1 users at present, but it will be soon that the we begin taking more orders.</p><p>Keep an eye on our <a href="https://www.youtube.com/channel/UCTx39_CFaov2O6ZLv7Y5oEA">Youtube channel</a> where we will be sharing some informative videos soon and also join our <a href="https://discord.gg/2rjBtz3WZr">Discord</a> if you’d like to talk with us or visit with members of the community. Of course we can be found on <a href="https://twitter.com/BoringProtocol">Twitter</a>, so see us there too.</p><p>We have published <a href="https://docs.boringprotocol.io/bop/information/boring-protocol">documentation on GitBook</a> which will be the best place find the most detailed information going forward.</p><p>Thank you all very much for all the support in 2021. Without you we wouldn’t be where we are now. 2022 will be a great year of growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e27fde4fb11f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>