Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Public node: the advanced conditions for transactions do not work at all. #6445

Closed
joeshae opened this issue Sep 2, 2017 · 8 comments
Closed
Assignees
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. P5-sometimesoon 🌲 Issue is worth doing soon.

Comments

@joeshae
Copy link

joeshae commented Sep 2, 2017

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.

@joeshae joeshae changed the title transactions are pending forever in web wallet transactions are delayed seriously before successful Sep 2, 2017
@joeshae joeshae changed the title transactions are delayed seriously before successful resolved Sep 2, 2017
@joeshae joeshae closed this as completed Sep 2, 2017
@joeshae joeshae changed the title resolved The advanced conditions for transaction does not work at all. Sep 2, 2017
@joeshae joeshae changed the title The advanced conditions for transaction does not work at all. In web wallet, the advanced conditions for transactions do not work at all. Sep 2, 2017
@joeshae joeshae reopened this Sep 2, 2017
@5chdn 5chdn added the Z1-question 🙋‍♀️ Issue is a question. Closer should answer. label Sep 4, 2017
@5chdn
Copy link
Contributor

5chdn commented Sep 4, 2017

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?

@joeshae
Copy link
Author

joeshae commented Sep 5, 2017

Have you tried turning it off and on again?
Yes.

Are you fully synchronized?
Yes.

Which version of Parity are you running?
https://wallet.parity.io/

Which operating system are you using?
No matter. Windows, MacOS, Linux have the same issue.

How did you install Parity?
Official web version ( https://wallet.parity.io/ ), no need to install.

Is your time synchronized?
Yes.

@5chdn 5chdn added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M7-ui Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. labels Sep 6, 2017
@5chdn
Copy link
Contributor

5chdn commented Sep 6, 2017

The public web wallet is not officially released yet.

@maciejhirsz can you look into this?

@5chdn 5chdn removed the Z1-question 🙋‍♀️ Issue is a question. Closer should answer. label Sep 6, 2017
@5chdn 5chdn changed the title In web wallet, the advanced conditions for transactions do not work at all. Public node: the advanced conditions for transactions do not work at all. Sep 6, 2017
@maciejhirsz
Copy link
Contributor

Will look into it, but I think best we can do there is disable the feature on the public wallet.

@maciejhirsz maciejhirsz self-assigned this Sep 6, 2017
@5chdn 5chdn added P5-sometimesoon 🌲 Issue is worth doing soon. and removed Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. labels Sep 6, 2017
@joeshae
Copy link
Author

joeshae commented Sep 25, 2017

Hi, has this issue been resolved?

@maciejhirsz
Copy link
Contributor

@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.

@5chdn
Copy link
Contributor

5chdn commented Sep 27, 2017

Is this fixed via #6588?

@maciejhirsz
Copy link
Contributor

Yap! Was meant to close this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. P5-sometimesoon 🌲 Issue is worth doing soon.
Projects
None yet
Development

No branches or pull requests

3 participants