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
Module accounts in the SDK are "blocked addresses". Any bank send TX would fail with them as token receiver.
We should ensure that contracts reject them as well.
As an example address (wasm module): tgrade1xds4f0m87ajl3a6az6s2enhxrd0wta48mx55a0
This is a placeholder issue to discuss and track. There is currently no query available, yet.
The query could go into wasmvm bank query or tgrade query. The later one is quicker to impl
The text was updated successfully, but these errors were encountered:
This is not a contract functionality issue actually. It is two parts:
x/wasm ensures any bank send to such an address with fail.
Anywhere a failing bank send could break a contract, and the address to send to can be set by a user (without signing a tx with that account... not info.sender), we should use SubMsg::reply_on_error and handle a failure gracefully
Module accounts in the SDK are "blocked addresses". Any bank send TX would fail with them as token receiver.
We should ensure that contracts reject them as well.
As an example address (wasm module):
tgrade1xds4f0m87ajl3a6az6s2enhxrd0wta48mx55a0
This is a placeholder issue to discuss and track. There is currently no query available, yet.
The query could go into wasmvm bank query or tgrade query. The later one is quicker to impl
The text was updated successfully, but these errors were encountered: