joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-28 02:06:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

P2P - Remove Alert guide info and code xref

Browse source
This commit is contained in:
thephez 2019-08-07 17:10:08 -04:00
parent c3527c18ab
commit 9cbf20780e
No known key found for this signature in database
GPG key ID: BBC8A06DBE236099
2 changed files with 0 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

23
_includes/devdoc/guide_p2p_network.md
View file

@ -636,27 +636,4 @@ information. If a peer gets a banscore above the `-banscore=<n>` threshold
| Spork | Signature<!--noref--> | **100** | Peer relayed a spork with an invalid signature (`spork` message)
{% endautocrossref %}
### Alerts
{% include helpers/subhead-links.md %}
{% autocrossref %}
*Removed in Bitcoin Core 0.13.0. Retained in Dash Core (see [PR1326](https://github.com/dashpay/dash/pull/1326)).*
In case of a bug or attack, the Dash Core developers can issue an alert via the
Dash network. Alerts will be displayed by the Dash Core UI. Users can also
check the error field of the `getinfo` RPC results to get currently active
alerts for their specific version of Dash Core or use the `-alertnotify` command
line parameter to specify a custom command to execute when an alert is received.
These messages are aggressively broadcast using the `alert` message, being sent
to each peer upon connect for the duration of the alert. These messages are
signed by a specific ECDSA private key that only a small number of developers
control.
**Resource:** More details about the structure of `alert` messages and a
complete list of message types can be found in the [P2P reference section][section P2P reference].
{% endautocrossref %}