You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before launching, we need to integrate on cli and frontend the coins refund implementing the withdraw function from the SC.
This should be pretty straight forward for the delete, but what about the edit ? technically since users are delete from storage, they should get refunded or should they request to be refunded ? How can we optimize this in the edit flow so users do not pay for what is already payed for ?
The text was updated successfully, but these errors were encountered:
All of this could either be automated in the SC (the smart contract itself refunds the caller with any excess coins when updating or deleting) or in the frontend (after an update/delete operation, the front-end looks into the balance of the SC and proposes withdrawing if anything is left there) but that would be a bit heavier for the user
All of this could either be automated in the SC (the smart contract itself refunds the caller with any excess coins when updating or deleting) or in the frontend (after an update/delete operation, the front-end looks into the balance of the SC and proposes withdrawing if anything is left there) but that would be a bit heavier for the user
cc @SlnPons indeed solution two would add an extra operation to sign for the user (in both cli and frontend)
Thanks guys! So I would go for the option 1: automated directly in the SC. I couldn't think of any use cases where this solution wouldn't fit. If you see any please share :)
The only thing that I would really like to do is: to get the info about how much coin will be refunded (if any). Is it possible?
Before launching, we need to integrate on cli and frontend the coins refund implementing the withdraw function from the SC.
This should be pretty straight forward for the delete, but what about the edit ? technically since users are delete from storage, they should get refunded or should they request to be refunded ? How can we optimize this in the edit flow so users do not pay for what is already payed for ?
The text was updated successfully, but these errors were encountered: