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
During all type of transfer (M->S, S->M, S->S) we set a receiver as msg.sender. So you can not send funds to anyone except your own address.
Some time ago we found a vulnerability about draining CommunityPool wallets during S -> M messages and decided to remove receiver field everywhere.
But right now we understand that some customers want to transfer funds to different address (From hot/cold wallets or from MultiSig wallets).
We can add receiver fields in M -> S and S -> S transfer without providing any vulnerabilitity holes
The text was updated successfully, but these errors were encountered:
Problem:
During all type of transfer (M->S, S->M, S->S) we set a receiver as msg.sender. So you can not send funds to anyone except your own address.
Some time ago we found a vulnerability about draining CommunityPool wallets during S -> M messages and decided to remove receiver field everywhere.
But right now we understand that some customers want to transfer funds to different address (From hot/cold wallets or from MultiSig wallets).
We can add receiver fields in M -> S and S -> S transfer without providing any vulnerabilitity holes
The text was updated successfully, but these errors were encountered: