Register WAM Coin: SLIP-0044 coin type 5718349 and SLIP-0173 hrp wam - #2051
Open
wam-coin-official wants to merge 1 commit into
Open
Register WAM Coin: SLIP-0044 coin type 5718349 and SLIP-0173 hrp wam#2051wam-coin-official wants to merge 1 commit into
wam-coin-official wants to merge 1 commit into
Conversation
wam-coin-official
added a commit
to wam-coin-official/wam-coin
that referenced
this pull request
Aug 21, 2026
…-pushes Bisq blocks a merge on "Commits must have verified signatures", so prepare_listing_pr.sh signs. It signs with SSH rather than GPG, because the key that already pushes to these forks can sign as well and there is no new secret to make, hold or lose. Registering that key at github.com/settings/keys as a Signing Key was not enough, and the reason is worth writing down where the next person will look. GitHub verifies a signature only when the key AND the committer email both belong to the same account. The commits carried a personal Gmail address that the account does not own, so a correctly signed commit with a correctly registered key reported "unknown_key" and looked unsigned. Two force-pushes went into checking the key before the cause turned out to be the other half of the condition. The script now commits as the project address, and the first push of any future submission arrives verified. BasicSwap's chainparams.py is edited rather than left to a human. Three anchored edits -- the import, the Coins enum member, the chainparams table -- each anchored on a line read out of their file, each aborting if its anchor is missing, and the result parsed with ast before the commit. A submission that does not import is worse than none, and the earlier note here said a script editing Python blind was the danger. It is, which is why these are anchored and verified rather than blind. The service-file insertion no longer adds a trailing newline that their file does not have. Haveno's ends without one, and writing it back with one turned a one-line insertion into a diff that also deleted and re-added the last entry. A reviewer opening a two-line diff to find half of it unrelated learns something about the submitter that is neither true nor useful. Three are open as of 2026-08-21: satoshilabs/slips#2051, bisq-network/bisq#8028 and haveno-dex/haveno#2528. None has been reviewed. A pull request is a request.
wam-coin-official
force-pushed
the
add-wam-coin
branch
from
August 21, 2026 10:14
65bbd76 to
4de29e7
Compare
WAM Coin is a Bitcoin Core v28.1 fork using RandomX proof of work. SLIP-0044 --------- 5718349 is 0x57414D, which is "WAM" in ASCII. The registry has no free number below a thousand, and this follows what recent entries do -- the row immediately below is Wanchain at 5718350, which is 0x57414E, "WAN". The same scheme with the adjacent ticker. The document's condition is that a wallet implementing BIP-0044 for the coin must already exist. It does, and it derives at the number requested here: $ wam-cli -rpcwallet=w listdescriptors | grep -o "8[46]h/[0-9]*h" 84h/5718349h 86h/5718349h Testnet is left at 1, as SLIP-0044 reserves it. SLIP-0173 --------- wam, twam and wamrt for mainnet, testnet and regtest. None appears among the registered prefixes. Source: https://github.com/wam-coin-official/wam-coin Explorer: https://explorer.wamcoin.org Mainnet launches 2026-09-15. Both values are being registered before the first block rather than after, so that no wallet is ever restored onto a branch that has since moved.
wam-coin-official
force-pushed
the
add-wam-coin
branch
from
August 21, 2026 10:22
4de29e7 to
7688cc0
Compare
wam-coin-official
added a commit
to wam-coin-official/wam-coin
that referenced
this pull request
Aug 21, 2026
prepare_listing_pr.sh committed as the founder personally. Nothing in this repository does that -- all sixty of its own commits are WAM Coin <wam.coin.official@proton.me> -- and the script should have followed the convention already in front of it instead of reaching for an identity from somewhere else. It had a second effect nobody would predict from reading it. GitHub attributes a commit to whichever account owns the committer email, and the account owning that personal address is named with a -bot suffix. So the SLIP-44 registration -- a request to write this coin into a public registry of identities -- arrived attributed to a bot, and unsigned. All five open submissions are re-authored and signed: satoshilabs/slips#2051, bisq-network/bisq#8030, haveno-dex/haveno#2528, tecnovert/basicswap#2 and blocknetdx/blockchain-configuration-files#197. Force-pushed, never deleted: deleting a branch closes its pull request, which is how one of them was lost earlier tonight. The founder is not anonymous. He is named in the legal brief, which is addressed to a lawyer and cannot be useful without a client, and he answers the project address. What changed is that a coin's submissions no longer carry one person's private account, because that is how a project reads as a hobby to everyone who opens it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WAM Coin is a Bitcoin Core v28.1 fork using RandomX proof of work.
SLIP-0044
5718349 is 0x57414D, which is "WAM" in ASCII. The registry has no free number below a thousand, and this follows what recent entries do -- the row immediately below is Wanchain at 5718350, which is 0x57414E, "WAN". The same scheme with the adjacent ticker.
The document's condition is that a wallet implementing BIP-0044 for the coin must already exist. It does, and it derives at the number requested here:
$ wam-cli -rpcwallet=w listdescriptors | grep -o "8[46]h/[0-9]*h"
84h/5718349h
86h/5718349h
Testnet is left at 1, as SLIP-0044 reserves it.
SLIP-0173
wam, twam and wamrt for mainnet, testnet and regtest. None appears among the registered prefixes.
Source: https://github.com/wam-coin-official/wam-coin
Explorer: https://explorer.wamcoin.org
Mainnet launches 2026-09-15. Both values are being registered before the first block rather than after, so that no wallet is ever restored onto a branch that has since moved.