Behind the MiniMax 'Pseudo-Open Source' Controversy: Has Yan Junjie's Ideal Succumbed to Capital Anxiety?

marsbitPublicado em 2026-04-16Última atualização em 2026-04-16

Resumo

The article discusses the controversy surrounding MiniMax's "pseudo-open-source" release of its flagship M2.7 model. Initially presented as open-source, the model was later released under a "Modified-MIT" license that restricts commercial use without written permission, sparking backlash from the developer community. This move is seen as a departure from true open-source principles and reflects the tension between technological idealism and commercial pressures. MiniMax, which recently went public, faces significant financial challenges, with substantial losses despite growing revenues. The company’s decision to limit commercial use is interpreted as an effort to protect its revenue streams and control how its models are deployed, especially after instances of third-party misuse affected its reputation. The incident highlights a broader industry trend where "open-weight" models are increasingly distinguished from fully open-source ones, raising concerns about trust and legal certainty for developers and enterprises. The author concludes that MiniMax’s shift represents a pragmatic, if controversial, business strategy aimed at ensuring profitability, even at the cost of community trust.

By | Big Model Home

In the jungle law of artificial intelligence, trust is often more expensive than computing power and more likely to be shattered in the trade-offs of business.

On April 12, MiniMax officially open-sourced its flagship model M2.7, released on March 18, on the HuggingFace platform. The model boasts 229 billion parameters, adopts a MoE (Mixture of Experts) architecture, and requires activating only 10 billion parameters to perform, a series of metrics that point directly to top-tier global closed-source models. On its first day online, it completed adaptations including Huawei Ascend, NVIDIA, and vLLM, sparking industry attention.

However, when developers attempted to deeply engage with the weight files, the appearance of the words "Modified-MIT" in the protocol section instantly dragged this technological feast back into the reality of commercial博弈.

This highly contentious change not only cast a shadow of profit distribution over the "free lunch" but also stung developers seeking a technological safe haven amidst the ecosystems of large companies and startups. For technical leads grappling with workplace anxiety, a legal department's statement that "commercial use requires written authorization" turned the highly anticipated top-tier model's commercial application scenarios into zones of legal uncertainty.

The Trust Hunt of "Open Source" vs. "Open Weight"

In the open-source world, the MIT License symbolizes ultimate freedom and low barriers to entry. Previously, MiniMax's M2 and M2.5 followed this path, and founder Yan Junjie借此 established an image as a promoter of "technology普惠" in the domestic open-source field.

However, the "Modified-MIT" protocol adopted by M2.7 is being questioned by the industry as a form of "nominal openness,实质上的管控" (nominal openness,实质上的 control). Records disclosed by the developer community show that six hours before the weight files went live, the repository protocol still maintained a commercially friendly open-source form similar to Llama 3, but at the moment of official release, it was changed to a modified version requiring "written authorization for commercial use."

This practice essentially alters the契约 spirit of open source. For technical骨干 experiencing an "AI midlife crisis" and trying to use open-source models for internal innovation or entrepreneurship, this "legal uncertainty" is fatal—the final interpretation of so-called "written authorization" rests entirely with the vendor.

In the view of Big Model Home, the core of this controversy is essentially the industry's long-term confusion between two concepts "open source" as defined by the OSI, and merely opening model files, "open weight". The Modified-MIT protocol, by explicitly restricting commercial use, no longer符合 the globally accepted open-source definition and belongs only to the "open weight" category.

Some netizens stated, "This is not open source at all; this is just公开了模型文件 (公开了 model files)." This gap between name and reality feels more frustrating than simply announcing it as closed source from the start. They指责 that if every vendor uses the MIT name to create "private property," the consensus system of the open-source community will completely collapse.

What's more致命 for developers and enterprises is: MiniMax is already a listed company, and all protocol changes must服从财报与合规 (服从 financial reports and compliance). Today it changes the protocol for "narrowing losses," tomorrow it might charge per Token for "quarterly performance"—the "certainty" of a listed company is always written in the financial reports, not in community promises.

When Technological Ideals Hit the Wall of Commercialization

From an enterprise operation perspective, MiniMax's shift is not without trace. Training a MoE model with 229 billion parameters is a multi-million dollar gamble involving投入的电力、算力集群折旧以及高昂的人力成本 (invested electricity, computing cluster depreciation, and high human costs).

Yan Junjie once publicly stated, "Open source can force us to improve algorithm innovation efficiency and also enhance our global technology brand."

But after MiniMax officially landed on the main board of the Hong Kong Stock Exchange IPO on January 9, 2026, hailed as the "first stock of general artificial intelligence," MiniMax, stepping into the capital market, also had to modify its own rules of the game. With the stock price experiencing剧烈波动 after hitting a high of 1330 HKD (as of April 14 close, the stock price was 951 HKD, down 28% from the peak), the focus of investors is no longer the number of likes on HuggingFace or community reputation, but the hard revenue growth rate and profit inflection point in the financial reports.

MiniMax Developer Relations负责人 Ryan Lee responded on X regarding the reason for prohibiting commercial use. He mentioned that (under the previous open-source protocol) MiniMax's models appeared on some hosting sites, but some users found the quality to be worse than the official ones after trying them—there was excessive quantization, template errors, silent replacements, or they weren't even their models, leading these users to believe MiniMax's quality was mediocre. The protocol adjustment was due to "third-party hosting platforms胡乱修改模型, causing reputational damage."

This is also a pain point for leading AI companies like MiniMax: sometimes investing money and people in technology普惠 ends up handing a knife to competitors. The anxiety of watching others use your model to create commercial shell products, sell them to clients for huge profits, while you bear the huge server costs, is enough to destroy any idealist's mindset.

For Minimaxes: Is it the羽毛 of the brand, or the活路 of business? It's a painful multiple-choice question.

Undoubtedly, Yan Junjie's ideal ultimately succumbed to the survival anxiety of commercialization.

On March 2, Minimax's first full-year financial report showed: 2025 revenue of $79.04 million, a surge of 158.9% year-on-year, but behind this, the annual loss widened from $465 million in 2024 to $1.872 billion in 2025. The adjusted net loss was still as high as $250 million, meaning for every $1 earned, they still lost over $3. More critically: over 60% of expenditure was directed towards computing power and model training. Training a model like M2.7 costs tens of millions of dollars per round. Meanwhile, the B-end open platform (API/commercial authorization) is Minimax's only high-growth, high-margin sector, with 2025 revenue of $25.96 million, a year-on-year increase of 197.8%, growing much faster than the C-end.

The tightening of the M2.7 protocol is essentially MiniMax circling its wagons. It allows research and individual developers to continue using it for free to retain the seeds of the ecosystem; but it strictly prevents commercial use to ensure every blade of grass grows in its own field during the upcoming commercialization harvest period.

Riding the "open source" traffic wave while keeping legal risks and income interpretation rights firmly in hand. This is not "ideal succumbing to reality," but "securing profit expectations first, then talking about community sentiment." From a business management perspective, it's无可厚非, but it also taints the originally pure open-source spirit with a strong whiff of "client mindset."

The Polarization of Rule-Followers and Performance-Seekers

In the game of large models, certainty is far more important than pure performance parameters.

Developers are a simple group; they are willing to stay up late tuning parameters for you, willing to fix bugs for you on GitHub, provided you respect their rules of the game. After the M2.7 open-source incident, the global developer community experienced severe polarization.

Pragmatic "performance-seekers" believe: Since the performance rivals GPT and it's free for research, it's无可厚非 for vendors to seek commercial收益.

However, in global open-source developer communities, the vocal majority of "rule-followers" felt a severe "trust幻灭" (trust disillusionment). On mainstream communities like Reddit, many voices have already turned to fully open-source series like Qwen.

Why? Because for enterprise users, "certainty" is far more important than "performance".

If a company's open-source promise can be微调 at any time based on "commercial anxiety," then who dares to build their core business on its foundation? Changing the protocol name today, will it charge per Token tomorrow? This fear of future uncertainty is quickly反噬 the technology brand that MiniMax worked hard to build.

The once most radical, purest open-source benchmark has now become a typical case of "definition confusion" in the global community. This shattering of trust is clearly not something a few PR responses can mend.

Survival Rules for Developers in the AI "Post-Open Source Era"

It's not just MiniMax's M2.7 protocol modification; previously, Ali's Lin Junyang's departure also caused震动 in the AI open-source industry. As more large model companies step into the capital market, many worry that the large-scale open-source era of "contributing for love" is accelerating towards its end.

The future large model industry might evolve into two ecosystems: one is the true "public good," like Llama, Qwen, backed by large consortia, using open source to exchange for monopoly on underlying standards; the other is conditional gifts like M2.7, which are more like "commercial show flats"—you can look, you can try staying, but to move in (commercial use), please turn the corner and pay the service fee.

In fact, in the context of large companies, survival itself is a morality. But if you choose pragmatism, please put down the banner of lofty ideals; if you choose commercial licensing, please stop蹭 the光环 of MIT.

This incident demonstrates three survival rules for all AI practitioners in the "post-open source era":

First, all "free" things have an expiration date. When selecting an architecture, the first step is not to test parameters, but to have legal review the protocol. Especially for those responsible for promoting projects within large companies, every word in the protocol could become a stain on your review six months later.

Second, "OpenWeights" does not equal "OpenSource". Future industry narratives will revolve more around the former. We must learn to get used to these "gifts with locks" and reassess their value within商业 logic.

Third, trust itself is an asset. Vendors焦虑 revenue, developers焦虑 changes. This bidirectional anxiety is precisely the阵痛 of the current AI industry bubble being squeezed out.

As of publication, Yan Junjie himself has not publicly responded. Perhaps in his calculation logic, compared to the虚无缥缈 community reputation, obtaining real commercial authorization contracts is the ticket to growth that MiniMax pursues.

Perguntas relacionadas

QWhat is the core controversy surrounding MiniMax's release of the M2.7 model on HuggingFace?

AThe core controversy is that MiniMax released the model under a 'Modified-MIT' license, which restricts commercial use without written authorization, rather than a true open-source license. This was seen as a 'nominal openness with substantive control' that violates the spirit of open-source and creates legal uncertainty for commercial developers.

QHow did the change in licensing agreement for the M2.7 model impact developer trust and the open-source community?

AThe last-minute license change from a commercially friendly open-source license to the restrictive 'Modified-MIT' caused a 'trust disillusionment' in the global open-source developer community. Many developers felt betrayed, leading some to shift to fully open-source alternatives like Qwen, as the move undermined the foundational trust and consensus of the open-source ecosystem.

QWhat were the stated business reasons behind MiniMax's decision to restrict commercial use of the M2.7 model?

AMiniMax's developer relations lead, Ryan Lee, stated the restriction was due to third-party hosting platforms improperly modifying their models (e.g., excessive quantization, template errors, or model substitution), which led to poor performance and damaged MiniMax's reputation. Financially, as a publicly traded company, MiniMax faces pressure to monetize its high-cost models, and its B2B platform is its fastest-growing, highest-margin revenue segment.

QWhat does the article suggest is the fundamental difference between 'Open Source' and 'Open Weight' in the context of this event?

AThe article clarifies that 'Open Source' (as defined by OSI) involves licenses like the standard MIT license that grant full freedom, including commercial use. 'Open Weight' merely means the model files are publicly available but come with usage restrictions, such as the 'Modified-MIT' license that prohibits commercial use. MiniMax's M2.7 is an 'Open Weight' model, not a true 'Open Source' one.

QAccording to the article, what are the three survival rules for AI developers in the 'post-open-source era' highlighted by this incident?

A1. All 'free' offerings have an expiration date; legal review of licenses is the first step in architectural selection. 2. 'Open Weight' (OpenWeights) is not the same as 'Open Source' (OpenSource); the value of 'gifts with locks' must be reassessed within a commercial logic. 3. Trust is an asset itself; the current mutual anxiety between vendors and developers is a growing pain as the AI industry bubble deflates.

Leituras Relacionadas

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.

marsbitHá 10m

PANews Column Registration and Article Submission Guide

marsbitHá 10m

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.

marsbitHá 26m

I Built Myself an Investment Workbench Using AI

marsbitHá 26m

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.

marsbitHá 39m

After Tokenization of Assets, How to Exit?

marsbitHá 39m

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.

链捕手Há 52m

After Tokenizing Assets, How to Exit?

链捕手Há 52m

Trading

Spot
Futuros

Artigos em Destaque

Como comprar HOME

Bem-vindo à HTX.com!Tornámos a compra de Defi.app (HOME) simples e conveniente.Segue o nosso guia passo a passo para iniciar a tua jornada no mundo das criptos.Passo 1: cria a tua conta HTXUtiliza o teu e-mail ou número de telefone para te inscreveres numa conta gratuita na HTX.Desfruta de um processo de inscrição sem complicações e desbloqueia todas as funcionalidades.Obter a minha contaPasso 2: vai para Comprar Cripto e escolhe o teu método de pagamentoCartão de crédito/débito: usa o teu visa ou mastercard para comprar Defi.app (HOME) instantaneamente.Saldo: usa os fundos da tua conta HTX para transacionar sem problemas.Terceiros: adicionamos métodos de pagamento populares, como Google Pay e Apple Pay, para aumentar a conveniência.P2P: transaciona diretamente com outros utilizadores na HTX.Mercado de balcão (OTC): oferecemos serviços personalizados e taxas de câmbio competitivas para os traders.Passo 3: armazena teu Defi.app (HOME)Depois de comprar o teu Defi.app (HOME), armazena-o na tua conta HTX.Alternativamente, podes enviá-lo para outro lugar através de transferência blockchain ou usá-lo para transacionar outras criptomoedas.Passo 4: transaciona Defi.app (HOME)Transaciona facilmente Defi.app (HOME) no mercado à vista da HTX.Acede simplesmente à tua conta, seleciona o teu par de trading, executa as tuas transações e monitoriza em tempo real.Oferecemos uma experiência de fácil utilização tanto para principiantes como para traders experientes.

327 Visualizações TotaisPublicado em {updateTime}Atualizado em 2026.06.10

Como comprar HOME

Discussões

Bem-vindo à Comunidade HTX. Aqui, pode manter-se informado sobre os mais recentes desenvolvimentos da plataforma e obter acesso a análises profissionais de mercado. As opiniões dos utilizadores sobre o preço de HOME (HOME) são apresentadas abaixo.

活动图片