While you run P2P practical exams you might be spinning up regtest nodes (working simplified Python code) that connect with your full node (working the complete C++ code) to check P2P performance.

As John Newbery outlines here:

A node is the bitcoind occasion. That is the factor whose habits
is being examined. Every bitcoind node is managed by a Python TestNode
object which is used to begin/cease the node, handle the node’s knowledge
listing, learn state in regards to the node (eg course of standing, log file),
and work together with the node over completely different interfaces.

One of many interfaces that we will use to work together with the node is the
P2P interface. Every connection to a node utilizing this interface is
managed by a Python P2PInterface or derived object (which is owned by
the TestNode object). We are able to open zero, one or many P2P connections to
every bitcoind node. The node sees these connections as friends.

For historic causes, the phrase mininode has been used to check with
these P2P interface objects that we use to connect with the bitcoind
node (the code was initially taken from the ‘mini-node’ department of
https://github.com/jgarzik/pynode/tree/mini-node).

Nonetheless, this PR 19760 (merged in August 2020) has eliminated all references to mininode and so no code or present docs within the Bitcoin Core repo at the moment check with mininode. Clearly earlier PRs and outdated documentation exterior the repo will nonetheless check with mininode.

Source link

LEAVE A REPLY

Please enter your comment!
Please enter your name here