Bitcoin Core 28.99.0
P2P Digital Currency
connection_types.cpp
Go to the documentation of this file.
1// Copyright (c) 2022 The Bitcoin Core developers
2// Distributed under the MIT software license, see the accompanying
3// file COPYING or http://www.opensource.org/licenses/mit-license.php.
4
6#include <cassert>
7
9{
10 switch (conn_type) {
12 return "inbound";
14 return "manual";
16 return "feeler";
18 return "outbound-full-relay";
20 return "block-relay-only";
22 return "addr-fetch";
23 } // no default case, so the compiler can warn about missing cases
24
25 assert(false);
26}
27
29{
30 switch (transport_type) {
32 return "detecting";
34 return "v1";
36 return "v2";
37 } // no default case, so the compiler can warn about missing cases
38
39 assert(false);
40}
std::string TransportTypeAsString(TransportProtocolType transport_type)
Convert TransportProtocolType enum to a string value.
std::string ConnectionTypeAsString(ConnectionType conn_type)
Convert ConnectionType enum to a string value.
ConnectionType
Different types of connections to a peer.
@ BLOCK_RELAY
We use block-relay-only connections to help prevent against partition attacks.
@ MANUAL
We open manual connections to addresses that users explicitly requested via the addnode RPC or the -a...
@ OUTBOUND_FULL_RELAY
These are the default connections that we use to connect with the network.
@ FEELER
Feeler connections are short-lived connections made to check that a node is alive.
@ INBOUND
Inbound connections are those initiated by a peer.
@ ADDR_FETCH
AddrFetch connections are short lived connections used to solicit addresses from peers.
TransportProtocolType
Transport layer version.
@ V1
Unencrypted, plaintext protocol.
@ V2
BIP324 protocol.
@ DETECTING
Peer could be v1 or v2.
assert(!tx.IsCoinBase())