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
{{ message }}
This repository was archived by the owner on May 20, 2026. It is now read-only.
there seems to be some incoherency in the docs around withdrawals, first it is stated that:
If msg is specified, the contract will use ft_transfer to process the withdrawal
If msg is not specified, or "msg": null in json, the withdrawal will be done using an ft_transfer_call function call
a couple of paragraphs later this line comes in:
However, this is not always the case. Due to complexities related to the asynchronous and sharded nature of the NEAR blockchain, refunds will only be processed when msg is unspecified or has a value null, i.e., when ft_transfer is used for processing the withdrawal.
https://docs.near-intents.org/near-intents/market-makers/verifier/deposits-and-withdrawals/withdrawals#refunds-on-failed-withdrawals-warning
there seems to be some incoherency in the docs around withdrawals, first it is stated that:
a couple of paragraphs later this line comes in:
normally
ft_transfer_callrequires a msg.