PrahladSingh1

<p>NEAR Protocol is a proof-of-stake layer-1 blockchain built around a sharding architecture called Nightshade, which splits the network's workload across multiple parallel segments so that transaction throughput can grow as the network grows. Launched on mainnet in 2020 by the NEAR Foundation, it competes with Ethereum, Solana and other smart-contract platforms for developers building decentralized applications (dApps), DeFi protocols and Web3 products.</p>

<h2>How NEAR's Architecture Works</h2>
<p>Most blockchains process every transaction on a single chain, which creates a bottleneck as usage increases. NEAR addresses this with <strong>sharding</strong>: the network is divided into multiple shards, each handling its own subset of accounts and smart contracts simultaneously. Nightshade is NEAR's specific implementation, where each shard produces a portion of each block — called a chunk — and validators combine those chunks into a single finalized block. The result is that adding more shards can increase overall capacity without requiring every node to store or process the entire chain's history.</p>
<p>Validators on NEAR are chosen through a <strong>proof-of-stake</strong> mechanism, meaning they lock up (stake) NEAR tokens as collateral to earn the right to produce and verify blocks. Misbehavior — such as signing conflicting blocks — results in a portion of that stake being destroyed, a penalty known as slashing. Token holders who do not run their own validator node can delegate their stake to an existing validator and receive a share of the block rewards in return.</p>
<p>NEAR also uses a concept called <strong>Doomslug</strong> for fast block finality. Rather than requiring multiple rounds of voting before a block is considered final, Doomslug allows blocks to achieve practical finality after a single round of communication among validators, which keeps confirmation times short under normal network conditions.</p>

<h2>Developer Experience and the Account Model</h2>
<p>One of NEAR's most distinctive design choices is its account system. Unlike Ethereum, where an account is identified solely by a long hexadecimal address, NEAR supports <strong>human-readable account names</strong> such as <em>alice.near</em>. These names are registered on-chain and can have sub-accounts, making it easier to build applications where users interact with named contracts rather than opaque strings of characters.</p>
<p>Smart contracts on NEAR are written in <strong>Rust</strong> or <strong>AssemblyScript</strong>, the latter being a TypeScript-like language that compiles to WebAssembly. Because JavaScript developers can learn AssemblyScript relatively quickly, NEAR has positioned itself as a friendlier entry point for web developers moving into blockchain. Contracts are compiled to WebAssembly (Wasm), which NEAR's runtime executes in a sandboxed environment.</p>
<p>NEAR also introduced a feature called <strong>access keys</strong> that separates full account control from limited, application-specific permissions. A user can grant a dApp a key that is only allowed to call specific contract functions and spend up to a defined amount of NEAR, without exposing the master key that controls the whole account. This reduces the risk of a malicious or compromised application draining a user's wallet.</p>

<h2>The Rainbow Bridge and Cross-Chain Connectivity</h2>
<p>NEAR operates the <strong>Rainbow Bridge</strong>, a trustless bridge that allows assets and data to move between NEAR and Ethereum. Unlike bridges that rely on a small group of validators to custody funds, the Rainbow Bridge uses light clients — compact versions of each chain's consensus logic running on the other chain — to verify transfers cryptographically. This design means neither side has to trust a centralized intermediary, though it does require users to pay gas fees on both networks when moving assets.</p>
<p>The project has also developed <strong>Aurora</strong>, an Ethereum Virtual Machine (EVM) running as a smart contract on NEAR. Aurora allows Ethereum-compatible dApps to deploy on NEAR with minimal code changes, giving developers access to NEAR's throughput while retaining compatibility with Ethereum tooling such as MetaMask and Hardhat. Aurora operates as a separate layer on top of NEAR rather than a distinct blockchain, so it inherits NEAR's security model.</p>

<h2>The NEAR Token: Utility and Staking</h2>
<p>The NEAR token serves several functions within the protocol. It is used to pay <strong>transaction fees</strong> (called gas on NEAR), to stake as a validator or delegator, and to participate in on-chain governance. A portion of each transaction fee is burned — permanently removed from supply — which introduces a deflationary pressure that partially offsets the new tokens issued as staking rewards.</p>
<p>Storage on NEAR is also priced in NEAR tokens. Accounts must maintain a minimum balance proportional to the amount of on-chain storage they use, a model NEAR calls <strong>storage staking</strong>. This creates an economic incentive to clean up unused data and keeps the state size manageable over time.</p>
<p>NEAR ranks among the top 25 cryptocurrencies by market capitalization, reflecting meaningful adoption relative to the broader landscape of layer-1 blockchains. Search interest has risen noticeably in late 2026, coinciding with broader ecosystem developments — including the <a href="https://www.cryptoknowmics.com/news/cryptocurrency-news/">launch of a U.S. spot NEAR ETF</a>, which marked a significant step in institutional accessibility for the token.</p>

<h2>Risks and Practical Considerations</h2>
<p>NEAR's sharding model is technically ambitious, and the full multi-shard vision has been rolled out incrementally. Cross-shard transactions — where a contract on one shard needs to interact with a contract on another — introduce additional latency and complexity compared with single-shard calls. Developers building applications that span multiple shards must account for this asynchronous communication, which is more involved than writing contracts on a single-shard chain.</p>
<p>Competition among layer-1 blockchains is intense. Ethereum's own scaling roadmap, combined with a mature ecosystem of layer-2 networks, means NEAR must continuously demonstrate advantages in speed, cost or developer experience to attract and retain builders. Solana, Aptos, Sui and others are pursuing similar goals with different technical trade-offs, and developer mindshare is a finite resource.</p>
<p>As with any proof-of-stake network, staking rewards are denominated in the native token, so their real-world value fluctuates with the token's price. Delegators should also evaluate the track record and commission rates of validators before choosing where to stake, since a validator's downtime or misbehavior can affect rewards. The access-key model reduces but does not eliminate smart-contract risk; auditing any application before granting it permissions remains good practice.</p>
<p>For those researching NEAR as part of a broader look at the <a href="https://www.cryptoknowmics.com/news/ethereum/">Ethereum ecosystem</a> and its competitors, understanding how each chain handles scalability trade-offs is more useful than focusing on short-term price movements. NEAR's architectural choices reflect a clear thesis — that sharding is the most sustainable path to scale — and evaluating that thesis against alternatives is the right starting point for any serious assessment of the project.</p>

NEAR Protocol Explained: What It Is and How It Works

<p>Cryptocurrency exchange Bitget has resumed Bitcoin withdrawals after temporarily suspending them in the wake of a security incident, according to reports published on 28 September 2026 by <a href="https://cointelegraph.com/news/bitget-btc-withdrawal-hacker-eth-swap-thorchain" target="_blank" rel="nofollow noopener">Cointelegraph</a> and <a href="https://www.coindesk.com/tech/2026/09/28/thorchain-rejects-bitget-request-to-block-hacker-as-usd6-million-moves-to-bitcoin" target="_blank" rel="nofollow noopener">CoinDesk</a>. An alleged hacker moved roughly $6 million in Ethereum through the decentralized cross-chain protocol THORChain, converting the funds into Bitcoin — a move that THORChain's network declined to block despite a direct request from Bitget.</p>

<h2>Key Takeaways</h2>
<ul>
<li>Bitget temporarily suspended Bitcoin withdrawals following a security breach before restoring access to users.</li>
<li>The alleged hacker converted approximately $6 million in ETH to BTC using the THORChain cross-chain protocol.</li>
<li>THORChain rejected Bitget's request to intervene and block the suspicious transactions, citing its decentralized design.</li>
</ul>

<h2>Main Details</h2>
<p>Bitget, a major centralized cryptocurrency exchange, paused Bitcoin withdrawals after detecting what it described as a security incident. The exchange subsequently restored withdrawal functionality once it had assessed the situation, though the precise timeline of the suspension and the full scope of the breach have not been publicly confirmed by Bitget at the time of writing.</p>

<p>According to CoinDesk, the alleged hacker used THORChain — a decentralized liquidity protocol that enables native cross-chain swaps without wrapped tokens or centralized intermediaries — to convert approximately $6 million worth of Ethereum (ETH) into Bitcoin (BTC). This technique is increasingly common among bad actors seeking to obscure the origin of stolen funds, as cross-chain swaps complicate blockchain tracing efforts.</p>

<p>Bitget reportedly contacted THORChain and requested that the protocol take action to block or freeze the transactions linked to the alleged hacker. THORChain declined the request. The protocol's governance structure and technical architecture are designed to be permissionless and censorship-resistant, meaning no single party — including the THORChain development team — can unilaterally halt or reverse user transactions. This design philosophy, while central to decentralized finance (DeFi), creates significant challenges for exchanges and law enforcement when attempting to recover stolen assets.</p>

<h2>Evidence and Source Information</h2>
<p>The incident was reported concurrently by two independent, reputable crypto news outlets. Cointelegraph published its account at 11:05 UTC on 28 September 2026, followed by CoinDesk at 12:13 UTC the same day. Both outlets corroborate the core facts: Bitget's withdrawal suspension and resumption, the ETH-to-BTC swap via THORChain, the approximate $6 million figure, and THORChain's refusal to intervene.</p>

<p>The identity of the alleged hacker, the specific exploit vector used to breach Bitget, and the total value of assets affected beyond the confirmed $6 million THORChain movement remain unconfirmed in available source material. CryptoKnowmics will update this article as further verified information becomes available.</p>

<h2>Market, Regulatory and Industry Context</h2>
<p>The incident highlights a recurring tension in the crypto industry between decentralized protocol design and the practical needs of centralized exchanges facing security breaches. THORChain has previously been at the center of similar controversies. In 2021, the protocol suffered multiple exploits itself, losing tens of millions of dollars across separate incidents. More recently, THORChain attracted scrutiny in early 2025 when its community debated whether to pause the network to prevent alleged proceeds from the Bybit hack — one of the largest exchange hacks in crypto history — from being laundered through its liquidity pools. That debate ended without a network halt, reinforcing the protocol's censorship-resistance stance.</p>

<p>For centralized exchanges, the use of decentralized cross-chain protocols by hackers represents a growing operational and reputational risk. Unlike centralized bridges or exchanges, DeFi protocols such as THORChain have no customer verification requirements and no mechanism for transaction reversal, making asset recovery extremely difficult once funds have moved on-chain.</p>

<p>From a regulatory standpoint, incidents of this nature are likely to attract attention from financial regulators who have increasingly scrutinized DeFi protocols' roles in facilitating the movement of illicitly obtained funds. The Financial Action Task Force (FATF) has previously flagged cross-chain bridges and swap protocols as high-risk tools for money laundering in its guidance on virtual assets.</p>

<p>Readers can follow broader <a href="https://www.cryptoknowmics.com/news/cryptocurrency-news/" target="_blank" rel="noopener">cryptocurrency news</a>, <a href="https://www.cryptoknowmics.com/news/bitcoin/" target="_blank" rel="noopener">Bitcoin developments</a>, and <a href="https://www.cryptoknowmics.com/news/ethereum/" target="_blank" rel="noopener">Ethereum updates</a> on CryptoKnowmics, including ongoing coverage of <a href="https://www.cryptoknowmics.com/news/tag/cryptocurrency-regulation/" target="_blank" rel="noopener">cryptocurrency regulation</a> as it relates to DeFi oversight.</p>

<h2>What Happens Next</h2>
<p>With the alleged hacker's funds now converted to Bitcoin and the THORChain swap complete, on-chain investigators and blockchain analytics firms are likely monitoring the destination wallets for further movement. Bitcoin's transparent ledger means the funds can be tracked, though mixing services or additional cross-chain hops could further obscure their trail.</p>

<p>Bitget has not publicly disclosed whether it has filed a report with law enforcement authorities or engaged a blockchain forensics firm. The exchange's decision to resume withdrawals suggests it has stabilized its systems, but users and industry observers will be watching for a formal post-incident report detailing the breach's scope, cause and remediation steps. The broader DeFi community will also be monitoring whether this incident renews calls for THORChain and similar protocols to develop voluntary compliance frameworks for handling verified theft proceeds.</p>

Author : Prahlad

NEAR Protocol Explained: What It Is and How It Works

Bitget Restores BTC Withdrawals After Hacker Routes $6M Through THORChain