Please describe your proposed solution
For reference, please see our demo of Csign here:
<https://www.youtube.com/watch?v=pvxL5z432cU>Anyone can try it out at https://demo.csign.io
Csign exists as a Proof of Concept demo. The demo allows users to create, sign, certify, and verify agreements between parties using Atala PRISM and Cardano, there is nothing faked here. This demo is currently using a database instead of Cardano Testnet, but we will point to Testnet with the help of Fund12.
To make this a publicly available MVP, we need to add more features and make some improvements.
With the help of Fund 12, here’s what we’ll add:
BYOS (Bring Your Own Storage):
Csign takes your document privacy seriously. When you upload a file, whether it be a PDF, image, or video, Csign encrypts that file locally first, then stores it on a server as a binary “blob of bits”. The file is encrypted with a key on your local computer, and never stored with the file. When someone you’ve invited to sign, wants to view that file, the decryption key is sent to them directly via an encrypted peer to peer connection using the DIDComm2 protocol. They can download the file and decrypt it locally. This means that no one, including Csign can read your agreement, except the creator and the signers. The Csign Proof of Concept demo uploads these encrypted files to our server, and while this is perfectly private and secure, we’d like to give users more choice. BYOS means you can point Csign to store uploaded files on a storage platform of your choice. If your company uses Dropbox, Google Drive, Box, etc, just login to that service and Csign will store files there. This allows you full control over your data in the way you and your team feel comfortable with. Csign will eventually support many BYOS platforms, but for now we’d like to focus on the most popular. Our plan is to publish a survey to the community and let them decide which service we should support first. Your data is your data, and it will be encrypted anywhere you store it.
Csign API:
Csign is a product anyone can use to securely and privately sign, certify, and verify agreements. Our team takes pride in crafting a smooth and delightful user experience for all, abstracting away all the complexities of technologies like Self-Sovereign Identity, managing identity wallets, cryptography, and encryption. However we have an even bigger vision for Csign. We want Csign to enable new, private and secure agreement signing functionality in YOUR apps. The Csign API is a service that other companies can use to leverage the power of Csign Core, in a fully custom branded flow of your own design. Want to add Csign capability to an internal tool at your company? We got you. Want to add secure and private multi-sig agreements into a DEX Onboarding flow? We’re here to help.
The Csign API will be delivered in three phases, and we welcome developer input as we build the tools you’ll love to implement. In Phase One, we’ll document the Csign API spec, showing developers how they can interact with Csign Core as a RESTful web service. We’ll detail what’s possible so we can accept feedback and talk to developers about their exciting and interesting use cases. In Phase Two, we will set up the infrastructure required to supply API consumers with a scalable and secure web service based on demand we see from Phase One. Phase Three will give developers beta access to a playground server where they can try the service and try integrating the power of Csign into their own projects.
The Csign API will eventually be a paid service but pricing and availability will depend heavily on developer reaction to our beta API. We welcome input as we build so we can provide a truly valuable service for the Cardano community and beyond.