Communications service providers have been putting a lot of energy into researching the use and application of blockchain/DLT to understand the benefit of the technology and where the value in adoption lies. The sector is now moving on from testing MVP solutions and doing PoCs to considering the demanding requirements of enterprise-grade deployments. This means that teams across communications service providers are having to critically decide which blockchain platforms to go into production with.
In this blog post, I’ll try and outline some of the questions CTOs, CIOs, and industry strategists might want to go through when considering which blockchain technology to use for communication services projects.
R3 has heard many of the same requirements from clients before, across some of the most demanding globally regulated markets such as financial services, which is why we built Corda from scratch as an enterprise-grade blockchain platform to answer many of the questions below.
“Traditional databases aren’t broke, so don’t fix ‘em”.
While this is true if you’re trying to manage a business process within a single firm or are content to trust a third party to manage a multi-party process on your behalf. But where you have a network requiring multiple parties to achieve consensus regarding the identity of counterparties, the parameters of agreements or the exact process of transactions and do not or can not rely on a centralised third party to manage this process, then a blockchain should be the most optimal platform for you.
Some problems, of course, are best delivered through traditional architectures, and there is never a need to choose blockchain for the sake of blockchain. But what traditional architectures can’t offer you is what we at R3 describe as the ability to know for sure that “what I see is what you see.”
Owning the first telephone wasn’t that exciting, apparently, and similarly, being the only organisation to use a particular blockchain platform offers limited value.
Therefore, when considering which blockchain platform to deploy think about who is already using it, what they are using it for, and how easily it will be for your counterparties to adopt. Organisations will also need to consider which adjacent networks you may want to transact with and access in the future. The future products & services of communications will be made possible by combining the capabilities of different networks. So look at where banks and insurers etc. are operating, and how your organisation could interoperate with their networks to leverage cross-sector capabilities to deliver new products & services.
For telecoms clients, one of the key motivations for adopting blockchain technology is to drive efficiencies and reduce operational costs. This means blockchain technology needs to remove complexities from doing business and using a platform that allows networks to interact with one another is essential. Corda was founded on a mission to make “duplicates, reconciliations, failed matches and breaks… things of the past. Isolated pools of trapped assets will be no more,” and this vision is being delivered by Corda Network. An independent ‘internet of Corda nodes’ empowering Corda nodes and networks to interoperate, thus delivering on the promise of massive efficiencies from distributed networks.
New tools like the Corda Settler are also supporting the interoperability of Corda with other rails such as the SWIFT payment network.
Blockchain platforms traditionally use global gossiping consensus protocols to bring non-trusting network participants into agreement. However, this lack of privacy is wholly inappropriate for enterprise clients handling sensitive data in regulated markets. Corda was designed from day one with a point-to-point transaction architecture to guarantee privacy. Businesses from across industries have adopted Corda because of its ability to bring multiple parties into consensus, whilst at the same time ensuring control and privacy of data which is only shared on a need to know basis.
Many questions have been raised about blockchains ability to scale to meet enterprise-grade client requirements. Corda, on the other hand, was designed specifically to tackle these concerns and for example, has been proven under independent test scenarios to be able to scale to support the average daily trading volumes of the US equities market, large scale trade finance networks and the world’s largest reinsurance blockchain network. Corda’s unique point-to-point transaction architecture means there isn’t a need for every node to process every transaction, which is significantly more efficient and scalable. Therefore, Corda is automatically optimally sharded.
At the end of the day, telecoms firms deal with critical national infrastructure. They will never adopt technology unless they are 100% certain it will meet their requirements. Here again, Corda has been proven to meet the security, resiliency, scalability and integration requirements of the most demanding regulated market participants and is being used in those environments today.
Corda has been built using tried and tested technology, such as the Java Virtual Machine. This means Corda is supported by a community of over 12M java developers globally and a fast-growing community contributing to Corda opensource. It is being used by a partner network of over 300 firms building solutions on Corda today, and is deployed
R3 is constantly striving to improve the platform and work with our growing community of partners providing feedback and contributions to help deliver the future of blockchain to communications.
R3 is actively engaged with the communications sector to identify new efficiencies as well as products and services that can be delivered on blockchain. If you are interested to learn more about how Corda can deliver this for your organisation, then please get in touch.
6 Questions CSPs should consider when selecting blockchain platforms 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.|