-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Here I add an rpc function, 'eatblock.'

This patch only makes sense if you have 'dumpblock'. [1]

Does just what is printed on the tin: attempts to receive the
next block from a raw dump of the latter found on disk, e.g.,

$ ./bitcoind eatblock 5.blk
true

Given the potential dangers of having this kind of loaded pistol
around, the 'eatblock' rpc call is DISABLED by default, and must
be explicitly permitted when starting a bitcoind instance,

./bitcoind -caneat -myip=my.ip.is.foo ...

Using 'dumpblock' and 'eatblock', it is now possible to move
blockchains around via various direct channels (e.g., pigeon.)

One could even sync via 'netcat' from a trusted phriend...

Use good judgement when experimenting with 'dumpblock' and 'eatblock.'

[1] http://therealbitcoin.org/ml/btc-dev/2015-June/000104.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBCgAGBQJVkfQpAAoJELmCKKABq//HmU4H/i9rrIqqsSxumeXCStrJYWyo
dKz3aqjPbv7GvfeJyAvO9pnKbz+A5Mz8lZyyfpyMP+7gOKrOATqx9u1BAsC8BlD+
/qQS3NL7pj0QTg2e7KuMx3Z+4+W0J/wT2G0HnSOlsVVVzPVqfGBo2dFVHjK+r6nK
1dosD5HQpf6uB/V4sQEDoLzgAUHxJd6z8Ba1950IUjUfKUkezNmYwI7T6Bb9lkt2
/TJeey3PRLC+G36Fy6zxJyKnQwNSvMP/AWaddg6LFBy5SZrsBJSjWm+hDNW5h5iG
zj01imdYJczYvFTCyBGEKjHZVXRKY7aosj2z28K40jNLVMGcoKg95SSshDFpjtU=
=0eWU
-----END PGP SIGNATURE-----