Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

Transaction Filters: By inputData #24

Open
mbaxter opened this issue Jun 20, 2018 · 2 comments
Open

Transaction Filters: By inputData #24

mbaxter opened this issue Jun 20, 2018 · 2 comments
Labels
Type: Feature New feature or request

Comments

@mbaxter
Copy link
Contributor

mbaxter commented Jun 20, 2018

It may be useful to filter transactions by inputData content. This would allow users to target transactions that invoke arbitrary contract methods. The filter might look something like: transactions(filter: { inputStartsWith: "0x12345678" }).

@akhila-raju akhila-raju added the Type: Feature New feature or request label Jun 20, 2018
@raulk
Copy link
Contributor

raulk commented Jun 20, 2018

Another possibility is for ethql to calculate the hash to match against from a user-provided Solidity function signature, e.g.:

transactions(filter: { solidityFunction: "transfer(address,uint256,bytes)" }) {
}

WDYT?

@mbaxter
Copy link
Contributor Author

mbaxter commented Jun 20, 2018

Nice - I like that idea 👍

@raulk raulk added this to To do in Ongoing planning via automation Jun 22, 2018
@raulk raulk changed the title Feature Request: Filter transactions by inputData Transaction Filters: By inputData Jun 22, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Feature New feature or request
Projects
Development

No branches or pull requests

3 participants