<?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 Andrey Petrov on Medium]]></title>
        <description><![CDATA[Stories by Andrey Petrov on Medium]]></description>
        <link>https://medium.com/@shazow?source=rss-1bbafa7b5f87------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*PmkVSUFUHg7qav54.gif</url>
            <title>Stories by Andrey Petrov on Medium</title>
            <link>https://medium.com/@shazow?source=rss-1bbafa7b5f87------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:24:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shazow/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[What happened to Vipnode?]]></title>
            <link>https://medium.com/vipnode/what-happened-to-vipnode-90530fc78018?source=rss-1bbafa7b5f87------2</link>
            <guid isPermaLink="false">https://medium.com/p/90530fc78018</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[vipnode]]></category>
            <dc:creator><![CDATA[Andrey Petrov]]></dc:creator>
            <pubDate>Mon, 21 Feb 2022 14:47:37 GMT</pubDate>
            <atom:updated>2022-02-21T14:47:37.765Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TL;DR:</strong> Development is suspended due to several blockers. Will re-evaluate once light clients are officially supported.</p><blockquote>In 2017, I was trying to run the Go-Ethereum light client for development purposes, but my client was unable to find full nodes to connect with for hours at a time. Why were so few people running full nodes configured to serve light clients?</blockquote><p><a href="https://vipnode.org/">Vipnode</a> is an open source project I launched in 2018 with the goal of creating an economic incentive to run full nodes serve support light clients.</p><p>I’ve written several blog posts throughout the project’s lifetime with various updates:</p><ul><li><a href="https://medium.com/vipnode/an-economic-incentive-for-running-ethereum-full-nodes-ecc0c9ebe22">An economic incentive for running Ethereum full nodes</a> (May 2018)</li><li><a href="https://medium.com/vipnode/vipnode-progress-update-b3b53e4ea7a2">Vipnode: Progress Update</a> (June 2018)</li><li><a href="https://medium.com/vipnode/vipnode-progress-update-2-6e7c65d7d638">Vipnode: Progress Update #2</a> (Sept 2018)</li><li><a href="https://medium.com/vipnode/vipnode-progress-update-3-16b07037d3b3">Vipnode: Progress Update #3</a> (Nov 2018)</li><li><a href="https://medium.com/vipnode/vipnode-2-0-released-9af1d65b4552">Vipnode 2.0 Released</a> (Feb 2019)</li><li><a href="https://blog.infura.io/how-infura-uses-vipnode-to-manage-ethereum-nodes-972cf2acc0f0/">How Infura Uses Vipnode to Manage Ethereum Nodes</a> (Dec 2019)</li></ul><p>The project was funded by an <a href="https://blog.ethereum.org/2018/05/02/announcing-may-2018-cohort-ef-grants/">Ethereum Foundation grant</a>, and later by <a href="https://infura.io/">Infura and ConsenSys</a>.</p><h3>Blockers</h3><p>By the time the last stable release was published (June 2020), several blockers from further development had become clear:</p><ol><li>To this day (January 2022), light clients are still not officially supported or enabled by default. In 2018, different clients were experimenting with different light client protocols — Geth and Parity each had their own incompatible versions, and neither were enabled by default. Today, iteration continues on light client protocols with a robust but lengthy roadmap. In principle, the merge to the Proof of Stake beacon chain should make light clients easier to implement with fewer sacrifices, so perhaps soon we’ll have more viable light clients sooner than later — certainly before sharding is completed.</li><li>Many-to-many micro-payments were too expensive to implement: The economic model of vipnode required many full nodes to interface with many light clients, and light clients were to send tiny balances per time period to all of the full nodes who service them. In practice, even in 2018 the transaction fees were way too high for this kind of thing (10–20 gwei at $300 ETHUSD). Today the gas fees are x100 higher (100–200 gwei at $3000 ETHUSD), but we have much more impressive rollup technology than we did in 2018, so we’re on the right track. We also have much more interesting DeFi mechanisms that could be used to amortize value distribution without N² transactions. I suspect we’re very close to having a fee-affordable economic model here, another x10 improvement from rollups should cinch it (these happen more frequently than you’d think!).</li><li>Nobody wants to pay for something that is otherwise free. We have many high-quality endpoint providers like Infura and Alchemy, and all modern wallets subsidize their own providers, too. There is some debate about <a href="https://shazow.net/posts/decentralization/">the consequences that this has on decentralization</a>.</li></ol><h3>Utility</h3><p>High-level, Vipnode is a sidecar daemon that lives along your node or client and gives it instructions. It was built to connect full nodes with light clients through a coordinator, and track the usage between them which could ultimately be converted into payments.</p><p>Turns out that this kind of command-and-control sidecar is extremely useful for managing network topologies of node deployments. When I worked at Infura, we deployed Vipnode along every Infura node, and the Vipnode daemon coordinated which node should be peered with which other node. We had a complex topology of various kinds of nodes: Full nodes, archival nodes; internal nodes, external nodes, backup nodes, nodes optimized for different kinds of workloads, etc. <a href="https://blog.infura.io/how-infura-uses-vipnode-to-manage-ethereum-nodes-972cf2acc0f0/">I published a blog post that talks about how we did that</a>.</p><p>In my original <a href="https://medium.com/vipnode/an-economic-incentive-for-running-ethereum-full-nodes-ecc0c9ebe22">An economic incentive for running Ethereum full nodes</a> (May 2018) blog post, I speculated about several other potential usecases for what Vipnode could do:</p><blockquote><strong><em>Extending Incentives</em></strong></blockquote><blockquote><em>The vipnode design can be extended for all kinds of server-client incentives. Imagine different kinds of pools that you can pay into with different kinds of guarantees:<br>- </em>Pools for managed clusters (like an Infura pool — a Decentralized Infura).<br>- Pools for risky experimental features (like when LES/2 first launched).<br>- Pools for non-standard extended API support (with inverted indices supporting complex queries like the the Etherscan API).<br>- Pools for Big Miners. When milliseconds matter, it can be valuable to guarantee direct access to some of the largest miners.</blockquote><p>One of my regrets is not pursuing the last one, which would later become known as MEV! Thankfully the <a href="https://flashbots.net/">Flashbots team</a> and several others have done a great job at it.</p><p>Another use-case I would add to that list is managing, monitoring, and multiplexing Ethereum staking nodes. Péter has already started building <a href="https://github.com/karalabe/minority">the Minority client</a> in this vein.</p><h3>Moving forward</h3><p>Work on Vipnode is currently suspended, but not completely abandoned. <a href="https://github.com/vipnode/vipnode/">There’s a lot of great code in there that I’m proud of</a>. Perhaps once light clients are closer to being a norm, I’ll dust the project off again! Or perhaps another more interesting use case will come up again.</p><p>In either case, I hope the permissively licensed open source code has found some use in other unexpected projects too!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90530fc78018" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vipnode/what-happened-to-vipnode-90530fc78018">What happened to Vipnode?</a> was originally published in <a href="https://medium.com/vipnode">Vipnode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner Sourdough: Does anything really matter?]]></title>
            <link>https://medium.com/@shazow/beginner-sourdough-does-anything-really-matter-d7cfcbed86ef?source=rss-1bbafa7b5f87------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7cfcbed86ef</guid>
            <category><![CDATA[sourdough]]></category>
            <category><![CDATA[quarantinelife]]></category>
            <category><![CDATA[baking]]></category>
            <dc:creator><![CDATA[Andrey Petrov]]></dc:creator>
            <pubDate>Wed, 22 Apr 2020 21:55:09 GMT</pubDate>
            <atom:updated>2020-05-28T21:17:33.682Z</atom:updated>
            <content:encoded><![CDATA[<p>There are bazillions of sourdough recipes in the wild, foaming with traffic from eager bakers trapped in quarantine, ready for their sourdough starter baby with a punny name to graduate into a tube of sustenance and distraction during dark times.</p><p>Sourdough recipes are more involved than regular bread recipes, that’s for sure. There are many steps, and bakers can’t seem to agree on many of them. That’s no accident, a great sourdough bake needs to be adjusted to our kitchen and our starter.</p><h3>What to expect when you’re expecting Sourdough</h3><p><strong>This article is not a sourdough recipe or guide.</strong> It’s more of a guide for reading sourdough recipes. It’s everything I wish I knew after reading my first sourdough recipe. When we get that faithful link from our baker friend with the only caption saying “just do what it says,” read through it, take it in, then come back here for some added context. (For some decent recipes, check the links at the end of the article.)</p><p>Let’s break down a standard sourdough bread recipe, look at what varies between them, and how to adjust the recipe fit our kitchen.</p><p>A typical sourdough recipe comes down to four things:</p><ol><li><strong>Component ratio: </strong>How to adjust recipe measurements to fit the size loaf we want.</li><li><strong>Component ingredients: </strong>What are we using to make our sourdough? What kind of flour?</li><li><strong>Time, Temperature, and Yeast: </strong>This is what varies from baker to baker, and what we need to know to compensate in our steps.</li><li><strong>Steps: </strong>The bulk of the recipe, from crucial technique to flourishes and rituals.</li></ol><h3>Component Ratio</h3><p>Whether our recipe measures in grams or ounces or cups, the thing that really matters is the ratio between ingredients: Starter to Water to Flour.</p><p>For example, 50 grams of starter, 50 grams of water, and 100 grams of flour is 1:1:2 in ratio short-hand.</p><p>It can also be expressed as a <a href="https://en.wikipedia.org/wiki/Baker_percentage">Baker’s Percentage</a>: 100% flour, 50% starter, 50% water. When using Baker’s Percentages, everything is relative to the weight of the flour, so flour is always 100%.</p><p>Once we have the ratio, we can scale the recipe to whatever total quantity we’d like, whether it’s a small 300g bun or a big ol’ 1.5kg absolute unit.</p><p>The ratio also tells us the hydration of the bread (baker percentage of total water content). Higher hydration can make the bread’s crumb more open and fluffy, but it can also make the dough stickier and more difficult to work with. This is one of the common things that vary in recipes, whether explicitly or indirectly.</p><p>We can use a Bread Calculator to figure all of this out ahead of time, and tweak the components to meet our goal.</p><ul><li><a href="https://breadcalc.com/">https://breadcalc.com/</a></li><li><a href="http://brdclc.com/">http://brdclc.com/</a></li></ul><p>Tried at 60% hydration loaf last time but want to bring it up to 75% this time? Plug in our measurements and tweak the water or flour components until our hydration ratio where we want it.</p><p>Other components are usually expressed in baker’s percentages too, like 2% salt is standard.</p><h3>Component Ingredients</h3><p>Okay, so we have our ratio of flour and water, but <em>what kind of flour?</em></p><p>Most beginner sourdough recipes recommend using Bread Flour. It has more protein than All Purpose Flour which gives the starter yeast more nutrition to work with.</p><p>There are many other kinds of flours out there, like Whole Wheat Flour and Rye Flour, which have even more protein. If all you have is All Purpose Flour and Whole Wheat or Rye, then considering mixing them to give your starter yeast more to work with. Too much Whole Wheat or Rye can be difficult to work with, so start with majority of your base flour (Bread Flour ideally, All Purpose otherwise). Maybe something like 5:1 base flour to other flour, and tweak from there.</p><p>Avoid flours designed to be low on protein, like pastry flour.</p><p>Once we’re ready to experiment more, we can toss in some herbs, cheese, seeds, the possibilities are endless!</p><h3>Time, Temperature, and Yeast</h3><p>Any sourdough bread recipe will have a bunch of steps with specific timelines they recommend. Half hour to rest, a few hours to bulk ferment, another period to proof. The problem with most recipes is that they’re written for the author’s specific kitchen and starter.</p><p>We’ll stumble on professional baker in one end of the world heatedly debating another baker on the other side, both with thousands of loafs under their belt but they just can’t agree on The Correct Way To Make Sourdough! “I’ve always proofed mine for no more than 3 hours and it comes out perfect every time,” one will insist. “No way, you need to proof for minimum 5 hours, until a flock of pigeons fly by the window,” the other will protest.</p><p>While I’m just someone who read too many recipes and discussion boards on the topic, here are some of my notes on what I discovered truly matters:</p><h4><strong>Ambient Temperature</strong></h4><p>A cold kitchen will take a lot longer for a dough to rise than a warm kitchen. It can be the difference between a 3 hour bulk fermentation and an 8 hour. Or 10% sourdough starter and 30% sourdough starter. If we have a really warm kitchen, we can scale down the amount of starter we use to slow down the fermentation. A longer fermentation can yield a richer sour flavour, so we want that.</p><p>It will also take a lot longer for a new sourdough starter to mature in a cold kitchen, one week can become two weeks. It can help to create a warm space for the dough to rise more efficiently: An oven with the oven light on, or a warming mat typically used for seedlings. Be careful to not go too warm, the yeast starts to die at around 100F. 80–85F is the recommended range for a good efficient rise. <a href="https://www.theperfectloaf.com/the-importance-of-dough-temperature-in-baking/">Periodically checking the dough’s core temperature</a> is a good way to control this variable better.</p><h4><strong>Starter and Yeast Activity</strong></h4><p>A less mature starter is less active, possibly not even ready to make bread with. If we used a low-protein flour for our starter, it can take longer to ramp up. When a starter is matured, it regularly doubles or triples in volume after a feeding. With consistent feedings, it gets a kind of metabolism where you can rely on it reaching peak activity at a specific time during the day. It can help to use the starter as it approaches its peak activity, especially if we’re working with a cold kitchen.</p><p>Watch out for the infamous starter false start: Around day 3 or 4, the starter will <em>spike</em> with massive growth and beginners will rejoice about how ready their starter is but it is for for nought: This happens because an adjacent bacteria took hold of the starter and consumed all of the nutrients until it burned itself out. With consistent feedings, the desired yeast sourced from our flour grains will ultimately prevail and develop a healthy cadence.</p><h4><strong>Time</strong></h4><p>Aside from changing the temperature, and the quantity and activity of our starter, we’ll need to adjust the timing of our steps. If the kitchen is cold, ferment and proof longer. If the yeast is not too active, extend our timeline even further. It can help a lot to learn what the quality of the dough should be at each step, to know whether to proceed to the next step or wait longer. There are various tests we can do, such as the floating test to see if the starter is ready to be used; the windowpane test to see if we have sufficient gluten development; the poke test to see if the dough is sufficiently proofed for baking. We’ll go more into it in the <em>Steps </em>section.</p><p>Our dough can be underproofed or overproofed, and we might not even realize it until we pull it out of the oven, wait the prerequisite hour, cut into it, share our joy on instagram and then receive a DM from a professional baker that just says “it’s underproofed.”</p><p>An underproofed bread won’t have enough structure to fully rise during the bake, all of the gasses from the yeast will accumulate into few large bubbles, parts of it will be very dense and maybe even raw tasting. It’s much easier to underproof as a beginner, especially with an immature starter and a cold kitchen.</p><p>An overproofed bread won’t have an ideal crumb, such as very small holes, or it could collapse under its own rise because the gluten relaxed too much. If we discover the dough is overproofed before baking, we can fold it a few more times to reactivate the gluten and give it another short proof before baking. I’ve found it hard to find consensus on what qualities an overproofed loaf has, so it’s safer to err on the side of overproofing than underproofing if we must.</p><p>For other kinds of baking, when we just mix some ingredients and toss them into a temperature-controlled oven, it’s appropriate to follow the recipe to the letter. For sourdough bread baking, we need to be ready to adjust the recipe to fit our environment and our needs.</p><h3>Steps</h3><p>Many recipes have a lot of steps in common. Some of them are necessary, others can be substituted or adjusted, others are purely ritual. It’s useful to know which is which, and what we can do with them.</p><p>Maybe we started our bread too late in the day and can’t stay up until 2AM to do 6 additional folds, or maybe we don’t have time to bake in the morning and would prefer to avoid refrigerating overnight.</p><ol><li><strong>Levain:</strong> This is a process for taking some of your existing starter and making a separate sister starter that we can use for making our loaf while keeping our original starter. <br>🤔<strong> </strong>If we have a large enough discard from our original starter, we can use that instead.</li><li><strong>Autolyse:</strong> Typically done while the levain is prepared, it’s for mixing the bulk of the recipe’s flour and water separate from the starter and letting it rest until the levain is ready to be mixed.<br>🤔 If we’re skipping the levain step, skipping the autolyse step is not catastrophic for beginners. We can mix our discard all together, or I prefer to mix most of the water with the discard first and then add the bulk of the flour.</li><li><strong>Mixing Techniques: </strong>As a beginner, do whatever it takes to get everything combined into a shaggy doughy mess. Minimize how much flour spills over the counter and makes a mess, and try to scrape what we can from our hands, but it’s not a big deal. We can slap, we can fold, we can slam, we can even yell profanities at it while we pinch it a bunch.</li><li><strong>Rest and Add Salt:</strong> Many recipes are <em>very serious</em> about leaving the salt and a bit of water until after mixing the bulk of the dough and water. The theory is that salt leeches moisture from the flour so it won’t be absorbed as evenly if we do it all at once. Once we mix in the salt, the feel of the dough instantly changes into something much less shaggy and less sticky, it’s delightful. <br>🤔 <a href="https://www.youtube.com/watch?v=Z0o-tkaDqps">Foodgeek did an A/B test on this</a>, and it doesn’t seem to matter if we mix in the salt with the Autolyse step. Seems it’s more ritual than anything, so no need to panic if we mixed in salt prematurely. It is convenient to save a bit of our water reserve for mixing the salt, though.</li><li><strong>Stretch and Fold:</strong> During the “bulk fermentation” step, we’re usually instructed to perform a number of folds to help develop the gluten in the dough so that the webby network of the bread will have enough structure to support itself around all of the lovely bubbles produced by the yeast as it rises and bakes. Different recipes have different techniques here, with different timing. Some recipes suggest using oiled hands for working with dough at this point, but water-wet hands are even better and less messy and doesn’t introduce oil to the dough which can affect the recipe composition. <br>🤔 <a href="https://www.youtube.com/watch?v=Lz9CO1PJ0sM">Another Foodgeek contribution on the topic</a>, it certainly seems worth doing at least a couple of good dough perturbations over a few hours. With a sufficiently mature yeast, even doing nothing produces decent sourdough but not quite as good and we’re taking a gamble on the activity of our yeast to compensate. If we’re busy, do at least two nice gentle lift and coil sets spaced out by 30–60 min, and let it rest until it rises 50–100%. <br>🤔 Do <a href="https://www.youtube.com/results?search_query=sourdough+windowpane+test">the window pane test</a> if we’re unsure if it needs to rest more. Colder environments or less mature yeast could require more time than prescribed here.</li><li><strong>Fold, Roll, and Stitch:</strong> By shaping our dough at this point, we create a tense form that will present the rough shape of the final loaf. With a good tight roll and stitch, the loaf will have a better chance to rise vertically rather than sprawl into a blob. <br>🤔 I’ve unintentionally totally for science skipped this step once and ended up with a very flat loaf that sprawled the circumference of the dutch oven. As far as technique goes, this is one of the harder steps but it pays off to get better at it.</li><li><strong>Banneton, Seam Side Up: </strong>The shape of the banneton helps reinforce the final form of the loaf as we give it additional time to rise. If we don’t have a banneton, we can use any form that is not too much bigger than the desired loaf size. I use a colander lined with a linen towel. <br>🤔 This is the companion step to the Fold, Roll, and Stitch. It’s similarly important, but the seam side up is not a huge deal if we messed up. The loaf won’t have that perfect smooth top to work with on the surface, but it will be just as good inside. Remember to dust the lining with flour so it won’t stick, or some corn meal if we’re feeling fancy.</li><li><strong>Overnight in the Fridge:</strong> Proofing in the fridge is a recurring step from all bakers who love to bake first thing in the morning. What about the hungry night owls? What about all the sourdough bakers who have been making this lovely bread for far long than refrigerators have existed in our society? <br>🤔 We can replace the fridge proofing with a 3–5 hour proof at room temperature, on the longer end if the temperature is low or the starter is less active. Do the poke test if we’re unsure if it’s ready: The recess in the dough from the poke shouldn’t spring back immediately when it’s ready. Cover in plastic or wrap in a bag to prevent the dough from drying out while it’s proofing, especially if we’re refrigerating overnight.</li><li><strong>Pre-heat and Bake From Cold:</strong> Pre-heat the oven to maximum heat, typically 500F, then quickly take out the dough from the fridge, flip onto parchment (since we did seam-side up), dust with some flour, spread the flour, score with a lame (a fancy razor holder), and commit it to the flames.<br>🤔 If we don’t have a dutch oven, or a covered cast iron pot, we can use a baking steel or even a baking sheet. We’ll need another pan placed at a lower rack full of boiling water, to add the moisture to the oven necessary for a nice crispy crust. The lidded dutch oven captures and retains the moisture from the dough, so it’s a bit simpler.<br>🤔 What if the dough is looking a little sad after an overnight in the fridge? This can happen if the yeast isn’t as active as it could be. Take it out from the fridge and give it one more room-temperature proof for 2–4 hours, bonus points if we can proof it somewhere a bit warmer (80–85F), like a seedling warming mat.<br>🤔 No lame? No problem. If we use a safety razor, carefully use a clean razor by hand. Worst case, just grab a nice sharp knife and use that to score. End to end, leaning 45 degrees, half-inch deep cut. Not a huge deal if the scoring step is botched or skipped, the bread will still form just fine but it won’t expand along a specific gorgeous seam of your making.</li><li><strong>Wait For The Hardest Hour Of Your Life: </strong>When we pull the loaf out of the oven, it’s not quite done baking. A rookie mistake is to huddle around the glorious steaming orb-treasure and tear into it like a pack of post-apocalyptic savages. A true intellectual will place an ear near the crust as it cools and hear the crackling transformation within.<br>🤔 If we don’t wait, it will still be edible but: The inside will be extra stretchy or gummy, it might have an “undercooked” vibe to it, some of the final notes of flavour won’t quite develop. Seriously, just wait at least an hour, or until it fully reaches room temperature. If it’s steamy when we cut into it, we didn’t wait long enough.</li></ol><h3>You Can Sourdo-ugh It</h3><p>Let’s be real, we’re all in this for the sourdough puns.</p><p>Here’s a list of ideas we can try if it’s just not working out:</p><ul><li>Suspect the starter is just not ready? Use extra starter, like 30%. If you desperately want vaguely sourdough-y bread and can’t wait, sprinkle a bit of instant yeast when you mix in the starter (half teaspoon should do).</li><li>Other kinds of breads to make while the starter is maturing? <a href="https://cooking.nytimes.com/recipes/11376-no-knead-bread">No-Knead recipes</a> are great, or Almost No Knead. I like ones with a lager beer. I’m a fan of sourdough-hybrid chimera breads. To improvise a recipe, substitute some of the hydration with sourdough starter (remember it’s 100% hydration dough, or 1:1), and substitute some of the water with beer.</li><li>Keep making that discard when you feed, sometimes I’ll keep the feeding ratio but skip a discard to have an extra-big discard the next day. Lots of things we can use that discard for, or even just toss some globs on a frying pan and make crumpets.</li><li>Starter not starting? Try a different flour. The bulk of the yeast in the starter comes from the grains that the flour is made of, and sometimes cheaper flours aren’t the best source of a good healthy yeast — especially avoid bleached flour. Buy the fanciest bread flour available, just to be sure. Try mixing in 5–20% whole wheat or rye in there for extra protein. Some restaurants or bakeries will give away (or sell for super cheap) their starter, if we’re desperate to bootstrap from a known quantity.</li></ul><p>Even if mistakes are made along the way, there’s a good chance we’ll end up with a decent tasting bread product in the end. We must eat our shame as we will our inevitable victory.</p><h3>Additional Resources</h3><ul><li><a href="https://www.theperfectloaf.com/simple-weekday-sourdough-bread/">The Perfect Loaf: Simple Weekday Sourdough Bread</a> Good comprehensive recipe with a handy timeline visualization, good for beginners.</li><li>Video: <a href="https://www.youtube.com/watch?v=jJpIzr2sCDE">The Ultimate Homemade Sourdough Bread</a> Charismatic long-haired fella with a large Youtube audience making sourdough, good instruction for beginners.</li><li>Video: <a href="https://www.youtube.com/watch?v=l0Ob6v8GpM0">Tartine Country Loaf by knormie</a> Nice simple quick video showing the process and techniques.</li><li>Video: <a href="https://www.youtube.com/watch?v=oidnwPIeqsI">Brad and Claire Make Sourdough</a> Hilarious but some advanced techniques without much context for beginners. Honestly this is what got me started, which did not yield the best first result. Feel free to skip until later.</li><li><a href="https://foodgeek.dk/en/">Foodgeek Blog</a> and <a href="https://www.youtube.com/channel/UC7eLtGAzNECUqurqMdiNYJg">Foodgeek Videos</a> Big fan of this, much of what I learned for this post was based on Sune’s work of methodically testing out variations of every variable in a sourdough recipe.</li><li><a href="https://www.reddit.com/r/Sourdough/">/r/Sourdough</a> Obligatory topical subreddit. Can’t go wrong. More resources in the sidebar.</li><li><a href="https://breadcalc.com/">Bread Hydration and Conversion Calculator</a> Anytime I start a loaf, I plug in my intended components here, make some tweaks to reach the desired hydration, and dive in.</li></ul><h3>🍞</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7cfcbed86ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Infura uses Vipnode to manage Ethereum nodes]]></title>
            <link>https://medium.com/@shazow/how-infura-uses-vipnode-to-manage-ethereum-nodes-972cf2acc0f0?source=rss-1bbafa7b5f87------2</link>
            <guid isPermaLink="false">https://medium.com/p/972cf2acc0f0</guid>
            <category><![CDATA[vipnode]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[infrastructure]]></category>
            <dc:creator><![CDATA[Andrey Petrov]]></dc:creator>
            <pubDate>Wed, 11 Dec 2019 22:43:23 GMT</pubDate>
            <atom:updated>2019-12-12T13:43:01.525Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Infura Uses Vipnode to Manage Ethereum Nodes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oCvAJ_AFWhBy6JaIDDgDzA.png" /></figure><p>At <a href="https://infura.io/">Infura</a>, we use Vipnode to control the peers of groups of nodes, where each group has a different role. We’ll explore several recent additions to Vipnode that make this possible. First, a little background about what Vipnode is and how it works.</p><p><a href="https://github.com/vipnode/vipnode">Vipnode is an open source project</a> designed for matchmaking Ethereum nodes with relevant peers. For example, if we have a geth light client, we can use a vipnode pool to find available geth full nodes who will serve our light client.</p><h3>Pools and Agents</h3><p>Vipnode can run in two modes: As a pool, or as an agent. The pool acts as a coordinator server that match-makes connected agents. The agent takes control of a local Ethereum node and connects to a pool to get further instructions about which peers the Ethereum node should connect with.</p><p>If we’re simply looking to peer our node with other nodes on the official demo vipnode pool, we can run:</p><pre>vipnode agent wss://pool.vipnode.org/</pre><p>The agent will connect to the demo pool at <em>pool.vipnode.org</em>, request compatible peers to whitelist the Ethereum node’s NodeID, then connect to the whitelisted peers. This works even if the peers’ normal limits are reached, because whitelisting bypasses the node’s limits.</p><p>At Infura, we take the same idea, but implement it a little differently.</p><h3>Managing Infrastructure</h3><p>By running our own private Vipnode pool, we can ensure that our Ethereum nodes are all peered with each other. By running a separate pool for different kinds of nodes, we can carefully control our internal network topology of our Ethereum nodes.</p><p>Some recent features we added to Vipnode to make this use case more powerful:</p><h4>vipnode agent --min-peers=3</h4><p>Control the number of pool-aware peers the Ethereum node maintains. If the number of node peers that are members of the pool drops below this number, the agent will request more whitelisted peers from the pool. We can use a high number here to always request more peers to make sure all of our nodes are cross-connected with each other.</p><h4>vipnode agent --strict-peers</h4><p>When we run an Ethereum node by default, it’s going to find other random peers to connect with. Strict peers is useful when we want to disable discovery and keep the peer set to be exactly what the pool tells our node to use. Additionally, if a node’s advertised routing information changes (such as the IP address or port), strict peers will force the Ethereum node to reconnect to it with the latest address.</p><h4>vipnode agent --enode.host=”10.1.2.3&quot;</h4><p>A fresh Ethereum node will use the built-in peer discovery mechanism by default. In that process, the node will find its’ own public IP address and use that to advertise connections to peers.</p><p>That’s great for normal nodes, but if we’re running many nodes within a single network cluster then we may want them to peer with each other over our internal network. There are many benefits: Better security isolation, lower latency, no bandwidth costs.</p><p>We can use the --enode= flag to override the entire advertised <em>enode:// </em>connection string, or just override the host component with --enode.host= with our internally-routed IP address.</p><h4>Network Topologies</h4><p>With these three new features, we can create complex arrangements of peer networks. We could have a set of nodes that are fully connected with each other. We could make a set of nodes that is fully isolated in a private network. We can reduce our bandwidth usage by making sure our nodes are connected to each other using the private network routing.</p><p>At its core, Vipnode is a tool for controlling which peers we connect with. Originally this power was used to integrate with a public paywall mechanic, but now it’s also useful for managing clusters of nodes. Keep an eye out for more interesting use cases!</p><p>Follow the project on Github:<br><a href="https://github.com/vipnode/vipnode">https://github.com/vipnode/vipnode</a></p><p>Subscribe to the Vipnode newsletter for release updates:<br><a href="https://tinyletter.com/vipnode/">https://tinyletter.com/vipnode/</a></p><p>. . .</p><p><strong>To stay-up-to-date with the latest Infura product news, tips and tricks, be sure to </strong><a href="https://blog.infura.io/"><strong>follow</strong></a><strong> the Infura blog or </strong><a href="https://infura.us14.list-manage.com/subscribe?u=7bec10aa5be97e80fcb0e7c52&amp;id=13433031de"><strong>subscribe</strong></a><strong> to the Infura newsletter.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=972cf2acc0f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open sourcing urllib3’s finances]]></title>
            <link>https://medium.com/@shazow/open-sourcing-urllib3s-finances-e183740fcba7?source=rss-1bbafa7b5f87------2</link>
            <guid isPermaLink="false">https://medium.com/p/e183740fcba7</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Andrey Petrov]]></dc:creator>
            <pubDate>Mon, 06 May 2019 21:13:09 GMT</pubDate>
            <atom:updated>2019-05-06T21:13:09.242Z</atom:updated>
            <content:encoded><![CDATA[<h3>Andrey 🦃 Petrov on Twitter</h3><p>Proud to be part of the team who built this chonk of vital internet infrastructure. ❤️ Big sincere thank you to our maintainers: @theavalkyrie @sethmlarson @haikuginger @Lukasaoz @sigmavirus24, and to all the other contributors for this very important work. https://t.co/ea3iFClKD5</p><p>Since <a href="https://github.com/urllib3/urllib3">urllib3</a> was created in 2008, we have gained several amazing maintainers and hundreds of contributors. Any time you do anything that touches HTTP in Python, you’re probably using urllib3 behind the scenes. It is the 2nd most downloaded third-party Python package, after pip.</p><p>Tens of thousands of engineering hours were <em>donated</em> by people working on their own time, unpaid. The whole world benefited from these important donations.</p><p>Generous companies have helped the urllib3 contributors and maintainers financially over the years. In the spirit of transparency, I’m going to take a moment to talk about some of our recent funding and how that money was spent.</p><h3>Supportive Employers</h3><p>Above all, I want to applaud employers who are actively encouraging their team to contribute back to open source as part of their job. <a href="https://github.com/urllib3/urllib3#sponsorship">You’re already part of our README</a>, but once more for the active supporters:</p><ul><li>Thank you <a href="https://cloud.google.com/">Google Cloud Patform</a> for supporting <a href="https://github.com/theacodes">Thea</a>, our lead maintainer.</li><li>Thank you <a href="https://www.abbott.com/">Abbott</a> for supporting <a href="https://github.com/sethmlarson">Seth</a>, who has been doing the bulk of the work for a long time now.</li></ul><p>And thank you to all of the employers who have contributed your company’s resources to our project in the past: <a href="https://www.akamai.com/">Akamai</a>, <a href="https://www.hpe.com/">Hewlett Packard Enterprise</a>, and others. If your work on urllib3 is actively being funded by your employer, please send a pull request to be added to the README.</p><h3>Grants and Sponsorships</h3><p>We have received a variety of support in various shapes and sizes over the years. Most recently:</p><ul><li>Thank you <a href="https://www.govcert.lu/">Computer Emergency Response Team of the Government of the Grand Duchy of Luxembourg</a> for funding 8 weeks of Seth’s time towards improving urllib3’s security and robustness.</li><li>Thank you <a href="https://gitcoin.co/grants/65/urllib3">Gitcoin</a> for allocating over $6,000.00 in funds over 3 months that will go towards Seth’s time on urllib3.</li></ul><p>Additionally, <a href="https://tidelift.com/subscription/pkg/pypi-urllib3?utm_source=pypi-urllib3&amp;utm_medium=referral&amp;utm_campaign=blog">urllib3 joined Tidelift Subscription</a> to provide better support guarantees for their paying customers. Our current revenue from the subscription is $417.00 per month ($10,000 over 2 years). This funding is going to Seth for handling support requests and releases. Previously, I was taking $208.50 per month for work as backup maintainer. Thank you <a href="https://tidelift.com/">Tidelift</a>!</p><h3>Does your company benefit from Python?</h3><p>With over 50 million installs per month, urllib3 is a core part of the world’s infrastructure. There is a never ending stream of improvements and fixes that need to be done, especially as HTTP continues to evolve as a technology.</p><p>If you can convince your management to allocate a budget to support the improvement of urllib3, please <a href="https://keybase.io/shazow">get in touch with me</a> or <a href="https://keybase.io/theacodes">Thea</a>. We will find the right urllib3 project and contributor to make good use of the funding, and the whole world will benefit from it.</p><p>Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e183740fcba7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vipnode 2.0 Released]]></title>
            <link>https://medium.com/vipnode/vipnode-2-0-released-9af1d65b4552?source=rss-1bbafa7b5f87------2</link>
            <guid isPermaLink="false">https://medium.com/p/9af1d65b4552</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Andrey Petrov]]></dc:creator>
            <pubDate>Tue, 12 Feb 2019 18:04:46 GMT</pubDate>
            <atom:updated>2019-02-12T18:04:46.058Z</atom:updated>
            <content:encoded><![CDATA[<h4>Progress Update #5</h4><blockquote><strong><em>What is vipnode?</em></strong> Vipnode is an open source implementation of economic incentives for running Ethereum full nodes who serve light clients — a critical component of ETH2.0 sharding! <a href="https://medium.com/vipnode/an-economic-incentive-for-running-ethereum-full-nodes-ecc0c9ebe22">More context here</a>.</blockquote><p>Vipnode has been approaching stability for a while now, so I quietly pushed out an <a href="https://github.com/vipnode/vipnode/releases/tag/v2.0">official 2.0 release</a>.</p><p><a href="https://github.com/vipnode/vipnode#quickstart">Give it a try</a> or watch this quick 7-minute walk-through video:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8TSOT68kB7A%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8TSOT68kB7A&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8TSOT68kB7A%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/d8fccf711d128b522c21aa24b356d8e3/href">https://medium.com/media/d8fccf711d128b522c21aa24b356d8e3/href</a></iframe><h4>What’s new?</h4><p>Bugs have been ironed out (including a couple from the walkthrough video — see if you spot them), documentation has been polished, beta users’ feedback has been implemented. Overall, things are looking good.</p><p>Check out the demo pool dashboard: <a href="https://vipnode.org/status/">https://vipnode.org/status/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yS-AFMJKulBILBHq8ByYtw.png" /><figcaption>Vipnode Pool Dashboard</figcaption></figure><p>If you run an Ethereum full node on mainnet, get yourself on here and start earning some sweet Rinkeby-ETH!</p><h4>What’s next?</h4><p>As we plan towards v3.0, there are lots of paths we can take. It really depends on community interest and finding additional funding. Some ideas:</p><ul><li><strong>Add a web3 proxy feature to pools</strong>, so your vipnode pool can be a “mini-Infura.” Should be a reasonably small amount of work for a baseline implementation, and pretty cool. Use vipnode to run your own Infura cluster!</li><li><strong>Add vipnode support for Ultra-Light Clients, </strong>which is a feature <a href="https://github.com/ethereum/go-ethereum/pull/16904">recently merged into Geth</a> courtesy of the Status-IM team. With any luck, this will require minimal changes to vipnode.</li><li><strong>Deploy a pool with mainnet payments</strong> so you can earn <em>real</em> money with the demo pool. Not super excited about the tax and legal liability with hosting this, but maybe it’s the right next step unless someone else wants to do it.</li><li><strong>Implement trustless payments</strong> using peer-to-peer state channels or a side-chain or using <a href="https://ethresear.ch/t/on-chain-scaling-to-potentially-500-tx-sec-through-mass-tx-validation/3477">some cutting edge ZK-SNARKs research</a>. This is clearly something that will need to happen eventually, but it’s a big chunk of work that would require a lot more funding.</li><li><strong>Build a demo wallet with native vipnode integration</strong> to show how seamless it can be. I’m still working towards integration with Status and WallETH but ultimately it might be easier to just make a super-simple wallet to illustrate the potential. (<a href="https://medium.com/vipnode/vipnode-progress-update-3-16b07037d3b3#bb8a">More about <em>Usability</em> in the previous progress update</a>.)</li></ul><p>Would love to hear what’s important to you! Please direct some discussion here: <a href="https://github.com/vipnode/vipnode.org/issues/13">https://github.com/vipnode/vipnode.org/issues/13</a></p><h4>How can you help?</h4><ol><li><a href="https://gitcoin.co/grants/32/vipnode"><strong>Support vipnode on Gitcoin</strong></a><strong>.</strong> They’re matching contributions based on the number of contributors, so every dollar counts. ❤️</li><li><a href="https://github.com/vipnode/vipnode#quickstart"><strong>Add your full node to the demo pool</strong></a><strong>. </strong>The best feedback is from people who are actually using vipnode. 😼</li><li><a href="https://tinyletter.com/vipnode"><strong>Sign up to the Vipnode Newsletter</strong></a> for future updates. 🍁</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9af1d65b4552" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vipnode/vipnode-2-0-released-9af1d65b4552">Vipnode 2.0 Released</a> was originally published in <a href="https://medium.com/vipnode">Vipnode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vipnode: Progress Update #3]]></title>
            <link>https://medium.com/vipnode/vipnode-progress-update-3-16b07037d3b3?source=rss-1bbafa7b5f87------2</link>
            <guid isPermaLink="false">https://medium.com/p/16b07037d3b3</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Andrey Petrov]]></dc:creator>
            <pubDate>Tue, 20 Nov 2018 20:18:10 GMT</pubDate>
            <atom:updated>2018-11-20T21:37:43.455Z</atom:updated>
            <content:encoded><![CDATA[<p>Overall: Feature complete for the v2 milestone, approaching the v2.0 release.</p><blockquote><strong><em>What is Vipnode?</em></strong><em> Vipnode is an implementation of economic incentives for running Ethereum full nodes who serve light clients. </em><a href="https://medium.com/vipnode/an-economic-incentive-for-running-ethereum-full-nodes-ecc0c9ebe22"><em>More context here</em></a><em>.</em></blockquote><h3>Current Status</h3><p>We’re approaching a stable release! You can try the latest demo binary release here: <a href="https://github.com/vipnode/vipnode/releases">https://github.com/vipnode/vipnode/releases</a></p><p>Once we’re done with the pre-releases, the plan is to dive straight from 0.2.x into v2.0. It’s a weird versioning strategy but I’ve been referring to the original MVP implementation as “v1” and the current roadmap as “v2” so that’s what we’re doing.</p><p>There is still a lot of love needed for all the pieces, but I’m comfortable to say that we’ve exceeding the deliverables of the “v2” milestone (which was the Ethereum Foundation grant milestone). 🎊</p><h3>Payments: A Walkthrough</h3><p>The big theme of this release is integrating payments. Recall that the premise of v2 is that full node hosts can earn money for servicing light clients, and light clients will be paying for the privilege.</p><p>The implementation of the payment mechanism is generalized. The demo example is using a smart contract, but it could really be anything —imaginary internet points, tokens, or even credit card! Adding another payment mechanism can be done by specifying your own settlement handlers for <a href="https://godoc.org/github.com/vipnode/vipnode/pool/payment#PaymentService">payment.PaymentService</a> or implementing a custom <a href="https://godoc.org/github.com/vipnode/vipnode/pool/balance#Manager">balance.Manager</a> provider.</p><p>The rest of this post will focus on the sample payment mechanism we’re shipping with: The <a href="https://github.com/vipnode/vipnode-contract">smart contract</a> and DApp solution.</p><h4>Client</h4><p>When you run the <em>vipnode</em> binary as a client, it looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SAQzP0yCZaIoVEioERUxgg.png" /><figcaption>Connecting with a vipnode client</figcaption></figure><p>Each pool will be able to supply their own welcome message with rules and instructions for managing your node’s balance. The demo pool allows you to accrue a negative balance for now, so you won’t get disconnected even if you’re unregistered.</p><p>If you open the link in the alert, you’ll land on the DApp (make sure to use a web3-enabled browser).</p><h4>DApp</h4><p>The current contract is <a href="https://rinkeby.etherscan.io/address/0x0244998de1c9f072aa560b5c0e5221ed7be0b1ec">deployed on Rinkeby</a> and the DApp lives on <a href="https://vipnode.org/pool/">https://vipnode.org/pool</a> for now. Another big thanks to <a href="https://medium.com/u/e611097a5bd4">Tracy Osborn</a> for helping clean up the design here!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FcxwGwYxJfb4TEX_8WjLRg.png" /><figcaption>Payment DApp for the vipnode demo</figcaption></figure><p>If you clicked the link from your vipnode client alert prompt, the <em>Add Node</em> input will be pre-filled, so all you have to do is mash the button.</p><p>As a client, your balance will decrease with usage (maybe we need a ‘Total’ field that adds the Balance to the Deposit). A less generous pool will kick you once your negative balance exceeds your deposit amount.</p><p>If you’re done with this pool and want to cash out, you can <em>Request Withdraw </em>which will trigger the pool to queue up a withdraw transaction. If the pool disappears for more than a week, you can <a href="https://github.com/vipnode/vipnode-contract/blob/b4c4b17112d6fc7d4c41b050f91f3454c602d62c/contracts/VipnodePool.sol#L61">force a settlement on-chain</a> and get your money that way.</p><h4>Host</h4><p>The host experience is similar to the client, except you need to provide a public enode string (<a href="https://github.com/vipnode/vipnode/issues/9">which includes your IP address and port for now</a>) and a payout address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3fFkNSuutjFNlWFZ06P1aA.png" /><figcaption>Connecting with a vipnode host</figcaption></figure><p>Once the host is connected, the pool will start routing clients to your host. As clients connect, the host’s balance will grow on every minute update.</p><p>When the host wants to cash out, they can go to the same DApp and use the same <em>Request Withdraw</em> process that the client can use. For the most part, internally, clients and hosts are symmetric. A user can be both a host and a client at different times, and contribute to or draw from the same balance.</p><h4>Usability</h4><p>“Boy, this seems a bit complicated for The Average User, no?”</p><p>Perhaps, but that doesn’t matter because your favorite wallet can integrate all of this natively and the user doesn’t need to see any of it!</p><p>Imagine: You fire up your local neighborhood wallet, and you might see a prompt: “Having trouble connecting. Do you want to deposit $10 to use with a paid provider?” The wallet can do the rest behind the scenes.</p><p>The command-line client above is a <em>proof of concept</em> that can totally be used today! Underneath, there is a simple API that any wallet can implement, and I’m talking with several teams about moving forward with integration.</p><h3>What’s next?</h3><ul><li>Recent focus was on adding importing features, so now it’s time to clean up and polish. For example: Make the payment settings configurable (they’re currently hardcoded). Host connecting shouldn’t require as many parameters (we can derive much of it). <a href="https://github.com/vipnode/vipnode/search?q=TODO&amp;unscoped_q=TODO">Lots of TODOs</a> in general.</li><li>I’m putting together an Ethereum Magicians Working Group for coordinating between wallet stakeholders who need a minimal-resource client support like light clients: <a href="https://ethereum-magicians.org/t/forming-a-ring-constrained-resource-clients/1944">https://ethereum-magicians.org/t/forming-a-ring-constrained-resource-clients/1944</a></li><li>Getting an integration with an actual wallet is a higher priority now in general.</li></ul><p>That’s all for now. <a href="https://github.com/vipnode/vipnode/releases">Give the latest demo a try</a> and let me know what you think. I’m travelling the next couple of weeks, so please be patient with replies.</p><p>Sign up to the <a href="https://tinyletter.com/vipnode">Vipnode Newsletter</a> for future updates.</p><p>🍁</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16b07037d3b3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vipnode/vipnode-progress-update-3-16b07037d3b3">Vipnode: Progress Update #3</a> was originally published in <a href="https://medium.com/vipnode">Vipnode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vipnode: Progress Update #2]]></title>
            <link>https://medium.com/vipnode/vipnode-progress-update-2-6e7c65d7d638?source=rss-1bbafa7b5f87------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e7c65d7d638</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Andrey Petrov]]></dc:creator>
            <pubDate>Tue, 04 Sep 2018 21:30:58 GMT</pubDate>
            <atom:updated>2018-09-04T21:30:58.013Z</atom:updated>
            <content:encoded><![CDATA[<p>Overall: Trimmed scope to meet end-of-August milestone due to some delays.</p><h3>What went well?</h3><ul><li><strong>Infura partnership is official!</strong> I’m collaborating with the team towards building out the Vipnode protocol and tooling to power a more decentralized Infura. 🎊</li><li><strong>New redesign of </strong><a href="https://vipnode.org/"><strong>vipnode.org</strong></a><strong> is up</strong>, thanks to <a href="https://medium.com/u/e611097a5bd4">Tracy Osborn</a>. 🎉</li><li>Ethereum Foundation grant funding was successfully disbursed. 💸</li><li>Blocking pull request to go-ethereum was finally merged and released (<a href="https://github.com/ethereum/go-ethereum/pull/16333">rpc: Add admin_addTrustedPeer and admin_removeTrustedPeer</a>). This was the only upstream blocker for the vipnode design. I’ve been trying to push this through for a long time so I’m quite excited. 🥳</li><li><a href="https://github.com/vipnode/vipnode">github.com/vipnode/vipnode</a> command-line is partially functional, and I am in the process of setting up a public demo. The payment component is entirely missing for now, but you can get a feel for the flow in general. 📠</li><li><a href="https://github.com/status-im/status-go/issues/1025">Some discussions with status-im about integrating vipnode</a>. Nothing formal yet, but there is a lot overlap here. 👩‍💻</li><li>Interest from several smaller groups who offered to put up resources or joining a vipnode pool with their own nodes. A bit too early for that, but soon! 😎</li></ul><h3>Unplanned Delays</h3><ul><li>The pool-host RPC connection requires bi-directional calling (<a href="https://raw.githubusercontent.com/vipnode/vipnode.org/master/docs/clientflow.png">diagram</a>). In theory, there is nothing about the JSONRPC2.0 spec that prevents this, but unfortunately I was unable to find any libraries that implement it. I ended up <a href="https://godoc.org/github.com/vipnode/vipnode/jsonrpc2">writing my own library</a> that supports bidirectional RPC — it has some good ideas but still needs a lot of cleanup and polish. Overall I’d say this detour used up 2 weeks so far, and probably needs another 2 weeks for “Production Ready” polish. I am also considering just switching to gRPC, which would also probably be around 2 weeks of work. Any informed thoughts on this are welcome.</li><li>I tried to get a hold of some go-ethereum core devs to confirm my findings regarding the <a href="https://medium.com/vipnode/vipnode-progress-update-b3b53e4ea7a2">Custom Boot Node progress in the previous post</a>, but it seems all the relevant people decided to take extended vacations during the past couple of months (related to why the PR took so long to merge). At this point it’s too late to pursue that path, which is fine.</li></ul><h3>What’s next?</h3><ul><li>Payment and client registration component for vipnode. The reference implementation will be smart contract based again, much of the work on it is already done here: <a href="https://github.com/vipnode/vipnode-contract">https://github.com/vipnode/vipnode-contract</a></li><li>Make sure Parity is well-supported (the plumbing is there, but it needs more attention to make sure there aren’t any surprises).</li><li>Deploy a vipnode pool that other third-party hosts and clients can join. This is the completion milestone for the Ethereum Foundation grant proposal. (Aiming for sometime in September.)</li><li>Write up good documentation for onboarding vipnode hosts and clients. Clean up Github issues to make it easier to get a feel for project state.</li><li>Start working with Ethereum wallets towards integration.</li><li>There are several not-critical Parity client RPC features that may need to be upstreamed. Particularly per-peer Connect/Disconnect RPCs for Parity, but it’s less urgent.</li><li><a href="https://github.com/vipnode/vipnode.org/issues/13">Lots of stuff in the v3 wishlist</a>, but not going to start thinking about this until the next milestone.</li></ul><p>Much to do over September and October. Expect an announcement when vipnode v2 is ready for your nodes!</p><p>🍁</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e7c65d7d638" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vipnode/vipnode-progress-update-2-6e7c65d7d638">Vipnode: Progress Update #2</a> was originally published in <a href="https://medium.com/vipnode">Vipnode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vipnode: Progress Update]]></title>
            <link>https://medium.com/vipnode/vipnode-progress-update-b3b53e4ea7a2?source=rss-1bbafa7b5f87------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3b53e4ea7a2</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Andrey Petrov]]></dc:creator>
            <pubDate>Tue, 19 Jun 2018 14:23:01 GMT</pubDate>
            <atom:updated>2018-06-19T14:23:01.413Z</atom:updated>
            <content:encoded><![CDATA[<p>Overall: On track for end of August, despite a couple dead ends.</p><h4>Engagement</h4><p>Last month, I published ‘<a href="https://medium.com/@shazow/an-economic-incentive-for-running-ethereum-full-nodes-ecc0c9ebe22">An economic incentive for running Ethereum full nodes</a>’ where I announced the vipnode grant funding, design, and goals.</p><p>The article did well, after receiving <a href="https://www.reddit.com/r/ethereum/comments/8moeug/an_economic_incentive_for_running_ethereum_full/">some attention from /r/ethereum</a> and even earned <a href="https://ethfans.org/posts/an-economic-incentive-for-running-ethereum-full-nodes">a Chinese translation on EthFans</a>. Pretty cool.</p><p><a href="http://tinyletter.com/vipnode">The newsletter</a> is up to 60 subscribers, and the old single vipnode has 20 paying customers (which was the cap in the smart contract — oops — raised to 100 now), raking in a modest 0.1691338 ETH (about $96 USD at time of transacting).</p><h4>Partnerships &amp; Upstream Updates</h4><ul><li>Ethereum Foundation grant paperwork was submitted last month, but the grant has not been disbursed yet.</li><li><a href="https://infura.io/">Infura</a> has been very supportive since we met during EDCON. They’ve already donated some server resources, and we’re in talks about additional collaboration/sponsorship. Our long-term goals are very aligned, and we hope to reach a design and implementation that works for everyone!</li><li><a href="https://walleth.org/">WallETH</a> expressed interest in integrating vipnode into the mobile client. <a href="https://github.com/vipnode/vipnode.org/issues/4">We’re looking for more third-party wallets which use the Light Node protocol to collaborate on the integration design</a>.</li><li><a href="https://github.com/ethereum/go-ethereum/pull/16333">go-ethereum PR for addTrustedPeer/removeTrustedPeer is pending</a>.</li><li><a href="https://medium.com/u/e611097a5bd4">Tracy Osborn</a> is starting to help with design and frontend work.</li></ul><h4>Migrated Website and Repos</h4><ul><li><a href="https://vipnode.shazow.net/">https://vipnode.shazow.net</a> → <a href="https://vipnode.org/">https://vipnode.org/</a></li><li><a href="https://github.com/shazow/vipnode">https://github.com/shazow/vipnode</a> → <a href="https://github.com/vipnode">https://github.com/vipnod</a>e</li></ul><h4>Design Changes</h4><p>The original design used ethstats to verify peering on both ends, and a custom bootnode to route clients to the next available vipnode. Due to inherent limitations, these are being replaced with a simple JSON RPC 2.0 API that third-party wallets will need to implement to participate. Details follow.</p><h4>Custom Ethstats Collector</h4><p>I completed an implementation of the ethstats/netstats collection protocol: <a href="https://github.com/vipnode/ethstats">https://github.com/vipnode/ethstats</a></p><p>As far as I can tell, this is the only alternative implementation to <a href="https://github.com/cubedro/eth-net-intelligence-api">the original NodeJS implementation</a>. If you’ve been looking to build a custom ethstats collector, this is for you!</p><p>Unfortunately, in the process of reversing the protocol, I discovered that it will be insufficient for what vipnode needs. There is <a href="https://github.com/vipnode/ethstats#appendix">some discussion in the README</a>, but the main incompatibility are:</p><ul><li>Stats messages are not authenticated. This means that as long as a client is <em>authorized</em> to publish, it can pretend to be any node and send false stats for it.</li><li>Stats do not include the list of peers. I misread the original code, thinking it did. Instead, it just includes the peer <em>count</em>. We need the list of peers to validate participation on both ends.</li><li>There are fewer client implementations than I suspected. It seems geth is the only client that ships with a built-in implementation. Parity does not. If clients are going to need to implement something anyways, then we may as well build our own simpler API.</li></ul><p>Lessons learned here will inform our design moving forward.</p><h4>Custom Boot Node</h4><p><a href="https://github.com/vipnode/ethboot">I started implementing a custom boot node</a> that was going to be used to route clients to the next available vipnode, but discovered that this won’t work.</p><p>It took some significant effort to figure out how discovery on the Ethereum network is supposed to work vs how it actually works.</p><p>Turns out the default client behaviour is not compatible with being forced to use specific nodes via a boot node. Instead, the client will continue to accumulate additional potential nodes by traversing the network, then choose a subset to connect with at ~random. This is unfortunate but not a blocker.</p><p>Since we’re already committing to having third party wallets implement a small vipnode API, then we’re going to add one more call there to acquire the set of vipnodes that are ready to accept connections instead of doing it automagically through a fancy bootnode like originally imagined.</p><h4>What else?</h4><p>I took some time to measure the minimum required resources for running a full node (big thanks to <a href="https://infura.io/">Infura</a> for donating a server!):</p><h3>Andrey 🦃 Petrov on Twitter</h3><p>Some stats from sync&#39;ing the Ethereum blockchain the other day: geth 1.8.7 with --fast, zero to recent block in 4 hours, then 2 more hours catching up on the states. Overall, 6hr43min to live. 94GB of storage used by the blockchain db, 67GB received from 50 peers, 18GB sent.</p><p>There is a lot of FUD going around about how much the Ethereum blockchain is growing and the associated resources. Hopefully this sets a more realistic baseline for people.</p><p>Some notes:</p><ul><li>While the bandwidth received is already far lower than storage used, it is still exacerbated by the fact that 50 peers were connected. The minimum bandwidth required will be less than this. I plan to run another test with just 1 peer.</li><li>Parity’s database compacting should perform even better.</li><li>The latest optimizations in geth (1.8.11) should improve these numbers substantially.</li></ul><p>I’ll try to do more tests like this in the future and possibly build out more streamlined measurement infrastructure as part of the vipnode project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3b53e4ea7a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vipnode/vipnode-progress-update-b3b53e4ea7a2">Vipnode: Progress Update</a> was originally published in <a href="https://medium.com/vipnode">Vipnode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An economic incentive for running Ethereum full nodes]]></title>
            <link>https://medium.com/vipnode/an-economic-incentive-for-running-ethereum-full-nodes-ecc0c9ebe22?source=rss-1bbafa7b5f87------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecc0c9ebe22</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[infrastructure]]></category>
            <dc:creator><![CDATA[Andrey Petrov]]></dc:creator>
            <pubDate>Tue, 08 May 2018 20:21:04 GMT</pubDate>
            <atom:updated>2019-01-09T16:41:21.198Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a story about <a href="https://vipnode.shazow.net/">vipnode</a>, an <a href="https://blog.ethereum.org/2018/05/02/announcing-may-2018-cohort-ef-grants/">Ethereum Foundation Grant recipient</a>.</p><h3>Full Node, Light Node: What’s the difference?</h3><p>When you connect to the Ethereum network, you can use a <em>full node</em> or a <em>light node </em>(also known as a <em>light client</em>).</p><p>A <strong>full node</strong> has a copy of the entire state of the Ethereum blockchain and executes every transaction that gets mined — this requires upwards of 120GB of storage and 8GB+ of memory (<a href="https://twitter.com/shazow/status/1004506114392838146">some actual stats</a>). It can take several hours for a full node to join the network and become fully synchronized. If you wanted to run a full node in the cloud, it would cost around $20/mo.</p><p>A <strong>light node</strong> has only the minimal amount of state to make sense of things while talking to full nodes. We’re talking just a few hundred megabytes of storage and 128–512MB of memory. The goal of a light node is to be small enough to run on a phone or embedded device.</p><p>Any time a light node wants to query the blockchain or send a transaction, it must ask a full node to do it on its behalf. In effect, a light node is a mooch. But that’s okay.</p><p>A light node can join the network and start using it almost instantly, <strong>assuming it can find a full node with a light node slot available for it.</strong></p><h3>“Why won’t my Light Node connect to the network?”</h3><p>Two things happened in late-2017 which broke light nodes.</p><h4>1. Cryptokitties</h4><p>A massive influx of new users swarmed the Ethereum network, many of them relying on light nodes to trade their fancy cats and make sweet bank. We can see the usage skyrocket by observing the transaction fees go up:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ejIHPlAcvi5fX_FYvRGjZQ.png" /><figcaption><a href="https://etherscan.io/chart/transactionfee">https://etherscan.io/chart/transactionfee</a></figcaption></figure><h4>2. Light Ethereum Subprotocol Upgrade</h4><p>Around the same time, LES/2 was released — an upgrade of the protocol used for serving Light Nodes. The new protocol was still considered experimental and the server implementation was buggy. This meant that a lot of clients switched over to the new protocol, but many of the old full nodes were still running older code which did not support the upgrade.</p><h4>The Result?</h4><p>I was running some light nodes myself around that time. Normally, I’d fire up my light node and it would be up and running within a minute. Come December, everything broke. I’d leave my node up overnight and it would still fail to find a compatible full node with a free spot for it.</p><p>The Github Issues on the project were flooded with complaints, too:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NbsAq_51o2E_BMBChQUhQQ.png" /><figcaption><a href="https://github.com/ethereum/go-ethereum/issues?utf8=%E2%9C%93&amp;q=syncmode+light+peers">https://github.com/ethereum/go-ethereum/issues?q=syncmode+light+peers</a></figcaption></figure><h3>We need more Full Nodes with Light Nodes slots!</h3><p>Okay. How do we convince more full nodes to spend time and effort running potentially risky experimental code? An economic incentive is in order.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MM3BW3_xm9GLBVas7GDRGA.png" /><figcaption><a href="https://vipnode.shazow.net/">https://vipnode.shazow.net/</a></figcaption></figure><p>The first version of vipnode was very simple: I hosted a single full node controlled by a short “driver” which monitored the smart contract for new subscribers. When someone paid for a VIP membership, the VIP’s public key (the enode ID) was whitelisted by my vipnode server. That means even if my server was full, it would still allow the VIP to bypass the server’s limits.</p><p>After chatting with the very-encouraging <a href="https://twitter.com/robbiebent1">Robbie Bent</a> and <a href="https://twitter.com/jon_choi_">Jon Choi</a> (thank you again), I was convinced to submit a grant proposal to the Ethereum Foundation to build out a more complete version of vipnode.</p><h4>Pools for vipnode</h4><p>In the Version 2 proposal, I outlined the design for vipnode pools. Any full node can join a vipnode pool and start earning proportional revenue from serving VIP subscribers.</p><p>In order to be able to track how much share each node deserves, we must rely on a few features of how Ethereum clients are designed:</p><ul><li>A client can specify an <em>ethstats</em> server which will receive handy analytics about the client like information about peers it’s connected to. The <em>vipstats</em> server will use this information to receive client-side claims about which vipnode it’s connecting to.</li><li>A server can be controlled through an RPC API. A companion <em>vipnode</em> process will use the API to manage whitelisted peers (Parity already supports this, Geth is <a href="https://github.com/ethereum/go-ethereum/pull/16333">pending the merging of my PR</a>). When a new VIP registers, all members of the pool will be instructed to whitelist the new enode ID. When a VIP connects, the node will send a claim to the <em>vipstats</em> server.</li><li>When the <em>vipstats</em> server corroborates the claims from the client and server, it will allocate a proportional fee of the pool’s revenue to that server. The structure of this fee is still up in the air. Perhaps per amount of time, or a flat rate, or something else. Each pool can decide their own structure.</li><li>If one side is inconsistent, then the <em>vipnode</em> will refuse to count it and the server will disconnect a client which fails to corroborate the claim without some timeout.</li><li>The <em>vipstats</em> server will also act as a custom bootnode that VIPs can use to direct their clients to connect to the correct set of full nodes.</li></ul><h3>Extending Incentives</h3><p>The vipnode design can be extended for all kinds of server-client incentives. Imagine different kinds of pools that you can pay into with different kinds of guarantees:</p><ul><li>Pools for managed clusters (like an Infura pool — a <em>Decentralized Infura</em>).</li><li>Pools for risky experimental features (like when LES/2 first launched).</li><li>Pools for non-standard extended API support (with inverted indices supporting complex queries like the the Etherscan API).</li><li>Pools for Big Miners. When milliseconds matter, it can be valuable to guarantee direct access to some of the largest miners.</li></ul><p>We can use the vipnode pool design as a measure of marketplace demand. Anyone can start a pool and put initial client funds in it to encourage people to start running full nodes to take the other side of it.</p><h3>Where are we now?</h3><p>I’m starting to work on the pool implementation now. I’m aiming to have a beta in August 2018 and a more polished version in September.</p><p>Everything is open source under the MIT license. You can follow along at: <a href="https://github.com/vipnode">https://github.com/vipnode</a></p><p>Newsletter is here:<br><a href="https://tinyletter.com/vipnode">https://tinyletter.com/vipnode</a></p><p>If you’d like to try the working v1 prototype, it’s here:<br><a href="https://vipnode.shazow.net/">https://vipnode.org/</a></p><p>Special thanks to the Ethereum Foundation for supporting this research and development. I continue to be impressed with the ambition, generosity, and effectiveness of this community, and I’m honoured to be a part of it.</p><p><strong>Update:</strong> <a href="https://medium.com/vipnode">Follow progress and announcements here</a>.</p><p>Translations of this article:</p><ul><li>Chinese: <a href="https://ethfans.org/posts/an-economic-incentive-for-running-ethereum-full-nodes">https://ethfans.org/posts/an-economic-incentive-for-running-ethereum-full-nodes</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecc0c9ebe22" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vipnode/an-economic-incentive-for-running-ethereum-full-nodes-ecc0c9ebe22">An economic incentive for running Ethereum full nodes</a> was originally published in <a href="https://medium.com/vipnode">Vipnode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My computer is my home]]></title>
            <link>https://medium.com/@shazow/my-computer-is-my-home-5a587dcc1d76?source=rss-1bbafa7b5f87------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a587dcc1d76</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[computers]]></category>
            <category><![CDATA[thinkpad]]></category>
            <dc:creator><![CDATA[Andrey Petrov]]></dc:creator>
            <pubDate>Thu, 08 Mar 2018 16:34:36 GMT</pubDate>
            <atom:updated>2018-03-08T16:34:36.044Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KK93rKoxPz4fHWVv6lSICQ.png" /></figure><p>I spent fifty hours setting up my new computer, and I feel a mixture of shame and pride about it.</p><p>We spend a lot of our lives in our computers. Working, socializing, relaxing. On the work laptop, at the home desktop, on the phone in bed.</p><p>We live in our computers, and we do little things to make ourselves feel more at home in them — a little more cozy. We change the wallpaper, install some new apps, buy a pretty case and some stickers for the back. We find ways to make our devices different from other peoples’. We personalize what we can. What we’re permitted.</p><p>In 2008, I bought my first iPhone. Shortly after, I bought my first Macbook Pro. Coming from Linux, the Apple ecosystem felt clean and fresh. It felt like checking into a hotel. Everything I will need was laid out on the counter, and anything else could be arranged by the concierge (perhaps for a fee). I made myself at home.</p><p>Over the years, I started to feel disassociated from my devices. They were mine, but they didn’t feel mine. The immersion of ownership would frequently break as a corporate policy kicked my favorite app out of their store, or a feature I wanted was forbidden by the exposed API, or the pressure to buy newer hardware grew each year with forced software upgrades.</p><p>Imagine living in a hotel. You check in, put your backpack down on the luggage rack, and kick off your shoes. It’s a little different from your last hotel, but also the same. A television that you avoid, not because there is work to do but because the remote looks kind of gross. A lamp that is using up the only power outlet next to the bed, which you need for charging your phone overnight. There is a desk, but the padded office chair doesn’t lift enough to use it comfortably.</p><p>You’ll be in the hotel for a while, so you can make yourself comfortable and add a bit of yourself to it. You request a <a href="https://www.cnbc.com/id/47890272">fish bowl from the concierge</a>, and you name the fish <em>Chee</em> (short for <em>Cheeto</em>). You bring some chocolates from the Quik Mart a few streets away. You play some music on the complementary bluetooth speaker.</p><p>Ultimately, the hotel is an organism that operates outside of you. The unfinished chocolates disappear after a cleaning. The speaker keeps disconnecting sporadically. <a href="https://www.peta.org/blog/making-waves-hotel-chain-ends-fish-rental-program-with-petas-help/">They take Chee away</a>.</p><p>I switched to Android a few years back (after Lollipop came out, the first <em>good</em> Android). This week, I am giving up my fourth Macbook Pro — my final Apple device. Apple makes beautiful devices that were unrivaled for a long time, but convenience and uniformity comes at a price. I have come to crave <em>fragmentation</em>.</p><p>The shame is obvious: I didn’t spend those fifty hours doing things like building better insulin control software for diabetic people or campaigning for affordable housing.</p><p>I spent those hours building my perfect computer home. Like a fresh cabin in the wilderness, there were some false starts. Some kernel modules were missing, or the full-disk encryption was misconfigured. At one point, about twenty hours in, I knocked it all down and started from the foundation again.</p><p>I learned very much — about binary firmware embedding in the kernel and LUKS disk encryption and systemd quirks.</p><p>More than anything, I made it feel <em>mine.</em> I will keep tweaking everything throughout the lifetime of <a href="https://www3.lenovo.com/us/en/laptops/thinkpad/thinkpad-x/ThinkPad-X1-Carbon-6th-Gen/p/22TP2TXX16G">this laptop</a> and I’m sure much of the configuration will survive to the next. Lay out some area rugs, new cutlery, softer lighting, art for the walls. Hopefully not fifty hours in one week, but a few hours here and there. With each improvement, I will feel more at home, and there is no limit to what I can do.</p><p>I am proud of my new computer home.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a587dcc1d76" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>