We’re rewarding the question askers & reputations are being recalculated! Read more.

Hot answers tagged

4

A transaction is confirmed when it is included in a block, so you will need to watch for a message that alerts your node (or whatever software you are using to watch the P2P gossip traffic) to a new block, that includes the transaction in question. It doesn't matter if a node run by a miner relays your transaction to other nodes on the network, it only ...


3

So assuming node A sends a version message to node B then the two fields have the following meaning and value: addr_recv: node A says "I believe you are reachable via this IP", hence its value is B's public IP address, the IP this message was originally sent to. addr_from: node A says "I believe my external IP is this", hence this is what A believes its ...


2

Yes Monero mining pools generally use the Stratum protocol for communication between the pool and the miners. However a modified version of the Stratum protocol is used. I've yet find proper documentation like the one you've linked, so your best bet is to look through the source code for the exact definition. Also there is a separate Stackexchange for the ...


2

The Bitcoin network operates over TCP sockets between nodes. This has several consequences. Blocking URL's or domain names is not possible. By default, Bitcoin uses port 8333. It's possible for a school/uni to block this port. For an ISP, however, this is not possible, other applications might use port 8333 as well. Also keep in mind that it is very easy to ...


2

This is gossip protocol. When you are connected to the bitcoin network, you are usually connected to some random nodes. When you want to send transaction, ultimately your goal is for the transaction to appear in a block. The blocks are created by miners who operate few network nodes. Usually you don't even know which nodes belong to such miners. Therefore ...


1

First the peer who chooses to connect shares their version. Each of the peers can only send one version message. PushNodeVersion is used to send the version message. It is called by two functions 1) PeerLogicValidation::InitializeNode when the connection is outbound. 2) ProcessMessage when a message is received. It looks like this: bool static ...


Only top voted, non community-wiki answers of a minimum length are eligible