Invest ideasNews
23 May 2026, 11:16
Bitcoin Drops to $74,300 as Spot ETFs Bleed $2.26B, SEC Greenlights Nasdaq Options
Bitcoin News Bitcoin sank to $74,305 in early Saturday trading, marking its lowest print since April 20 and capping a brutal stretch that has shaved roughly 10% off the cryptocurrency from a recent...
23 May 2026, 11:14
NEAR’s AI Breakout: Why Dynamic Resharding and Quantum-Safe Signing Matter
AI agents are moving on-chain, and the platforms that serve them must scale elastically while staying secure for decades. NEAR’s sharded design and account model put it in a unique spot as builders rethink infrastructure for autonomous apps and data-heavy workloads. This article unpacks why two ideas—dynamic resharding and quantum-safe signing—are central to NEAR’s AI moment. You’ll learn how they work, what they change for developers, the risks to weigh, and pragmatic steps to prepare. Quick Answer NEAR’s dynamic resharding is about automatically splitting and merging state shards to match demand, which can smooth fees and throughput for spiky AI workloads. Quantum-safe signing refers to adopting post-quantum cryptography (PQC) or hybrid keys so accounts remain secure if powerful quantum computers emerge. Together, they point to an elastic and future-resilient stack: scale when agents surge; rotate keys as cryptography evolves. Elastic capacity: shards adapt to load instead of forcing apps to migrate manually. Better UX: steadier fees and lower congestion during AI-driven bursts. Crypto agility: account-level key rotation enables gradual PQC adoption. Risk-aware: resharding adds cross-shard design complexity; PQC adds overhead. How does NEAR’s dynamic resharding actually work? NEAR’s core architecture, Nightshade, partitions state across multiple parallel shards, with validators producing “chunks” for each shard and assembling them into blocks. Dynamic resharding is the capability to automatically split a hot shard into multiple shards or merge underused shards, based on network conditions. The intent is to keep capacity responsive without manual coordination by app teams. In practice, this kind of elasticity aims to reduce hotspots. When an AI-driven app spikes (think inference payments or agent-to-agent bidding), the shard hosting its state can be split to distribute load, while quieter periods allow merging to reduce overhead. This helps smooth fees and confirms transactions faster under pressure. NEAR has iterated sharding in stages (e.g., Simple Nightshade, incremental rollout of more shards). Automatic split/merge has been on the roadmap and has seen testing and progressive deployment. Because production details evolve, builders should consult NEAR’s official documentation for current status and parameters before relying on specific behaviors. Key developer implications include avoiding reliance on static shard IDs, designing contracts for cross-shard calls, and planning for the possibility that your contract’s state may be migrated as the network optimizes layout. Why do AI agents and data-heavy apps benefit from elastic sharding? AI agents behave unpredictably. A model update, a viral prompt market, or a batch of on-chain inference tasks can produce sudden surges. Elastic sharding is well-suited to bursty demand: it adds capacity where needed, then rightsizes when traffic normalizes, avoiding “build for peak” costs. Many AI-on-chain patterns—pay-per-call inference, streaming data attestations, and marketplace-style auctions—generate short, intense periods of activity centered on a few contracts. Dynamic resharding can keep these hotspots from degrading network-wide UX, preserving low-latency confirmations for users and bots. Crucially, elasticity improves predictability. If fees and blockspace availability are steadier during spikes, it’s easier to price an inference marketplace or guarantee a service-level objective (SLO) for agent transactions. Stable fee envelopes also simplify budgeting for teams that pre-fund agent wallets. Checklist for AI builders on NEAR Avoid assuming a fixed shard layout; expect state to move. Design idempotent cross-contract calls to tolerate retries. Instrument end-to-end latency and cross-shard hop counts. Use queues or batching for bursts; backoff on congestion signals. Pre-fund agent wallets with margins for transient fee variance. What is “quantum-safe signing,” and why care now? Quantum-safe (post-quantum) signing refers to digital signature schemes designed to resist attacks from quantum computers. Today’s common signatures (like ed25519 and secp256k1) could be vulnerable to sufficiently powerful quantum adversaries running Shor’s algorithm. While timelines are uncertain, the “harvest-now, attack-later” risk is real: adversaries can record traffic today and attempt to break keys in the future. Standards bodies have been selecting PQC algorithms suitable for general use. The U.S. National Institute of Standards and Technology (NIST) has announced candidates for standardization, including CRYSTALS-Dilithium, Falcon, and SPHINCS+. These schemes vary in signature size, verification speed, and implementation complexity. Production blockchains will likely adopt “hybrid” approaches first—combining classical and PQ signatures—so that either can validate an action, enabling staged migration. For Web3 teams, this is not just theoretical. Long-lived treasuries, identity systems, and cross-chain bridges require crypto agility now because migration takes time: wallets, SDKs, hardware modules, and smart contracts must agree on formats and recovery paths. Warning: PQC adoption is a multi-year journey. Start with crypto agility—policies and tooling that let you rotate or add keys—before committing to a specific algorithm. Verify current guidance in official standards and NEAR documentation. Can NEAR’s account model simplify PQC migration? NEAR’s account model differs from many chains: accounts are human-readable, and each account can hold multiple access keys with distinct permissions. Full-access keys sign any transaction; function-call keys authorize specific contract calls with spending limits. This native key granularity supports safer experimentation with new signature schemes and staged rollouts. In a PQC context, teams could add a new access key that uses a PQ or hybrid signature scheme once supported by the runtime or via a contract-based wallet approach. During the transition, actions might require both a classical and a PQ signature (multi-algorithm multisig), or a threshold of keys including a PQ key, reducing single-algorithm failure risk. NEAR’s support for multisig and account-level key rotation can help large treasuries and infrastructure providers pilot crypto-agile policies: rotate keys on a schedule, test on canary accounts, and fall back if issues arise. While native PQC is an ecosystem decision and may be introduced incrementally via standards and contracts, NEAR’s flexible accounts provide a realistic path to adopt it without disrupting users. As always, consult NEAR’s official docs for current capabilities and proposals, and consider third-party audits for any custom wallet or multisig logic. How does NEAR compare for AI-era scaling? Different L1s and L2 stacks are tackling AI-era workloads with varied philosophies. Elastic sharding is one path; monolithic high-throughput designs and rollup-centric models are others. Below is a high-level comparison focused on developer experience for AI agents and crypto agility. Verify specifics in each ecosystem’s documentation, as implementations evolve. PlatformScaling approachElasticityAccount modelPQC readiness (qualitative)NEARSharded L1 (Nightshade)Designed for dynamic resharding (split/merge)Named accounts, multiple access keys, native multisigFavorable via key rotation and hybrid policies; native PQC subject to ecosystem rolloutEthereum (+ rollups)Base L1 + L2 rollups (modular DA/execution)Elasticity via L2s scaling independentlyExternally owned accounts + contract wallets (ERC-4337)Likely hybrid via smart wallets first; standards guided by NIST and communitySolanaMonolithic high-throughput with parallel runtimeElasticity via hardware scaling and scheduler optimizationsKeypairs per account; program-derived addressesResearch ongoing; migration paths require wallet/runtime upgradesOther sharded L1sVarious (state or execution sharding)Some support resharding conceptsVaries (account abstraction maturity differs)Mixed; many exploring hybrid signatures For AI agent builders, the trade-off is clear: NEAR’s elasticity aims to reduce operational surprises during bursty workloads while its account model can ease crypto-agile upgrades. Rollup ecosystems offer modularity and choice, but add cross-rollup fragmentation. Monolithic chains simplify composability but rely more on hardware and scheduler headroom during spikes. What are the risks and trade-offs to weigh? No scaling or security path is free. Dynamic resharding and PQC introduce their own complexities that architects must confront early, especially for AI systems where downtime or mispriced fees break product promises. First, resharding adds cross-shard coordination. Contracts that synchronously depend on other contracts may experience extra hops and latency variance if they land on different shards. Tooling and design patterns (asynchronous messaging, retries, timeouts) become essential. State migration also raises observability needs: you’ll want alerts when shard layouts change. Second, PQC brings performance and UX considerations. Many PQ signatures are larger than today’s, affecting transaction sizes, storage, and bandwidth. Verification costs can be higher. Hardware wallets and secure enclaves need firmware updates, and backup formats must be rethought. Hybrid schemes—using both classical and PQ signatures—mitigate risk but compound complexity. Finally, both features require governance and standards. You need clear policies for key rotation, incident response if a PQ scheme is deprecated, and a way to communicate changes to users. On the resharding side, published parameters, dashboards, and testnets are critical so teams can rehearse migrations safely. What should builders do next? Preparation beats prediction. You don’t need to wait for a specific algorithm or shard layout to start reducing risk. Treat this as an engineering program with milestones you control. Start with crypto agility. Inventory all keys, define rotation cadences, and implement multisig or threshold policies that you can later extend with hybrid PQ keys. Maintain an allowlist of supported algorithms per environment and make it upgradable via audited governance. Then, harden for resharding. Avoid shard-coupled assumptions, use asynchronous patterns, and load test with synthetic bursts that mimic AI traffic. Observe P50/P95/P99 latencies across shard boundaries and profile gas/fee sensitivity. Action plan for the next quarter Read NEAR’s sharding and account docs and verify current resharding status: NEAR Documentation . Implement account-level key rotation on staging; add an auxiliary key and exercise recovery paths. Pilot a contract wallet that can accept multiple signature schemes (classical today; PQ-ready interface). Add cross-shard observability: shard layout alerts, hop counters, and fee/latency dashboards. Run chaos drills: simulate shard splits/merges and key compromise; document operator playbooks. Track PQC standards at NIST: NIST PQC . Common Mistakes Hardcoding shard assumptions: Designing contracts that rely on static shard IDs or synchronous calls to a specific shard. Fix by using asynchronous patterns and avoiding storage layouts that assume immobility. Skipping key rotation drills: Waiting for a PQC “final answer” before practicing rotations. Fix by instituting regular rotations and canary accounts so you can swap algorithms later without user pain. Underestimating PQC overhead: Assuming signature sizes and verification costs are negligible. Fix by benchmarking larger payloads, adjusting fee buffers, and planning storage impacts. Neglecting wallet UX: Rolling out new key types without clear recovery flows. Fix by updating backup formats, educating users, and ensuring hardware/software wallet support. One-shot migrations: Flipping all keys to a new scheme at once. Fix by adopting hybrid signatures and phased rollouts with rollback plans. Thin observability: Lacking metrics on cross-shard latency, failure rates, and layout changes. Fix by instrumenting hop counts, queue depths, and alerting on shard reconfigurations. For more editorial insights and hands-on explainers as this space evolves, visit Crypto Daily . Frequently Asked Questions Does dynamic resharding break composability across contracts? Composability remains, but it becomes more asynchronous. Cross-shard calls introduce latency variance and potential retries. Good patterns include message queues, timeouts, and designing contracts to tolerate eventual consistency. Testing with simulated shard splits helps catch brittle assumptions. Will dynamic resharding lower my fees automatically? It can help by distributing load, which reduces hotspots that drive fees up. But fees still respond to demand and network parameters. Design with buffers and surge policies rather than assuming a fixed fee floor. How soon do I need quantum-safe signatures? No one can guarantee a timeline for practical quantum attacks. However, long-lived assets and identities should prioritize crypto agility now—multi-key accounts, rotation playbooks, and support for hybrid schemes—so they can adopt PQC without disruption when the ecosystem is ready. Which PQC algorithms are most likely for blockchains? NIST’s selections—such as CRYSTALS-Dilithium, Falcon, and SPHINCS+—are leading candidates. Each has trade-offs in key/signature size and verification speed. Many chains will likely start with hybrids that pair a classical signature with a PQ signature to ease migration and de-risk early adoption. Can I implement PQC on NEAR today? Teams can prepare via contract wallets, multisig, and rotation policies that are PQ-ready in interface and storage. Native support for specific PQ schemes depends on ecosystem standards and runtime upgrades. Check NEAR’s docs and community proposals before implementing custom cryptography. How do I avoid vendor lock-in with PQC? Favor standards-based algorithms, use upgradable wallets with auditable governance, and store metadata that indicates the signing scheme. Keep migration paths to add or retire algorithms without changing addresses where possible. What’s the best way to communicate these changes to users? Provide clear timelines, staged rollouts, and recovery guides. Offer test environments for users to try new wallets or keys. For treasuries, publish rotation calendars and sign-off procedures. Transparency reduces confusion during resharding events or cryptographic upgrades. Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
23 May 2026, 11:12
French-Moroccan man sentenced to 25 years in prison for France crypto kidnaps
A French-Moroccan man convicted of organizing some of the recent daring kidnappings of crypto figures in France has been sentenced to 25 years in prison. The news comes amid a growing debate in French society over the massive number of data leaks in the country that are compromising personal security. Moroccan court sends crypto kidnapper to prison The Court of Appeal in the Moroccan city of Tangier gave Mohamed Hamid Bajou the harsh sentence on Thursday, May 21, local and French media reported. The 25-year-old man is the alleged mastermind of a gang that committed a series of brazen abductions of wealthy individuals in France, including prominent people from the crypto space. Bajou was facing serious charges, the French crypto information portal Journal du Coin noted in an article on Saturday, quoting a post by the Moroccan news website Tanja7 from Friday. These included establishing a criminal group, kidnapping, unlawful detention and torture for ransom, attempted premeditated murder, illegal possession of firearms, and drug trafficking. One of Bajou’s victims was David Balland, a co-founder of Ledger , the French company known for its popular hardware cryptocurrency wallets. The crypto entrepreneur was abducted in January 2025 along with his female partner at their home in Central France. The attackers demanded a 10-million-euro ransom, and Balland had a finger cut off before the couple was rescued by the French police. This was not the only such case. Another crypto executive, kidnapped in May 2025, also lost a finger before his release. The Moroccan court ordered Bajou to pay 1 million dirhams (nearly $110,000) to each of the individuals known to have been targeted by his gang. Convicted kidnapper denies all charges Mohamed Bajou was arrested in Tangier in June last year. He was wanted under a Red Notice issued by Interpol on the request of French authorities. At the time, media reports identified him as “Badiss Mohamed Amide Bajjou.” During a search at his home, Moroccan law enforcement found a whole arsenal of bladed weapons, hidden in the apartment’s ventilation ducts. At the time, the Moroccan prosecutor leading the probe stated that the suspect posed a serious threat, noting that he was evidently planning his next move. Investigators added that seized messages and other analyzed correspondence indicated he was indeed the mastermind of the kidnapping operation. However, Bajou denied all charges during the subsequent trial. He maintained he left France and settled in Morocco , where he worked on his grandfather’s farm. He insisted that the accusations against him were based on false statements made by a cousin, who was allegedly motivated by a family conflict. Mohamed Bajou also disputed the authorities’ claims that the victims had formally identified him before he was implicated. Data leaks blamed for string of kidnappings France has been hit by a wave of kidnappings of crypto figures and their family members since last year. The attacks are continuing despite multiple arrests . The public debate over what’s causing the phenomenon has been growing, with Telegram founder Pavel Durov recently warning that leaks of personal data may be putting crypto holders at risk. Bajou will certainly be succeeded by someone else until more than 6,000 leaks a year continue to fuel black markets for such information, Journal du Coin remarked in its piece, adding: “A stolen file containing an address, estimated net worth, and lifestyle habits is enough to transform a Bitcoin holder into an operational target.” All the attackers need is one such file, an address, and a weapon, the French crypto website noted, calling to condemn the “digital negligence” that made this possible. In his post in late April, Durov, who holds a French passport, alleged that tax officials in France are “selling crypto owners’ data to criminals,” on top of “massive tax database leaks.” The smartest crypto minds already read our newsletter. Want in? Join them .
23 May 2026, 11:05
Trump’s Latest Fintech Push Could Open an Unseen Door for Ripple & XRP at the Federal Reserve
Trump’s Fintech Order Reopens the Fed Access Debate, Putting Ripple Back in Focus President Donald Trump’s recent fintech executive has reopened a long-standing policy debate: who should have direct access to America’s core financial infrastructure? As highlighted by RippleXity, the heart of the order is a review of the rules governing access to Federal Reserve payment systems such as Fedwire and FedNow. Today, those rails are largely limited to federally insured banks, meaning fintech and crypto firms must rely on partner banks to move money through the system indirectly. The order does not remove those restrictions. Instead, it instructs regulators, including the Federal Reserve, to reassess whether frameworks built for a traditional banking era still make sense in a financial system now defined by real-time payments, digital assets, and cross-border settlement demands. More importantly, this shift in tone is particularly relevant for companies like Ripple. Delving Deeper into Ripple’s Fed Ambitions Ripple has long focused on blockchain-based infrastructure for cross-border payments and settlement. In 2025, one of its regulated entities applied for a Federal Reserve Master Account, which if approved would allow direct access to central bank payment rails without relying on intermediary banks. The application remains under review, with no indication of approval. Furthermore, Ripple has continued to feature in broader policy discussions around whether U.S. payment infrastructure is ready for modern financial technologies, including during congressional scrutiny of the Federal Reserve’s operational readiness. Why does the current development matter? Well, there is more than meets the eye since Trump’s order does not single out any company, but it does force regulators to formally revisit long-standing boundaries between banks and non-bank financial innovators, boundaries that have remained largely unchanged for decades. In this context, Ripple is often discussed as part of a wider infrastructure conversation. Direct access to Federal Reserve systems could, in theory, reduce settlement friction and improve efficiency in cross-border payments with XRP consequently serving as a potential liquidity bridge asset. Moreover, growing momentum around broader crypto legislation, including how the proposed CLARITY Act could be an ideal XRP stepping stone has added to industry expectations that regulatory definitions are gradually evolving. Ultimately, the significance of the current moment is not that the system is changing, but that it is being re-examined. Whether this leads to expanded access for non-bank players like Ripple and its native token XRP, or simply reinforces existing boundaries, will depend on how regulators balance innovation with financial stability in the years ahead.
23 May 2026, 10:25
Chinese Man Sentenced to 12 Years for Stealing Friend’s Bitcoin
BitcoinWorld Chinese Man Sentenced to 12 Years for Stealing Friend’s Bitcoin A Chinese court has finalized a 12-year and seven-month prison sentence for a man convicted of stealing and selling Bitcoin belonging to an acquaintance. The case, which highlights the growing legal scrutiny around cryptocurrency custody and trust, was decided by the People’s Procuratorate of Changshan District in Fuzhou City. Theft Through Breach of Trust According to court documents, the convicted individual, identified only as Lin, was asked by the victim, Wang, for assistance in cashing out Bitcoin in late 2020. During this process, Lin secretly obtained the private key to Wang’s cryptocurrency wallet from his computer. He then transferred four Bitcoin to his own account and subsequently sold the assets, realizing an illicit profit of approximately 900,000 yuan (about $124,000 at the time of the theft). The victim did not discover the missing assets until 2024, when he reported the theft to authorities. This led to Lin’s arrest and prosecution. An appellate court upheld the original sentence, which also included a fine of 300,000 yuan (approximately $41,000). Legal and Market Implications This case underscores the legal risks associated with self-custody of cryptocurrency, particularly when relying on third parties for technical assistance. In China, where cryptocurrency trading has been effectively banned since 2021, legal cases involving digital assets are often handled under broader theft or fraud statutes. The severity of the sentence — over 12 years for a theft of roughly $124,000 — reflects the serious view Chinese courts take on crimes involving digital assets, even when the value is relatively modest by international standards. What This Means for Crypto Owners For cryptocurrency holders, this case serves as a stark reminder of the importance of private key security. The theft was only possible because the victim shared access to his computer and wallet credentials. Security experts consistently recommend using hardware wallets, never sharing private keys, and avoiding assistance from untrusted parties for transactions. The long delay between the theft and its discovery — nearly four years — also highlights the difficulty of tracking stolen cryptocurrency without robust record-keeping. Conclusion The finalization of this sentence in China adds to a growing body of case law around cryptocurrency theft globally. While the value stolen was not exceptionally large, the length of the prison term signals that courts are treating digital asset crimes with increasing severity. For readers, the key takeaway is that cryptocurrency custody requires rigorous personal security practices, and that breaches of trust can have severe legal consequences for perpetrators. FAQs Q1: How did the thief obtain the private key? The thief, Lin, secretly accessed the victim’s computer while helping him cash out Bitcoin, and copied the private key to the victim’s wallet without authorization. Q2: Why did it take so long for the victim to discover the theft? The victim did not check his cryptocurrency wallet for nearly four years after the theft occurred in late 2020. He only discovered the missing Bitcoin in 2024 and reported it to authorities. Q3: Is cryptocurrency trading legal in China? No. China has banned cryptocurrency trading and exchanges since 2021, though holding cryptocurrency as an asset is not explicitly illegal. Legal cases involving crypto are prosecuted under general theft, fraud, or money laundering statutes. This post Chinese Man Sentenced to 12 Years for Stealing Friend’s Bitcoin first appeared on BitcoinWorld .
23 May 2026, 10:00
Grayscale Files Third Hyperliquid ETF Amendment With SEC — Details
Hyperliquid’s native token HYPE has been the major center of attention in the cryptocurrency market over the last week. Besides its impressive price action — outperforming other large-cap assets by a significant margin in the past week — the cryptocurrency seems to be becoming the new darling of institutional investors. A fairly strong first full trading week for Bitwise’s HYPE exchange-traded fund (ETF) was identified as one of the catalysts behind the coin’s all-time high rally. Interestingly, the latest development suggests that Grayscale’s Hyperliquid ETF might also be making its trading debut soon. Grayscale Confirms GHYP Ticker For Hyperliquid ETF On Friday, May 22nd, Grayscale submitted the third amendment to its spot HYPE ETF S-1 application with the United States Securities and Exchange Commission (SEC). According to Bloomberg ETF analyst James Seyffart, this latest amendment confirms that the asset management firm’s Hyperliquid ETF will trade with the GHYP ticker upon launch. After initially submitting a proposal in March, Grayscale has made a series of changes to its Hyperliquid ETF offering, including switching custodians from Coinbase to Anchorage Digital and incorporating native staking yields. Meanwhile, the firm has finally settled on the GHYP ticker after introducing the HYPG ticker in the second amendment. As Seyffart pointed out, the latest amendment of its SEC filing suggests that Grayscale might be getting closer to launching its spot HYPE exchange-traded fund. This would bring the number of Hyperliquid ETFs on US exchanges to three, including 21Shares and Bitwise’s spot HYPE exchange-traded products. Interestingly, this development coincides with Grayscale’s reported on-chain activity, with the asset management firm found accumulating significant amounts of the Hyperliquid native token over the past week. On-chain data shows that Grayscale bought 682,190 HYPE (roughly $35 million) over the past week. HYPE Price Overview As of this writing, the Hyperliquid token is valued at around $54.7, reflecting a decline of over 5% in the past 24 hours. The past day’s price action suggests the cryptocurrency may be slowing down after a strong bullish run this week, with a move toward a new all-time high above $62. According to CoinGecko data, the HYPE price is up more than 26% on the weekly timeframe. Meanwhile, the cryptocurrency’s value has grown by roughly 115% so far in 2026, riding on the wave of surging volume and institutional validation of the Hyperliquid platform.
