v0.2.1

Stable upload overlay in daemon mode

A daemon-mode upload used to land under a fresh random overlay every time. The
daemon signs an upload with SwarmSigner::from_hex, which randomises the
nonce, while the in-process path uses the --nonce-file nonce. The overlay is
keccak256(eth_addr || network_id || nonce), and bee's kademlia memory is
keyed on it: peers that learned our overlay can route back to us, which is the
whole point of hoverfly vanity-overlay. So the mode built for long-lived,
repeated uploads was the one throwing the benefit away.

The upload request now carries an optional nonce, and the daemon derives the
upload signer from it — the same overlay the in-process path produces.
hoverfly upload --daemon passes the --nonce-file nonce over the socket.
The field is optional and unknown fields are ignored, so a new client against
an old daemon (and the other way round) still works; the fallback is the old
random-per-upload overlay.

Peerlists moved to their own repo. The peerlists were regenerated every
hour and committed straight into this repo — most of the commit log was data
churn. They now live in
omnipin/hoverfly-peers, refreshed
hourly, and the release tarball bundles the copy fetched at release time
instead of a frozen one.

Also in this release

• fix(batch): an insufficient balance is reported in BZZ, not raw PLUR.

Compatibility

The upload request gained an optional field; older daemons ignore it and older
clients don't send it. Nothing else changes — a patch bump says it all: no new
commands, no new flags, no wire-format change.

What's Changed

• fix(batch): report insufficient BZZ balance in BZZ, not raw PLUR by @v1rtl in #34
• feat(daemon): let an upload carry the overlay nonce by @v1rtl in #35
• chore(peers): move the hourly peerlist refresh to its own repo by @v1rtl in #36

Full Changelog: v0.2.0...v0.2.1