WAM Coin v0.1.11

If you mine solo, update. v0.1.10's miner threw away most of the blocks it
found. It asked the node for new work every five seconds and remembered only
the last eight jobs — about forty seconds — while a worker keeps hashing one
job until the chain moves, which is around two minutes. So when a block was
finally found, the miner usually no longer recognised the job it came from
and dropped it without submitting. A miner reported it, and he was right.

Roughly two blocks in three were lost this way. The fix keeps every job until
the tip it was built on is gone, and the miner now counts blocks it found but
could not send, writes each one to a file with its full header, and fails the
run instead of finishing quietly. A block you found and did not send is the
one failure this program must never report as success.

WHAT ELSE IS IN IT

A graphical wallet, in a file of its own. wam-qt opens a window, syncs,
creates and encrypts a wallet, sends and receives. It is a separate download
on every platform so that a node is not several times larger for the people
who never open a window:

wam-qt-v0.1.11-x86_64-linux-gnu.tar.gz
wam-qt-v0.1.11-x86_64-w64-mingw32.zip
wam-qt-v0.1.11-arm64-apple-darwin.tar.gz

On Linux it needs your distribution's Qt 5 installed; the archive's README
carries the one line for apt, dnf and pacman, read out of the binary rather
than remembered.

The wallet used to say it was somebody else's. Its welcome screen offered to
download "the full Bitcoin block chain (4 GB) starting with the earliest
transactions in 2009" — this chain is a few megabytes and started this
September. Its Pay To field gave a Bitcoin address as the example of a WAM
one. On Windows the firewall prompt named the publisher as "Bitcoin". And all
123 translation catalogues inside it named that coin, in their own alphabets,
where no check written in English could see them: 95 of the 123. All of it is
corrected, and the check that now looks for it does not read English — it
asks whether the translation says what the English says, which needs no
alphabet to answer.

WHAT IS NOT CLAIMED

The macOS wallet has been built on a Mac, started on a Mac, and synced the
test chain from genesis on a Mac, by the build machine. No person has sat in
front of it. The Windows and Linux wallets have been opened by hand.

This release changes no consensus rule.

The verification commands are added below this text by the workflow, and are
deliberately not repeated here: the first draft of these notes carried its own
copy, so the page showed two verify blocks that did not agree -- one naming a
download path that answers 404, the other naming an account that was suspended
on 24 September. Two wrong answers to the one question a careful reader asks.
-----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgXrrENzksEFxBfnaQmyz6+r+jI2
NE2YmsqiHkE2tpIWcAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
AAAAQGVzRMZcDxEb41yRf/IWfhH7AqeqOC8kc3Y1QyAsgmZB+7mNXdFss9qHbVNtVqh+Qi
jUiay9TThIiVAp0lLqIgs=
-----END SSH SIGNATURE-----

---

Built by GitHub Actions from 8a3f4fe4f1d804c378f795d4cc281ec5125f75f3 on ubuntu-22.04.

Verify before running:

curl -LO https://github.com/wamcoin-core-dev/wam-coin/releases/download/v0.1.11/SHA256SUMS
curl -LO https://github.com/wamcoin-core-dev/wam-coin/releases/download/v0.1.11/SHA256SUMS.asc
curl -LO https://raw.githubusercontent.com/wamcoin-core-dev/wam-coin/main/scripts/verify_release.sh
curl -LO https://raw.githubusercontent.com/wamcoin-core-dev/wam-coin/main/SIGNING-KEY.asc
bash verify_release.sh .

WAM has no market value and may never have one. Mainnet has been
running since 15 September 2026, and this is young software: two
independent developers have reviewed it and their findings were
adopted; no security firm has audited it.

Build it yourself instead, if you prefer -- the release above is
produced by install.sh --build-only, the same script in this
repository, with no manual steps.

WAM Coin v0.1.10

You can now mine WAM on your own machine against your own node, with no pool
at all. wam-miner --solo -u YOUR_ADDRESS needs nothing but a running wamd
with server=1. When you find a block you keep the whole 47.5 WAM instead of a
share of it, and you wait longer between them.

Before you spend any electricity, wam-miner --check -u YOUR_ADDRESS builds a
real block from your node's template and asks the node whether it is valid. It
hashes nothing and answers in about a second. If your node accepts it, every
part of a block except the proof of work is correct.

Both work on Linux, Windows and macOS, and from this release every build
proves the second one on each: a regtest node is started and --check is run
against it, so the miner must build a block that node accepts before the
release exists. That covers everything in a block except the proof of work.

Hashing and submission are proved on hardware this project owns, and never in
CI. Running a miner on a hosted build service is against the terms of every
one of them, which this project learned the expensive way on 2026-09-24 when
a step of ours did exactly that and cost it its code-hosting account for a
day.

Also fixed, all found by reading rather than by anyone reporting them:

The graphical wallet would have carried Bitcoin's logo. Four icon files ship
with the GUI -- the window and taskbar icon, its testnet variant, the macOS
bundle icon and the splash image -- and the rename replaced one of them. The
releases are built --without-gui, so nothing published so far has shown the
wrong mark to anybody; the first GUI built from this tree would have. All
four are generated from one master now, and preflight refuses a release whose
icons are missing or malformed.

The miner reached for the mainnet RPC port whatever --network said, so mining
alone on testnet or regtest failed with "could not connect" — which reads as
"your node is not running" to somebody whose node is running perfectly, on
another port. The port now follows the chain.

The miner also never started Winsock on the solo path, so --solo and --check
could not work on Windows at all: getaddrinfo failed for every host and the
miner reported "cannot resolve 127.0.0.1" to people whose address was right.
It was found by running them on Windows for the first time, in the gate this
release adds.

The announcement bot cut these notes at twelve lines regardless of where a
sentence ended. Every release before this one was announced mid-sentence, and
twice mid-word. It also called every mainnet release "testnet software",
because GitHub's pre-release flag means pre-1.0 and the bot read it as a
statement about the chain.

The mining pool credited block rewards one block before the coin could be
spent — COINBASE_MATURITY is 100 and a coinbase becomes spendable at 101 — so
it believed it held 47.5 WAM more than the node would let it send. Nothing
was lost and nobody was paid twice; the books reconcile to 0.1 WAM of
accumulated transaction fees. What it cost was time: payouts drifted from
every ten minutes to every twenty or forty. scripts/treasury_spend.py chose
inputs on the same wrong boundary, where the failure would have arrived at
broadcast instead.

Verify the download before running it. Every archive is listed in SHA256SUMS
and that list is signed:

gpg --import SIGNING-KEY.asc
bash verify_release.sh .

The fingerprint to check it against lives in one place and nowhere else:

https://wamcoin.org/security/