SamuraiDocuSign

Screenshots

Problem Statement

Current Web2 electronic signature softwares need censorship and Web3 signing dApps have following problems:Contract documents are stored on centralized storages like: Cloud, DBApplication has a full control over the documents and signing process.Non-Civil Resistant for issuing contract and user don't see the legit document.Bad wallet UX and paying gasSo, we've revolutionized the whole experience and solve problems with features below:✨ Secure access control, encryption & decryption without censorship & control by App🔥 Gasless signing user experience by AA and paymaster.Signer doesn't need wallet & gas fee👁 Sybil Resistant by WorldID.Only humancan issue a legit contract document.Contract issuers upload the PDF document, specify the signer's email and provide proof of personhood. Contract signers don't need wallet and gas fee. They can social login and sign the document.Docusign3 enables trustless & simple UX document signing.

Solution

Issuer (create a contract document)Connect wallet by Wallet ConnectVerify issuer is a legit human with WorldcoinSpecify the signer by providing the signer's emailUpload contract document(PDF) to IPFSEncrypt the IPFS CID with Lit SDK, then set access-control-condition(ACC) with LitAction. FetchingencryptedCIDandencryptedSymmetricKeyHash the signer's emailWrite (encryptedCID, hashedEmail, encryptedSymmetricKey) on smart contractSigner(sign a contract issued by Issuer)Social Login with emailCreate EOA with PrivyCreate SCW(Smart Account) with Biconomy SDKVerify the signer has a expected Gmail with LitAction. Fetching user's JWT token and recover email by Privy API, hash the Gmail and verify that it matches theHashedEmailon smart contractDecrypt theencryptedCIDwith Lit SDK and get original document IPFS CIDEnabling to view the PDF contract document with CIDSign with Gasless transaction by Biconomy SDK with paymaster.Access Control & Verification for P2P signingWe handle P2P access control for the contract document by IPFS & Lit & Privy. If you want to look into it, we explain the verify flow onREADMEcheck this!!