Wcash is an independent network. It has its own consensus rules, state, difficulty, issuance, and transaction history. It supports transparent and Ironwood-shielded transfers. Those capabilities only become useful when the software around them is reliable enough for people and services to use.
From code to access
The node needs review, tests, releases, and maintenance. Wallets need understandable privacy choices, safe recovery flows, and compatibility work. Public infrastructure needs monitoring, indexing, documentation, and clear descriptions of what can and cannot be observed on-chain. Pools need integration paths, and operators need time to adopt changes.
Some of this work is visible in the Wcash source, wallet developer preview, and block explorer. A preview is not a supported consumer release, and an integration effort is not a promise that a service will list or adopt WEC.
Continuity is a choice
Participating miners can reuse Equihash work through compatible merged-mining pools. Development does not become automatic as a result. The founder currently carries much of the engineering and coordination. Renting hashrate to obtain WEC is not a durable compensation model for that work.
The fixed-term development rule supports contributors and builds a reserve for continued work. It allocates 30% of WEC block subsidies from block 33,000 through 621,454, then ends automatically. Funding creates capacity; the quality of the work still has to be demonstrated.
The term is approximately 511 days, 17 months, or 1.4 years at the 75-second target interval. Read the exact block range and mechanics in the funding section.