Question about "bitcoincore_zmq::Message::Tx"

[kkthmyh]

When I monitor new transactions, what does this u32 mean? I printed it on the console and found that it is auto-incrementing, so will it grow until u32::MAX? Then wouldn't the program panic?

 for msg in bitcoincore_zmq::subscribe_receiver(&["tcp://127.0.0.1:28332"]).unwrap() {
        match msg {
            Ok(msg) => {
                match msg {
                    bitcoincore_zmq::Message::Tx(tx, seq) => {
                        println!("{:?}", seq);
                        println!("{:?}", tx.txid());
                    }
                    _ => {}
                }
            }
            Err(err) => println!("Error receiving message: {err}"),
        }
    }

[antonilol]

I wrote some documentation on that, but it is on the sequence method of Message (see docs here).

This number is in Bitcoin Core for each zmq publisher, it is defined as uint32_t, and incremented every time a zmq message is sent, without additional special logic, so after u32::MAX it rolls over back to 0.

This number can be used to track if any messages are lost. Lets say you have to restart your program (but not bitcoin core), if the program records the last seen sequence number before restarting it can compare it to the first seen one after booting up, and know if and how many messages were missed.

If you need more info on Bitcoin Core zmq specifics like this, I linked some documentation in the readme, "Useful resources".

[kkthmyh]

I wrote some documentation on that, but it is on the sequence method of Message (see docs here).

This number is in Bitcoin Core for each zmq publisher, it is defined as uint32_t, and incremented every time a zmq message is sent, without additional special logic, so after u32::MAX it rolls over back to 0.

This number can be used to track if any messages are lost. Lets say you have to restart your program (but not bitcoin core), if the program records the last seen sequence number before restarting it can compare it to the first seen one after booting up, and know if and how many messages were missed.

If you need more info on Bitcoin Core zmq specifics like this, I linked some documentation in the readme, "Useful resources".

Thank you very much, I'll read the documentation.