Blockusign

@francesco_bellanca also curious about your question

@francesco_bellanca This article explains the approach Docusign is taking in regards to the Blockchain (Ethereum) . I think they are always going to maintain ownership of your document and your keys to decrypt it (if they even encrypt at rest in the first place) in their centralized database (honeypot) https://www.docusign.com/product....

@francesco_bellanca @rrhoover Blockusign's take on "smart contracts" for this use case is you don't need an on-chain smart contract (like Ethereum). You simple have two parties provide a final state hash of the document they signed with e-signatures, then you simply create a digital signature of that document hash. Both parties have their separate digitally signed copies (in user controlled blockstack storage) and persist that hash to the bitcoin blockchain using the OP_RETURN. That hash can be linked back to the users blockstack name (and attestations, like facebook/twitter) to prove who they are. To save on costs I am actually currently implementing Blockstack Subdomains to batch hashes and only persist a Merkle root hash occasionally to bitcoin. I think this architecture can be used for many different use-cases for "off chain" smart contracts using state hashes. Unless Docusign drastically changes their entire architecture I do not think they will ever support user controlled storage and identity (self sovereign). Tim Berner's Lee has a similar philosophy with his SOLID project https://solid.inrupt.com/ . Blockusign uses Blockstack to accomplish this https://blockstack.org/ . (edited) Here's a link to a video explaining my architecture (at a very high level) with the app demo https://blockusign.co/signup.html