<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>m</title>
    <description></description>
    <link>https://speakerdeck.com/mmmmm</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/mmmmm.rss"/>
    <lastBuildDate>2020-01-30 04:19:48 -0500</lastBuildDate>
    <item>
      <title>Why did we pick Substrate?</title>
      <description>Substrate is a modular and open-source framework for building blockchains. 
At KILT Protocol / BOTLabs, we were very early adopters of Substrate. We favoured it over much more widely-used tooling. But why?
Substrate's technical advantages are only part of the answer; the ideology behind it and  its developer experience played a huge role.</description>
      <media:content url="https://files.speakerdeck.com/presentations/39b6ae53dabd433d9006a4058ea4a37a/preview_slide_0.jpg?14763533" type="image/jpeg" medium="image"/>
      <content:encoded>Substrate is a modular and open-source framework for building blockchains. 
At KILT Protocol / BOTLabs, we were very early adopters of Substrate. We favoured it over much more widely-used tooling. But why?
Substrate's technical advantages are only part of the answer; the ideology behind it and  its developer experience played a huge role.</content:encoded>
      <pubDate>Thu, 05 Dec 2019 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/mmmmm/why-did-we-pick-substrate</link>
      <guid>https://speakerdeck.com/mmmmm/why-did-we-pick-substrate</guid>
    </item>
  </channel>
</rss>
