1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
Return-Path: <policeterror@dyne.org>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 460E8C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 4 Jul 2022 08:01:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 1260560A4F
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 4 Jul 2022 08:01:58 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 1260560A4F
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level:
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001]
autolearn=ham autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id E3d4m3wAvczA
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 4 Jul 2022 08:01:56 +0000 (UTC)
X-Greylist: delayed 00:08:01 by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org EE2EA60C01
Received: from mail.dyne.org (mail.dyne.org [141.95.83.167])
by smtp3.osuosl.org (Postfix) with ESMTPS id EE2EA60C01
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 4 Jul 2022 08:01:55 +0000 (UTC)
Received: from [127.0.0.1] (localhost [127.0.0.1])
(Authenticated sender: policeterror@dyne.org)
with ESMTPSA id D66CB6617F7
Message-ID: <5ccaa7d4-dc64-6bf0-c4e6-3667c986466b@dyne.org>
Date: Mon, 4 Jul 2022 09:53:48 +0200
MIME-Version: 1.0
To: bitcoin-dev@lists.linuxfoundation.org
Content-Language: en-US
From: popo <policeterror@dyne.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 04 Jul 2022 08:34:49 +0000
Subject: [bitcoin-dev] addr/getaddr behaviour
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2022 08:01:58 -0000
Is this specced anywhere? Or where can I find this in the code?
In particular I saw mentioned in the protocol docs, that nodes will
heartbeat their own external addr periodicially.
Do node repropagate these messages? If so then how do they distinguish
them from other addr messages?
Where can I find the places in the code where addr messages are sent and
received?
Thanks
|
