Happy new year! (A belated) welcome to 2019, the year where we will see end to end solutions come into being. The commercial deployments of blockchain, and specifically Corda, continue to increase at rapid pace. But where those commercial deployments, stakeholders, and networks begin to connect is where the full benefits of blockchain are captured. What I mean by “connect” is fitting together multiple solutions to discrete pieces of the lifecycle of a transaction or asset (many of which you can find today on the R3 Marketplace), thousands of which have been developed in PoCs. This connecting requires public and private sector solutions working together. Then, the next layer on top of that, is interoperability, which allows assets from one network to be used or spent in another.
Connecting solutions driven by the public sector with those driven by the private sector
In my last blog I wrote about blockchain being deployed in the public sector, which is something we see increasing around the world (albeit some regions are moving faster than others). What’s most interesting, however, is the intersection of the public sector and the private sector. What will happen when business interests and public sector deployments touch? The answer is simple: the efficiencies and advantages are multiplied. Said a different way, the sum is greater than the parts.
Let’s use real property as an example. The work that Her Majesty’s Land Registry has begun with its Digital Street Project is, as the name suggests, about the UK’s land registry (a public interest). However, the Digital Street Project is not just about recording the transfer. There are private sector elements as well because it is about using blockchain in the processes that lead up to updating the central database of property ownership. For example, there are banks involved for mortgages (and potentially other secured lenders against the property), lawyers for structuring the transfer and getting proper signatories, and realtors to put buyers and sellers together. HMLR customers range from private individuals to major financial institutions, large-scale developers, a wide variety of legal and conveyancing service providers, and third-party businesses that make use of the data to innovate and inform their own work.
Beyond the land registry
Take another piece of the real property example: mortgage reporting. Mortgages — their issuance, transfer, and closing — are reported to regulators. R3 embarked on a journey with member banks and the UK’s Financial Conduct Authority to show how Corda can not only facilitate the issuance and transfer of mortgages, but also enable the FCA to see those issuances and transfers. That project demonstrated that Corda can be used to save mortgagors the time and cost associated with regulatory reporting and provide regulators accurate and timely reports.
Now, taking these together, we have the negotiations and record access elements ahead of the property transfer, then the issuance of a mortgage token, property title token, and legally enforceable smart contract on the Corda network, and the requisite reporting. Then the question is who else can benefit from seeing those transactions? One answer is the tax and revenue authorities. When property changes hands, it must be reported to tax authorities and taxes come due, both for increase in the value of the property while the seller held it and also from the transfer itself, which is subject to a tax in most jurisdictions. The CorDapp trial of the Instant Property Network solution, which kicked off today, includes all of the stakeholders mentioned in this blog post and will be a live demonstration of how all of them come together for one real property solution.
I’ve just described the process for a real property transfer, largely as we know it today, but with the benefits of blockchain. A new twist that we’re seeing in real property on blockchain is fractional ownership (i.e. tokenizing real estate in pieces, not as a whole). With real property becoming more liquid and affordable, a higher number of people — including young people who currently cannot get on the property ladder — can now be owners. This is one of the reasons why UK housing associations have started to look at Corda.
As I mentioned at the beginning, connecting solutions is one thing. The other piece to the puzzle is how the nodes connect, meaning how you can take the money you just got from a real estate sale and turn around and invest it through another DLT solution. The answer is you can’t do that unless the network is interoperable as Corda is (meaning, all nodes can connect to all other nodes, and that assets from one CorDapp can be used in another).
So when choosing a blockchain solution two things to think about are: (1) what related solutions are on that platform already, which are indicators of the likelihood of getting an end to end solution in the near term, and (2) can those assets be used in other applications or will they be required to be taken off chain and put back on in another network?
What’s to come?
This post used real property as an example, but this same coming together of stakeholders and solutions is happening in other markets and is picking up speed. For example, healthcare and insurance are both developing and growing toward one another. The same is happening with trade finance and supply chain. Stay tuned for more developments in real property and beyond!
Putting it all together: combining public and private sectors to get the best out of blockchain was originally published in R3 Publication on Medium, where people are continuing the conversation by highlighting and responding to this story.
Sign up for our newsletter to receive the latest R3 news, updates, and materials
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
|__cfruid||session||This cookie is set by the provider Cloudflare. This cookie is used for load balancing and for identifying trusted web traffic.|
|ARRAffinity||This cookie is set by websites that run on Windows Azure cloud platform. The cookie is used to affinitize a client to an instance of an Azure Web App.|
|cookielawinfo-checbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|JSESSIONID||session||Used by sites written in JSP. General purpose platform session cookies that are used to maintain users' state across page requests.|
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
|bcookie||2 years||This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page.|
|lang||session||This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website.|
|language||This cookie is used to store the language preference of the user.|
|lidc||1 day||This cookie is set by LinkedIn and used for routing.|
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
|_BUID||1 year||This cookie is used to store a universal user ID to identify the same user across multiple clients' domains.|
|_ga||2 years||This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.|
|_ga_1ECB5XX5W0||2 years||This cookie is installed by Google Analytics.|
|_gat_UA-87760032-2||1 minute||This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.|
|_gcl_au||3 months||This cookie is used by Google Analytics to understand user interaction with the website.|
|_gid||1 day||This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.|
|_hjAbsoluteSessionInProgress||30 minutes||No description available.|
|_hjFirstSeen||30 minutes||This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.|
|_hjid||1 year||This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.|
|_hjIncludedInPageviewSample||2 minutes||No description available.|
|_hjIncludedInSessionSample||2 minutes||No description available.|
|_uetsid||1 day||This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site.|
|_ym_d||1 year||This domain of this cookie is owned by Yandex.Matrica. This cookie is used to store the date of the users first site session.|
|_ym_isad||20 hours||This domain of this cookie is owned by Yandex.Matrica. This cookie is used to collect information about the user like his characteristics, behaviour on page and targeted actions.|
|_ym_uid||1 year||This cookie is by Yandex.Metrica. This cookie is used to set a unique ID to the visitor and to collect information about how visitor use the website. Thus it help to track the user and the collected informationn is used to improve the site.|
|CONSENT||16 years 5 months 12 days 10 hours||These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video.|
|pardot||past||The cookie is set when the visitor is logged in as a Pardot user.|
|vuid||2 years||This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.|
|yabs-sid||session||These are cookies used by Yandex Matrica script belonging to the company Yandex. This cookies are used to measure and analyse the traffic of the website by giving information about how the users use the website.|
|yandexuid||1 year||This cookie is used to identify the users. This cookie collects information about how visitors use the website. This information is used for internal analysis and site optimization.|
|ymex||1 year||This cookie is set by yandex. This cookie is used to collect information about the user behaviour on the website. This information is used for website analysis and for website optimisation.|
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
|_fbp||3 months||This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.|
|anj||3 months||No description available.|
|bscookie||2 years||This cookie is a browser ID cookie set by Linked share Buttons and ad tags.|
|fr||3 months||The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin.|
|i||10 years||The purpose of the cookie is not known yet.|
|IDE||1 year 24 days||Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.|
|MUID||1 year 24 days||Used by Microsoft as a unique identifier. The cookie is set by embedded Microsoft scripts. The purpose of this cookie is to synchronize the ID across many different Microsoft domains to enable user tracking.|
|NID||6 months||This cookie is used to a profile based on user's interest and display personalized ads to the users.|
|personalization_id||2 years||This cookie is set by twitter.com. It is used integrate the sharing features of this social media. It also stores information about how the user uses the website for tracking and targeting.|
|test_cookie||15 minutes||This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.|
|uuid2||3 months||This cookies is set by AppNexus. The cookies stores information that helps in distinguishing between devices and browsers. This information us used to select advertisements served by the platform and assess the performance of the advertisement and attribute payment for those advertisements.|
|VISITOR_INFO1_LIVE||5 months 27 days||This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.|
|YSC||session||This cookies is set by Youtube and is used to track the views of embedded videos.|
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
|_uetvid||1 year 24 days||No description available.|
|AnalyticsSyncHistory||1 month||No description|
|ARRAffinitySameSite||No description available.|
|bEkAYwpdRGcM||1 day||No description|
|LEAfgqMGWpwUs||1 day||No description|
|li_gc||2 years||No description|
|lpv413292||30 minutes||No description|
|metrika_enabled||session||No description available.|
|UserMatchHistory||1 month||Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences.|
|visitor_id413292||10 years||No description|
|visitor_id413292-hash||10 years||No description|
|visitorId||1 year||No description|
|yt-remote-connected-devices||never||No description available.|
|yt-remote-device-id||never||No description available.|
|yuidss||1 year||No description available.|