-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Public node: the advanced conditions for transactions do not work at all. #6445
Comments
Have you tried turning it off and on again? Are you fully synchronized? Which version of Parity are you running? Which operating system are you using? How did you install Parity? Is your time synchronized? |
Have you tried turning it off and on again? Are you fully synchronized? Which version of Parity are you running? Which operating system are you using? How did you install Parity? Is your time synchronized? |
The public web wallet is not officially released yet. @maciejhirsz can you look into this? |
Will look into it, but I think best we can do there is disable the feature on the public wallet. |
Hi, has this issue been resolved? |
@joeshae I've looked into it more and, just as I thought before, there isn't any feasible way for this to work on public nodes. Even if we added an RPC endpoint to schedule pre-signed transactions that wouldn't cause issues with nonce. We will hide this feature in the public node UI. |
Is this fixed via #6588? |
Yap! Was meant to close this. |
In web wallet, the advanced conditions for transactions do not work at all.
No matter you set blockNumber or Timer as a condition, the transaction will be handled immediately.
The text was updated successfully, but these errors were encountered: