Hello Zama Team,
I have councerns about the winners of the developer program Season 3 that it’s winner were recently announced. Bounty track. The task was to turn zama registry into a raw product
This is a genuine concern with no purpose of talking down on anyone’s input but for to show some disparity between the winners and my submission
The first winner - ct-7984-chriswilder(.)netlify(.)app/
This doesn’t have error recovery method for missing finalizing unwrap for custom pair added ( it has for registry pair but not custom pair)
The 2nd position
confidential-wrapper-registry-weld(.)vercel(.)app/
This also does not have error recovery at all for any missing approval for finalizing unwrap
Same for the third
blackout-phi(.)vercel(.)app/
The problem here is when a unwrap request is signed by user, and then before finalizing, say a problem occur ( maybe mistakenly cancel finalizing approval signature ) the token get stuck in the contract forever with no recovery method to recover them, while the initial amount has already been burnt onchain as per zama tech)
Again this isn’t to talk down on anyone submission but comparing with what i have here, it fall short of the requirements for the bounty track which says
*does your app handles error gracefully?*
Which was well stated on the judging criteria for on the zama blog fpr Developer program s3 bounty track
Pls look into this
Thank you
Here is my submission for comparison:
Confidential-asset-hub(.)vercel(.)app
github(.)com/Oluwatimothy/confidential-asset-hub