Bitcoin Forum
August 16, 2026, 01:27:08 AM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: WAM Coin: A RandomX Fork of Bitcoin Core v28.1 (Launching Sept 15, 2026)  (Read 49 times)
Waleed Al80 (OP)
Newbie
*
Offline

Activity: 2
Merit: 0


View Profile
August 14, 2026, 12:37:27 PM
Last edit: August 15, 2026, 11:25:33 PM by Waleed Al80
 #1

WAM Coin: A RandomX Fork of Bitcoin Core v28.1
Mainnet Launching Sept 15, 2026 · Testnet Live Now

WAM Coin — a RandomX fork of Bitcoin Core v28.1, launching 15 September 2026. Review welcome.

WAM is a fork of Bitcoin Core v28.1, not a rewrite. Roughly 250,000 lines of networking, script and wallet code are inherited from a codebase that has been adversarially reviewed for fifteen years. About 3,000 lines are ours — and those are the ones worth reviewing.

What Differs from Bitcoin
  • 22,000,000 hard cap, 2-minute blocks, 50 WAM initial subsidy
  • RandomX proof of work, so CPUs stay competitive
  • DarkGravityWave v3, retargeting every block
  • A consensus-enforced 5% treasury output that stops permanently at block 400,000
  • Founder reserve of 2,000,000 locked in genesis by
Code:
OP_CHECKLOCKTIMEVERIFY
    , releasing 20% a year to 2030

Founder + treasury is 12.50% of supply. Both are disclosed and enforced by every node.

Every upstream change is a scripted, anchored transformation in
Code:
scripts/patch_upstream.py
— no patch files — so
Code:
--list
prints every difference from Bitcoin Core with its rationale. There has been no third-party security audit.

Testnet & Code
Testnet is live. Two seed nodes (France and Singapore). A node finds the network by itself through DNS; there is a prebuilt release on GitHub (11.7 MB), needing
Code:
libevent
and
Code:
libsqlite3
and nothing else.

I would value review of the consensus changes in
Code:
src/wam/
in particular.

Official Links:
GitHub: github.com/wam-coin-official/wam-coin
Website: wamcoin.org

Bug Bounty
Report privately. Do not post a consensus or security bug in this thread — a public consensus bug is an attack that has not happened yet. Email wam.coin.official@proton.me or open a GitHub Security Advisory on the repository.
Code:
SECURITY.md
has the details.

In scope:
Code:
src/wam/
(consensus, subsidy, treasury, DGW, RandomX), the stratum pool in
Code:
pool/
,
Code:
scripts/patch_upstream.py
, and the release tooling.
Out of scope: inherited Bitcoin Core code — report those upstream; DoS against the testnet; anything needing physical access or social engineering.

Rewards (paid in mainnet WAM after launch, from the founder reserve):
  • 50,000 WAM: Consensus split, inflation beyond the 22,000,000 cap, or theft of pool funds
  • 10,000 WAM: Remote crash, or a way to steal another miner's shares
  • 1,000 WAM: Everything else accepted
Said Plainly: WAM has no market value and may never have one. These figures are units of a coin that does not trade. If that is not worth your time, I would rather you knew before you spent it.

Duplicates and already-known issues do not qualify. I decide what is verified, and I will publish every accepted report with credit once it is fixed.
Waleed Al80 (OP)
Newbie
*
Offline

Activity: 2
Merit: 0


View Profile
August 15, 2026, 12:42:56 AM
 #2

WAM Coin — a RandomX fork of Bitcoin Core v28.1, launching 15 September 2026.
Review welcome.

WAM is a fork of Bitcoin Core v28.1, not a rewrite. Roughly 250,000 lines of
networking, script and wallet code are inherited from a codebase that has been
adversarially reviewed for fifteen years. About 3,000 lines are ours.

What differs:
* 22,000,000 hard cap, 2-minute blocks, 50 WAM initial subsidy
* RandomX proof of work, so CPUs stay competitive
* DarkGravityWave v3, retargeting every block
* A consensus-enforced 5% treasury output that stops permanently at block 400,000
* Founder reserve of 2,000,000 locked in genesis by OP_CHECKLOCKTIMEVERIFY,
  releasing 20% a year to 2030

Founder + treasury is 12.50% of supply. Both are disclosed and enforced by
every node.

Every upstream change is a scripted, anchored transformation in
scripts/patch_upstream.py — no patch files — so --list prints every difference
from Bitcoin Core with its rationale. There has been no third-party security
audit.

Testnet is live. Two seed nodes, France and Singapore. A node finds the network
by itself through DNS; there is a prebuilt release on GitHub, 11 MB, needing
libevent and libsqlite3 and nothing else.

github.com/wam-coin-official/wam-coin · wamcoin.org

I would value review of the consensus changes in src/wam/ in particular.


Bug bounty

Report privately. Do not post a consensus or security bug in this thread — a
public consensus bug is an attack that has not happened yet. Email
wam.coin.official@proton.me, or open a GitHub Security Advisory on the
repository. SECURITY.md has the details.

In scope: src/wam/ (consensus, subsidy, treasury, DGW, RandomX), the stratum
pool in pool/, scripts/patch_upstream.py, and the release tooling.

Out of scope: inherited Bitcoin Core code — report those upstream; DoS against
the testnet; anything needing physical access or social engineering.

Rewards, paid in mainnet WAM after launch, from the founder reserve:
* Consensus split, inflation beyond the 22,000,000 cap, or theft of pool funds — 50,000 WAM
* Remote crash, or a way to steal another miner's shares — 10,000 WAM
* Everything else accepted — 1,000 WAM

Say plainly: WAM has no market value and may never have one. These figures are
units of a coin that does not trade. If that is not worth your time, I would
rather you knew before you spent it.

Duplicates and already-known issues do not qualify. I decide what is verified,
and I will publish every accepted report with credit once it is fixed.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!