<?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 Roger Willis on Medium]]></title>
        <description><![CDATA[Stories by Roger Willis on Medium]]></description>
        <link>https://medium.com/@rog_dam?source=rss-89948936a239------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ycf5IhdR4AgaDhgXA5hMWQ.png</url>
            <title>Stories by Roger Willis on Medium</title>
            <link>https://medium.com/@rog_dam?source=rss-89948936a239------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 06:27:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rog_dam/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 is DeFi lending?]]></title>
            <link>https://medium.com/dam-d2o/what-is-defi-lending-4aeb47c51722?source=rss-89948936a239------2</link>
            <guid isPermaLink="false">https://medium.com/p/4aeb47c51722</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Roger Willis]]></dc:creator>
            <pubDate>Sun, 24 Jul 2022 18:37:11 GMT</pubDate>
            <atom:updated>2022-12-05T11:16:23.846Z</atom:updated>
            <content:encoded><![CDATA[<p>This post explains how deFi lending works by making a comparison to banking and introducing the concept of credit as money.</p><p>Hey guys, I’m Roger, a contributor for DAM. I’m on the engineering side of things but have an interest in monetary economics and banking, so I thought I’d take some time out of writing smart contracts to explain a bit more about what we are up to.</p><p>In the <a href="https://medium.com/dam-dprime/introducing-dprime-asset-modules-on-moonbeam-6c73cfb2f302">DAM introduction post</a> we wrote:</p><blockquote>In the Protocol, investors are bankers, portfolios are collateral, d2O is the means of creating purchasing power, and DAM is a risk management wrapper.</blockquote><p>What does this mean? Let’s start with “investors are bankers” and everything else flows from there.</p><h4>Investors are bankers</h4><p>So what actually is banking and what does it have to do with deFi?</p><p>A bank is a company which makes a market in credit. <strong>Banks are in the business of swapping their credit in return for your credit.</strong> In other words, banks give out loans of their credit and it just so happens that their credit is accepted as money in the general economy. When a bank issues a loan, it creates credit (or money) and their balance sheet gets larger (or “grosses up”). Therefore, the amount of credit (or money) circulating in the economy increases.</p><p>This is a good thing. Credit based monies allow for a flexible money supply and can, in theory, effectively respond to structural changes in the underlying economy, assuming governance is managed appropriately. E.g. politically neutral central bank governance, appropriately set interest rates and not issuing insane amounts of new credit 🤨</p><p>Let’s take an example.</p><p>When you buy a house and need a mortgage, what you are actually doing is swapping your credit (collateralised by the house which you are going to buy), which most people won’t accept, not least the seller of the house, for the bank’s credit — which almost everyone <em>will</em> accept.</p><p>DAM works in a similar way. Whilst you can create your own credit money collateralised against your crypto, it is unlikely anyone will accept it. At the very least, having to deal with a different coin per borrower is just annoying! Instead, DAM provides a set of rules and procedures which give a stable value to the credit you create. Anyone who uses DAM must follow the rules set out in the smart contracts. The benefit of this to users is the privilege of issuing d2O, a trusted credit based money (or stablecoin), as opposed to their own credit.</p><p>Back to mortgages. The interest rate you pay for the loan takes into account the bank’s view on you as a credit risk, the price of short term credit set by the central bank, time value of money and some other factors. In other words, the interest rate is the cost of money, it’s what you have to pay to get the bank to issue new credit for you, so you can buy the house. This credit is what we call money in day-to-day life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*cGv5TVzUDZI4856L-nzTmA.png" /><figcaption>A borrower gets a loan from a bank collateralised by the property. Note that the loan is the bank’s asset and the borrower’s liability. The deposit is the bank’s liability and the borrower’s asset. In other words, getting a loan from a bank is just a swap of your credit (the loan) for the bank’s credit (the deposit).</figcaption></figure><h4>Why is bank credit, money, and my credit, not money?</h4><p>It is due to trust. Trust is important for all types of money — even cryptocurrencies — and especially credit based money like USD, GBP, EUR, <strong>d2O</strong> and DAI.</p><p>Trust in the banking system is derived from a set of laws and prudential rules which govern what types of collateral banks can accept and what procedures they must have in place to ensure proper risk management and underwriting. It is these rules which provide confidence for everyone that the bank’s credit is worth what they claim it to be i.e. one dollar or one pound. This is why people will almost always accept bank credit as money, because they know it can always be redeemed — in this case that means transferred to another bank or converted to central bank credit, i.e. bank notes.</p><p>Regarding you, or us… It is simply not feasible for <em>everyone</em> to perform credit risk due diligence on <em>everyone else</em> to determine if their issued credit has value, or even what the specific value of it should be. Instead, we rely on banks to do this for us. That’s why banks are market makers in credit — they are credit risk managers and so, in theory, have the knowledge to navigate the credit markets effectively (but sometimes don’t).</p><p>Interestingly, <a href="https://rumplepay.com/">the original Ripple created by a guy called Ryan Fugger</a>, wanted to create a decentralised peer to peer credit based payment system, where participants could create credit lines with peers. The cool thing about the original Ripple was that it only required users to perform due diligence on their direct peers. Transitive credit flows were handled by the system whereby payments to someone who is not a direct peer of you could be routed through a mutual peer. I really like the idea of this but the network effects needed to get it working effectively are considerable. There was also no collateral in this system, making it only effective for smaller payments.</p><p>DAM has the same intention as the original Ripple — to create a decentralised credit based money. The main difference being that that the original Ripple was essentially a system with few common rules across borrowers. As such, there were many different credit monies created: $10 owed to you by Alice is not the same as $10 owed to you by Bob, even if they are in your close circle, and you had to manage this. In contrast, with DAM, all borrowers are subject to the same comprehensive set of risk management rules which ensure that the credit for all borrowers — the d2O they issue — can be treated as a fungible instrument. With this approach, all holders of d2O need to know is that 1 d2O is worth $1 and the protocol works to ensure this will be the case.</p><h4>What happens if trust is broken?</h4><p>Let’s imagine a hypothetical bank had poor underwriting procedures and accepted as collateral a bunch of uninsurable properties on a flood plain for high LTV/risky loans.</p><p>The properties subsequently flood and this is a problem for the bank.</p><p>They will have to impair the loans against the flooded properties because at this point it becomes unlikely the loan will be repaid. Why does it matter if the loan doesn’t get repaid? Because if it doesn’t, then the bank’s assets decrease (their balance sheet “grosses down”) and their liabilities stay constant. To balance the accounting invariant of <em>assets = liabilities + equity</em>, they must take a hit to their equity. This means shareholders lose money. If enough loans go bad and they eat through all their equity, then the bank may end up in negative equity and become insolvent.</p><p>But before that would even happen, people would soon find out on Twitter that the bank underwrote risky loans for flooded properties and transfer their deposits to other banks. This is because trust in the system is beginning to falter. People don’t trust that this bank will make good on <em>their</em> credit obligations — or deposits — to their customers. People don’t want to accept this bank’s credit as money. This has the effect of reducing their assets (and liabilities, as deposits are liabilities) as transferring a deposit to another bank requires transferring an equivalent amount of central bank credit — via the inter-bank real-time gross settlement system or deferred net settlement system — which is an asset for the struggling bank, to the recipient bank.</p><p>In crypto parlance, this is equivalent to a stablecoin “losing the peg”.</p><p>If this happens, it is likely that this bank’s deposits or issued credit would trade at a discount to other bank’s deposits but in practise, people would just withdraw deposits until the bank would require explicit emergency support from the central bank or government E.g. what happened to Northern Rock, a UK based bank, in 2008.</p><p>Interestingly, some banks in the UK issue physical bank notes which is unusual these days. The Royal Bank of Scotland <a href="https://www.acbi.org.uk/banknotes/royal-bank-of-scotland.html">issues notes</a> which could potentially trade at a discount to Bank of England issued notes if RBS were to have (another) solvency issue!</p><p>Of course, a DeFi protocol like DAM is completely transparent. Stakeholders can see in real-time the breakdown of collateral backing d2O and have confidence of the protocol’s solvency.</p><h4>Why is credit issued by different banks fungible?</h4><p>In other words, why is an HSBC deposit worth the same as a Barclays deposit?Many different banks with different balance sheets and risk profiles can issue credit and despite the banks being different, their credit or money usually trades at the same price — it is fungible. Shops don’t care which bank is the issuing bank for a debit or credit card. It’s all the same stuff to them.</p><p>It is the trust and confidence in the system, derived by the rules mentioned above which allow all this credit to have the same value and be perceived as a good/useful type of money <em>even if</em> one bank has a slightly riskier balance sheet than another. It doesn’t matter in the long run because it is assumed that the rules will force riskier banks to eventually de-lever and reduce their risk.</p><p>Having a central bank as a lender of last resort also clearly helps to maintain bank credit fungibility.</p><p>Lack of trust in the system as a whole is disastrous for credit based monies which is why central banks and governments will do <em>anything</em> to save the banking system and why lending protocols such as DAM and MakerDAO will do the same to ensure the stability of their respective eco-systems.</p><h4>I can issue my own credit money, just not very much of it</h4><p>As an aside, it turns out that <em>anyone</em> can create credit money but probably not very large amounts of it. I could create some £100 IOUs secured against the fact that I’m a good chap and promise to redeem them for £100 on demand. I just probably won’t be able to get many people to accept them because there is an absence of trust or it is difficult for the recipients to perform due diligence to establish trust. In which case it’s easier for potential recipients just to not accept the IOUs.</p><p>I could even secure the IOUs against some physical asset I own. That might make potential recipients of the IOUs more willing to accept them but still, they would be relying on me to custody the collateral and unless there’s no explicit legal agreement or lien written into the terms of the IOU, people still wouldn’t accept them, I imagine.</p><p>But what if there was a transparent way to force me to behave well in such a way that people would readily accept my IOUs? Hold that thought. This concept is particularly useful for when understanding how DAM works…</p><h4>Enter: Decentralised banking</h4><p>A decentralised approach to banking looks much like a regular bank except that all of the functions are outsourced to other parties. In many cases this makes DeFi protocols more accessible than traditional banks.</p><p>It might sound strange but with a decentralised approach to lending, the lender and the borrower are the same entity! In other words:</p><blockquote>Investors are bankers</blockquote><p>Just like the example above where I create my own IOUs, the protocol (DAM) allows the borrower to create new d2O (or credit) secured against their cryptocurrency collateral.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*cllRRKuVeYwafZjz_V6P5w.png" /><figcaption>In this image, we can see that the bank and borrower has been compressed into a single entity, the borrower. There is still a loan and still a balance of money (d2O) but there’s no need for a bank deposit now and instead of the loan being originated by the bank, it is originated by the borrower themselves!</figcaption></figure><p><strong>There is no need for a bank.</strong> The deposit function of the bank is not necessary in DeFi because people use wallets instead (either controlled by themselves or someone else — which is basically just a custody function).</p><p>How is this possible? DAM is a protocol and community which enforces a set of rules and it is these rules which provides the trust necessary for the newly issued d2O (or credit) to have value. The protocol defines the underwriting criteria for how much new d2O can be created and other risk management controls such as maximum d2O issuance across the whole protocol, what type of collateral can be accepted and the specific LTV for each type of collateral, etc.</p><p>It is the presence of these rules which are applied across each user (and their respective vaults) which allow the issued d2O by each vault to be worth the same for each user despite different amounts and types of collateral being present in their vaults. In this regard, a vault is analogous to a bank and just like how different banks each issue credit which is fungible, with DAM, different vaults each issue d2O which is fungible.</p><h4>We need price discovery for d2O</h4><p>It’s all very well issuing credit money but we need a means to value it and the only way to do this is to facilitate a market in it with some other instrument. With d2O we intend 1 d2O to be worth $1. Therefore, we need to facilitate a market in d2O with another instrument which is worth $1. It just so happens there’s a few dollar proxies: USDT, USDC, DAI, etc.</p><p>In our case, the market making function is likely to be a stableswap pool. The stableswap pool is analogous to an interbank payment system which allows holders of d2O to swap it for other credit based monies issued by other entities or users of decentralised protocols. You could also swap d2O for an algorithmic stablecoin but I wouldn’t recommend it!</p><p>Just like in the banking example above, if holders in d2O lose confidence because the underwriting rules set by the protocol are poorly conceived, then they are likely to sell their d2O for other stablecoins or cryptocurrencies and thus the value of d2O relative to the dollar (or proxy for it) will fall. On the other hand, because d2O will be over-collateralised and have prudent underwriting in place, it is likely that it will trade around $1 under normal circumstances. There’s a buffer of collateral and other preventative measures before d2O becomes under-collateralised.</p><h4>If there is no need for a bank can I just create credit without DAM?</h4><p>If the lender is the borrower, then, in theory, people can just create credit collateralised against their cryptocurrency portfolio without DAM.</p><p>You could try that but you would have to create an equivalent secure protocol yourself and convince people that the protocol can be trusted to safely lock the collateral and that you would put in place sensible governance around risk management. That’s quite a lot of effort and requires knowledge and restraint to be effective and trusted in the long-term.</p><p>It makes more sense to have a protocol which multiple people can use. It also makes sense to have multiple protocols which compete on capital efficiency, cost and utility.</p><h4>What if something goes wrong?</h4><p>Taking a specific vault into account, in the event that the collateral which d2O is redeemable for falls by what we — as the risk managers for the protocol — deem to be too much, then a portion of the collateral must be liquidated (sold) to pay back the outstanding loan of d2O. This de-levers or “grosses down” the vault and collective balance sheet of the protocol. By collective balance sheet, I mean the consolidated balance sheet comprising all the vaults.</p><p>If we do not forcibly de-lever the consolidated balance sheet of the protocol then holders of d2O may eventually lose out due to inflation, which is what happens if the value of collateral does not fully cover the value of issued d2O.</p><p>We certainly cannot have under-collateralised d2O floating around the markets because it undermines the confidence and trust in the currency as a whole. Indeed, this is why “unhealthy” vaults will be liquidated in advance of them actually being under-collateralised.</p><p>Liquidations are performed by third parties who can purchase the collateral associated to a vault in distress at a discount, so they can sell it back to the market for a small profit. They do this by sourcing d2O on the secondary markets and using it to purchase the collateral.</p><p>The protocol has a number of mechanisms to ensure that d2O borrowers always remain solvent and and that the d2O/dollar peg holds and we will articulate these closer to launch.</p><h4>All this banking stuff is cool but what about stablecoins?</h4><p>In the intro post we said:</p><blockquote>d2O is the means of creating purchasing power</blockquote><p>This means that, with DAM, it is possible for users to create credit or purchasing power against their own crypto portfolios.</p><p>In this regard, the issued d2O <em>is </em>the stablecoin. That’s basically it. So now you know what d2O is — d2O is a credit based money, collateralised by cryptocurrencies. And as we have seen above in the beginning of this article, stablecoins are conceptually no different to bank credit money or central bank credit money (otherwise known as fiat currency). Bank deposits are collateralised by loans to customers. Central bank deposits are collateralised by loans to the government, swap lines with other central banks, gold and various other financial instruments. DeFi stablecoins are collateralised by cryptocurrency, only because that’s the easiest thing for us to use as collateral. Hence, from the intro post quote above:</p><blockquote>portfolios are collateral</blockquote><p>However, there is no reason why d2O cannot be collateralised by real-world assets such as shares of real-world property, tokenised equities or fixed income instruments. In this regard, the fact that d2O is crypto-collateralised is orthogonal to the fact that it is a stablecoin.</p><p>Lastly, as mentioned above, the protocol allows people to be their own bank. Everything that the protocol allows has a parallel in traditional banking and the only reason why it works is because of the governance in place which sets the necessary credit risk management policy. In this regard:</p><blockquote>DAM is a risk management wrapper</blockquote><p>DAM, the protocol, doesn’t lend to users of the protocol. Instead, DAM and its community comprise the set of rules for making the protocol work. The smart contracts, the appropriately set risk management parameters and the means to have a set of experts on hand in case they are needed.</p><p><em>Roger Willis, DAM contributor.</em></p><h4>References</h4><p>It would be rude not to include — what I believe — are the two best sources to learn about monetary economics and banking. I was only able to write this blog post because I’ve learnt from the best:</p><ul><li>Perry Mehrling, The Economics of Money and Banking, 2016</li><li>Alfred Mitchell-Inness, What is money?, The Banking Law Journal, May 1913, pages 377- 408</li></ul><p><em>Medium Post was updated on December 5th to include the new stablecoin name d2O</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4aeb47c51722" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dam-d2o/what-is-defi-lending-4aeb47c51722">What is DeFi lending?</a> was originally published in <a href="https://medium.com/dam-d2o">DAM_d2O</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Corda: Lego for Distributed Ledgers]]></title>
            <link>https://medium.com/corda/corda-lego-for-distributed-ledgers-34211869f4fa?source=rss-89948936a239------2</link>
            <guid isPermaLink="false">https://medium.com/p/34211869f4fa</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Roger Willis]]></dc:creator>
            <pubDate>Mon, 14 Jan 2019 12:07:09 GMT</pubDate>
            <atom:updated>2019-01-15T13:19:40.098Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QbCv5EEok2fuoszyApg2nA.png" /></figure><p>Last December I had the pleasure of speaking at the <a href="https://events.sap.com/de/2018-enterprise-blockchain-summit-berlin/en/home">SAP Outside The Block</a> conference in Berlin. It was a lot of fun to get out from behind the code and see so many clients and partners at a great event. SAP is a top-tier partner and the conference shows just how well they are able to bring lots of initiatives from across the organisation together.</p><p>I was on a panel where the questions got to the heart of what we’re doing with Corda, so I wanted to share both the questions (in bold) and my (rough) answer notes here.</p><blockquote><strong>10 years in Blockchain and past its Hype according to Gartner. How has the technology evolved, and where do you still see potential?</strong></blockquote><p>Blockchain has evolved massively in 10 years. We’ve come from Bitcoin — a permissionless public-only network created to solve a very specific problem — to DLTs like Corda, which were born out of requirements for regulated finance. In my day to day, I now see the aspirations of developers — to create decentralised networks — converging with business requirements. This is a good thing! For example: the work we are doing at R3 to make Corda highly available as well as satisfying our customers’ network compliance requirements.</p><p>Now, blockchain platform vendors are easing into product marketing fit. The best fit so far: Tokens, otherwise known as digital assets, securities, cash, etc. The power of platforms like Corda will be self evident as an increasing number of companies choose to issue ledger native assets or tokenize existing assets.</p><blockquote><strong>What is the use one case/application that convinces you the most about Blockchain//DLT applicability in the enterprise?</strong></blockquote><p>Tokens. Full stop. We’re not talking about ICOs, but rather about companies issuing securities onto a blockchain platform. We are working with a range of companies and FMIs to do just this!</p><p>We want to make it as easy as possible for companies to issue tokens on Corda. At the moment we are developing the infrastructure required for digital assets on Corda. Standards, SDKs, mobile wallets, account management, you name it, it’s on the road map. You’ll be hearing a lot from our team in the coming months!</p><blockquote><strong>Data Sharing is amongst the paradigms that you hear often when talking to Blockchain — or DLT — enthusiasts. What is your take on the concept, how can we manage the wish for limited visibility?</strong></blockquote><p>The need for privacy is obvious, but it seems to have eluded some Blockchain vendors who started with gossip networks and have had to bolt-on hacks to provide privacy. They didn’t understand their customer requirements.</p><p>Instead, start with point to point messaging. Don’t send data to those that don’t need to see it. Send the de-minimis amount of data required for transaction verification. Broadcast and gossiping of data can be added using point to point messaging primitives for the limited set of scenarios that require it. Use pseudo-anonymous identities on ledger but which can be linked back to real-world identities off-ledger.</p><p>In addition, at R3, we are exploring the use of Intel SGX to create a fully encrypted ledger. We have a working prototype. We are also exploring the use of specific applications of ZKPs for things like range proofs. We believe that use of generic ZKPs e.g. constraint compilers is premature. Also the impact of quantum computing on ZKPs needs to be further assessed. Good luck to those who are relying on this as it’s just a matter of time before it breaks!</p><blockquote><strong>Corda takes a slightly different approach than most of the other Enterprise Blockchain Technologies. How did you start thinking about building what is Corda today, and what is the most important difference that you would like to highlight?</strong></blockquote><p>Firstly, this is important, when thinking about Corda, one needs to view it as <strong><em>“Lego for distributed ledgers”.</em></strong> Instead of “the private Blockchain for banks blah blah, notary, blah blah not blockchain blah blah”.</p><p>There is <strong>NOTHING</strong> you can’t do with Corda, that you can do with other blockchains. I don’t think the reverse holds though. For example, some people spend a lot of time tweeting that public permissionless networks are superior than the alternatives. That, of course, is debatable. But in reality… Corda <em>can</em> be no less public and permissionless than Bitcoin.</p><p>The properties of a Corda ledger depend entirely on <strong>how</strong> you choose to deploy it. This way, Corda has the best of all worlds.</p><p>It can be a product that serves the needs of R3’s customers. Indeed, we have initially chosen to deploy Corda as a permissioned network because this is what our customers want. They want deterministic finality, performance, real world identities and privacy.</p><p>Having said that, the Corda platform is flexible enough such that you can build both Bitcoin and Ethereum as a CorDapp, you could probably build IBM Fabric as an CorDapp as well, although you probably wouldn’t want to!</p><p>So, why and how is Corda <em>“Lego for distributed systems”</em>? It’s because our founders threw out all blockchain “cargo culting” and started from the beginning. They figured out that the fundamental problem we needed to solve was that Alice cannot see what Bob sees and Bob can’t see what Alice sees. Performing duplicative work in mutually exclusive silos is, costly, etc. and most DLT-like problems can be reduced to this.</p><p>The answer is to build a platform that allows Alice and Bob to see the same things and know the same facts even if they don’t trust each other. It’s as simple as that. Add on the need for transaction validity, consensus, and the ability to scale etc. and you get something which looks like a general purpose Bitcoin blockchain with a shared ledger, and the choice of any consensus mechanism. The platform is built around this core premise and is basically an SDK for building distributed ledgers.</p><p>In summary, Corda allows developers to choose the trade-offs which are most desirable for their use case. Choose the Lego bricks you need and start building. It’s also quite fun as well!</p><blockquote><strong>Now we have an extremely diverse set of panel participants — Blockchain, DLT, and Applications covered — if you had one wish, one thing to improve or focus on from one of your peers up here, what would it be?</strong></blockquote><p>Remain focused on the end user. Build stuff that people want and that makes people’s lives better!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34211869f4fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/corda/corda-lego-for-distributed-ledgers-34211869f4fa">Corda: Lego for Distributed Ledgers</a> was originally published in <a href="https://medium.com/corda">Corda</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In response to “the block chain […] could help you buy your house”]]></title>
            <link>https://medium.com/linkreply-blockchain/in-response-to-the-block-chain-could-help-you-buy-your-house-4c4484cc681a?source=rss-89948936a239------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c4484cc681a</guid>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[property]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Roger Willis]]></dc:creator>
            <pubDate>Wed, 22 Jul 2015 18:00:08 GMT</pubDate>
            <atom:updated>2015-07-23T15:02:06.524Z</atom:updated>
            <content:encoded><![CDATA[<p>Yesterday, there was quite a good piece in <a href="http://www.cityam.com/220590/blockchain-won-t-just-change-banking-it-could-help-you-buy-your-house">the CityAM</a> by Jerry Norton from CGI. He discussed uses of the block chain in banking. He probably means shared replicated ledgers (“SRLs”) but that term has not permeated into the main stream media yet.</p><p>He states:</p><blockquote>Adoption has multiple advantages: from eliminating error and reducing manual processes, to lowering operational costs and improving accuracy and transparency. Ultimately, this could lead to a large number of ‘back-office’ roles common in today’s banks becoming extinct in the medium term.</blockquote><p>All true. And:</p><blockquote>The exciting part is that the ‘ledger’ doesn’t have to be a traditional ‘balance’: It could be any asset that can be represented in digital form.</blockquote><p>Also true.</p><p>He then makes the leap to say that ‘smart contracts’ — known hereafter as dumb contracts, as they are not smart — can be used to automate the delivery vs payment (“DvP”) workflow when buying a house:</p><blockquote>With the blockchain concept of a smart contract, the exchange of the deeds and the funds transfer could be proven, linked together automatically, whilst happening in near real time and theoretically on a 24/7 basis.. The same principles are true for many asset types and purchases, such as buying a second-hand car — a process fraught with risk today.</blockquote><p>I’m actually in the process of buying a house and I believe my experience is of some relevance here.</p><h4>The anxiety</h4><p>Contracts were exchanged months ago. The vendor currently has the place let out to a family, so in order for the transaction to complete, we require vacant possession, i.e. the tenants must be gone.</p><p>The tenants agreed to leave on 8th July and as per the contract, we were due to complete 10 days after this — 18th July.</p><p>Sadly, the tenants reneged on their promise to leave the house and as of 22nd July, we have no concrete date to complete the purchase.</p><p>UK law significantly favours the tenant in this case. The only way to remove them from the property would be to obtain an eviction notice through the courts.</p><p>This takes 2–3 weeks to obtain and as the tenants have young children, the courts are unlikely to force them to leave immediately.</p><p>To further complicate matters, we have a “long stop” date on the contract. This is legal jargon for:</p><blockquote><strong>The last date by which something must be done. </strong>I.e. the transaction must complete by this date, otherwise the contract is terminated.</blockquote><p>The long stop date is in 10th August.</p><p>We vacate our flat on 31st July.</p><p>Unless the tenants leave on their own terms, 10 days before the long stop date, the property will go back on the market and we will be homeless.</p><blockquote>In essence, both parties to the transaction are at the mercy of the tenants</blockquote><p>The tenants are unpredictable — this is pretty much a hallmark of most human beings.</p><p>Other property examples:</p><ul><li>Absentee or uncooperative freeholders, refusing to sign lease agreements.</li><li>Extensions with no building regs or planning permission.</li><li>Boundary disputes.</li><li>Vendors leaving tonnes of stuff in the property.</li><li>Money laundering revelations which come to light the day before completion.</li><li>One of two buyers dies in a car crash a week before completion. There’s now not enough money to complete, yet the deposit has been paid.</li><li>Fraud involving fake conveyancing solicitors absconding with cash.</li><li>Etc.</li></ul><p>Put simply, smart contracts cannot capture the human elements of business. They are not designed with human behaviour in mind.</p><p>Instead, they are designed for simple, deterministic workflows and they are no more effect than standard business logic you’ll find in a standard ERP system.</p><h4>The smart contracts solution</h4><p>In our case, the answer might be to employ the use of an infrared satellite oracle.</p><p>The oracle could ascertain the location of the tenants primary residence and update the — now smart — contract in real-time.</p><p>If their primary residence <strong>is</strong> still the property in question, then the contract will know that vacant possession is not possible, thus will not complete on the date stated.</p><p>Or…</p><p>The dumb contract could just be over-ridden by the purchaser’s and vendor’s solicitors, in which case, is there any need for smart contracts in the first place?</p><blockquote>Humans are smart, contracts are dumb</blockquote><p>It seems to me that ‘smart contracts’ only work in scenarios where there’s a distinct absence of any unpredictability. As soon as the business logic cannot deal with the situation, humans will have to take over anyway.</p><h4>Are we jumping the gun?</h4><p>Of course, it’s great to have a vision of what might be possible in the future but it’s also important to concentrate on what’s possible now.</p><p>For smart contracts to work we need an appropriate platform for them — the SRL.</p><p>There has only been one reasonably successful implementation of a SRL to date. That’s Bitcoin and Bitcoin has it’s own problems.</p><p>All the other remotely credible SRL implementations are still a work in progress.</p><p>Lets crack the SRL first and then build the ‘business logic’ platforms afterwards.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c4484cc681a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linkreply-blockchain/in-response-to-the-block-chain-could-help-you-buy-your-house-4c4484cc681a">In response to “the block chain […] could help you buy your house”</a> was originally published in <a href="https://medium.com/linkreply-blockchain">LinkReply: Blockchain</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A follow on from “block chains and the future of audit”]]></title>
            <link>https://medium.com/@rog_dam/a-follow-on-from-block-chains-and-the-future-of-audit-b31fe711516a?source=rss-89948936a239------2</link>
            <guid isPermaLink="false">https://medium.com/p/b31fe711516a</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[auditor]]></category>
            <category><![CDATA[future]]></category>
            <dc:creator><![CDATA[Roger Willis]]></dc:creator>
            <pubDate>Tue, 14 Jul 2015 16:36:06 GMT</pubDate>
            <atom:updated>2015-07-16T10:47:03.726Z</atom:updated>
            <content:encoded><![CDATA[<p>This post is in response to a <a href="http://www.coindesk.com/blockchains-and-the-future-of-audit/">great article</a> by Matthew Spoke on Coindesk, which discusses financial audit and how the block chain may help to improve it.</p><p>Have a read and get up to speed. All done? Good.</p><p>One thing that article didn’t discuss was any specific architecture or implementation details. That’s what I’ll explore here, with the aim of answering the question, “is the future of financial audit all about block chains?”.</p><p>We’ll have to cover a fair bit of ground but firstly…</p><h4>Focusing on audit misses part of the problem</h4><p>Auditing is <strong>hard</strong>. It’s also terrible value for money as only ‘reasonable’ assurance is provided and this assurance is often misplaced. Everyone loses as a consequence when fraud and errors go unnoticed.</p><p>The expense and fallibility of audit are symptoms of two broad ranging problems, only one of which gets any air time</p><blockquote><em>“Financial audit and the audit firms need reforming”</em></blockquote><p>The solutions range from <a href="http://blogs.wsj.com/cfo/2014/04/03/european-parliament-approves-mandatory-auditor-rotation/">mandatory auditor rotation</a> to big data. Will they have any impact?</p><p>Perhaps. Auditors have their own problems, however I’d argue that one of the key issues actually lies with our approach to building accounting infrastructure, transaction systems and developing accounting workflows.</p><p>I’ve <a href="https://medium.com/@3ntry/distributed-accounting-ledgers-d527d31870fe">touched on this before</a>, so I won’t go in to detail here. Summary:</p><blockquote>ERP software is abysmal, no digital signatures, bad data interoperability, poor usability, poorly built spreadsheets, reliance on manual tasks, data duplication, etc…</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*LNQ_xhEIGKc-qNquSX9NDg.jpeg" /><figcaption>A common busy season occurence</figcaption></figure><p>Audit is an afterthought to all but the auditors themselves. To quote Paul Graham, it’s a <a href="http://paulgraham.com/schlep.html">“schlep task”</a> — tedious unpleasant work. As each accounting journal is posted the ‘audit debt’ silently accumulates, like <a href="https://medium.com/@3ntry/audit-and-the-mechanical-dish-washer-8b209505b176">dirty plates that gradually build up next to the kitchen sink</a>.</p><p>Audit partners are ambivalent providing they can charge over-runs for their staff to locate paper bond indentures in the basement and review a multitude of spreadsheet cluster-fucks. Don’t hate the partner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/173/1*1v19Rxt4QD0D7SN-_ztvtg.gif" /><figcaption>Mission critical spreadsheet workflow</figcaption></figure><p>Believe me when I say there are a lot of hidden costs here. It doesn’t have to be like this though — it turns out that the thinking and technology to edge us closer to audit utopia has actually existed for over a decade.</p><p>Clue; it’s not</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*5fw1gqEmPfKE7hKAouO4ZA.jpeg" /><figcaption>At the “audit innovation” meeting…</figcaption></figure><p>as some would have you believe.</p><p>Instead, we should focus on auditing as much as we can when it happens, rather than doing a “reasonable” job making sense of the mess afterwards.</p><h4>Back to the block chain</h4><p>In creating Bitcoin, Satoshi’s key innovation was the permissionless block chain, a <a href="http://gendal.me/2015/06/08/towards-a-unified-model-for-replicated-shared-ledgers/">shared replicated ledger</a> (“SRL”) with a focus on censorship resistance. It’s a pretty amazing piece of technology, but hold your horses — we aren’t going to jump on the block chain band-waggon just yet.</p><p>Censorship resistance driven by proof-of-work is key when one is operating in a highly adversarial environment, like a cash system, where the identities of your counter-parties and transaction verifiers are not necessarily known. The Bitcoin block chain was designed for this exact use-case — where exploits and government crack-downs are the most concerning threats. A currency system <em>needs</em> to be secure and Bitcoin achieves that.</p><p>And what are the disadvantages? Bitcoin is slow, proof-of-work (although currently subsidised by mining rewards) is expensive, transactions must be publicly broadcast and governance is sub-optimal.</p><p>Similar trade-offs are inherent in the design of any SRL. Take <a href="https://erisindustries.com/">Eris</a> for instance; to allow for more effective governance, oversight and control of their block chain design, they have had to sacrifice decentralisation and censorship resistance.</p><p>This is the key — each SRL must be carefully designed to match domain requirements and block chains won’t always match our requirements optimally.</p><h4>SRL as a concept, block chain as an implementation</h4><p>We should cease thinking in terms of block chains and instead view them as just one very particular implementation of a SRL. Indeed, there are many ways to implement an SRL; <a href="http://hyperledger.com/">Hyperledger</a>, <a href="https://erisindustries.com/">Eris</a>, <a href="https://ripple.com/">Ripple</a>, <a href="http://opentransactions.org/wiki/index.php/Main_Page">Open Transactions</a>, etc.</p><p>Firstly, what is a SRL? <a href="http://gendal.me/">Richard Brown</a> defines “shared” and “replicated” as</p><blockquote><strong>Shared:</strong> because multiple actors can read or write to different parts of the ledger</blockquote><blockquote><strong>Replicated:</strong> because everybody who needs a copy can have a copy, rather than relying on a powerful central entity</blockquote><p>and for completeness, I’ll bolt on</p><blockquote><strong>Ledger:</strong> An immutable append-only collection of records</blockquote><p>In my view, SRLs mostly solve accounting and transacting problems so our efforts should focus on</p><blockquote><em>“What things do we need to transact and account for, what’s the problem with the current method and what do we want to achieve?”</em></blockquote><p>As opposed to</p><blockquote><em>“What can we apply block chain technology to?”</em></blockquote><p>Companies of all shapes and sizes around the world are currently at panic stations, <a href="http://uk.businessinsider.com/santander-has-20-25-use-cases-for-bitcoins-blockchain-technology-everyday-banking-2015-6">asking the latter question</a>.</p><p>Perhaps we can use a block chain, Factom will do, to expensively, securely and pseudo-anonymously — because it’s embarrassing — record all the superfluous block chain uses we came up with, so we can look back in 100 years time to laugh about the band-waggon of investor money that was wasted.</p><h4>Workflows and infrastructure</h4><p>The main problem which SRLs can elegantly solve is this:</p><blockquote><em>“Parties to the same transaction, record all source data and subsequent accounting journals unilaterally, in separate systems”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*PxYH_M_UiNnHNeMtkqB2jQ.png" /><figcaption>Bob and Alice are at it again!</figcaption></figure><p>In other words, performance of the transaction is separate to the recording of the transaction and its associated audit trail.</p><p>Some of the consequences are; wasted time, operational risk, fraud, increased audit costs, mistakes and more hidden costs.</p><p>Accounting frameworks, reporting currencies and fraud aside, both parties <em>should</em> be posting equal and opposite journals.</p><p>Each party <em>should</em> post a journal which is based upon the raw transaction data, e.g. bond indenture, swap agreement, invoice, certificate of deposit, repo agreement, building contract etc.</p><p>Therefore, for a valid transaction to happen, both parties must agree on a transfer of value at a point in time. Makes sense?</p><p>So, if all of this is communicated when the transaction happens, why can’t we build a robust, legally defensible audit trail for that transaction, for both parties, the moment it happens?</p><p>This audit trail gives us real-time assurance at the transaction level for potentially huge amounts of transactions.</p><p>So, how do we do it? What’s the lowest common denominator we require from a SRL to be useful from an general accounting (and audit) perspective?</p><h4>Triple entry as a concept, SRL as an implementation</h4><p>To make this work, we need a few (implementation agnostic) components:</p><ul><li>A secure channel to communicate transaction data between counter-parties.</li><li>A way for counter-parties to robustly confirm agreement of a transaction.</li><li>An entity or entities to notarise new transactions and store past transactions when required.</li></ul><p>How would this work? Taking the classic Bob and Alice example above, here’s the work flow:</p><ol><li><strong>Alice</strong> issues the instrument, she signs it.</li><li><strong>Bob</strong> receives the instrument, agrees with it and he signs it.</li><li><strong>Bob</strong> passes the record to the <strong>Notary</strong>, who signs and then stores the instrument.</li><li><strong>Bob</strong>, <strong>Alice</strong> (or an authorised third party) can now query the <strong>Notary</strong> to ascertain whether the transaction happened. <strong>Bob</strong> and <strong>Alice</strong> can also keep a copy of the notarised instrument themselves.</li><li>As the <strong>Notary</strong> is a SRL, it’s practically impossible to delete or update the instrument without counter-party approval.</li><li>Even if someone does, we’ve got an instrument with their signature on it.</li></ol><p>Now, the part which is interesting for accountants and auditors. The instrument, triple signed by <strong>Alice</strong>, <strong>Bob</strong> and the <strong>Notary</strong></p><blockquote><strong><em>“is the transaction </em></strong><em>as well as </em><strong><em>the raw accounting data</em></strong><em> for that transaction”</em></blockquote><p>Therefore we can say that this workflow which <a href="http://iang.org/papers/triple_entry.html">Ian Grigg calls Triple Entry Accounting</a></p><blockquote><em>“combines the </em><strong><em>act of performing the transaction</em></strong><em> with the </em><strong><em>recording of that transaction and its associated audit trail</em></strong><em>”</em></blockquote><p>Ian’s paper has been on the web for over 10 years.</p><p>Now, instead of accounting for the instrument unilaterally in their respective accounting ledger’s. Alice and Bob can simply point to the triple signed instrument on the SRL, which contains all the metadata required to post the correct accounting journal and revisit the definitive transaction particulars.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*1Ag7GnPanA0jhX61h1ND1Q.jpeg" /><figcaption>Note the existence, occurence and valuation procedures — we get these for free with triple entry.</figcaption></figure><p>Alice and Bob now always have the same data — no need for reconciliations. Furthermore, accounting fraud is practically impossible using this system. Auditing is now easy-peasy as all SRL driven journals have a robust audit trail built in.</p><p>Lets look at Bitcoin in more detail.</p><h4>Bitcoin in an audit context</h4><p>It turns out Bitcoin already implements a triple entry system as standard. Perhaps Satoshi read Ian’s paper when he was developing bitcoind.</p><p>When we send bitcoin, the resultant transaction hash not only refers to the transaction but also the gives us the robust audit trail we need to post the associated accounting journal.</p><p>From an audit assertion perspective, we get</p><ul><li><strong>transaction occurrence</strong> — did the transaction occur?</li><li><strong>balance existence</strong> — does the balance exist?</li><li><strong>balance rights &amp; obligations </strong>— do we own the bitcoin?</li><li><strong>balance valuation</strong> — assuming the reporting currency is BTC</li><li><strong>balance and transaction cut-off </strong>— recorded in correct period?</li><li><strong>presentation &amp; disclosure</strong> — we know bitcoin is cash.</li></ul><p>for free — no need for bank confirmations and tedious reconciliations here!</p><p>Completeness is more difficult as Bitcoin is a pseudo-anonymous system. However we can use <a href="http://radar.oreilly.com/2014/12/clustering-bitcoin-accounts-using-heuristics.html">heuristic clustering</a> on transaction inputs to figure out addresses which users may have not have disclosed to us. In any case, auditors can off-load responsibility to management through the <a href="https://en.wikipedia.org/wiki/Management_representation">rep letter</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*x96NQCL9LB552JfF1fqcFw.png" /><figcaption>Auditors will have to leave bitcoin completeness checks to the crypto-boffins. Image credit O’reilly</figcaption></figure><p>As no rights or obligations arise due to cash payments we don’t need to worry about what happens in the future. A payment either happens, or it doesn’t and thus in most cases, a public key, digital signature and a <a href="https://en.bitcoin.it/wiki/Transaction">Pay2PubKey Hash</a> script is all that is needed to ‘audit’ new bitcoin transactions at a basic level.</p><p>In the case of Bitcoin, the block chain is fit for purpose but of course, there are other ways to do cash. Ripple also implements a triple entry system — they just sacrifice censorship resistance for gains in other areas.</p><p>The above is indicative of other permissionless proof-of-work driven block chains.</p><p>Other instruments are more difficult to handle.</p><h4>What about bonds?</h4><p>A bond is a fixed-income credit instrument used by entities to raise funds.</p><p>Upon issuance of a bond, certain rights and obligations arise</p><blockquote>The right of the bond holder to receive interest coupons and ultimately receive the principle in full.</blockquote><blockquote>The equal and opposite obligation of the bond issuer to pay interest coupons and repay the principle in full.</blockquote><p>These rights and obligations could continue for up to 30 years in the case of a 30 year bond or in the case of a perpetuity, indefinitely. The obligations may run into billions of dollars.</p><p>For this to work in a SRL context we have to address</p><ol><li><strong>Identity.</strong> Who is the bond issuer?</li><li><strong>Reputation.</strong> Will they pay?</li><li><strong>Performance.</strong> How will they pay? What happens if they don’t?</li></ol><p>Lets skim over identity and reputation for the moment. Assume we use <a href="https://en.wikipedia.org/wiki/Public_key_infrastructure">PKI</a> for identity and a credit ratings agency for reputation. We still need to consider performance and we have two options</p><ol><li><strong>A robust and fair legal framework that enforces penalties in the case of non-performance, i.e. English law. </strong>Payments are automated to a degree, however they still require sign-off by treasury.</li><li><strong>Smart contracts.</strong> Smart contracts would be great but instead we only have dumb ones. These contracts manage the payments in an autonomous manner with decisions based on data feeds from 3rd party <a href="https://blog.ethereum.org/2014/07/22/ethereum-and-oracles/">Oracles</a>. The smart contracts platform would need to be robust enough to run the course of the contract. Likely?</li><li><strong>A bit of both.</strong></li></ol><p>All this gets rather complicated, especially as we haven’t begun to consider issues such as managing credit risk, default, cross-default, monitoring, insolvency, debt subordination, securitisation, call provisions, etc. The solicitors and accountants have this covered — get your cheque books out!</p><p>Thoughts on the problem domain:</p><ul><li>We know the identity of counter-parties before we transact.</li><li>Reputation, in the form of credit worthiness, matters.</li><li>Longevity and robustness of the SRL is critical. There’s lots at stake.</li><li>We need coherent governance, <a href="http://www.reddit.com/r/Bitcoin/comments/37vg8y/is_the_blockstream_company_the_reason_why_4_core/">not a decentralised farce</a>.</li><li>Censorship resistance is not of great concern.</li><li>There are a tonne of edges cases.</li></ul><p>Putting my pragmatist hat on, it’s unlikely that block chains are the optimal SRL implementation here. Certainly not the permissionless proof-of-work driven type.</p><p>Permissioned block chains like Eris may have a place but it’s easier just to use something that isn’t as bamboozling, like a mysql database cluster and concentrate on things which matter, like good UX and coherent work flows.</p><p><a href="http://www.opentransactions.org/">Open transactions</a> looks like a more appropriate approach.</p><p>Whatever implementation we go with, we should get the triple entry power and in terms of audit assertions, that means;</p><ul><li>occurence</li><li>completeness (if we enforce the identity element)</li><li>existence</li><li>rights &amp; obligations</li><li>cut-off</li></ul><p>come out of the box.</p><p>Valuation should be done as usual by looking for a market price or a decent proxy, otherwise do what most auditors do and use a heavily caveated report from the in-house expert. That’ll be £800/hour please.</p><p>Of course, I haven’t even scratched the surface here. Needless to say, it’s all bloody complicated and we’re going to need much more than our block chain hammer to figure it out.</p><h4>Practical SRLs</h4><p>If you are this far, thanks for sticking with me. Here are some concluding thoughts</p><ol><li>Going forward, I believe we’ll have a SRL for each type of thing. One-size-fits-all SRLs wont work for a whole range of reasons, not least that they would be the mother of all (vendor) lock-ins. Ironic?</li><li>As each type of thing is quite different, these SRLs will be implemented in different ways. Some may use a block chain, others may use a classic federated (server) system, others may use something we haven’t designed yet.</li><li>Projects which use a block chain when one is not required will fail. Someone else will implement a better version using a mysql database whilst the block chain chaps are busy fixing a buggy distributed hash table, or something.</li><li>Ideally, accounting ledgers and other corporate systems of the future will ingest all this SRL data in order to post accounting journals and perform analytical functions. <strong>Note:</strong> we are not posting the actual accounting journal to a SRL, however we can use the SRL data to generate our journals.</li><li>Triple entry powered SRLs give you some audit assertions for free. So the lesson here is not to use block chains for audit but capitalise on the robustness of triple entry powered transaction data in SRLs.</li><li>Auditing things in the future will be a case of running scripts on the SRL’s data to grab the low hanging fruit. This is not “big data”, it’s just a database query that an auditor could write. Standard audit procedures apply for more subjective elements like valuation.</li><li>Smart contracts are not smart. They are dumb and will continue to be so. It’s more appropriate to view them as “business logic” executed in an expensive, decentralised virtual machine.</li><li>Smart contracts also don’t capture any of the intangible human elements of commerce and they probably will never do until we crack <a href="https://www.ocf.berkeley.edu/~arihuang/academic/research/strongai3.html">strong AI</a>.</li><li>Some crypto-boffins have trouble building software for humans as we are today. Instead, they are focused on developing software for robots in 20 years time. <a href="https://forum.ethereum.org/discussion/628/marriage-and-divorce-i-want-half">For example the Ethereum marriage contract is great when your helper robots of the future want to tie the knot</a>. Despite this, we thank them (and their investors) for their venerable efforts.</li><li>Intuitive work flows, good user experiences matter more than you might think. Barely anyone has cracked this yet and it’s of incredible importance as the majority of high paying corporate clients are infrastructure agnostic.</li><li>I suspect that most SRLs will be privately run (not by auditors as they should be independent!) to ensure flexibility and robust governance. No-one wants commerce to grind to a halt because some stubborn developers won’t approve a github pull request.</li></ol><h4>Closing remarks</h4><p>The future of audit won’t necessarily be involve block chains. Instead, it will involve triple entry powered SRLs of all shapes and sizes which will be specifically designed to meet domain requirements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b31fe711516a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Distributed Accounting Ledgers]]></title>
            <link>https://medium.com/@rog_dam/distributed-accounting-ledgers-d527d31870fe?source=rss-89948936a239------2</link>
            <guid isPermaLink="false">https://medium.com/p/d527d31870fe</guid>
            <dc:creator><![CDATA[Roger Willis]]></dc:creator>
            <pubDate>Tue, 20 Jan 2015 15:46:48 GMT</pubDate>
            <atom:updated>2015-03-27T09:39:13.913Z</atom:updated>
            <content:encoded><![CDATA[<p>There is an infectious <a href="https://www.youtube.com/watch?v=JGuhailQK9c">decentralisation epidemic</a> sweeping the globe — the blockchain inspires us all to root out and disrupt the rent collecting oligarchs!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*WgDLR5k6Q5czJJm6." /></figure><p>Is decentralisation appropriate in all cases? When it comes to solving <strong>real </strong>world problems decentralisation isn’t always the best solution.</p><p>This is the first in a series of posts in which I aim to discuss what’s wrong with accounting and audit and how distributed ledgers may help to solve some of these problems.</p><h4>What is accounting and why do we need it?</h4><p>Naturally, I turn to Wikipedia, which states</p><blockquote>“Accounting, or accountancy, is the measurement, processing and communication of financial information about economic entities”</blockquote><p>Yes, I’d agree with that. Accounting is set of rules or a grammar to aid in the description of real-world business events. Double entry book keeping and the basic accounting principles are the foundation of this grammar.</p><p>Just to dispel any ambiguities, an accounting ledger should be viewed as an append-only immutable database table.</p><p>I would also add, that for me, accounting also covers the processes and controls which must exist and be operating effectively to enable the honest recording, processing and reporting of real world business events in a ledger. For most companies, this involves investing in ERP systems and employing an army of clerks and developers to keep it all ticking over.</p><p>For the purpose of this post, I’ll take the universe of entities to mean any legal person (natural or otherwise) that needs to record business activities. All of these entities have an incentive to maintain records. The de minimis requirement common to all entities is the payment of tax, therefore entities must keep records to calculate the correct amount. Also, it goes without saying that for managers interested in monitoring the performance of their business, keeping honest records is a must! Other entities have more onerous requirements; annual accounts filing, quarterly reporting, due diligence, regulatory reporting — the list is <em>actually </em>endless.</p><p>Consumers are not required to maintain a ledger, though from a purist stance, consumer activities can be modelled using double entry bookkeeping. The majority don’t bother as there is no requirement to do so.</p><p>Some in the crypto-currency community have an acute disdain for such reporting and regulations. I can empathise but the reality is that for serious enterprises, reporting requirements and regulations exist and entities have no choice but comply. Non-compliance results in fines (<a href="http://www.theguardian.com/business/2010/jun/03/jp-morgan-fined-33m-by-fsa">JPMorgan client money breach</a>), repetitional loss (<a href="http://www.bbc.co.uk/news/business-29821061">Tesco</a>) or even worse, a material loss of assets (<a href="http://www.accounting-degree.org/scandals/">Enron</a>). The appropriateness of these reporting requirements and regulations is a discussion for another post.</p><h4>What’s the problem with accounting?</h4><p>It turns out there is only one <strong>big </strong>problem and we have solution for it already.</p><blockquote>“How can we trust that an entity’s accounts an honest reflection of reality?”</blockquote><p>The solution, of course, is financial audit. Audit has its own problems which are the subject of another post — here is a taster:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/0*DFBDOX8H5K-G3sBZ." /><figcaption>The audit value curve. Otherwise known as <strong>log(n)</strong> where <strong>n</strong> is a natural number &gt; 0.</figcaption></figure><p>There are other issues with accounting but they are not considered serious enough to warrant a fully mobilised war effort. Here are a few which I see:</p><ul><li><strong>Companies maintain their own private ledgers where they unilaterally record their own interpretation of real world events. </strong>This results in data duplication and inter-ledger inconsistencies. Accountants and auditors try to fix this problem with time consuming reconciliations. Todd Boyle wrote about <a href="http://linas.org/mirrors/www.gldialtone.com/2001.07.14/exploration.htm">data duplication</a> back in 2001 and his comments are still very relevant today. Last week, <a href="http://gendal.me/2015/01/15/cost-trust-something-else-whats-the-killer-app-for-block-chain-technology/">Richard Brown</a> posted an interesting article on how distributed ledgers may be relevant in this respect.</li><li><strong>Complexity. </strong>Financial accounting controls are really complex for large enterprises. Much of it is needless — I call this ERP spaghetti.</li><li><strong>ERP Systems. </strong>ERP system vendors are still in the stone age. This might attract some criticism but through my years in audit I hated the clunky interfaces and abysmal reporting capabilities. Clients could barely use the systems to run simple reports! Interoperability capabilities are generally poor — this is why businesses spend so much on integration. The advent of cloud accounting is fixing this for the SME market.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*XI7O1yIdYlWfS3W0FPWGBg.jpeg" /><figcaption>Usability horror</figcaption></figure><ul><li><strong>Time consuming, manual and error prone. </strong>A product of all the above. Accounting remains a mostly manual process and humans make a lot of errors. As an ex-auditor we regularly found multi-million pound errors; fat fingers, double counting and huge reconciling items no-one knew how to deal with! It doesn’t have to be this way — <a href="https://medium.com/@3ntry/audit-and-the-mechanical-dish-washer-8b209505b176">much of it could be automated</a>.</li><li><strong>Fraud. </strong>Even if humans don’t make errors, it’s still relatively easy for them to fudge the numbers, if they want to or are forced to. Through my fraud investigation experience, I can tell you it is exceedingly difficult and frustrating to retrospectively find accounting fraud.</li><li><strong>Auditing difficulty. </strong>Double entry accounting records are difficult to audit. Imagine a auditing a ledger with millions journals for the year! Audit becomes a complex ass covering exercise.</li></ul><p>Put simply, the basics of accounting have not changed for hundreds of years.</p><p>Today, the issues enumerated above are solved by formulating new rules, employing more clerks and investing in more IT infrastructure. This is the wrong approach.</p><p>I believe most of the above are solvable by doing three things;</p><blockquote><strong>Make accounting of a business activity an integral part of that activity. </strong>Instead of treating it as a separate process. What if the invoice was the journal?</blockquote><blockquote><strong>Sharing data between entities. </strong>Any business transaction involves an agreement of value by one or more parties. Privacy is not a problem as all parties should be recording the same data.</blockquote><blockquote><strong>Using cloud accounting ledgers. </strong>Large enterprises maintain simple private ledgers. APIs allow for easy integration and the development of plug-ins.</blockquote><p>Bitcoin achieves the first two things for cash payments.</p><p>By creating and signing a Bitcoin transaction, one generates a proof (which is consensus verified) that the transaction happened and they had the rights &amp; obligations to the unspent transaction outputs referenced in the transaction.</p><p>One can easily prove to anyone that they have the rights and obligations to a specific wallet by signing a message using the wallet’s private key.</p><p>Both parties to a Bitcoin transaction share the same ledger — the block chain. It follows that, with a bit of effort, any accounting for Bitcoin transactions can be performed algorithmically using pointers from a local ledger to the Bitcoin block chain. This is a clue for later.</p><h4><strong>What’ the ideal accounting ledger?</strong></h4><p>We are a long way off the ideal ledger. Cloud accounting packages are taking small steps but there is still much progress to be made. Here’s my take:</p><ul><li><strong>Lightweight and simple to use. </strong>I believe this would take the form of a cloud accounting package; a simple immutable append-only database to record journals and a set of API end-points which allow developers to build applications on top of the ledger.</li><li><strong>Easy interoperability with other ledgers and data stores. </strong>Entities can easily share and agree data with their counter-parties as opposed to unilaterally recording multiple versions of events and reconciling afterwards. Ledgers now rarely duplicate data.</li><li><strong>Forces honesty. </strong>If counter-parties share records, it becomes more difficult to fudge things.</li><li><strong>Facilitates a continuous audit process. </strong>If data is shared, then most transactions are audited as and when they happen, or soon after.</li><li><strong>Complete. </strong>If it’s not in the ledger, it doesn’t exist. Bitcoin does this well.</li><li><strong>Sensible approach to valuation. </strong>Instead of, absolute valuations, <a href="http://www.zyen.com/PDF/Confidence%20Accounting1.pdf">use a valuation distribution</a>. Banks do this with <a href="http://en.wikipedia.org/wiki/Value_at_risk">VaR reports</a>.</li><li><strong>Internet of Things integration. </strong>Auditors can ascertain existence and rights &amp; obligation through direct communication with an entity’s assets. E.g. “I’m a widget machine and I belong to Bob Ltd, here’s a digital signature to prove it”.</li><li><strong>Integrating reporting. </strong>A means to take the ledger and spit out US GAAP accounts, IFRS accounts or a tax compliance report at the click of a button. Aside from valuation, most rules are very prescriptive and can be implemented by an algorithm. Some ERP systems attempt this already.</li></ul><p>That’s an ambitious list of requirements.</p><p>Lets start with the low hanging fruit, <em>sharing, </em>which features in at least 4 of the above.</p><p>What if we can merge <em>sharing</em> with <em>Make accounting of a business activity an integral part of that activity? </em>It turns out we can.</p><h4>Transactions and Adjustments</h4><p>I’m not suggesting that companies ditch their locally maintained ledgers and start recording everything on a blockchain.</p><p>Distributed ledgers are not appropriate for the majority of accounting workflows, however they do have a place.</p><p>I find that most in the crypto community don’t <em>get</em> that accounting is a different beast to issuing tokens and regulating their transfer (Bitcoin).</p><p>Share certificates and other transferable agreements sit in this <em>Bitcoin </em>bucket, however accounting journals don’t, this generally includes invoices in my opinion.</p><p>With accounting, there’s no requirement for tokens as we just create and destroy value at will through journal entries. Account balances rise and fall as business is conducted. Things that are <em>accountable</em> can clearly be represented with tokens however, such as money, shares and option agreements.</p><p>The existence of accounting principles dictate that the treatment of cash will always differ to the accounting of business activities (P&amp;L versus cash flow statement), therefore using a Bitcoin like system is inappropriate as it does not allow us to effectively model the accruals concept, for example.</p><p>Assuming there exists an appropriate distributed ledger for things that are accountable, we need to consider which journals will sit in this distributed ledger. There are two broad types:</p><ul><li><strong>Transactional journals </strong>pertaining to an agreed transfer of value with counter-parties.</li><li><strong>Adjustment journals </strong>which are used to maintain the accounting grammar. There is no counter-party involvement. They may or may not depend 3rd party data e.g. valuations.</li></ul><p>It follows that adjustment journals depend on transactional journals, for example, one cannot post an accrual if there is no expense to accrue. One can procedurally assert the validity of these adjustments through simple rules based on the accounting grammar.</p><p>We assert that adjustment journals always depend on transactional journals. If we can agree on transactions the accounting and audit gets much easier for all involved.</p><p>It seems that as adjustment journals do not involve counter-parties they are best confined to a local ledger. There are other reasons why this should be the case but I won’t discuss them here.</p><p>So now we have the concept of a local cloud ledger and a bunch of accountable transactions which may sit in a distributed ledger.</p><h4>Transaction Pointers</h4><p>If we had an accepted place to store transactional data then we can just store pointers to that data in our local ledgers. Bitcoin does this for cash, I’m building Triplentry for invoices and BitShares exists for issuance and transfer of share certificates. See below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*CPULPbeuXSYo4wxKF6-KFA.png" /></figure><p>The distributed ledgers store digitally signed receipts. The receipt <strong>is</strong> the transaction. Ian Grigg and Todd Boyle coined the term <a href="http://iang.org/papers/triple_entry.html">Triple Entry Accounting</a> which describes the digitally signed receipt.</p><p>The receipt can be viewed as an immutable record held by a third party, proving all parties agree to the transaction. It follows that each party to the transaction can procedurally generate the local double entry for the transaction, on demand.</p><p>Entities may wish to store additional meta data about a transaction which they point to in a distributed ledger.</p><p>All these distributed ledgers combine the act of performing the transaction with the accounting of the transaction — this is the Triple Entry magic!</p><p>Richard Brown touched on this in his <a href="http://gendal.me/2015/01/15/cost-trust-something-else-whats-the-killer-app-for-block-chain-technology/">last blog post</a> — perhaps there may exist a distributed ledger for all transactions, e.g. <a href="https://www.ethereum.org/">Ethereum</a>?</p><p>It seems more likely to me that there will be a ledger for each type of thing. The inherent complexity of building a system to deal with all accountable things and successfully integrate with existing accounting workflows is a massive challenge!</p><h4>Putting it all together</h4><p>In some ways the technology is the easy bit. Bringing it to market is a different challenge altogether:</p><ul><li><strong>How do we integrate the distributed ledger with existing legacy accounting software and accounting workflows?</strong> This is always easier said than done.</li><li><strong>How distributed does the ledger actually have to be? </strong>The whole point of this article was to discuss distributed ledgers but of course the same functionality could be achieved with a centralised ledger.</li><li><strong>What’s the incentive for companies to use distributed ledgers? </strong>Reduced cost, more assurance, less fraud. Are these enough to warrant implementing a new system?</li><li><strong>How will regulators and industry incumbents react?</strong></li><li><strong>How do we handle privacy and security of data?</strong> Richard Brown touched on this. By design, decentralised ledgers are public and this is not always appropriate for accounting.</li></ul><p>I hope to answer some of these questions in coming blog posts and with the release of my first product, Triplentry. I will leave the implementation discussion for another post.</p><p>Thanks to Ian Grigg for his comments on this blog post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d527d31870fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Audit and the mechanical dish washer]]></title>
            <link>https://medium.com/@rog_dam/audit-and-the-mechanical-dish-washer-8b209505b176?source=rss-89948936a239------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b209505b176</guid>
            <dc:creator><![CDATA[Roger Willis]]></dc:creator>
            <pubDate>Mon, 19 Jan 2015 14:55:13 GMT</pubDate>
            <atom:updated>2015-07-14T16:58:08.054Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*uhkRT-QAckMjG9Dgh0ocqg.jpeg" /><figcaption>Your typical audit</figcaption></figure><p>Audit is like washing dirty plates.</p><p>Imagine so many dirty plates sitting on the counter which haven’t been washed for months. The kitchen staff leave them until year end for the auditors to wash up. This is because they are not allowed to wash their own plates — they cannot be trusted to do it properly.</p><p>The kitchen staff don’t like auditors who apparently judge them based on how dirty the plates are. The head chef is usually friendly though, after all, he needs to ensure that his plates are washed properly.</p><p>There is a constant dialogue between the auditor and head chef. The head chef is always concerned that the plates don’t get washed in time, or the auditors find a really dirty plate.</p><p>Sometimes the auditor and the Kitchen staff argue about how dirty the plates are. The auditor usually wins though.</p><p>The auditor comes in now and then to inspect the plates and review the washing up process guidelines, however they tend to not actually wash the plates until year end. That’s the generally accepted way.</p><p>The washing often gets expensive due to the sheer amount of plates to get through, especially for large kitchens. The auditor needs to employ lots of washers.</p><p>Some plates are very easy to wash, while others are tougher, such as large saucepans and baking trays. They take ages and it’s easy to miss bits.</p><p>Some plates require specialist cleaning which is more expensive. The auditor is required as per the regulations to seek assistance from a specialist cleaner if they cannot do it themselves.</p><p>The auditor for the most part, does a good job at washing the plates though every now and then they miss bits.</p><p>There are multiple high profile cases where customers were given dirty plates. The kitchen and the auditor can get in big trouble. The auditors tend to have very good solicitors and are used to dealing with claims they didn’t wash off enough dirt.</p><p>To combat these claims, a risk based methodology is introduced; wash the greasy pans first and then work on the regular plates. It is hoped that this will ensure the dirtiest plates are cleaned first. After all, as long as most of the dirt is washed off, then they’ll still get paid and no customers will complain.</p><p>After the audit, all the cracked plates are discarded — they can’t be used again. Sometimes the head chef and kitchen staff try to put cracked plates back in the cupboard. Skeptical and experienced auditors are good at finding cracked plates though it is not their responsibility to do so. It is accepted that auditors just have to wash plates.</p><p>Unfortunately some plates were so dirty they could not be cleaned — they also go in the bin.</p><p>If only the auditor had more time to concentrate on the really dirty plates.</p><p>The senior auditors come up with a plan — the leveraged model! Why don’t we employ a tonne of University graduates to wash the easy plates. We can get the experienced auditors to inspect the plates that the graduates have washed. This way, we as the senior auditors, can do multiple audits at once and only get involved when there is a really dirty plate to clean.</p><p>The auditors are perhaps aware that they could just tell the kitchen staff to invest in developing a mechanical dish washer but they never do! Maybe because they don’t know how and even if they did, the manual way is still very profitable for the auditors. They know that no-one else has the scale to wash so many plates on demand.</p><p>The kitchen staff are also skeptical about investing in a machine as it’s expensive and doesn’t help them sell any more meals — what’s the point they think?</p><p>If there was a mechanical dish washer then the auditors wouldn’t need so many graduates and the graduates that were still employed could concentrate on the dirtier plates, knowing that the easy plates will be washed. The washing machine also does a better job than a graduate could ever do. It’s much quicker as well.</p><p>From the kitchen staff’s perspective, if they had a mechanical dish washer, they could actually wash the plates as they became dirty instead of leaving them until the year end. All the auditor has to do is open the machine at year end and check all the plates are clean. Simple.</p><p>What if someone built a really effective washing machine using a shared replicated ledger. It could be offered to kitchens for a <em>really </em>small fee on a per plate basis. Easily low enough such that it makes their audit fee cheaper and reduces their operational costs. The auditor also pays a fee to look inside the machine at the year-end. If the auditor doesn’t pay the fee they will have to buy new plates. They realise this is pointless, so they just pay the fee.</p><p>The auditor can actually increase their margins this way, though there is a side effect — revenue decreases as the audit doesn’t take as long. The head auditors realise they have to fire some of the senior and junior auditors. They are smart and already know this, as they’ve all read an <a href="http://www.oxfordmartin.ox.ac.uk/downloads/academic/The_Future_of_Employment.pdf">academic paper</a> which describes how their profession will be mostly automated in a few decades time.</p><p>Now, all but the most awkward plates can be washed by machine.</p><p>Click <a href="http://www.3ntry.co/">here</a> for further details on the dishwasher.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b209505b176" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>