<?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 Stephen Fiser on Medium]]></title>
        <description><![CDATA[Stories by Stephen Fiser on Medium]]></description>
        <link>https://medium.com/@stephen_fiser?source=rss-40e57b6ee3be------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*csGIvrAcV1OHj1A5Xi2Stw.png</url>
            <title>Stories by Stephen Fiser on Medium</title>
            <link>https://medium.com/@stephen_fiser?source=rss-40e57b6ee3be------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:15:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stephen_fiser/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[The Case for Small Contracts]]></title>
            <link>https://medium.com/bluebear-tech/the-case-for-small-contracts-186b39b8fb3e?source=rss-40e57b6ee3be------2</link>
            <guid isPermaLink="false">https://medium.com/p/186b39b8fb3e</guid>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Stephen Fiser]]></dc:creator>
            <pubDate>Fri, 10 Aug 2018 14:47:21 GMT</pubDate>
            <atom:updated>2018-08-10T14:47:21.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QM40c2jKcYy8a5SHjpjwTA.jpeg" /></figure><p>Software changes.</p><p>Requirements change. Needs expand. Bugs are found. Better ways to do things are identified. Security is breached.</p><p>What do we do? We change the code.</p><p>Blockchain smart contracts present a problem. Once deployed, the code can no longer be changed. So what happens when we find a bug after people are using the contract in production?</p><p>The whole idea behind blockchain is decentralization, so once you have deployed a contract, you can’t know who is using it and update them with a new contract address to which to switch. That rules out fixing the bug and redeploying the contract as a serious solution. (This is because the newly deployed contract will have a new address, and the old contract will still live at the old address.)</p><p>A different idea is to break up big contracts into many small contracts and have the top level contract point to them. (You’d also include methods to change all of the pointers.)</p><p>This is essentially object oriented programming (OOP).</p><p>In OOP, you want to be able to send messages to objects to trigger some kind of behavior without caring what the underlying implementation details are. To this end, if you have many small contracts that implement features, you could deploy an update to the implementation of a specific function on one of them, and then you could update the top level contract to point to the newly deployed version.</p><p>A limitation of this strategy is that the public API of all of the underlying contracts cannot be edited. It can be extended, but method names and signatures already in use must remain the same. However, the code inside those methods can change, and that is what we care about.</p><p>In reality, this creates a very similar situation to running a large scale public API on the web. Changing the web endpoints for a public API is very difficult because you will break applications that communicate with your API. If you rule out breaking client applications as an option, you could say that changing those sorts of things is impossible. However, you are free to change the underlying implementation.</p><p>Considering this, I would argue that the strategy I outline is a viable and reasonable approach to changing code over time on the blockchain.</p><p>In future articles, I’ll dig into specific examples.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=186b39b8fb3e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bluebear-tech/the-case-for-small-contracts-186b39b8fb3e">The Case for Small Contracts</a> was originally published in <a href="https://medium.com/bluebear-tech">Blue Bear Digital Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Supply Chain Finance Reimagined on the Blockchain]]></title>
            <link>https://medium.com/bluebear-tech/supply-chain-finance-reimagined-on-the-blockchain-417d857e1791?source=rss-40e57b6ee3be------2</link>
            <guid isPermaLink="false">https://medium.com/p/417d857e1791</guid>
            <category><![CDATA[supply-chain]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Stephen Fiser]]></dc:creator>
            <pubDate>Fri, 10 Aug 2018 02:19:18 GMT</pubDate>
            <atom:updated>2018-08-10T02:19:18.176Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*el-XGTNcGvMTcyPXPwBkmg.jpeg" /></figure><p>Supply Chain Finance is a financial service that allows buyers and suppliers across markets to better manage their own cash flow.</p><p>This video will catch you up to speed:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FINphwcI4X7o%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DINphwcI4X7o&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FINphwcI4X7o%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/83aedfafc7326060f5bd9ee6e6e07c1c/href">https://medium.com/media/83aedfafc7326060f5bd9ee6e6e07c1c/href</a></iframe><p><strong>In a Nutshell</strong></p><ol><li>A buyer places an order with a supplier.</li><li>The supplier submits an invoice to the buyer for X amount, due within a certain period of time.</li><li>The buyer approves the invoice and uploads the details to a supply chain finance platform.</li><li>The supplier is allowed to request early payment (at a discounted rate).</li><li>If the buyer finances out the invoice, they must pay it to the funder when it comes due.</li></ol><p>This is a great system that helps both parties a great deal. However, blockchain could be leveraged to greatly improve efficiency and open up some new opportunities. Here’s one possibility.</p><p><strong>SCF on the Ethereum Blockchain</strong></p><ol><li>A buyer places an order with a supplier.</li><li>The supplier generates an Invoice smart contract for the buyer for X amount, due within a certain period of time.</li><li>The buyer clicks a button to agree to the terms, and X <em>temporary</em> ERC20 compliant tokens are created and given to the supplier immediately.</li><li>The supplier can then do whatever they please with these tokens (more on this in a minute).</li><li>When the invoice is due, the buyer sends the correct amount of a <em>stable token</em> to the invoice contract. This executes a function that replaces all of the temporary tokens with the stable tokens.</li></ol><p>That’s a bit technical, so let’s outline the mechanics and the benefits in clear terms.</p><p>When the buyer agrees to the invoice, temporary tokens are immediately given to the supplier. These tokens will be replaced with real-valued, price-stabilized tokens once the buyer pays off the invoice.</p><p>Whoever is holding the tokens will receive the real-valued tokens immediately when the transaction completes, regardless of who or how many people are holding them.</p><p><strong>Let’s look at an example.</strong></p><p>Suppose our supplier is a woman named Julie.</p><p>She receives an order from Massive Corp to send them a supply of cosmetics. Julie submits an invoice due on May 12th, 2018 for $10,000.</p><p>Massive Corp agrees, and then Julie immediately receives 10,000 temporary tokens in her Ethereum wallet. Let’s call these XYZ tokens for simplicity.</p><p>Since these XYZ tokens are ERC20 compliant, Julie can now do whatever she wishes with them:</p><ul><li>Sell them for 90% of the mature value on a decentralized exchange (or any other %)</li><li>Pass them downstream as payment to her shipping companies</li><li>Pass them along as employee bonuses</li><li>Give them to her annoying nieces and nephews</li></ul><p>Julie does a bit of the above, and she sells and/or trades 8,000 XYZ for $7,200 on day 1 that she can immediately put back into her business. She also still has 2,000 XYZ that she decides to hold.</p><p>On May 12th, Massive Corp pays their bill with 10,000 USDT. Julie’s 2,000 XYZ dissapear, and she receives 2,000 USDT.</p><p>Also, all of the other token holder’s XYZ vanish, and they are replaced with USDT. All of this happens for just a few dollars (or less) in transaction fees across borders worldwide.</p><p><em>Note: </em><a href="https://coinmarketcap.com/currencies/tether/"><em>USDT</em></a><em> is a “stable token” tied to the value of $USD. It’s has some shakeups in recent months, and its future is not certain.</em></p><p><strong>Beyond the Basics</strong></p><p>If we look into the not-so-distant future, we can see some other benefits of this system emerge.</p><p>It’s not hard to imagine a bundling mechanism for these tokens so that tokens in different risk categories can be grouped together and purchased in bulk — similar to an ETF.</p><p>KYC and AML issues aside for the moment, this could open up doors for smaller operations to receive financing — that they currently struggle to receive — at higher interest rates for riskier shipments based on diversification.</p><p>Also, if we look at the nature and direction of decentralized exchanges that are emerging, it’s not hard to imagine that these types of investments migrate outside the walls of the current world of SCF into the average investors portfolio.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=417d857e1791" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bluebear-tech/supply-chain-finance-reimagined-on-the-blockchain-417d857e1791">Supply Chain Finance Reimagined on the Blockchain</a> was originally published in <a href="https://medium.com/bluebear-tech">Blue Bear Digital Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Iterative, Documentation-Driven Development]]></title>
            <link>https://medium.com/bluebear-tech/iterative-documentation-driven-design-4dc5ef08fc27?source=rss-40e57b6ee3be------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dc5ef08fc27</guid>
            <category><![CDATA[project-managment]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Stephen Fiser]]></dc:creator>
            <pubDate>Thu, 09 Aug 2018 03:45:20 GMT</pubDate>
            <atom:updated>2018-08-09T15:56:11.318Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uRGVyK4N4O6vtixHFV411g.jpeg" /></figure><p><a href="https://www.bluebear.tech/">Blue Bear</a> has always used some version of the following workflow to develop software features:</p><ol><li>Write User Stories</li><li>Create UI/UX Design</li><li>Define Backend Architecture</li><li>Build It</li><li>QA</li><li>Ship It</li></ol><p>The core idea is that you should design interfaces and workflows first because it helps you identify what you are actually building, decide if it really solves the problems you want to solve, and clarify any confusion amongst the team.</p><p><strong>We’ve recently been working on some projects that have caused us to rethink this workflow a bit.</strong></p><p>In <a href="https://paradigm.market/">one of our projects</a>, one of the primary users is a software developer. Given that, we chose to think of the public API of the code as the user interface.</p><p>So far, this isn’t anything unusual. Most people in the industry would nod their heads and say this is what they always do.</p><p>While trying to figure out how this fits into our workflow, we decided to write the documentation first. This was our way of creating the UI/UX design before defining the architecture. Essentially, we asked the question, “What code would we love to write if we were the end user?”</p><p>This has been amazingly effective at organizing our team communication and collaboration. We each understand the big picture much better than we otherwise would have.</p><p>After we came up with this methodology, we discovered that it’s actually <a href="https://collectiveidea.com/blog/archives/2014/04/21/on-documentation-driven-development">already a thing</a>.</p><p>One important point to note that Tom Preston-Werner points out in “<a href="http://tom.preston-werner.com/2010/08/23/readme-driven-development.html">Readme Driven Development</a>” is that it’s critical to keep things simple. The switch to Agile was a rebellion against Big Up Front Design, and that has led to No Up Front Design in many cases.</p><p>We’re not suggesting a reversion to the former, but rather an iterative, design-development workflow where you move forward in the simplest steps possible by writing documentation for what you are about to do first.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dc5ef08fc27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bluebear-tech/iterative-documentation-driven-design-4dc5ef08fc27">Iterative, Documentation-Driven Development</a> was originally published in <a href="https://medium.com/bluebear-tech">Blue Bear Digital Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decentralization vs. UX]]></title>
            <link>https://medium.com/bluebear-tech/decentralization-vs-ux-760b46d0183d?source=rss-40e57b6ee3be------2</link>
            <guid isPermaLink="false">https://medium.com/p/760b46d0183d</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Stephen Fiser]]></dc:creator>
            <pubDate>Tue, 07 Aug 2018 21:27:22 GMT</pubDate>
            <atom:updated>2018-08-07T22:02:21.949Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UE_QbYaC-uzS3oLgC46hNg.jpeg" /></figure><p>Great UX is well-known to be one of the key attributes that any startup needs to have in order to be successful. For example, an incredible user on-boarding experience can be the catalyst that turns a moderately interested visitor into a passionate member of a platform.</p><p>Blockchain projects have a tremendous hurdle to overcome with regard to UX.</p><p>At present, most decentralized projects require a person to <strong>a)</strong> get a Chrome extension like MetaMask and <strong>b)</strong> obtain some kind of cryptocurrency like Ether. This leads to additional processes like <strong>c)</strong> registering for some kind of exchange like Coinbase where you can trade fiat for crypto, <strong>d)</strong> entering bank account information, <strong>e)</strong> possibly uploading Government IDs and <strong>f)</strong> waiting for approval — and on and on and on.</p><p>It’s just too much.</p><p>In the US, Coinbase is the most common way for people to get into the cryptocurrency market, and it’s for good reason. They make it easier than anyone else.</p><p>What is the key to doing what they do? They store their user’s public and private keys for the various tokens they buy. This minimizes the complication that a new user experiences, but it leaves the “ownership” of the assets in the hands of the platform. It also makes things centralized.</p><p>To suggest that a blockchain project do this is heresy to some.</p><p>I also lean toward decentralization, but I think we have to recognize the UX challenges that pure decentralization presents to us. To that point, I’ve now worked out architectures on a few projects that involve <strong>graduated decentralization</strong>.</p><p>For many projects, it’s worth considering an architecture where you hide blockchain aspects from your users initially and introduce them over time as they become more familiar with the platform. This means that you have some ability to manage private keys / accounts for your users, but you give them instruction and opportunity to transfer out any currency to their own wallet when they are ready.</p><p>A smart platform design would also allow for a seamless switch from a platform controlled wallet to a user controlled wallet. For example, I can transfer funds away from Coinbase to my own wallet, but (the last time I checked) there is no way for me to connect my own Ethereum wallet and swap my ETH for BTC.</p><p>Platforms built in this manner could lead to <em>eventual decentralization -</em> where over time, users become more comfortable with managing their own tokens &amp; assets.</p><p>I’m certainly not suggesting that every project follow this pathway, but I think it’s a very interesting solution in many cases.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=760b46d0183d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bluebear-tech/decentralization-vs-ux-760b46d0183d">Decentralization vs. UX</a> was originally published in <a href="https://medium.com/bluebear-tech">Blue Bear Digital Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>