Getting Started

Smart Contract

1

Creation

A defined framework is implemented in the current version.

Establish the framework for how reports will be submitted and managed. For instance, define submission criteria and develop rules that automatically check the completeness of tasks/ reports.

2

Attestation

Create a system for reviewers to provide feedback on submitted reports. This could include options for comments, approvals, or requests for revisions.

3

Trigger

Specify actions that should occur upon successful submission and validation of a report

Data Storage

In our protocol, the reports are stored using Pinata, a service that provides reliable IPFS storage. This approach not only guarantees that reports are immutable but also offers the ability to track and retrieve them with ease—even without using our web application. Importantly, the data belongs solely to the user, ensuring they retain full ownership.

---

Use Case

Snapture introduces a system where client must deposit a specified amount as collateral before engaging contractors. Upon task completion, contractors submit their claims which are recorded using smart contract.

We use Sign Protocol to establish our attestation schema and the hook feature to trigger our custom smart contract.

The hook contract is implemented to require a predefined threshold of validator signatures. Once the required number of approvals is reached, the contract executes the payout in USDC to the contractor. This mitigates the risk of disputes and advocates trust amongst players since multiple validators contribute to the approval process.

To enhance ownership, an NFT will be minted for each completed task. It maps the contractor's identity to the specific task performed, encapsulating essential metadata such as completion timestamps and detailed task descriptions. The NFT will also be a verifiable proof of work for the tender submission.

Snapture Web App