Open maryjaf opened 2 months ago
Implementation: After a transaction is detected by the cron job, an additional check is triggered 2 seconds later. This second check searches for any similar transactions that match specific criteria: the same source address, destination address, amount, and (if provided) memo, with a timestamp within 1 minute of the initial transaction. If such a matching transaction is found, a new donation is created.
cc: @maryjaf
I think this implementation makes some problem consider this scenario:
@Meriem-BM
- in this case I see two record in donation table for maryam user and my donation in firefox is still shown pending
Two donations are recorded in donation tabel but the user for both of them are shown maryam, but my donation on firefox was with not signed user
Got it, this happened because of using same wallet.
Got it, this happened because of using same wallet.
So another condition should be added to prevent this behavior ?
still have some edge cases that needs to find a way - 2 donations with same QR we can add them both, still needs to figure out solution
@Meriem-BM still needs to do research on this
The users be able to donate to a project twice with one QR code In this situation one of these donations is shown in project donations and user donations list
for example these two transaction was made by a QR code and the one of them is shown in project donation table
Transaction ad504d24e7b83b0e22f152b4643361756dcbbee1c4aac0371137b806bf6e6c46
Transaction d02a1bf00da3ffcc344d4700ff2dfadfe3d28bd981a8765565a8fcf27babd305 (it is shown in list of project donation)
cc: @MoeNick