Mix Asset Widget

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
blockchain, security

Research direction

Start by clarifying the two questions and the intended behavior of the Mix Asset Widget, since the issue names no files, tests, or entry points. Review the deposit and withdrawal steps in the issue, then define the data sources, privacy constraints, and acceptance criteria before implementation.

Written by the indexing model from the issue text.

Description

documentation

Questions Tornado.cash specific (for now)

  • How many deposits happened after this users latest deposit?
  • What is the users' IP address?

Deposit:

  1. Client generates a secret
  2. Send the commitment (hashed secret) along with ETH (of standardized amounts 0.1, 1, 10, or 100 ETH)

Withdraw:

  1. Client generates a zk proof to prove knowledge of commitment without revealing it.
  2. Client does withdrawal action w/ specified relayer (or none)
Dominant language
HTML
Stars
3
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dOrgTech/Mix

All issues in dOrgTech/Mix

Similar issues

More Blockchain issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.