This PR adds BIP324-specific labels to the peer details widget:
- a transport version
- a session id
See: https://github.com/bitcoin/bitcoin/pull/28331#issuecomment-1693239025.
This PR adds BIP324-specific labels to the peer details widget:
See: https://github.com/bitcoin/bitcoin/pull/28331#issuecomment-1693239025.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
See the guideline for information on the review process.
Type | Reviewers |
---|---|
ACK | achow101, theStack, RandyMcMillan, MarnixCroes |
Concept ACK | jarolrod, jonatack |
Stale ACK | Sjors |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
No conflicts as of last run.
I don’t think we should add a lock icon or something like that…
A screenshot has been added to the PR description.
Concept ACK.
Am updating -netinfo
as well (adding columns to the peer details, and adding P2P_V2
to the upcoming peer services column).
Concept ACK
Will review this PR right after https://github.com/bitcoin/bitcoin/pull/28331.
But can you add the session id?
Done.
519- ui->peerConnectionTypeLabel->setToolTip(ui->peerConnectionTypeLabel->toolTip().arg(list));
520+ const QString connection_types_list{"<ul><li>" + Join(CONNECTION_TYPE_DOC, QString("</li><li>")) + "</li></ul>"};
521+ ui->peerConnectionTypeLabel->setToolTip(ui->peerConnectionTypeLabel->toolTip().arg(connection_types_list));
522+ const std::vector<QString> TRANSPORT_TYPE_DOC{
523+ //: Explanatory text for "detecting" transport type.
524+ tr("detecting: incoming connection; peer could be v1 or v2"),
In the latest version of https://github.com/bitcoin/bitcoin/pull/28331 (since the change in https://github.com/bitcoin/bitcoin/pull/28331#issuecomment-1721167073 was applied), the “detecting” state can appear in both directions, i.e. the description should be adapted accordingly:
0 tr("detecting: peer could be v1 or v2"),
Tested this PR with both in- and outbound connections, and it seems to work just fine :ok_hand:
It might be worthwhile to show the transport type also as extra column directly in the table rather than only in the details (useful for e.g. quickly identifying all v2 peers by sorting by type), but that’s not urgent and can probably wait until the first release that has set -v2transport
to default-on.
It might be worthwhile to show the transport type also as extra column directly in the table rather than only in the details (useful for e.g. quickly identifying all v2 peers by sorting by type), but that’s not urgent and can probably wait until the first release that has set
-v2transport
to default-on.
Considering the total number of columns, I believe we should provide users with the ability to hide selected ones.
ACK 805273d043055d8c93fa7571fd4845a4b026f803
Tested on macOS Ventura 13.6 and lightly reviewed the code.
Tested ACK 805273d043055d8c93fa7571fd4845a4b026f803
Ran this branch on OpenBSD 7.3 with Xfce Window Manager, using Qt version 5.15.8. Checked that the new BIP324 labels are correct with two v2 connections (1 inbound + 1 outbound). :ok:
maybe only display Session id
property when Transport is v2?
nit, everywhere in the BIP they use Session ID
(capital ID), maybe use the same