Fixpending

[debris]

fixes querying pending in most cases except:

• eth_getTransactionReceipt, cause the docs state Note That the receipt is not available for pending transactions..

[tomusdrw]

Pending transactions is used also when propagating transactions - does it mean that we don't want to propagate everything from queue?

[arkpar]

All valid transactions should be propogated

[gavofyork]

doesn't actually work according to spec - watched pending events are notified many times over.

[gavofyork]

eth_getTransactionReceipt, cause the docs state Note That the receipt is not available for pending transactions..

so that was never ratified by me. fabian added it unilaterally on July 7, 2015 in https://github.com/ethereum/wiki/wiki/JSON-RPC/_compare/f5d8c9d4c99cd3a4502eba1384e19244e1bf0e0d...88b78a4cb70ccf401c088b928365c87de45064f5 almost certainly just proscribing based on geth's behaviour. cpp-ethereum did provide pending receipts (since they're rather useful).

[debris]

yes :/ And I don't know if we should change this, cause there might be a code relying this behaviour

[gavofyork]

we'll do our own pending behaviour and issue our own JSONRPC spec until i get word from vitalik that there will be an inclusive process for managing alterations to the spec.

[gavofyork]

still broken. gets called multiple times as the client syncs new blocks.

[gavofyork]

it should be called once and only once when:

• when transaction goes from being unknown into 'pending'/'mined' (e.g. local user submitted the transaction/new block imported that contained a previously unknown transaction)

rarer events that should also be supported:

• when transaction goes from being 'mined'/'pending' to unknown (e.g. a double-spend)

also, transactionHash should be supplied.