WAM Coin v0.1.9 -- arm64-apple-darwin

These binaries were compiled natively, on a macOS runner,
by the platform-build workflow. Nothing here was cross-compiled.

They were then run against the live test chain on a macOS (Apple Silicon) machine, which
synced from the genesis block over the real peer-to-peer protocol and
compared four blocks the Linux nodes have held since August: 0, 1, 5000 and
6000. Block 1 is where the 5% treasury rule is first enforced, so a binary
that disagrees about consensus disagrees there.

The chain was synced with the files in THIS archive, after stripping and
packaging, not with an earlier build of them.

The miner in the separate archive was compiled on that
same machine, so it ran --self-test there during the build rather than on
another one afterwards.

That check covers SHA-256, stratum byte order, the difficulty targets, and
RandomX against the two official test vectors. A miner whose RandomX
disagreed with the network would hash all day, find nothing, and report no
error at all, so it is the whole question.

That is what is being claimed, and all of it. What is NOT claimed:

  * no human had double-clicked these before the release that carries them
  * before v0.1.9 the packaging and the signature covered Linux and
    nothing else, so this path is newer and less worn than that one

VERIFY BEFORE YOU RUN IT. The checksum file is signed with a key kept
offline, and the fingerprint is published in SECURITY.md in the source
repository and nowhere else:

  4BD4 A8D3 AFD4 3F5C BCB5  00E2 3798 462F E00A DBA4

  curl -LO .../SHA256SUMS
  curl -LO .../SHA256SUMS.asc
  curl -LO .../scripts/verify_release.sh
  curl -LO .../SIGNING-KEY.asc
  bash verify_release.sh .

A release without SHA256SUMS.asc beside it cannot be checked. Do not run it.
