Commit Graph

12 Commits

Author SHA1 Message Date
davide e0d04af154 constants: add BitcoinPurple (BTCP) and BitcoinPurpleTestnet network classes
Add per-chain PoW fields to AbstractNet (DIFFICULTY_ADJUSTMENT_INTERVAL,
POW_TARGET_TIMESPAN, MAX_TARGET, MAX_ADJUSTMENT_FACTOR, POW_GENESIS_BITS)
with Bitcoin defaults so existing chains are unaffected.

Add BitcoinPurple and BitcoinPurpleTestnet as independent AbstractNet subclasses
with BTCP-specific parameters:
- 120-block retarget interval, 7200-second target timespan
- powLimit 0x1e0fffff, genesis nBits 0x1e0ffff0 (POW_GENESIS_BITS)
- P2PKH prefix 56 (0x38), P2SH 55 (0x37), WIF 0xb7, bech32 HRP "btcp"/"tbtcp"
- SLIP-0132 HD key headers identical to Bitcoin mainnet/testnet respectively
- ElectrumX default ports 50001/50002 (mainnet) and 60001/60002 (testnet)

Add chain data directories:
- electrum/chains/bitcoinpurple/{servers,checkpoints,fallback_lnnodes}.json
- electrum/chains/bitcoinpurple_testnet/{servers,checkpoints,fallback_lnnodes}.json
servers.json is populated with 5 known BTCP ElectrumX nodes (TCP 51001, SSL 51002)
2026-04-29 10:07:54 +02:00
Jochen Hoenicke e31ce7dce6 Update my Electrum server details in servers.json
I moved my node to standard port again because the non-standard one was apparently used by malware.  I also updated the domain name (both work at the moment, but I prefer the shorter one).
2026-03-10 17:58:43 +01:00
SomberNight d72b741173 update block header checkpoints 2026-02-26 17:49:31 +00:00
f321x 52b554a5f2 servers.json: add additional default server
Add new additional default server on protocol version 1.6.0 operated
by a known contributor.
2026-02-17 09:33:43 +01:00
Sanksari12 67f3fcfb16 Update servers.json
Remove lavahost.org from servers.json as the host does not host a public electrum instance.
2026-02-16 19:47:42 +00:00
SomberNight 08fa871f39 update block header checkpoints 2026-01-22 14:55:02 +00:00
f321x 348ca667ca contants: add support for mutinynet signet
Adds the mutinynet signet (https://github.com/MutinyWallet/mutiny-net/)
to the supported networks so it's possible to
use it with Electrum. Mutinynet is similar to signet, except for a
shorter block interval (30 sec), a nice faucet
(faucet.mutinynet.com) and some extra features in its core fork.
It also has some lightning network nodes, see
the mempool instance on mutinynet.com.
2025-08-14 15:59:11 +02:00
SomberNight 1355f849c3 constants.py: reorganise file hierarchy in chains/ 2025-05-29 15:31:27 +00:00
SomberNight 400934b771 network: hardcoded servers: add a few more 2025-05-29 15:02:04 +00:00
SomberNight 5e2c52081d update block header checkpoints 2025-05-29 15:02:01 +00:00
f321x 2c67ed8491 update mainnet ln fallback nodes 2025-02-04 09:43:40 +01:00
SomberNight 9bef4a5322 constants: move mainnet/testnet/regtest-specific json files to chains/
note: I find "chains" less ambiguous than "networks" or "net".
Though the codebase already uses "net"/"network" for the same meaning,
e.g. see `electrum.constants.net` or the `getinfo` cmd dict containing a "network" key.. :/
2025-01-27 13:40:41 +00:00