Topic: How do I use ZeroMQ to monitor addresses? (Read 733 times)
thanks
is the rawtx validated or does it requires tx validation?
Before Core gives the user access to anything, it will always validate the data. The transaction is already validated when it tells you about it.
is the rawtx validated or does it requires tx validation?
I've worked out the following scheme:
1. Listen for rawtx topic using ZeroMQ in order to receive raw transaction body.
2. Parse binary body and extract addresses from output scripts.
3. Compare addresses with local database in order to find matches.
Of course, list of pending transactions could be loaded into memory entirely in order to prevent too much requests to the database. Each address takes 20 bytes of memory, so you could store ~50K of them in 1MB of RAM.
Is this an optimal way to monitor specific addresses?
1. Listen for rawtx topic using ZeroMQ in order to receive raw transaction body.
2. Parse binary body and extract addresses from output scripts.
3. Compare addresses with local database in order to find matches.
Of course, list of pending transactions could be loaded into memory entirely in order to prevent too much requests to the database. Each address takes 20 bytes of memory, so you could store ~50K of them in 1MB of RAM.
Is this an optimal way to monitor specific addresses?
Hello!
We're developing a Bitcoin service and we need to monitor local addresses for new transactions and transaction updates (confirmations).
ZeroMQ built into bitcoind looks like a pretty cool feature, however, as I see, it only receives IDs of the new transactions.
Is it possible to map transaction ID to Bitcoin address without issuing an RPC call to the node?
We don't want to flood the server with RPC requests, because new transactions are appearing very quickly.
Any suggestions are highly appreciated!
Thank you!
We're developing a Bitcoin service and we need to monitor local addresses for new transactions and transaction updates (confirmations).
ZeroMQ built into bitcoind looks like a pretty cool feature, however, as I see, it only receives IDs of the new transactions.
Is it possible to map transaction ID to Bitcoin address without issuing an RPC call to the node?
We don't want to flood the server with RPC requests, because new transactions are appearing very quickly.
Any suggestions are highly appreciated!
Thank you!
Jump to: