Hi Ali,
I've run into this multiple times myself. I've opened a draft PR [0]
adding a rawmempooltx publisher.
You're right. In zmq/zmqnotificationinterface.cpp the
CZMQNotificationInterface is notified about TransactionAddedToMempool.
Currently, this calls NotifyTransaction() (the publisher with
Wasn't this already not a problem because you can check if it was confirmed?
The transaction is not finalised in the mempool it is just speculation of a
transaction, so it makes sense to emit when the transaction is confirmed. Just
already check..
> It appears that the ZeroMQ topic I'm listeni
Theoretically that would be the desired outcome for me but this change is going
to be implemented as part of a casino which must display the status of new
deposits that are made, even when they are unconfirmed to now. Hence why I need
to receive the unconfirmed messages.
- Ali Sherief
On Mon,
Hi everyone,
Fee-bumping is paramount to the security of many protocols building on Bitcoin,
as they require the
confirmation of a transaction (which might be presigned) before the expiration
of a timelock at any
point after the establishment of the contract.
The part of Revault using presigned
