You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge bitcoin-core/gui#163: Peer details: replace Direction with Connection Type
06ba9b3 rpc: move getpeerinfo connection_type help to correct place (Jon Atack)
c95fe6e gui: improve connection type tooltip (Hennadii Stepanov)
2c19ba2 gui: replace Direction with Connection Type in peer details (Jon Atack)
7e2beab gui: create GUIUtil::ConnectionTypeToQString utility function (Jon Atack)
Pull request description:

Closesdashpay#159.
ACKs for top commit:
hebasto:
re-ACK 06ba9b3, the tooltip content is organized as unordered list.
jarolrod:
re-ACK 06ba9b3
Tree-SHA512: 24f46494ceb42ed308e4a4f2a543dbc4f4e6409a6f738c145a9f16e175bf69d411cbc944a4fd969f1829d57644dfbc194182fa8d4e9e6bce82acbeca8c673748
<string>The type of peer connection:<ul><li>Inbound: initiated by peer</li><li>Outbound Full Relay: default</li><li>Outbound Block Relay: does not relay transactions or addresses</li><li>Outbound Manual: added using RPC %1 or %2/%3 configuration options</li><li>Outbound Feeler: short-lived, for testing addresses</li><li>Outbound Address Fetch: short-lived, for soliciting addresses</li></ul></string>
"When a message type is not listed in this json object, the bytes received are 0.\n"
166
163
"Only known message types can appear as keys in the object and all bytes received of unknown message types are listed under '"+NET_MESSAGE_COMMAND_OTHER+"'."}
0 commit comments