-
Notifications
You must be signed in to change notification settings - Fork 697
Transaction Receipts do not include logsBloom #440
Comments
@elenadimitrova per the JSON RPC wiki, the That said, I'm still uncertain as to how much we should treat that wiki page as a spec. Further, I need to balance the goal of adhering to the spec (weakly-defined as it is) so that people write dapps which are portable across ethereum clients, against supplying people what they need in order to test their Dapps adequately for their environments. As a rule, we usually do our best to follow the RPC wiki page unless there's disagreement amongst major client implementations. In that case, we tend to take the intersection of functionality between Parity and geth rather than the union. To help me make the decision:
|
It is breaking for As for
This points to omission in the JSON RPC wiki but the yellow paper clearly defines it. |
That's good enough for me, then - we'll go ahead and add it. |
From comparison of both objects you submitted, it seems we also don't respond with the |
As per the JSON RPC this is actually correct as it states the transaction receipt returns either the To enable that in |
@elenadimitrova what version of geth was that output from above? It seems strange that it also has the |
I'm on |
Fixed in |
@elenadimitrova I've actually just pushed out a beta release of |
I've installed Ganache v1.2.0-beta.0 and I am still getting this problem when using Ethers.js |
I caught up with @naddison36 offline, but for those reading along, this is in the |
Thanks, @benjamincburns. I can confirm that the new version fixed this problem |
The transaction receipts are missing the
logsBloom
property. Below are outputs from a non-specific transaction usingtestrpc
andparity
where the property is available.Test with
testrpc
Test against Parity:
The property is otherwise available on the
block
usingtestrpc
.According to the yellow paper, both the
block
and thetransaction
receipt definelogsBloom
in their properties.The text was updated successfully, but these errors were encountered: