Overview

The goal of this bounty is to explore and implement how the specific capabilities of Zama's fhEVM can enhance and improve the functionality of the ERC-3643 security token standard for security tokens. Participants will leverage the encrypted types and FHE operations supported by the fhEVM to create a confidential variant of this security token standard.

What we expect

First, the bounty participants should get familiar with the ERC-3643 standard as well as its current official implementation. Notice that this standard also relies on a decentralized identity standard such as ERC 735 via the OnchainID implementation, which could also be adapted to the fhEVM by adding confidentiality.

Judging criteria

• Smart Contract: The smart contracts need to be written in Solidity running on the fhEVM. The code should be cleanly commented, with adherence (as close as possible) to the standard is important.
• Testing: Testing smart contracts using hardhat is also highly recommended.
• Deployment: The smart contract should be compatible with Zama's fhEVM devnet.
• Use of fhEVM: The contract should employ hidden information, showcasing the capabilities of the fhEVM. Care should be taken by the bounty hunter to decide which state variables to encrypt and which should stay unencrypted. Suggestions (non-exhaustive) of state variables to encrypt: transfer amounts, allowances, number of frozen tokens, identities such as country codes, etc.
• Bonus points: Implement an additional contract to showcase a concrete scenario for security settlements, leveraging the confidential security token. For instance, DVP (Delivery Vs Payment) or DVD (Delivery Vs Delivery), and so on. (Here are some examples from an old hackathon on DVP using a different security token standard for inspiration)

Reward

🥇Best submission: up to €5,000.

To be considered best submission, a solution must be efficient, effective and demonstrate a deep understanding of the core problem. Alongside the technical correctness, it should also be submitted with a clean code, clear explanations and a complete documentation.

🥈Second-best submission: up to €3,000.

For a solution to be considered the second best submission, it should be both efficient and effective. The code should be neat and readable, while its documentation might not be as exhaustive as the best submission, it should cover the key aspects of the solution.

🥉Third-best submission: up to €2,000.

The third best submission is one that presents a solution that effectively tackles the challenge at hand, even if it may have certain areas of improvement in terms of efficiency or depth of understanding. Documentation should be present, covering the essential components of the solution.

Reward amounts are decided based on code quality, model accuracy scores and speed performance on a m6i.metal AWS server. When multiple solutions of comparable scope are submitted they are compared based on the accuracy metrics and computation times.

Related links and references

• Confidential variant of ERC 20 for fhEVM specific sources.
• Compliant ERC20 with confidential decentralized identities and its corresponding blog post.
• Zama's fhEVM documentation

👉 Register

Step 1: Registration

Click here to register for the fhEVM Bounty. Fill out the registration form with your information. Once you fill out the form, you will receive a confirmation email with a link to the submission portal for when you are ready to submit your code.

Step 2: Work on the Challenge

Read through the Bounty details and requirements carefully. Use the provided resources and create your own GitHub repository to store your code.
If you have any questions during your work, feel free to comment directly in the Bounty issue and our team will be happy to assist you.

Step 3: Submission

Once you have completed your work, upload your completed work to the submission portal using the link provided in the confirmation email.

We wish you the best of luck with the challenge!

✅ Support

• Comment on this issue with any questions regarding this bounty.
• Email for private questions: [email protected]
• Join the Zama community channels here.