Loading today’s stories
Invest1 distinct publisher2 min readUpdated
LayerTwo Labs plans to assign ECX one-for-one to Bitcoin holders at a snapshot near block 973,728. Replay protection is opt-in, which lands the work on custodians first.
The Investor · Invest desk
Compiled by The InvestorSomething wrong?How this is made
Opt-in replay protection is the line item that turns this from a listings question into engineering work. The project's official software warns users before they transact, but the default condition is that moving Bitcoin can carry the matching ECX with it unless the two assets are deliberately separated [9]. That reaches cold-storage sweep procedures and change handling, both of which were written on the assumption that a Bitcoin spend has exactly one consequence.
Nobody has to opt in to acquire the asset. Holders who control their keys at the relevant heights receive matching ECX without registering or filing a claim [10]. A venue that judges ECX not worth supporting therefore still holds client-attributable balances on a chain it is ignoring, and its ordinary Bitcoin operations are the mechanism by which those balances get spent.
The binding trigger is a height, not a date: alpha at Bitcoin block 963,648, beta at roughly 967,680, mainnet near 973,728, with the calendar dates offered as approximations of when the chain arrives there [3][5][6][20]. The gaps are 4,032 blocks and then 6,048 [19], 10,080 in total [17]. A change-freeze calendar pinned to October 31 rather than to the height is pinned to the wrong variable.
The one-to-one promise also carries an asterisk. Balances are assigned one-for-one for nearly all addresses [8], with a portion of early Satoshi-era coins handled differently on the new chain to fund development, while the corresponding Bitcoin stays untouched [11]. Whoever reconciles client entitlements has to locate those exceptions before a support queue does.
The reward for doing this early is also unpriced. Practice tokens from the alpha and beta stages can be burned and redeemed for a portion of the official coins after mainnet activation, and the portion is not stated [4]. On the other side of the ledger, the new chain reuses Bitcoin's SHA-256 proof of work with a temporary difficulty reset at activation, which is the pitch to miners [15], and the stated point of the whole exercise is to enable drivechains, opt-in sidechains that leave Bitcoin's base-layer rules alone [16]. Adoption by major infrastructure providers is still an open question and community support has been limited so far [14]. None of that changes what a custodian has to settle first, which is not whether to list ECX but whether the next cold wallet sweep after the snapshot quietly spends something a client may later claim.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
LayerTwo Labs, under longtime Bitcoin contributor Paul Sztorc, is developing eCash (ECX), a hard fork that mirrors Bitcoin's transaction history at specific points without altering the original Bitcoin chain, and it is proceeding in three stages rather than one event.
The alpha phase activates around Bitcoin block height 963,648, corresponding roughly to August 23, 2026.
During alpha, participants can test software, mining, wallets and trading of temporary practice tokens called pECX or alpha ECX; these carry no permanent value on their own but can later be burned and redeemed for a portion of the official coins once the full network is live.
A beta stage follows around September 20 at block height approximately 967,680, and is expected to involve greater participation from exchanges, custodians, wallet providers and miners.
The permanent mainnet release is scheduled for around October 31 at block height near 973,728.
At the mainnet snapshot, permanent ECX balances will be assigned one-to-one with Bitcoin holdings at that time for nearly all addresses; Bitcoin itself remains completely unaffected and holders simply gain an additional asset on the new chain.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Single-source explainer, no primary artifacts
Everything rests on one publisher's write-up. The schedule, allocation rule, replay-protection design and developer allocation are reported without a linked specification, code release, LayerTwo Labs statement or independent technical review, and calendar dates are hedged as approximations tied to block heights. The article also contradicts its own timeline arithmetic, which lowers confidence in how closely it tracks primary material.
Pre-adoption, no named integrators
The only observable event is the start of an alpha test phase with valueless practice tokens. The source itself states that adoption by major infrastructure providers is unresolved and community support has been limited, and no exchange, custodian, wallet or miner is named as participating or committing to credit ECX.
Windfall framing runs ahead of the evidence
The framing that Bitcoin holders are 'getting ready to claim' a matching balance implies a settled, valuable entitlement, while the same piece admits infrastructure support is unresolved, liquidity is unproven, exchanges may not credit anything, and the sidechain use case is unbuilt. Symbolic dressing (the white-paper anniversary) and a preparation window overstated by about two weeks push the same direction. The gap is moderated by the article's genuine, non-promotional operational caveats about opt-in replay protection and exchange freezes.
Promoter-side incentives disclosed but unquantified
Two structural incentives are visible in the source: a portion of early Satoshi-era coins is redirected on the ECX chain to fund development, and pECX practice tokens are redeemable for official coins after mainnet, which rewards early testers and boosts apparent participation. Neither is quantified, and the article's own text notes this 'creat[es] incentives for early testing'. Publisher-side incentives are not disclosed in the supplied material.
Low-moderate
The operational shape of the story is clear and internally consistent enough to act on for custody purposes: heights, an opt-in replay-protection design, and exchange discretion. But with one publisher, no primary artifacts, unquantified allocation details, an internal date inconsistency and block-height timing that will drift, the specifics deserve verification against official releases before anything irreversible is done.
invest
Jane Street's $990M in Bitcoin ETFs looks like inventory, not conviction1 distinct publisher
build
Your meter now runs on someone else's machine: signed receipts, fsync, and failing open1 distinct publisher
build
Once the question needs a cube, you own the parser1 distinct publisher
invest
Two years of stablecoin plumbing, and 0.2% of euro area online sellers take crypto2 distinct publishers
Distinct publishers with included, body-backed reporting in this cluster.