BTC $80,067.67 -0.87%
ETH $2,322.56 -0.90%
BNB $740.14 -2.10%
XRP $1.29 -2.02%
SOL $100.37 -1.17%
TRX $0.3311 -0.03%
DOGE $0.0787 -0.78%
ADA $0.2001 -1.83%
BCH $278.88 -6.01%
LINK $11.60 -0.07%
HYPE $88.00 +9.04%
AAVE $132.60 -0.12%
SUI $0.9212 -0.89%
XLM $0.1701 +0.20%
ZEC $1,262.55 -2.22%
AAPL $348.06 +0.42%
AMZN $249.21 -1.66%
GOOGL $288.16 -11.25%
MSFT $540.04 +1.72%
META $618.11 -0.76%
NVDA $213.94 -2.67%
TSLA $403.35 -1.86%
SNDK $1,363.09 +0.57%
INTC $92.55 -2.78%
SPCX $142.91 -4.03%
MU $953.84 -0.52%
AMD $563.48 -0.95%
BTC $80,067.67 -0.87%
ETH $2,322.56 -0.90%
BNB $740.14 -2.10%
XRP $1.29 -2.02%
SOL $100.37 -1.17%
TRX $0.3311 -0.03%
DOGE $0.0787 -0.78%
ADA $0.2001 -1.83%
BCH $278.88 -6.01%
LINK $11.60 -0.07%
HYPE $88.00 +9.04%
AAVE $132.60 -0.12%
SUI $0.9212 -0.89%
XLM $0.1701 +0.20%
ZEC $1,262.55 -2.22%
AAPL $348.06 +0.42%
AMZN $249.21 -1.66%
GOOGL $288.16 -11.25%
MSFT $540.04 +1.72%
META $618.11 -0.76%
NVDA $213.94 -2.67%
TSLA $403.35 -1.86%
SNDK $1,363.09 +0.57%
INTC $92.55 -2.78%
SPCX $142.91 -4.03%
MU $953.84 -0.52%
AMD $563.48 -0.95%

v2

All
Article
Flash

first_img Zakura released the experimental P2Pv2, and the testnet is now running in dual stack

Zakura has announced an experimental network layer P2Pv2 for Zcash nodes, intended to replace the old protocol inherited from Bitcoin. This layer combines high-throughput networking, resource control, and a consensus engine tested for properties, allowing developers to add services without permission. Zakura states that approximately 50,000 transactions per second require each full node to continuously receive about 100MB/s of block data, while the 25-second block of NU7 can carry a maximum of 2MB, with existing network throughput differing by more than a thousand times from this rate. Tachyon can reduce the proof after entering the block, but the network still needs to propagate a large number of individual transactions.P2Pv2 replaces the protocol stack from about a decade ago with protocols that can be optimized for latency, throughput, or robustness, allowing a secure connection to carry multiple independent services. The transport layer uses its own zakura-quic, based on quinn-proto, utilizing QUIC and TLS 1.3, and authenticating peers with Ed25519 node identity. Related changes remove the dependency on Iroh, allowing nodes to configure socket buffers, flow control windows, timers, and connection admission before the TLS handshake. The new transport directly connects to peer addresses without using relays, external address lookups, automatic port mapping, or QUIC NAT traversal. Nodes sign identities, addresses, protocol scopes, and service IDs, allowing clients to find peers based on specific services.The independent component zakura-header-chain verifies block headers and retains competing branches in a directed acyclic graph, selecting the best qualified chain. Block synchronization schedules requests based on the delivery rates measured by each peer, and a verified commitment tree is used to skip the reconstruction of Sapling, Orchard, and Ironwood trees for each block. Currently, the Mainnet still defaults to the old P2P stack, while the Testnet and Regtest run dual stacks by default, with the native protocol version being p2p-v2/3. Zakura notes that P2Pv2 still has known denial-of-service risks and has not yet become a hardened trust boundary; production hardening, resource control, and block relay protocols are still in progress.

Polygon Labs: Bor v2.1.3 released, fixing two DoS security vulnerabilities

Polygon Labs official announcement, Bor v2.1.3 is officially released to the public, previously distributed in private version form to validators and major infrastructure providers. This update fixes two medium-severity denial-of-service vulnerabilities in BlockSTM V2 parallel block execution, both submitted by security researchers through the Immunefi bug bounty program.Unbounded keccak256 cache issue: Attackers can fill hundreds of MiB of cache during the speculative execution phase by constructing specific transactions, leading to node memory exhaustion and delayed block production. The fix is to set a capacity limit on the shared cache. Repeated code hash calculation issue in parallel execution: A single transaction can cause the parallel processor to take about 11 seconds, severely affecting node activity. The fix is to cache code hash results on a per-transaction basis.In addition, this update also includes several internal hardening measures: the transaction pool address filtering adds interception for EIP-7702 SetCode authorization, RPC batch execution pool concurrency limit fixes, consistency fixes for reading balances across self-destruct boundaries in parallel execution, and an automatic cleanup mechanism for pending transactions (default 3 hours). The affected versions are Bor v2.1.1 and v2.1.2. v2.1.3 is a non-hard fork, and nodes can upgrade individually without coordination. No exploitation records of the two vulnerabilities have been found on the mainnet and testnet Amoy.

Polymarket launched Protocol V2, reconstructing the underlying architecture of the existing protocol

Polymarket has launched the next-generation prediction market smart contract system, Polymarket Protocol V2, which reconstructs the underlying architecture of the existing protocol. The current protocol is based on the Gnosis Conditional Tokens Framework from 2019, requiring additional adapters, trading contracts, and authorization processes for each new market type; V2 unifies this by using a single ERC1155 position token contract, pUSD collateral assets, trading platform contracts, and routers.V2 adopts a modular architecture, initially supporting binary, atomic negative risk, incremental negative risk, and composite markets, and connects to UMA, Chainlink, and other future oracles through a new OracleAggregator. The protocol natively supports cross-chain positions, collateral assets, and settlement results, reserving a foundation for future multi-chain deployments; all contracts can be upgraded under a secure governance process.V2 has been audited by Cantina, Certora, Quantstamp, SigmaPrime, Zellic, and Pashov, with formal verification completed by Certora, offering a maximum bounty of $5 million for critical vulnerabilities. Polymarket will operate a limited number of grayscale markets in the production environment from October 5 to 30, with plans to switch new markets to V2 starting November 2, along with the launch of Data API V2 built on Rust and an internal on-chain indexer.

first_img Polymarket released Protocol V2, planning to switch to a new market in November

The prediction market platform Polymarket has announced the launch of Polymarket Protocol V2, calling it the next-generation prediction market smart contract system. The existing contracts are based on the conditional token framework from Gnosis in 2019, with various markets subsequently integrated through additional adapters. V2 rebuilds position tokens from scratch, using a single ERC1155 position contract, a single collateral pUSD, a single exchange, and a single routing, with position IDs directly encoding market type, market, and outcome.V2 supports binary, atomic negative risk, incremental negative risk, and composite markets with a modular architecture, and expands position operations to enhance capital efficiency. Settlement is accessed through OracleAggregator, integrating pluggable oracles, including UMA, Chainlink, and future sources. The protocol features built-in cross-chain bridging designs for positions, collateral, and settlement, and can be upgraded through governance processes. Future research directions include scalar settlement and directional collateral return.The code has been audited by Cantina, Certora, Quantstamp, SigmaPrime, Zellic, and Pashov, and has undergone formal verification by Certora, with a maximum critical vulnerability bounty of $5 million. The canary market will operate in the production environment from today until October 30, with new markets tentatively scheduled to switch on November 2. At the same time, Data API V2 will be launched, based on a self-developed on-chain indexer, supporting V2, unified response formats, and cursor pagination.

Liquid Network releases emergency fix: Elements v23.3.4 fixes Proof verification cache vulnerability

Liquid Network has released the latest update stating that the emergency version Elements v23.3.4 is now online. Functionary nodes have immediately begun upgrading and all Liquid node operators are advised to synchronize updates. This version addresses the previously discovered Proof verification cache vulnerability and strengthens the cache keys used for Range Proof.Regarding network recovery, Blockstream states that it is still formulating a recovery plan, which is expected to proceed in three phases: restoring block production while continuing to suspend Peg operations; replaying verified valid transactions; and restoring Peg operations after the network status is fully restored and funds are confirmed to be returned. Currently, the first two phases are being tested in parallel, and any phase will only advance once safety is confirmed. Liquid Network indicates that Elements v23.3.4 has completed multiple rounds of internal and external reviews, with participants including the Bitcoin Red Team, Alpen Labs, and other teams.At the same time, Liquid Network reminds users to be vigilant against fraudulent upgrade websites exploiting this incident. Information should only be obtained through official Liquid Network and Blockstream channels, and users should never send funds to strangers or disclose private keys or recovery phrases.
app_icon
ChainCatcher Building the Web3 world with innovations.