[ANN] WAM Coin v0.1.11 — solo mining fix, and a graphical wallet
Two things.
1. The solo miner was losing blocks it had already found.
It polled getblocktemplate every five seconds and kept the last eight jobs —
about forty seconds of memory — while a worker goes on hashing one job until
the chain moves, which is around two minutes. So when a block was finally
solved, the miner often no longer recognised the job it came from and dropped
it without submitting. Roughly two blocks in three.
It was reported by a miner who noticed his standalone miner had produced
nothing in nine hours while the same machine on a pool had produced several.
The fix keeps every job until the tip it was built on is gone. The miner now
also counts blocks it solved and could not send, writes each one to a file
with its full header, and fails the run rather than finishing quietly.
Confirmed on mainnet, not on our own machines: a miner on Windows found block
11385 ninety-seven seconds after the job was issued, and the node accepted it.
On the old build that job would already have been forgotten. He has since
found a second, also accepted. found 2, accepted 2.
2. There is now a graphical wallet.
wam-qt — a window, syncing, wallet creation and encryption, send and receive.
Linux, Windows and macOS, as a separate download so a node is not several
times larger for people who never open a window.
https://wamcoin.org/downloads/v0.1.11/On Linux it needs your distribution's Qt 5; the archive's README carries the
one line for apt, dnf and pacman. On macOS it has been built, started and
synced from genesis by the build machine — no person has yet sat in front of
it, and that is said rather than left out.
Verify before running, ours included:
curl -LO
https://wamcoin.org/downloads/v0.1.11/SHA256SUMS curl -LO
https://wamcoin.org/downloads/v0.1.11/SHA256SUMS.asc curl -LO
https://wamcoin.org/verify_release.sh curl -LO
https://wamcoin.org/SIGNING-KEY.asc bash verify_release.sh .
RandomX, 2-minute blocks, 22,000,000 cap, no premine held liquid.
Source:
https://gitlab.com/WAMCoin/wam-coin
WAM paid its first security bounty, and it was paid in WAM.
In September an independent reviewer went through the pool code and found
that the same pending block could mature more than once, crediting miner
balances twice out of the pool operator's own wallet. Two further reports
turned out to be the same accounting fault wearing different clothes. It was
fixed the day it arrived, and a test now holds it down.
He wrote in his first email: "no reward expectation (you state up front there
is none, that's fine)". He came to read the code, not to be paid.
The finding was classified at 10,000 WAM under the tiers published before
launch, and he was paid that — in WAM, which he asked for and accepted.
It went out in nine transactions, and the reason is arithmetic: consensus
pays the treasury 2.5 WAM per block, so its balance is thousands of small
outputs. Ten thousand in one transaction would have been about 4,000 inputs
and 590 KB — six times the standard size limit, which no node would relay. It
would have been signed and broadcast and simply never arrived. The first of
the nine was 10 WAM, sent alone and confirmed received before the rest moved,
because an address is typed once and a chain forgets nothing.
Every one of the nine ids is written down with its amount and its reason:
docs/TREASURY_LEDGER.md
Add them up yourself. The total is 10000.00000000 WAM.
Credited to chovy, by his own choice of name.
