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
With the current signature of ft_on_transfer, every time a contract implementation of this method returns a PromiseOrValue::Promise, the latter call on ft_resolve_transfer refunds a user with the total amount that was sent to the given contract. This behavior is implicit and misleading, and it would be more explicit to enforce ft_on_transfer to return a type like U128. Moreover, the current documentation does not address this scenario.
The text was updated successfully, but these errors were encountered:
With the current signature of
ft_on_transfer
, every time a contract implementation of this method returns aPromiseOrValue::Promise
, the latter call onft_resolve_transfer
refunds a user with the total amount that was sent to the given contract. This behavior is implicit and misleading, and it would be more explicit to enforceft_on_transfer
to return a type likeU128
. Moreover, the current documentation does not address this scenario.The text was updated successfully, but these errors were encountered: