EFTA00815691.pdf

DataSet-9 1 page 364 words document
D1
👁 1 💬 0
📄 Extracted Text (364 words)
From: "jeffrey E." <[email protected]> To: Subject: Re: Sharia Banking Date: Sat, 08 Oct 2016 11:33:28 +0000 the experts in sharia are coming today at 12 , if you would like to sit in. I am not fully versed in the field On Sat, Oct 8, 2016 at 7:25 AM, a- wrote: So I've gone through and read up on the basics of Sharia banking. I think it's a great angle for a lot of this technology. Let me ask a couple fundamental questions: 1) It seems that trustlessness is not the issue here; institutions are semi-trusted because they have to be compliant with religious ideals, a breach of such contract would be duly punishable 2) What is needed is clarity; making sure terms are fully understood and appreciated by all parties, ie, "true consent". 3) Significant uncertainty in contracts is expressly forbidden, use cases which must rely on uncertainty can rely on other mechanisms. From this, my feeling is that the opportunity here is in creating a smart-contract language/compiler for Sharia Law which allows for unambiguous & automatic execution of terms as well as a contract dis-assembler which explains all the possible executions of such contract. The need for the immutability properties of a bitcoin like blockchain are actually minor, parties do conduct honestly under typical Sharia banking. Therefore the system can focus on local record keeping (having evidence of party-wise agreement) but there is limited need for global agreement. Does this seem somewhat right? Or are the problems these groups are facing more in the interface to westem banking realm, where they need a shim to access western banking and be Sharia Compliant? Best, please note The information contained in this communication is confidential, may be attorney-client privileged, may constitute inside information, and is intended only for the use of the addressee. It is the property of JEE Unauthorized use, disclosure or copying of this communication or any part thereof is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by return e-mail or by e-mail to jeevacation®gmail.com, and destroy this communication and all copies thereof, including all attachments. copyright -all rights reserved EFTA00815691
ℹ️ Document Details
SHA-256
f7ca867d5597f6b5f89a5801a3dcbba3072076ea2fc3e57ae671b067a840fe87
Bates Number
EFTA00815691
Dataset
DataSet-9
Type
document
Pages
1

Community Rating

Sign in to rate this document

📋 What Is This?

Loading…
Sign in to add a description

💬 Comments 0

Sign in to join the discussion
Loading comments…
Link copied!