-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
pendingTransactions subscription returns transaction hash instead of object #1144
Comments
I'm having the same issue. |
Also seeing the same. |
Having the same issue, using a parity node. |
Can we get some clarification on this? Calling getTransaction on every hash that I get from the subscription is too slow for me - I have to be getting those pretty much in real time (I have a private geth node running on version 1.8.12), so this is a big deal for me - dunno if getting the whole transaction object instead of just the hash will be as slow as calling getTransaction for each hash. Are there any alternatives currently? EDIT: I guess one way to solve this is to create a websocket server wherever the node is hosted, which listens for pending transactions and gets more information about them over IPC and emits anything of interest. |
@baiumbg This is an mistake in the documentation we only get the transaction hash from the rpc call as you can see here: https:/ethereum/go-ethereum/wiki/RPC-PUB-SUB#newpendingtransactions |
fixed in #1876 |
web3.js
version: 1.0.0-beta.24
nodejs
version: v8.4.0
Geth
Version: 1.7.0-stable
Git Commit: 6c6c7b2af3efdad4d2f64f70f3a724af434bbcd2
Architecture: amd64
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.8.3
Operating System: linux
tl;dr
subscription returns transaction hash instead of transaction receipt
Full story short
Here is my code
Here is log I am getting
Here is web3.js documentation -
http://web3js.readthedocs.io/en/1.0/web3-eth-subscribe.html#subscribe-pendingtransactions
It says
Am I getting something wrong? Is that is bug or that is intended behavior?
The text was updated successfully, but these errors were encountered: