Support voucher execution about bug-less

[claudioantonio]

@guidanoli here come some suggestions to discuss.

Suggested workflow for hackers:

• Given that, when a hacker submits a successful exploit, the dapp backend automatically emits a voucher in their favor (They don't have to request). I added a notiication in the header that appears when the connected user (hacker or sponsor) has vouchers. When they click in the notification, they go to a page where all vouchers are presented. If the voucher already has a proof, the execute button is enabled. If there is not proof yet, there will be a message "Wait until the proof is available"

For Sponsors:

• Maybe we could have the same approach of automatic voucher emitting. Currently the client polls the dapp backend frequently to get latest bounties and the backend updates bounties if they are expired. In the case of finding an expired bounty, the backend could emit vouchers for the sponsor.
• With that, the workflow in the client would be same for sponsors and hackers (as described above) and we would eliminate the need for the sponsors to request for refunding. 😉

What do you think about it?

[guidanoli]

@claudioantonio That's an amazing insight, and it does make a lot of sense to streamline both withdrawal actions in the same place, regardless of role. With this notification feature, the user wouldn't have to look for withdrawals in each bounty they have participated. Instead, they would all be aggregated in one place for easy access. Way to go!

[guidanoli]

I'm eager to know your thoughts on this, @edubart, @fmoura, and @gligneul.

[fmoura]

Sorry for the late reply I would like to complete a simple Voucher Execution schema firts, but I also agree that a streamlined approach is better for ux and costs

…

On Wed, Feb 14, 2024 at 4:30 PM Guilherme Dantas ***@***.***> wrote: I'm eager to know your thoughts on this, @edubart <https://github.com/edubart>, @fmoura <https://github.com/fmoura>, and @gligneul <https://github.com/gligneul>. — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA3ANZPOGMAJKK3TAQ52ZLYTUGE3AVCNFSM6AAAAAA6R753WGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBUGQ2TSOJXHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[guidanoli]

This has been addressed already by #14.