Four days out. Everything that can be checked before the chain exists.Mainnet opens 15 September 2026 at 00:00 UTC. This is the whole state of the
project in one post, four days from genesis, so nobody has to read the
thread backwards to find it.
The part worth your time is not the feature list. It is that
almost
everything below can be verified before the chain exists - and where
something cannot be, that is said plainly rather than left out.
WHAT IT ISalgorithm RandomX - CPU, ASIC-hostile, key rotates every 2048 blocks
supply 22,000,000 WAM, hard cap
block reward 50 WAM, halving every 200,000 blocks (~9.1 months)
block time 120 seconds, DarkGravityWave v3 retarget every block
premine 2,000,000 WAM in the genesis block, all of it time-locked
treasury 5% of the block subsidy, ends at height 400,000
ports 9555 p2p / 9554 rpc
SLIP-44 5718349, registered with SatoshiLabs (slips PR #2051)
codebase Bitcoin Core v28.1
licence MIT
No presale. No ICO. No airdrop. No exchange listing. No token sale. The
chain opens at 00:00 UTC on 15 September and everyone starts from the
same block.
1. THE PREMINE IS LOCKED BY CONSENSUS, NOT BY PROMISE2,000,000 WAM is minted in the genesis block. That is a premine and calling
it anything else would be dishonest. What is different is that
not one
coin of it can move on launch day, or in the first year.It is five outputs of 400,000 WAM each, every one behind a bare
OP_CHECKLOCKTIMEVERIFY script with a calendar date in it:
tranche 1 400,000 WAM unlocks 2027-09-15
tranche 2 400,000 WAM unlocks 2028-09-15
tranche 3 400,000 WAM unlocks 2029-09-15
tranche 4 400,000 WAM unlocks 2030-09-15
tranche 5 400,000 WAM unlocks 2031-09-15
The scripts are
bare, not P2SH. A P2SH output would show you a hash
and you would have to trust a redeem script published somewhere else. A bare
script puts the unlock date in the scriptPubKey where anyone reads it
directly out of block 0:
wam-cli getblock $(wam-cli getblockhash 0) 2
The locks are timestamps, not block heights. A height-based lock of
"262,980 blocks" only equals one year if the chain holds 120 s per block
forever; if hashrate falls, a four-year promise silently becomes five. The
public will hold this schedule to calendar dates, so calendar dates are what
consensus enforces.
An earlier design had the first tranche liquid at genesis, described as
working capital. It was removed. The 5% treasury already covers operating
cost, so the only thing an unlocked tranche bought was 400,000 WAM the
founder could sell on day one into a market with no liquidity - the exact
shape of the objection every premine attracts, granted for no benefit.
2. THE TREASURY ENDS, AND IT COMES OUT OF THE SUBSIDY5% of the block subsidy goes to a development treasury. It is carved
out
of the reward, not added on top of it, so emission and the hard cap are
untouched:
epoch 0 miner 47.5 WAM + all fees treasury 2.5 WAM total 50
Transaction fees are never touched. They are the miner's entirely.
And it stops:
heights 1 .. 200,000 2.50 WAM/block 500,000 WAM
heights 200,001 .. 400,000 1.25 WAM/block 250,000 WAM
heights 400,001 .. 0
--------------
lifetime treasury 750,000 WAM
Roughly eighteen months of funding, then miners take 100% of the subsidy
forever. A permanent 5% tax reads to a miner as a tax for twenty-five years.
The same money over a fixed published window is launch funding. RandomX's
audience is precisely the audience that cares about the difference.
3. THE RELEASES ARE SIGNED, AND THERE IS ONE COMMAND TO CHECK ITUntil 3 September the releases carried SHA256SUMS and nothing else. A
checksum file hosted beside the file it describes proves only that both came
from the same place: whoever can replace the binary can replace the list,
and the two agree perfectly. It protects against a corrupted download. It
protects against nobody.
Every release from v0.1.6 is signed with an offline key:
4BD4 A8D3 AFD4 3F5C BCB5 00E2 3798 462F E00A DBA4
https://github.com/wam-coin-official/wam-coin/releases/tag/v0.1.7
Download the release, SHA256SUMS and SHA256SUMS.asc into one directory.
Then get the checker and the public key from the repository - deliberately
a different place from the binary - and run it:
curl -LO https://github.com/wam-coin-official/wam-coin/releases/download/v0.1.7/SHA256SUMS
curl -LO https://github.com/wam-coin-official/wam-coin/releases/download/v0.1.7/SHA256SUMS.asc
curl -LO https://raw.githubusercontent.com/wam-coin-official/wam-coin/main/scripts/verify_release.sh
curl -LO https://raw.githubusercontent.com/wam-coin-official/wam-coin/main/SIGNING-KEY.asc
bash verify_release.sh .
It refuses to print ok unless three things hold: the signature is good, it
was made by
that fingerprint, and the file in front of you is the
file that fingerprint signed for. It verifies in a throwaway keyring, so it
does not touch yours, and the fingerprint - not the key file - is the trust
anchor. Check that fingerprint over HTTPS, here, and not in this post - a
post is exactly the thing an attacker gets to write:
https://github.com/wam-coin-official/wam-coin/blob/main/SECURITY.md
testnet genesis 2026-08-01
height now 8,291
independent nodes 2 people outside this project have run one
Two. Not a number worth inflating, and deliberately not a count of who is
connected at this instant -- people close their laptops, and a figure that
becomes false when somebody goes to bed is not worth printing.
They do not dip in and out. The first found the network on 2 September and
has been on it since, and one single connection of his was measured at 135
hours -- five days and six hours unbroken, ended by a restart of ours and
not of his. The second built under WSL on Windows this week, synced from
genesis, and his node reported the same block hash at height 7738 that
ours did. He then mined: his miner rebuilt its RandomX dataset across a key
rotation and did not drop a share. Until this week both of those had only
ever been proved on our own machines.
The seeds are ours, and saying otherwise would be the first checkable lie
in this post.
5. THE LAUNCH IS BEING REHEARSED, AND WHAT EACH REHEARSAL FINDS IS
PUBLISHEDOne rehearsal a day until launch. Not because something is expected to be
wrong, but because every rehearsal so far has found something no amount of
reading found, and
how much a rehearsal still finds is the only
honest measure of whether this is ready.
docs/REHEARSALS.md carries the schedule and a table of what each one found,
including the days that found nothing. Some of what is in there:
28 Aug a pre-launch mainnet node cannot survive a restart
29 Aug ElectrumX ports 50001-50004 collided between networks
30 Aug wallets are not created under wallets/ unless it already exists
4 Sep four defects in two hours, in the pool, explorer and announcer
4 Sep the verify command in section 3 told a first-time reader that a
correctly signed release was FORGED. It resolved its own location
after changing directory, so it never found the public key and
fell back to a keyring that, for a first-time reader, is empty.
Found by running it the way a stranger runs it -- clean machine,
nothing imported -- rather than from inside the repository, where
it had always passed. Fixed and re-proved before this post
7 Sep the launch-night announcement command failed before reaching its
own safety check. Two files disagreed about where the config
lives, so the guard that stops the announcement going out on the
wrong chain never ran at all
8 Sep the signed channel list verified on this disk and was BAD in the
repository. It was signed with CRLF line endings and git stores
LF, so the file and its signature differed by 142 bytes and
anybody cloning got "BAD signature" -- which reads as tampering
10 Sep a Windows build and a macOS build each synced the test chain from
genesis and agreed with the Linux nodes block for block. The
first independent node under WSL, and the first outside miner,
both reported by people who are not us
11 Sep a third seed node, and the clean machine found five more: both
production servers were carrying a v0.1.5 wallet tool in PATH
beside a v0.1.7 node, and the runtime library line this project
publishes names a package that does not exist on Ubuntu 24.04
A project that publishes its defect list before launch is doing something
unusual, and it is deliberate. Read it and judge for yourself whether the
rate is falling fast enough.
WHAT WE ARE NOT GOING TO PRETEND- No security audit. Two independent developers read the consensus
changes and their findings were adopted. Peer review is not an audit and we
will not call it one. - The hashrate will be small. True of every new proof-of-work
chain, and not made less true by omitting it. A chain with little hashrate
can be reorganised by somebody renting enough CPU. That costs money to those
who accept payment on few confirmations - exchanges mostly, not people
holding coins. We ask 20 confirmations wallet-to-wallet, 60 for an exchange
deposit, and we will publish a review of those numbers against measured
hashrate rather than quietly leaving them. - No exchange, no price, no listing. There is nothing to buy. If
someone offers you WAM before 15 September, they are selling something that
does not exist. - No pre-built Windows or macOS binary yet. Linux x86_64, and
building from source.
LINKSwebsite https://wamcoin.org
source https://github.com/wam-coin-official/wam-coin
telegram https://t.me/wam_coin_updates
x https://x.com/WAMCoinCore
discord https://discord.gg/Gxvmrjy9Qb
bluesky https://bsky.app/profile/wamcoin.org
youtube https://www.youtube.com/@WAMcoin-l1z
reddit https://www.reddit.com/user/WAMCoinCore/
tiktok https://www.tiktok.com/@wamcoin
twitch https://www.twitch.tv/wamcoin
email wam.coin.official@proton.me
There are no others -- no second account on any platform above, no "support"
account, no exchange listing, no presale, no airdrop. The full list is signed,
and checkable rather than merely believed:
https://wamcoin.org/CHANNELS.txtThe Bluesky handle @wamcoin.org is not a name chosen on Bluesky, it is the
domain itself -- granted only to whoever can write a DNS record under it. So
it proves itself without trusting us and without trusting Bluesky:
dig +short TXT _atproto.wamcoin.org
The Reddit account u/WAMCoinCore is ours. One post was made from it and Reddit
removed it under a temporary spam restriction -- a new account posting external
links -- so the page looks empty.
Nobody official will ever message you first, ask for a seed phrase, or offer
you an allocation.
RUN A NODEgit clone https://github.com/wam-coin-official/wam-coin
cd wam-coin && ./install.sh
Builds from source, checks its own checksums, and requires no trust in a
binary anybody handed you.
Four days. Questions here get answered.
