kumavis/eth-tx-finder

Binary search blockchain for tx history over rpc

Ethereum RPC backed sender->txs lookup

Status: Experimental

note: search is in series as parallel is causing problems...

live internet statistics

be warned, this is really heavy weight on network I/O

2 txs in 1.6 mil blocks

searching for all txs for 0x6aaa5f611b08f8ae98d377ba3f09b1717822b322
8.746s total

50 txs in 1.6 mil blocks

searching for all txs for 0x7773dc77b66d96ee4c2f72cdc402349366c7b11d
2m55s total

initial statistics

txCount	blockchain length	requests incl cache	network requests
1	2 million	24	23
1	2 million	24	23
1	2 million	24	23
2	2 million	50	42
2	2 million	48	43
2	2 million	48	43
10	2 million	231	182
10	2 million	221	175
10	2 million	228	182
20	2 million	421	335
20	2 million	431	327
20	2 million	441	337
50	2 million	1034	780
50	2 million	1034	768
50	2 million	1035	772
100	2 million	1967	1450
100	2 million	2025	1418
100	2 million	1996	1440

eth-tx-finder's Issues

search in parallel not series

is causing some bug... searchRange results are different

Callback was already called.

hihi
i got Callback was already called
how do i fix it thanks

cheer@cheer-H97-D3H:~/mtest/eth-tx-finder-master$ node example.js 
/home/cheer/mtest/eth-tx-finder-master/node_modules/async/dist/async.js:985
        if (fn === null) throw new Error("Callback was already called.");
                         ^

Error: Callback was already called.
    at /home/cheer/mtest/eth-tx-finder-master/node_modules/async/dist/async.js:985:32
    at /home/cheer/mtest/eth-tx-finder-master/node_modules/async/dist/async.js:3850:13
    at apply (/home/cheer/mtest/eth-tx-finder-master/node_modules/async/dist/async.js:41:25)
    at /home/cheer/mtest/eth-tx-finder-master/node_modules/async/dist/async.js:76:12
    at /home/cheer/mtest/eth-tx-finder-master/node_modules/eth-store/query.js:143:21
    at Request._callback (/home/cheer/mtest/eth-tx-finder-master/example.js:34:16)
    at Request.self.callback (/home/cheer/mtest/eth-tx-finder-master/node_modules/request/request.js:186:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (/home/cheer/mtest/eth-tx-finder-master/node_modules/request/request.js:1060:10)

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.