Written by R3’s Peter Michalopoulos
In an increasingly global capital markets landscape, Islamic finance products, such as the popular Sukuk instruments, have contributed to the growing portfolio of investment opportunities. These products are often structured to comply with Shariah law, which can make them more complex relative to conventional bond structures.
A new R3 Research market analysis, “Innovating in Sukuk Capital Markets,” cowritten with Clifford Chance and Wethaq, evaluates the Wethaq platform, a solution built on Corda intended to streamline and expand the Sukuk market.
Benefits of the Wethaq platform include greater efficiency and transparency throughout the end-to-end Sukuk lifecycle, easier Shariah compliance, interactions with cash settlement innovations, and interoperability with other CorDapps.
The Sukuk al-Ijara is a common Islamic finance instrument that allows capital raisers and capital providers access to Shariah-compliant products certified by Shariah boards.
Conventional bond structures are not considered to be Shariah compliant as they involve the payment and receipt of interest. Sukuk securities, by contrast, comply with Shariah principles through passing on the returns from an underlying asset or through a contractual arrangement with respect to that asset.
Under current industry practice, the Sukuk issuance is exclusively led by banks and fundraisers. For this, the bank relies on its own private and proprietary processes within a ‘closed’ ecosystem. The Wethaq platform intends to open and expand the ecosystem by streamlining coordination between market participants, standardize processes and automate the administration of financial services.
The Wethaq Platform applies distributed ledger technology to Sukuk markets with the objective of having a system that can:
Though there have been ‘data-driven’ clauses used in finance for decades, ‘smart clauses’ introduce a crucial aspect: performance of obligations is automated using strict and formal programming language which is deployed on a distributed ledger beyond the control of any single party to that ledger.
This automation creates several efficiencies:
Public (permissionless) distributed ledgers are a unique innovation in the history of finance, given their operational decentralization, settlement times, and global liquidity access. However, within regulated wholesale capital markets, distributed ledger architectures must meet the functional and non-functional requirements of network participants. Most public distributed ledger architectures, such as Ethereum, weren’t originally built to be used for business transactions and encounter architectural complexities when the base codebases are adjusted to fit within an enterprise setting.
Corda was built from the ground-up through an intensive requirement-gathering process alongside the teams from 40+ of the largest global banks. As a result, Corda differentiates itself from other distributed ledger technologies due to its:
By using Corda, Wethaq can interoperate with the global Corda ecosystem, and take advantage of new developments with cash (fiat) settlement functionality within a distributed ledger environment, while maintaining the unique structure of the Sukuk Al-Ijara.
The value proposition of the Wethaq Platform is the streamlining of processes, reduction of intermediaries, and automated performance of contractual obligations through the use of smart clauses on a distributed ledger-based platform.
The Wethaq Platform is not an ‘island’ but benefits from the openness and functionalities of the Corda ecosystem. Many of the world’s largest financial institutions are deploying Corda nodes; R3 has designed Corda to be the platform that bridges seamlessly from legacy infrastructure to ‘digital-first’.
Read more about interoperability between CorDapps by the SIX Swiss stock exchange.
Within the Wethaq Platform itself, third parties may use open-sourced Corda Developer Tools and, for their specific Sukuk needs, the Wethaq Developer Tools to ‘plug in’ and offer their services and products on the platform.
The Wethaq Platform will integrate Corda Settler, an open-sourced CorDapp that allows payment obligations arising on the Corda Protocol to be settled via any traditional rail capable of providing cryptographic proof of settlement, whether ‘on-’ or ‘off-ledger’.
Read more about use cases with Corda Settler.
Sukuk markets have less cost efficiency and transparency than conventional debt markets due to relatively higher structural, compliance and document complexity. As an alternative to this, Wethaq would facilitate functions that would otherwise be performed by a number of banks, clearing and trustee entities all incurring separate fees and other engagement costs.
The distributed ledger facilitates cashflow record keeping in a transparent and easily reconcilable way that demonstrates the source and timing of payments. In the Sukuk context this can support transparency in the issuance and payment process and in tracking the underlying assets or cashflows generated. Additionally, the employability of ‘smart clauses’ gives Shariah boards the opportunity to ensure Shariah compliance by building and mapping real world Shariah requirements within the structure itself.
The rapid development of enterprise-distributed ledgers will inevitably disrupt Sukuk markets. Benefiting from the unique architecture of Corda and interoperability with both incumbent as well as newer market infrastructures, Wethaq is well placed to lead an evolution of the securities ‘value chain’ in these markets within existing regulatory frameworks.
Read the full R3 Research Paper
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.|