# Fork İlgili Makaleler

HTX Haber Merkezi, kripto endüstrisindeki piyasa trendleri, proje güncellemeleri, teknoloji gelişmeleri ve düzenleyici politikaları kapsayan "Fork" hakkında en son makaleleri ve derinlemesine analizleri sunmaktadır.

What Happens When Two Miners Find a Block in the Same Second? How the 'Orphan Race' Unfolds

Bitcoin mining is a race without a real-time referee. A newly mined block must physically propagate across the global peer-to-peer network before consensus is reached on the chain's tip. This takes seconds, sometimes longer on congested connections. If a second miner finds a valid block before learning of a competing one, they build on their last-known version and broadcast their own block. For a short time, two equally valid blocks exist at the same height, creating a temporary chain split. The network resolves this not by voting or timestamps, but by Proof-of-Work: the chain that accumulates the most work becomes canonical. Blocks on the losing side are "orphaned" or "stale." Their miners lose the block reward and fees, though unconfirmed transactions return to the mempool. Usually, a single subsequent block resolves the tie. A notable two-block reorganization occurred on March 24, 2026. Antpool and Foundry USA mined competing versions of block 941,881 seconds apart. ViaBTC extended Antpool's chain, while Foundry extended its own, creating a one-block split. Foundry then pulled ahead by mining six consecutive blocks, making its chain the heaviest. All nodes switched to Foundry's chain, orphaning blocks from Antpool and ViaBTC. While such multi-block reorganizations are rare, the underlying race condition is common. Analysis shows about 9.2% of block intervals in a sample period were under 60 seconds, each representing a potential short-lived race. Fast relay networks have reduced propagation delays, making prolonged splits rarer. However, the event highlighted a trend of hash rate concentration, where well-resourced pools have a higher chance of winning any specific race and mining consecutive blocks, marginalizing smaller miners.

cryptonews.ru19 saat önce

What Happens When Two Miners Find a Block in the Same Second? How the 'Orphan Race' Unfolds

cryptonews.ru19 saat önce

Zcash Developers Recommend Upgrading Nodes to Ironwood Fork

The Zcash Foundation has released Zebra 6.0.0 and recommends all node operators upgrade to the Ironwood fork. This update introduces a new shielded pool and version 6 transaction format. The change was prompted by a vulnerability discovered in the old Orchard pool that could have allowed an attacker to create counterfeit $ZEC undetected. Developers patched the vulnerability in June, finding no evidence of exploitation, though Zcash's privacy architecture prevents absolute certainty. Ironwood utilizes the Orchard action structure and Halo2 proof system. It adds a separate note commitment tree, a nullifier set, a network value pool, and network history data. After activation, nodes can track the new pool independently from Orchard. Zebra also updates node commands for operators to verify pool and commitment tree states. This upgrade is critical, as older software will not follow the correct chain post-activation. Ironwood's key protection mechanism is a "turnstile" between the Orchard and new pools. Once activated, Orchard will stop accepting new outputs and internal transfers. Funds can be withdrawn, but an accounting rule prevents withdrawing more $ZEC from Orchard than was legitimately deposited. This design allows public auditing of the circulating supply without revealing private balances or transaction details, with any excess capital becoming locked inside Orchard. Zcash had scheduled this hardfork for July 28 after developers confirmed the patched bug raised inflation concerns.

cryptonews.ru2 gün önce 16:36

Zcash Developers Recommend Upgrading Nodes to Ironwood Fork

cryptonews.ru2 gün önce 16:36

An Undercurrent of Bitcoin Civil War: BIP-110 Raises Fork Concerns

**A Summary of the Bitcoin Governance Crisis: The BIP-110 Showdown and Forking Risks** Bitcoin is facing internal division alongside a market downturn. The core of the conflict is BIP-110, the "Reduced Data Carriage Soft Fork" proposal introduced in December 2025. It aims to restrict non-financial data (like inscriptions) in future transactions, citing concerns over node costs and Bitcoin's original purpose. The controversy lies in its activation mechanism. BIP-110 requires 55% miner support within a difficulty period. However, its voting signal has remained below 1% since monitoring began. If this threshold isn't met by the August 7, 2026 deadline (block height 961,632), compatible nodes (primarily running Bitcoin Knots) are programmed to *enforce* the new rules, rejecting non-compliant blocks. Critics warn this minority-enforced activation could split the chain. Major figures like Michael Saylor, Adam Back, and Jameson Lopp strongly oppose BIP-110. Saylor argues it sets a dangerous precedent for defining "valid" transactions and could stifle future innovations. Opponents view the enforcement strategy as a risky governance overreach, contrasting it with past upgrades that achieved over 90% consensus. BIP-110 was partly a reaction to Bitcoin Core's v30 update in October 2025, which significantly increased the default data relay limit. Core developers called this a policy change, not a consensus rule, but it prompted the creation of the Bitcoin Knots branch and, subsequently, BIP-110. Compounding the pressure, Paul Sztorc plans a separate hard fork around the same time to launch a new chain (eCash) featuring his Drivechain scaling proposal. While independent, these dual forking events create operational and market uncertainty. The market, already in a corrective phase, must now price in this governance tail risk. Analysts predict the original chain, backed by the vast majority of miners and exchanges, would likely retain primary value and liquidity if a split occurs. However, the process would be disruptive, causing short-term chaos with replay attacks, exchange confusion, and widened spreads. August 2026 presents a critical test of Bitcoin's ability to resolve deep governance disputes without fracturing.

Foresight News2 gün önce 13:10

An Undercurrent of Bitcoin Civil War: BIP-110 Raises Fork Concerns

Foresight News2 gün önce 13:10

With Less Than 1% Support, Will BIP-110 Still Force a Bitcoin Soft Fork?

**English Summary:** Despite garnering minimal support (less than 1% from miners and around 14.6% of nodes), the controversial BIP-110 proposal is poised to enter its "forced activation" window in early August. Proposed in December 2025 by Dathon Ohm and backed by Bitcoin Core developer Luke Dashjr, BIP-110 aims to temporarily restrict non-monetary data (like Ordinals and Bitcoin NFTs) in transactions for one year to reduce network "spam" and refocus Bitcoin on its monetary function. The proposal's contentious mechanism means that supporting nodes will enforce the new rules starting at block height 965,664 (late August/early September), even without reaching the 55% activation threshold. This will likely cause a chain split between nodes enforcing BIP-110 and the main chain. **Supporters**, led by Luke Dashjr and his Ocean mining pool, view BIP-110 as a necessary correction to stop what they consider an "attack" on Bitcoin—the use of block space for data storage, which they argue drives up transaction fees and burdens nodes. They believe the stricter BIP-110 chain could eventually become the longest chain. **Opponents**, including figures like Adam Back, Jameson Lopp, and Michael Saylor, argue that BIP-110 fails to solve core issues while creating new risks. Their concerns include stifling future innovation (e.g., hindering BitVM), compromising Bitcoin's censorship-resistant and decentralized ethos, introducing potential chain-split uncertainties like double-spend risks, and fracturing the ecosystem's resources and consensus. They maintain the proposal addresses a cultural problem with a flawed technical solution and are confident it will fail economically. Potential outcomes post-activation range from the BIP-110 chain stalling due to insufficient miner support, to a sustained minority chain that struggles to attract economic activity, potentially leading to a permanent hard fork—an outcome Luke Dashjr currently opposes. Most analysts and prediction markets assign a low probability (around 10%) to BIP-110 successfully becoming the dominant Bitcoin chain.

Odaily星球日报07/17 10:10

With Less Than 1% Support, Will BIP-110 Still Force a Bitcoin Soft Fork?

Odaily星球日报07/17 10:10

Those Pre-Bitcoin PoW Protocols Have Recently Been Reimplemented

This article details a recent surge in replicating pre-Bitcoin Proof-of-Work (PoW) protocols, specifically focusing on Hal Finney's 2004 RPOW (Reusable Proofs of Work). Within five days in May 2026, multiple independent builders in the Bitcoin/cypherpunk community launched projects inspired by this early electronic cash proposal. The initiative began with Fred Krueger's `rpow2.com`, a centralized but auditable system that replaced RPOW's original IBM 4758 hardware with Ed25519 signatures. Initially a faithful replica, it later adopted Bitcoin-like features (21M supply cap, difficulty adjustment) and a controversial 5.24% founder allocation. This sparked rapid forks, including `rpow4.com` which incorporated full Bitcoin parameters, a prediction market (`rpowmarket.com`), and a DEX (`rpow2swap.com`). Concurrently, Mike In Space created a prototype of Wei Dai's 1998 b-money proposal (`b-money.replit.app`), pushing the historical exploration even further back. The article contrasts these centralized, server-dependent experiments with Bitcoin's core innovation of decentralized, trustless consensus. It also highlights a parallel development: the `HASH` project on Ethereum, which uses smart contract hooks to enable a purely fair-launch, browser-mineable PoW token with 0% allocations to team or VCs. The collective activity is framed as a meme-driven, educational exploration of cypherpunk history rather than a serious financial movement, with all projects heavily disclaiming any investment value.

marsbit05/11 09:12

Those Pre-Bitcoin PoW Protocols Have Recently Been Reimplemented

marsbit05/11 09:12

One Article to Understand $UORE: The V4 Hook Project That Packs Mining, Lottery, and NFT Into a Single Transaction

An In-Depth Look at $UORE: The V4 Hook Project Packing Mining, Lotteries, and NFTs into a Single Transaction $UORE is the latest project leveraging the Uniswap V4 Hook mechanism, following in the footsteps of projects like SATO, uPEG, and Slonks. It distinguishes itself by integrating multiple functions—on-chain mining, a buy-to-enter lottery, auto-generated pixel NFTs (Orelings), and a deflationary burn mechanism—all within a single Uniswap V4 liquidity pool transaction. This complexity results in transaction gas fees that are 2-3 times higher than a standard swap. The project's tokenomics are intricate. Each whole $UORE token held automatically mints a corresponding Oreling NFT, a 32x32 pixel miner character with random traits determined by the next block's hash. Each Oreling has a Class (rarity) and Hash value, which combine to form its Mining Power for staking rewards. Rewards are distributed daily from an emission that decays by 1% daily, with an 80/20 split between stakers and a Motherlode lottery pool. A "refined-ore boost" mechanism taxes early reward claims, redistributing 10% to remaining stakers. The Motherlode lottery awards tickets for buys of ≥0.1 ETH, with winning chances scaling up to 1% for 1 ETH purchases. Wins split the pool 50% to the buyer and 50% to a random staker. A 1% buy tax is burned, and a 1% sell tax funds an automatic buyback-and-burn mechanism triggered at 0.1 ETH. The project's code is a fork of uPEG, with claimed fixes for NFT duplication and flash loan attacks. Its creator, Noah, describes it as a fusion of Solana's ORE mining concept with uPEG's V4 Hook framework. Key challenges noted include high gas costs, the narrowing attention window for V4 Hook narratives as it's the fourth such project, and significant complexity that creates a high barrier to understanding for users. The project's whitepaper notably advises users to "Read the contracts and understand the mechanics before deploying capital," underscoring its complex and fast-moving nature within a trend where the "alpha" lifespan for new projects appears to be shrinking rapidly.

marsbit05/09 02:23

One Article to Understand $UORE: The V4 Hook Project That Packs Mining, Lottery, and NFT Into a Single Transaction

marsbit05/09 02:23

Whitepaper 2.0, Two Sets of State Forks, the Rise of Clones: What Happened to Sato Overnight?

On the night of May 7, 2026, the SATO project released "Whitepaper 2.0" alongside significant front-end changes, shifting from "buy/sell" to "mint/burn" terminology. This update aimed to clarify market confusion regarding trading mechanics, token burns, and price discrepancies between its bonding curve and secondary markets. Key changes included explicitly defining the separate existence of the bonding curve pool (for minting/burning) and the secondary SATO/USDT pool, and detailing the core mathematical formulas governing the curve. Concurrently, SATO's market cap fell sharply from near $40 million to around $14.4 million. A fork project, SAT1, emerged with a similar bonding curve model but a key technical difference: SAT1 uses a single unified state variable (`ethCum`) for all core logic (minting, burning, halt trigger), whereas SATO's mechanism relies on two state variables (`ethCum` and `totalMintedFair`), which can drift apart and cause operational discrepancies. Both projects position themselves as operator-free "issuance machines" with asymptotic supply curves approaching 21 million tokens and charge a 0.3% fee on transactions, which remains in the protocol. The article emphasizes that despite intricate designs, both SATO and SAT1 are in highly volatile, sentiment-driven phases, and warns that mechanism innovation does not replace the need for personal risk management.

marsbit05/08 16:12

Whitepaper 2.0, Two Sets of State Forks, the Rise of Clones: What Happened to Sato Overnight?

marsbit05/08 16:12

Core 'Key Contributors' Depart One After Another, Has Aave's DAO Dream Shattered?

Recent weeks have seen major internal turbulence within Aave, one of DeFi’s most successful DAOs. The Aave Chan Initiative (ACI), a core governance team, announced it would cease operations and exit the ecosystem on March 3, following the departure of BGD Labs, the development team behind Aave V3, just two weeks earlier. The crisis stems from governance disputes that began in December, when Aave Labs unilaterally switched the protocol’s front-end aggregator from ParaSwap to CoW Swap, redirecting fee revenue from the DAO treasury to Aave Labs. In response, Aave Labs proposed the bundled “Aave Will Win” proposal in February, requesting $51M in funding for V4 development in exchange for routing all future product revenue to the DAO and phasing out V3. ACI strongly criticized the proposal, alleging that a significant portion of supporting votes came from addresses linked to Aave Labs, raising concerns about self-dealing and lack of transparency. Despite ACI’s attempts to introduce stricter accountability measures, their proposals were not adopted. The departures of both BGD Labs and ACI—key contributors responsible for technical development and governance—raise serious questions about Aave’s future, including technical risks associated with transitioning to V4 and the centralization of decision-making power. The situation highlights broader challenges in DAO governance, where power often remains concentrated among founders, developers despite the ideal of decentralized token-holder control. Moving forward, the resolution of the “Aave Will Win” proposal and the possibility of a protocol fork remain critical points to watch. How Aave addresses its governance flaws and rebalances power among stakeholders may determine its ability to sustain long-term growth.

比推03/03 23:09

Core 'Key Contributors' Depart One After Another, Has Aave's DAO Dream Shattered?

比推03/03 23:09

活动图片