From 84731ab4a958dbc024a0c2319a3aaaae61d522b5 Mon Sep 17 00:00:00 2001 From: "drusselloctal@gmail.com" Date: Thu, 30 Oct 2014 19:14:50 -0700 Subject: [PATCH] Made changes to ch06.asciidoc --- ch06.asciidoc | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/ch06.asciidoc b/ch06.asciidoc index 91a4f78a..3f81dd3a 100644 --- a/ch06.asciidoc +++ b/ch06.asciidoc @@ -268,12 +268,23 @@ Alert messages are a seldom used function, which is nevertheless implemented in Alert messages are propagated by the +alert+ message. The alert message contains several fields, including: -* ID - An alert identified so that duplicate alerts can be detected -* Expiration - A time after which the alert expires -* RelayUntil - A time after which the alert should not be relayed -* MinVer, MaxVer - The range of bitcoin protocol versions that this alert applies to -* subVer - The client software version that this alert applies to -* Priority - An alert priority level, currently unused +ID:: +An alert identified so that duplicate alerts can be detected + +Expiration:: +A time after which the alert expires + +RelayUntil:: +A time after which the alert should not be relayed + +MinVer, MaxVer:: +The range of bitcoin protocol versions that this alert applies to + +subVer:: +The client software version that this alert applies to + +Priority:: +An alert priority level, currently unused Alerts are cryptographically signed by a public key. The corresponding private key is held by a few selected members of the core development team. The digital signature ensures that fake alerts will not be propagated on the network.