Skip to content

Network Specifications

tgibbsz32 edited this page Oct 25, 2026 · 3 revisions

ForgeCoin native mainnet specifications

Scope: the proposed independent ForgeCoin fresh-mainnet candidate, not the Monero blockchain and not ForgeCoin's older development chain. Parameters below are exactly specified development targets where recorded, but not frozen or activated until consensus audits and release approval.

Proposed network identity

Parameter Fresh-mainnet candidate (provisional)
Native asset / ticker ForgeCoin / FRG
Monero base v0.18.5.1-derived CryptoNote/Monero native chain
Public address prefix — standard 190
Integrated address prefix 191
Subaddress prefix 192
Peer-to-peer port 39480/TCP
Daemon RPC port 39481/TCP; bind to loopback unless independently secured
ZMQ RPC port 39482/TCP; loopback by default
Network UUID 9e51307a-72a4-4865-b229-114f836ca7d0
Candidate genesis nonce 20261020
Recorded candidate genesis hash 2a91ebe3007fb301072c5b0c8e130c782d1218e4633f6a30e6c2d692b6ac5f05
Protocol version Genesis v1 at height 0; v19 at height 1 in tested candidate
Proof of work RandomX
Target block interval 120 seconds
Starting difficulty 500,000 through height 15 in candidate
Difficulty transition Progressive LWMA from height 16, up to 90 intervals
Minimum difficulty 400,000 proposed floor
Currency precision 8 decimal places = 100,000,000 atomic units per FRG
Coinbase unlock 60 blocks (~2 hours at target spacing)
Typical output spendable age 10 blocks (~20 minutes at target spacing)

Network separation is mandatory

The old development chain instead uses prefixes 90 / 91 / 92, P2P/RPC/ZMQ 19480 / 19481 / 19482, genesis nonce 10000, and a different fork/difficulty activation schedule (v17 at 500, v18 at 600, LWMA90/v19 at 700). Its running Oracle node and explorer are not the fresh-mainnet rollout. No automatic wallet balance transfer, genesis carry-over or old-chain coin redemption is planned.

Even if a program calls either chain mainnet, the network UUID, genesis and consensus schedule determine compatibility.

Transaction privacy and validation

The codebase inherits Monero-family stealth addressing, ring signatures (CLSAG), RingCT confidential amounts, Bulletproofs+ and view tags. Version-specific ring behavior (including historically fixed ring size 16) must be checked against the actual released fork code. Full nodes independently validate transactions and cumulative-work fork choice. A public explorer can display heights, hashes, block metadata, network difficulty, transaction IDs, fees and confirmation status; it cannot legitimately reveal ordinary private sender/recipient identities or confidential amounts.

Privacy is not absolute: endpoint compromise, traffic analysis, wallet data disclosure and exchange records can reduce anonymity. Do not claim instant settlement; new transactions and confirmations depend on block production and network conditions.

Outstanding consensus caveats

  • The recorded candidate genesis has an indexed 11.92092895 FRG output (unlock height 60). Permanent unspendability has not been proven. Current owner policy allows retaining it only after independent verification; otherwise a replacement design and retest require explicit approval. This is a launch blocker, not an authorized allocation.
  • Native mining to isolated RPC height 17, a branch-reorganization repeat and selected difficulty calculations are evidence, not independent audits of height 90–92 native acceptance or ARM64 consensus.
  • Genesis, addresses, ports, seed nodes, LWMA bootstrap and release binaries are provisional until reviewed/frozen together. Do not connect candidate binaries to the older public network.

Source detail: Candidate vs development chain · Whitepaper · Owner decisions.

Clone this wiki locally