Closed karelbilek closed 7 years ago
(This is currently blocking mytrezor integration, since we use these notifications.)
as I wrote to slack - my bet is it's some combination of multibyte prefixes and zmq (that are used by notifications)
Looking at this now.
For what it's worth, I just tried the same thing with waterhole.io and their zcash bitcore (and livenet zcash), and it seems there is the same issue there.
So it is 90% with the code and not with the deployment.
It's fixed here - I tested it on my private server, it fixes the issue and notifications arrive
Bitcore at https://explorer.testnet.z.cash doesn't send any notifications on
bitcoind/addresstxid
.I am not sure if it's an issue with the code itself or with your deployment. (I am leaving the issue here, since it's the only insight/bitcore repo, that has issue tracking.)
A simple code, that works in bitcoin testnet and doesn't work with your server. (I wrote it for browser but it should probably work for node too.)
Bitcoin Testnet:
Use your own address, send a testnet transaction there and it works.
Zcash testnet:
Doesn't work.
Note that notifications in general work. This will alert at each block.