2026-08-07 Sexta

Notícias de cripto - Página 347

Mantenha-se a par do mercado de cripto. Notícias em tempo real, análises, preços, histórias em alta e análise de especialistas — tudo num só lugar.

After the U.S. Banned Fable 5, Zhipu's Stock Soared 47%

On June 15, Chinese AI company Zhipu's stock surged up to 47.6% in Hong Kong, closing with a 32.82% gain. This sharp rise followed two key industry events. On June 12, Anthropic was compelled by a U.S. government export control order to suspend global access to its latest flagship models, Claude Fable 5 and Claude Mythos 5, impacting developers and businesses reliant on them. The next day, Zhipu announced it was opening access to its new open-source flagship model, GLM-5.2, for all Coding Plan users, with API and model weights (under the MIT license) to follow. The Anthropic incident highlighted a critical shift in the AI industry: beyond raw capability, the stability, continuous accessibility, and control over AI models are becoming equally vital, especially as AI integrates deeper into business workflows. Zhipu's move, emphasizing that "frontier intelligence should not belong to a few nor be subject to arbitrary revocation," positioned its open, accessible model as an alternative. GLM-5.2 focuses on "Long Horizon Tasks" with a 1M context window, aiming for consistency in complex, extended projects. Market analysts suggest this event exposes the risk of dependency on closed-source models subject to single jurisdiction policies, potentially accelerating a shift toward domestic base models and localized deployments. The investment response indicates a new valuation metric is emerging—prioritizing which companies can provide AI capabilities that are not only advanced but also reliably and sustainably accessible.

marsbit06/16 06:49

After the U.S. Banned Fable 5, Zhipu's Stock Soared 47%

marsbit06/16 06:49

PANews Column Registration and Article Submission Guide

"PANews Column Registration and Submission Guide" provides instructions for users to register as columnists and publish articles on the PANews platform. Key application requirements are emphasized: content should focus on in-depth analysis within Crypto, Web3, blockchain, data, and viewpoints. Content primarily for brand/product introductions will not be approved, and heavily AI-generated content will be rejected. Promotional (PR/soft) content is directed to the business channel. **Registration Process:** * **Web:** Go to the official website footer, click "Apply for Column," and register with a phone number or email (login via verification code, no password). Fill in the column name, description, upload an avatar, and submit links to previously published work. * **Mobile:** Navigate to "My" -> "Contribute & Create" and complete the form. **Article Submission Tutorial:** 1. Log in to the PANews website. 2. Access the "Creator Center" from your personal homepage. 3. Use the editor to create and publish articles. **Video Upload:** The platform supports embedding videos from third-party sites (e.g., Bilibili). Copy the embed code from the source video, use the editor's "Insert/Edit media" button, paste the code under the "Embed" tab, and adjust the display size (recommended: width 100%, height 560px). **PANews Skills (AI Agent Tool):** PANews offers an official AI Agent skill set called PANews Skills, enabling AI tools to query platform content, track trends, and publish column articles directly. It includes three main skills: 1. `panews`: For tracking daily must-read lists, popular articles, and funding news. 2. `panews-creator`: For managing columns, publishing articles, and uploading images. 3. `panews-web-viewer`: For parsing PANews webpages into Markdown. These skills are compatible with various AI Agent tools (OpenClaw, Cursor, Claude Code, ChatGPT, Gemini, etc.). To use the `panews-creator` skill, users must obtain a specific authentication value from the PANews website after logging into their columnist account.

marsbit06/16 06:38

PANews Column Registration and Article Submission Guide

marsbit06/16 06:38

I Built Myself an Investment Workbench Using AI

For the past two weeks, I've been immersed in Vibe Coding—using AI to write code from natural language descriptions. This process has enabled me to quickly build functional tools that address long-standing personal ideas. Previously, I had many concepts but found execution too cumbersome. Key ideas included a unified dashboard for assets across US stocks, Crypto, HK stocks, and A-shares; a real-time alert system for price movements; an investment map visualizing sector relationships; and a tool to correlate prediction market bets with news and market data. Traditional development hurdles meant these often remained unrealized. Using AI (Codex, Claude Code, and DeepSeek API), I built four initial tools: 1. A **Cross-Market Asset Dashboard** showing total assets, daily P&L, and holdings by market, with added features for alerts and sector mapping. It's deployed locally for privacy. 2. A **Prediction Market (PM) Monitor** tracking bets on events (e.g., company valuations) and correlating probability shifts with news and market movements. I categorize bets by conviction to filter noise. 3. A **Simple Operations Backend** for managing my writing workflow (topics, progress, publishing). It's cloud-deployed for mobile access. 4. A **One-Click Formatting Tool** that automates converting drafts into various platform-specific formats, saving manual effort. While these tools are basic, they represent a significant shift: AI lowers the barrier to creating personalized systems. I believe individual investors can now feasibly build core systems for: * **Asset Observation** (tracking holdings and changes) * **Signal Monitoring** (watching for key market shifts) * **Sector Mapping** (understanding network relationships within a sector) * **Performance Review** (documenting rationale and outcomes) The power of Vibe Coding is its fast feedback loop. Ideas can be implemented, tested, and iterated on rapidly, turning "want-to-do" into "done." This marks the start of my new phase, where I'll share investment thoughts, tool tests, on-chain operations, and educational Web3 content.

marsbit06/16 06:22

I Built Myself an Investment Workbench Using AI

marsbit06/16 06:22

After Tokenization of Assets, How to Exit?

Title: How to Exit After Asset Tokenization? Author: Symbiotic Compiled by: Hu Tao, ChainCatcher Summary: Tokenization addresses how assets go on-chain but largely leaves the redemption question unresolved. While tokenized assets can settle instantly, the underlying redemption for assets like treasuries, private credit, or real estate can take from T+1 to 180 days. This gap hinders DeFi adoption of Real World Assets (RWAs). Three emerging models aim to provide instant exit liquidity, differing primarily in their capital structure and efficiency: 1. **Balance Sheet Model (e.g., Grove Basin):** A single entity (like Sky) provides immediate liquidity from its balance sheet, acting as a bridge during the settlement period. It offers simplicity and deep initial liquidity but is constrained by a single entity's capacity and risk appetite. 2. **Asset-Specific Vault Model (e.g., Upshift Clear):** Independent liquidity providers fund dedicated vaults for each supported asset, earning fees. It decentralizes capital sources but isolates liquidity and capital per asset, leading to potential fragmentation. 3. **Shared Liquidity Layer Model (e.g., Symbiotic Liquid Lane):** A shared capital pool supports multiple RWA types simultaneously. Funds remain productive between redemptions (e.g., earning yield in lending markets). Exits are settled via a competitive RFQ market. This model aims for higher capital efficiency, scalability across assets, and serves longer-duration assets like private credit. Key differentiators are: 1) Source of capital and risk bearer, 2) Redemption pricing mechanism, 3) Capital efficiency, 4) Scalability to new asset types, and 5) Composability. The shared liquidity layer model represents a move from piecemeal solutions toward scalable infrastructure, enabling T+0 exits by pooling capital, maintaining yield, and using competitive pricing, thus enhancing RWA utility in DeFi.

marsbit06/16 06:09

After Tokenization of Assets, How to Exit?

marsbit06/16 06:09

After Tokenizing Assets, How to Exit?

After tokenization, a key unresolved issue is providing holders with a reliable exit mechanism, as underlying asset settlement (taking days to months) lags far behind on-chain token settlement. Three primary models for instant liquidity have emerged, differing in their capital structure and efficiency: 1. **Balance Sheet Model (e.g., Grove Basin):** A single, well-capitalized entity (like Sky) provides immediate liquidity from its own reserves. This offers simplicity and deep initial liquidity but is constrained by that single balance sheet's capacity and risk appetite, limiting scalability. 2. **Dedicated Vault Model (e.g., Upshift Clear):** Independent liquidity providers (LPs) fund separate vaults for each supported asset. This decentralizes capital sources but isolates liquidity and capital, which becomes inefficient as the number of tokenized assets grows. 3. **Shared Liquidity Layer Model (Symbiotic Liquid Lane):** Independent capital providers fund shared vaults that can support multiple tokenized assets simultaneously. Capital remains productive between redemptions (e.g., earning yield in DeFi markets). Exits are settled via a competitive RFQ market where market makers bid. The article argues that the shared layer model offers superior capital efficiency and scalability. It transforms exit liquidity from an asset-specific patch into shared market infrastructure, allowing liquidity capacity to grow with overall market participation rather than being fragmented per asset. This is particularly valuable for longer-duration assets like private credit, where reliable T+0 exits can significantly enhance their utility in DeFi.

链捕手06/16 05:55

After Tokenizing Assets, How to Exit?

链捕手06/16 05:55

Anthropic's Triple Moment: Code Leak, Government Confrontation, and Weaponization

This article analyzes Anthropic's recent conflicts and strategic moves following the U.S. government's emergency halt of its new Fable model, citing national security concerns over potential "jailbreaks." The author argues this incident reveals deeper tensions between AI labs, governments, and the software industry. While critics view Anthropic's safety-focused rhetoric as marketing fear, the author suggests it serves as a commercial moat masking the company's core economic imperative: moving closer to end-users and their valuable data to avoid being commoditized. The piece outlines a coming clash between frontier AI labs like Anthropic and established software companies. Labs need real-world usage data for model improvement via reinforcement learning, creating a cycle where better products attract more users and more data. This threatens software firms who, as Microsoft's Satya Nadella warns, risk having their value captured by a few dominant models. Anthropic's controversial policy changes—initially secretly degrading Fable's performance for LLM development and expanding data retention—are framed as assertions of control, justified by its safety narrative. The company's foundational belief that it alone is sufficiently concerned about superintelligent AI dangers legitimizes its actions, from resisting government demands to shaping usage policies. The author concludes that this alignment of mission, talent, and business strategy is powerful but concerning, as it concentrates immense potential power in the hands of those convinced of their own righteous understanding.

marsbit06/16 05:45

Anthropic's Triple Moment: Code Leak, Government Confrontation, and Weaponization

marsbit06/16 05:45

Xpeng and NIO Compete on Computing Power, Li Auto Shifts Architecture

On June 15, 2026, Li Auto unveiled details of its self-developed chip, Mahe M100, for its new L9 Livis model. CTO Xie Yan stated the goal was not just a faster chip, but a fundamentally different one, targeting the chip architecture itself. While competitors like NIO, Xpeng, and Huawei highlight TOPS (computing power) figures for their self-developed chips, Li Auto’s Mahe M100 focuses on redesigning the underlying architecture. It employs a "dynamic data flow architecture" to address memory bandwidth bottlenecks in large model inference, claiming up to 3x the effective computing power of Nvidia's Thor U for its specific workloads and a 40% reduction in latency. The chip's design was peer-reviewed and accepted at ISCA 2026. However, this performance is highly optimized for Li Auto's own VLA2.1 algorithm, meaning it may not generalize as well to other tasks. Li Auto aims to achieve full-stack in-house development with Mahe M100, covering chip, compiler, OS, AI algorithms, and domain controller—a level of vertical integration few competitors match. Beyond the chip, CEO Li Xiang introduced a new strategic narrative: the "embodied intelligent vehicle," defined as an integration of an EV, a professional driver, an AI computer, and a life assistant. This shifts competition from features like large screens to systemic AI capabilities. A key commitment was that Li Auto's Mahe VLA autonomous driving model will match Tesla's FSD V14 by Q4 2026, with specific OTA milestones set for July, September, and December. Financially, Li Auto faces pressure with declining revenue and vehicle gross margins since Q4 2025, while maintaining high R&D investment (approx. ¥12B in 2026, 50% AI-related). Its 2026 sales target is 550,000 vehicles, up from 406,000 in 2025. The new L9 Livis garnered over 10,000 pre-orders in two weeks. The effectiveness of these strategic moves—new products, OTAs, and the novel chip architecture—will begin to show in Q3 2026 financial results, with the year-end FSD V14 benchmark being the ultimate test.

marsbit06/16 04:52

Xpeng and NIO Compete on Computing Power, Li Auto Shifts Architecture

marsbit06/16 04:52

The Year of AI Applications: Saying 'Yes' While Ignoring Risks? A Comprehensive Open Source Log of Software Development's Journey

The Year of AI Applications: Blindly Saying "Yes" While Ignoring Risks? A Software Development Log Goes Fully Open Source. AI-generated code harbors risks hidden within seemingly correct programs, potentially leading to data leaks or asset loss. The open-source project "Narwhal AI Code Risks," from Peking University's Narwhal-Lab, compiles real-world cases, early warning signs, and typical risk pathways. Its goal is to help developers identify potential hazards early and avoid repeating past mistakes. In 2026, code is generated faster than ever but deployed with less scrutiny. The danger often lies not in glaring errors, but in code that appears normal—syntactically correct, passing all checks—yet introduces subtle but critical flaws like non-existent dependencies, excessive permissions, or exposed databases. A stark example is the Moonwell cbETH oracle incident. A configuration file error, where a cryptocurrency price was set to ~$1.12 instead of ~$2,200, slipped through 28 checks and a pull request signed by both AI (Claude, Copilot) and human developers. This "semantic deviation" resulted in a loss of $1.78 million. The risk is that AI can produce functionally valid code that is semantically wrong for the business context. As AI moves beyond simple code completion to modifying configurations, installing dependencies, and operating via autonomous agents, it traverses longer, less traceable paths within software engineering, blurring traditional boundaries and oversight points. The Narwhal AI Code Risks project structures information into three layers: `/cases` for documented real-world incidents, `/inferred` for early warning signals, and `/scenarios` for clear, generalized risk patterns not yet tied to specific events. This aims to create a lasting, public record to prevent collective amnesia about past AI-coding pitfalls. Risks are categorized into seven areas: Software Supply Chain (e.g., recommending fake packages), Code-Level Vulnerabilities (e.g., reintroducing path traversal bugs), Cloud & Infrastructure Misconfiguration (e.g., overly permissive settings), Agent Risks (from autonomous tool execution), Vertical Domain Risks (e.g., in finance, healthcare), Intellectual Property & Compliance issues, and Human Factors (like over-reliance on AI output). The project's core value is transforming isolated incidents into reusable knowledge—a foundational resource for developers to spot similar issues, for security researchers to build upon, for toolmakers to create detection rules, and for the community to contribute new findings. As AI integration accelerates, this open-source "logbook" serves as a crucial navigational aid, charting past errors to help future projects steer clear of the same traps.

marsbit06/16 04:52

The Year of AI Applications: Saying 'Yes' While Ignoring Risks? A Comprehensive Open Source Log of Software Development's Journey

marsbit06/16 04:52

活动图片