-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Replace minBlock
property on eth_sendTransaction
Transaction parameter in documentation with condition
property.
#5391
Comments
{
"from": "0x123...123",
"condition": { "block": 1 }
} Seems that the documentation is outdated. |
Do you happen to know if this API change will occur in geth as well? When writing a dApp, working with multiple node client types is desirable and little API differences like this can really make that difficult. |
Also, does this mean that parity isn't following semantic versioning? This is a backwards incompatible change after all. |
That feature is not available in |
Hmm, okay. I wonder how it ended up in our code (which was originally written for Geth). Searching in the go-ethereum repository doesn't return anything for |
minBlock
property on eth_sendTransaction
Transaction parameter.minBlock
property on eth_sendTransaction
Transaction parameter in documentation with condition
property.
Reopening as the wiki is still outdated. @tomusdrw I can update the wiki, what else does |
RPC wiki should be updated from auto-generated files from code, so please don't update it manually.
Update |
Thanks for the hint. |
I'm running
ethcore/parity:v1.6.5
in Docker with:When I try to call
eth_sendTransaction
via HTTP with this payload (note theminBlock
property):I get this response:
According to the documentation,
minBlock
is a valid property to have on a Transaction.This seems related to #3921, but that has been merged for several months so I would expect to see it in the release from a week ago.
The text was updated successfully, but these errors were encountered: