Polysign

'- Polysign enables anyone to create and collect esignature against documents without a vendor agreement.

• Each packet of documents for esignature is made accessible at an IPFS url.
• When the esignature is completed, an NFT is generated that links both the signer's signature and the documents being agreed on.
• Hosted documents and the request are immutable.
• Smart contract deployed on Polygon which marks the progress/fulfillment of the esignature request. The contract can only be marked completed by the designated signer address at time of final signature.
• View history of requests and completed esignatures using the covalent chain history API directly from the app.
• An individual in the context of the Polysign application is the pairing of a canvas (handwritten) signature and wallet signature/address.

View the full detail here: https://github.com/cbonoz/road22. Starts with a react template for the app with routes for creating the request, esigning, and viewing history for polygon addresses. Sponsors each play a key piece in fulfilling the signature requests. - Covalent: Enables in-app history queries of past esignature requests and fulfillment for a given polygon address.

• NFTPort: Generation of the esignature record / proof. Attaches the final esignature/agreement to an NFT and saves a link to it in the smart contract.

• Moralis: Serves as main backend for the app - uses IPFS to enable support/hosting of the document packets for each request.

• Polygon: In-app deployment of the request smart contract and marked completed upon completion/fulfillment of the each request signer's signature.

• Sequence: Wallet for facilitating polygon and submitting final sign request. Deployment can toggle between sequence wallet or metamask.