New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Web Stacks Wallet] Contract post conditions replaced by standard conditions #1013
Comments
It's actually worse than this - the current post conditions logic assumed that post conditions could only be applied to the tx-sender. Jude recently updated some wording in this SIP that clears this up. So, the Stacks Wallet actually overwrites every post condition with the current account's STX address. Related: #969 |
Can fixing this get a higher priority. This is making it impossible to test ft-transfers using the explorer sandbox or any other app. |
I agree that it's important, and we have this bucketed in our highest-priority milestone. But, for testing purposes, you don't have to add post conditions for addresses other than the sender. You should in production, but to get the tx to go through, you only need to add them for the sender. |
Removing the contract condition does not help: https://explorer.stacks.co/txid/0xa14334f26ff547516135b5510809dee33db5797c836f8954c0ed45c2fb51f87b?chain=testnet On https://speed-spend.org/poxlite it is not possible to redeem stingers because the post condition for the sender of STX, i.e. the smart contract can't be specified in the stacks web wallet. |
What I'm suggesting is that it would be better for that tx to just have no post conditions at all. Because the |
Can you be more clear? |
Wait. I will try that. Thanks. |
Fixed and released in version 2.3.0 👍 |
A tx with contract post condition and standard post conditions are shown in the same way. See screenshot:
The contract post condition should mention the contract
The text was updated successfully, but these errors were encountered: