joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-27 09:46:12 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

replace getinfo with getnetworkinfo

Browse source
This commit is contained in:
Michael Rotarius 2017-08-01 14:59:46 +02:00
parent 3e4a6b694b
commit fb1e138712
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
_includes/devdoc/guide_block_chain.md
View file

@ -362,7 +362,7 @@ provide incomplete information.
Bitcoin Core includes code that detects a hard fork by looking at block
chain proof of work. If a non-upgraded node receives block chain headers
demonstrating at least six blocks more proof of work than the best chain
it considers valid, the node reports an error in the `getinfo` RPC
it considers valid, the node reports a warning in the `getnetworkinfo` RPC
results and runs the `-alertnotify` command if set. This warns the
operator that the non-upgraded node can't switch to what is likely the
best block chain.
@ -370,12 +370,12 @@ best block chain.
Full nodes can also check block and transaction version numbers. If the
block or transaction version numbers seen in several recent blocks are
higher than the version numbers the node uses, it can assume it doesn't
use the current consensus rules. Bitcoin Core 0.10.0
reports this situation through the `getinfo` RPC and
`-alertnotify` command if set.
use the current consensus rules. Bitcoin Core reports this situation
through the `getnetworkinfo` RPC and `-alertnotify` command if set.
In either case, block and transaction data should not be relied upon if it comes from a node
that apparently isn't using the current consensus rules.
In either case, block and transaction data should not be relied upon
if it comes from a node that apparently isn't using the current
consensus rules.
SPV clients which connect to full nodes can detect a likely hard fork by
connecting to several full nodes and ensuring that they're all on the