connection__types_8h_source.html

 // Copyright (c) 2022 The Bitcoin Core developers

 // Distributed under the MIT software license, see the accompanying

 // file COPYING or http://www.opensource.org/licenses/mit-license.php.


 #ifndef BITCOIN_NODE_CONNECTION_TYPES_H

 #define BITCOIN_NODE_CONNECTION_TYPES_H


 #include <string>


 enum class ConnectionType {

     INBOUND,


     OUTBOUND_FULL_RELAY,


     MANUAL,


     FEELER,


     BLOCK_RELAY,


     ADDR_FETCH,

 };


 std::string ConnectionTypeAsString(ConnectionType conn_type);


 #endif // BITCOIN_NODE_CONNECTION_TYPES_H

ConnectionType
ConnectionType
Different types of connections to a peer.
Definition: connection_types.h:17

ConnectionType::BLOCK_RELAY
@ BLOCK_RELAY
We use block-relay-only connections to help prevent against partition attacks.

ConnectionType::MANUAL
@ MANUAL
We open manual connections to addresses that users explicitly requested via the addnode RPC or the -a...

ConnectionType::OUTBOUND_FULL_RELAY
@ OUTBOUND_FULL_RELAY
These are the default connections that we use to connect with the network.

ConnectionType::FEELER
@ FEELER
Feeler connections are short-lived connections made to check that a node is alive.

ConnectionType::INBOUND
@ INBOUND
Inbound connections are those initiated by a peer.

ConnectionType::ADDR_FETCH
@ ADDR_FETCH
AddrFetch connections are short lived connections used to solicit addresses from peers.

ConnectionTypeAsString
std::string ConnectionTypeAsString(ConnectionType conn_type)
Convert ConnectionType enum to a string value.
Definition: connection_types.cpp:8