@vimwitch is this issue duplicated from the V2 epic?

@vimwitch @ChialiT @vivianjeng
Hi,I would like to work on this issue.
So could you tell me detail about "spending reputation"?

@vimwitch @ChialiT @vivianjeng Hi,I would like to work on this issue. So could you tell me detail about "spending reputation"?

There is an epoch tree that stores hash(epochKey, data)
and spend reputation is to make one epoch key data increases and another epoch key data decreases
e.g.
A want to spend rep 3 and give it to B
we need to compute

1. A has data[0]-data[1] >= 3 rep
2. A's epoch key is epk_A
3. epk_A has data_A in epoch tree
4. epk_B has data_B in epoch tree
5. compute the previous epoch tree root
6. update data data_A[0]-3, data_B[0]+3
7. compute the updated epoch tree root

and if epk_A and epk_B is not in epoch tree before, then insert a new leaf in the epoch tree
then the smart contract should check that epk_A and epk_B are really not in the epoch tree

@vivianjeng
OK, Thank you for your polite response !
I'll try this !

@sorag20 thank you as well~
In this case, I think you will need a verifierHelper to verify the spend rep proof
e.g. #549 (still WIP)
the verifier helper should be able to read the Unirep.sol and check if the state is correct

@vivianjeng
I understand. thank you!