LATEST MOVES · Latest Actions Overview

Note: This article is compiled based on RootData, public regulatory documents, and MAGNE.AI official disclosures; company disclosures, verified capabilities, and future goals are marked in the text, data is as of August 23 2026.

If we only view MAGNE.AI as a Web3 phone, it is easy to overlook its recent shift towards edge AI and Agent infrastructure over the past six months. Financing, team, and event information can be continuously checked atMAGNE.AI's RootData project page; product, certification, and engineering progress are updated byMAGNE.AI's official website.

From the company's disclosed $2.64 million additional strategic funding to Phone Gen1 entering PVT P2; from publicly available FCC, GMS, GSMA TAC and other compliance materials, to launching a viewable modular phone engineering structure; then to MAGNE AI BOX and Agent Pay testnet evidence, MAGNE.AI is expanding its early “phone as a Web3 entry point” 定位 into a product roadmap that encompasses devices, edge computing, identity, and machine payments.

This roadmap is still in the engineering realization phase, but a batch of verifiable materials has appeared. At this stage, what is more suitable for observation is not the size of the vision, but whether mobile mass production, AI BOX prototype validation, Agent Pay testnet progress, and community participation can be transformed into real device users.

Therefore, the evaluation of MAGNE.AI should focus on system integration, delivery speed, public verification, and sustainable operational capabilities, rather than a single parameter or concept label.

Signals from RootData: Entering Traceable Project and Funding Coordinates

Discussions of “Tier 1.5” or “Tier 2” have emerged in the market, but RootData has not provided a publicly unified Tier level for MAGNE.AI. The verifiable fact is thatMAGNE.AI has established the RootData project page, and in RootData's “2025 Web3 Industry Annual Report,” it appears in the AI track financing Top 30 chart with the disclosed $10 million funding amount.^[1]

On August 5, 2026, MAGNE.AI announced the completion of $2.64 million in additional strategic funding, with participants including GAEA Ventures, Titans Ventures, and Go2Mars Labs. According to company disclosures, its cumulative public financing has reached $12.64 million. The funds will be used for engineering verification and commercial delivery of MAGNE AI BOX, integration of AI BOX with MAGNE L1/MHash L2, and the research and development of MAGNE Agent Pay and x402 compatible payments.^[2]

$12.64 million does not automatically prove industry status. It is more suitable as a continuous funding signal to observe: after the first round of strategic financing in 2025, the company disclosed additional funding in 2026. However, the structure, receipt status, and rights arrangement of the new round primarily come from company press releases, requiring more independent materials for confirmation.

From the perspective of third-party observation, clear Pre-TGE preparation signals have already appeared in public materials, but are still insufficient to prove an upcoming TGE or exchange listing. MAGNE.AI's official milestone page lists exchange due diligence, Token disclosure, protocol auditing, exchange coordination, and market-making/liquidity arrangements as ongoing matters, while marking the TGE preparation checklist and launch window as planned, clearly subject to legal, auditing, exchange, liquidity, and operational conditions. Season 2 will also link subsequent MHA distributions to future TGE arrangements.^[13] Combined with additional financing, these changes make the judgment of “TGE is being prepared” a reasonable market assessment; however, a more rigorous statement should still be “TGE is being prepared,” rather than “TGE is imminent,” until full audits, final token contract/mainnet information, confirmation of dates, or announcements from exchanges are made public.

Phones Are Not Obsolete; They Are Becoming the First Trustworthy Endpoint of the Entire Infrastructure

The configuration of MAGNE Phone Gen1 does not win with flagship consumer electronics parameters. Current specifications on the official website show it uses a UNISOC T9100 5G SoC, an IMG AX3596 10 TOPS INT8 NPU, up to 12GB RAM, and 512GB UFS 3.1 storage, running on Android 15, with a 5000mAh battery and a 6.78-inch 120Hz screen.^[3] What truly differentiates it is the three-tier security structure established around keys, recovery, and isolation: TEE is responsible for trusted execution isolation, independent secure elements handle private key storage and signing, and an NFC recovery card takes offline backups outside the device.

This makes MAGNE Phone more like “a hardware wallet for everyday use and an Agent control terminal”, rather than simply an Android phone layered with wallet App. When individual Agents start calling external services, requesting permissions, and initiating payments, the phone can simultaneously take on the roles of identity carrier, manual authorization interface, and secure signing terminal. Its role in the entire MAGNE stack has also transformed from a consumer product to a network entry point.

What better reflects engineering progress is the project's proactive public disclosures of production and compliance traces. The official progress page shows that Phone Gen1 has completed Pre-EVT and EVT P1, and is currently in the PVT P2 production validation phase; design freeze, component procurement, and manufacturing partner alignment have been marked as completed, with the initial manufacturing target aiming for the third quarter of 2026.^[4] Public records of FCC ID 2BVCPGC603606 cover testing materials for cellular communications, Wi-Fi, Bluetooth, NFC, EMC, and SAR.^[5]

The project has also launched a 3D phone engineering structure viewer, which lists 31 visible components, including 6 precise STEP parts, 13 V51 appearance parts, and 12 modeling supplements, allowing users to disassemble layer by layer according to the shell, camera, and core structure.^[6] A webpage viewer cannot replace mass production acceptance but indicates that the team is willing to make industrial design, internal stacking, and product structure into public communication assets. For a DePIN track long troubled by doubts of being “PPT hardware,” this engineering transparency itself holds market value.

AI BOX Fills a Larger Commercial Space Beyond Phones

If Phone Gen1 targets individual users, MAGNE AI BOX is steering the project towards enterprise-private AI and edge computing scenarios. Its technical specifications, validation boundaries, and Release Gate status are continuously disclosed byW3.MAGNE.AI.

The product logic of AI BOX is not complex: models, knowledge bases, and Agents are designed to run as locally as possible; enterprise original files are not directly on-chain, and only device identity, task summary, authorization status, and settlement receipts are retained on-chain. High-risk tool calls or payment requests still require manual confirmation from a bound phone or wallet, with private keys not entering the model. This makes it not just“a smaller cloud server,” but an attempt to become a physical boundary of AI that enterprises can control.^[7]

The public specification control page provides 56 TOPS INT8 NPU, over 600GB/s bandwidth, 8—15W AI power consumption, and a capacity list made up of main system memory, NPU near-end memory, and extended memory of 34GB/38GB; at the same time, the page also marks some indicators as“supplier statements” or“to be tested,” and clarifies that the total capacity does not equal a unified available memory.^[7]

It is noteworthy that the page separates“PDF configuration,”“supplier statement,”“already verified,” and“to be tested.” The page shows that the Qwen3.6-35B-A3B Q4_K_M model artifacts have completed the first local operational validation; the project is currently at the Gate 0 specification freeze phase, and the next step, Gate 1, will manufacture 3 prototype machines for performance, power consumption, heat dissipation, offline security, upgrades, and recovery testing, followed by design partner validation and small batch stages.^[7]

This indicates that the technical team’s understanding of hardware industrialization does not just stop at “making a demo.” It has begun to manage risks from specifications, prototypes, customer validation, to small batches using Release Gates. For the outside world, the AI BOX also extends MAGNE.AI's commercial imagination from crypto users to fintech, digital asset institutions, Web3 teams, and enterprise customers that require local knowledge boundaries.

Agent Pay Truly Connects Hardware, Identity, and On-Chain Payments

One of the noteworthy technical moves of MAGNE.AI recently is Agent Pay.

x402 uses the HTTP 402 status code to allow the server to return price and payment requirements, with the Agent completing payments and re-requesting resources after receiving authorization. This provides a path for machine payments for APIs, data, reasoning, and digital services without the need for traditional account systems. Cloudflare has already provided x402 payment capabilities in the Agents SDK, indicating that “Agent native payments” are moving from concept into the realm of development tools.^{[8, 9]}

The goal of MAGNE Agent Pay is to place x402 related payment processes into the device identity and hardware signature environment. According to the current official status page, the project has demonstrated local contract Demo and testnet evidence; the HTTP 402 end-to-end process is still under development, MHash L2 receipts are on the testnet path, and production payments have not yet been opened.^[10]

Its design goal is to form an auditable control link: Agents initiate requests, policy checks permissions and budgets, high-risk actions enter manual confirmation, payments are executed after signature by the phone or wallet, and the system generates task receipts. Computation, identity, authorization, and settlement are undertaken by AI BOX, MAGNE L1, MHash L2, and Agent Pay, but this cross-module closed loop still requires public testnet transactions and third-party service access for verification.

This link explains why MAGNE.AI needs to make phones, AI BOX, L1, L2, and payments simultaneously. When viewed separately, each layer is not scarce; when combined, it attempts to answer four real questions of the Agent economy: where the model runs, how devices prove identity, who authorizes machine spending, and how transactions leave a record of responsibility.

Operating Team: Transforming Engineering Progress into Sustainable Tracking Information

TEAM OPERATING MODEL · Team Capability Portrait

From the recent year's public actions, continuous disclosure and milestone arrangement are MAGNE.AI most prominent operational capabilities.

First, it excels in“transparency marketing.” Ordinary projects typically create attention with grand visions, while MAGNE.AI creates publicly viewable content from FCC query pages, GMS support materials, GSMA TAC, PVT progress, 3D engineering structures, AI BOX Gate, and Agent Pay status. Many ordinary users may not understand every engineering document, but these details create an intuitive understanding: the team is dealing with certification, supply chain, and testing issues that real hardware projects encounter.

Second, it continuously orchestrates product milestones. After the phone completed a batch of security and compliance disclosures, the project introduced AI BOX, extending the direction to enterprise-edge AI; subsequently, it connected Agent Pay with AI BOX, dual chains, and x402 research; financing and Season 2 then respectively addressed institutional and community concerns. Different actions formed a continuous context, but each capability should still be expressed according to its actual verification stage.

Third, it understands how to provide different entry points for different audiences. Consumers see phones, wallets, and NFC recovery; institutions see certifications, data rooms, and production phases; developers see L1, L2, x402, and Agent Pay; community users participate in device distribution and point systems through Season 1/2. The ability to organize these narratives simultaneously indicates that the team is not just generating social media exposure, but building a set of market infrastructure aimed at products, capital, developers, and the community.

This kind of operational capability is not a subsidiary of technology. Hardware projects have long cycles and high explanation costs; the team needs to continuously transform stage progress into verifiable information to help the supply chain, investors, developers, and the community understand the project's current phase. MAGNE.AI has already established a relatively complete public information path, and the next key is to ensure that disclosures align with actual delivery.

Technical Team: Not Founders of Basic Models but a Pragmatic Systems Engineering and Productization Team

Evaluation of MAGNE.AI technical team should not only rely on whether it has“self-developed large models.”

Phone Gen1 uses mature mobile SoC, NPU, secure elements, and the Android ecosystem; AI BOX adapts the open-source Qwen3.6-35B-A3B model; Agent Pay is built on open standards of x402 and ERC-20. In other words, the team’s advantage is not to replace chip manufacturers, Google, Qwen, or protocol ecosystems, but to integrate these mature capabilities into the same product architecture and complete the connections of edge-side optimization, security isolation, authorization state machines, device identity, and on-chain settlement.

This is closer to an excellent systems engineering team: knowing which parts should be self-built and which should utilize the supply chain and open-source ecosystem; knowing how to define the interfaces among phones, boxes, chains, and payments; and understanding that consumer electronics must go through EVT, PVT, certification, recovery, upgrades, and after-sales rather than directly writing laboratory prototypes as mass-produced products.

More notably, its engineering expression is becoming restrained. The AI BOX page proactively marks supplier statements, to-be-tested indicators, and Gate conditions; the security page indicates that EAL level corresponds to components or assessment scope, which should not automatically equate to overall certification of the entire configuration; the Agent Pay page distinguishes between testnet evidence, developing capabilities, and production payments that have not yet opened.^{[7, 10, 11]} This awareness of boundaries helps the outside world to understand product progress based on engineering status rather than marketing completion level.

While the operational team excels at clarifying complex projects, the technical team's strength lies in “leveraging but not losing control”: lowering the cost of building hardware from scratch by using a mature supply chain, shortening edge-side AI development cycles using open-source models, and keeping the more project-identifiable security architecture, device identity, and Agent payment control layer in their hands.

At the current stage of Web3, a combination of “sustainable operation + pragmatic development” may benefit the project in completing the transition from prototype to delivery, but it ultimately still needs to be verified by mass production, customer usage, and public network data.

Season 1/2 is Not a Simple Lottery but a Cold Start Mechanism for Device Network

The community operation of MAGNE.AI also serves the product roadmap. The official progress page discloses that Season 1 involves a total of 76,650 independent on-chain addresses; this number represents participant addresses and does not equate to the final number of device users or delivered quantities. Season 2 announced 1600 active devices, each participation cost of 17 USDT, with every 100 valid participations triggering a phone draw, and introduced MS2 as an activity record and subsequent qualification certificate.^{[12, 13]}

If the phone is seen as a regular consumer product, this is merely a customer acquisition activity; if the phone is viewed as an endpoint with a hardware signature, on-chain identity, and future Agent capabilities, then the Season mechanism concurrently undertakes device distribution, address retention, on-chain behavior education, and network cold start.

This also marks the most pronounced synergy between MAGNE.AI's operations and technical routes: the operational team creates user engagement through activities, and the technical system connects participation records, devices, identities, and future network rights. As long as subsequent shipments, activations, and continuous online data can occur as planned, these activities will not merely be noise but will become the early foundation of network scale.

“Complete Stack” is Transitioning from Narrative Advantage to Organizational Advantage

Many projects doing hardware, chains, and payments simultaneously may be questioned for spreading their fronts too wide. For MAGNE.AI, this concern is not unfounded, but recent developments provide another perspective: the complete stack is not only about the number of products but may also reflect the team's collaborative ability.

The phone provides user entry and secure signatures, AI BOX offers local models and enterprise knowledge boundaries, L1 provides device identity and ownership logic, L2 offers low-cost execution, Agent Pay handles service calls and settlements, while Season activities take on community cold starts. There is already an increasingly clear causal relationship between the various modules, rather than unrelated product assortments.

Thus, what is currently worth observing in MAGNE.AI is not “every item has already succeeded” but whether it can gradually organize capital, supply chain, hardware, AI, chains, and community into a verifiable delivery path. Certifications, PVT, model adaptations, payment controls, and community activities have already left publicly traceable marks, but execution results still require proof from the next stage of data.

What Should MAGNE.AI Prove Next?

FROM ATTENTION TO NETWORK · Three-Phase Growth Path

Evaluating MAGNE.AI can remain positive, but it needs to land on verifiable outcomes.

At the narrative level, it is extending from Web3 phones to Agent infrastructure; at the credibility level, it possesses RootData funding records, public FCC documents, compliance pages, engineering structures, and phased progress; at the product level, Phone Gen1 has entered PVT P2, AI BOX established Release Gate, Agent Pay has shown local demo and testnet evidence; at the organizational level, it demonstrates sustainable operations and engineering integration capabilities.

What can truly transform this advantage into industry status are several more concrete advancements: Phone Gen1 completing its first batch of production and delivery; AI BOX prototype passing performance, power consumption, heat dissipation, and offline security tests; design partners beginning to validate the product with real contracts or knowledge base tasks; Agent Pay producing third-party verifiable service payments on public testnets; Season participation addresses further converting into real device users and active network nodes.

These are not meant to “find faults” with the project, but are steps that must be taken in transitioning from an ascending dark horse to a mature project.

In summary, MAGNE.AI's characteristics are not a single parameter or concept, but an attempt to form a relatively complete organizational and product path: the operational team continuously discloses engineering progress, the technical team utilizes mature ecosystems for system integration, and the product roadmap encompasses phones, AI BOX, chains, and Agent Pay, converging towards “local intelligence + trusted identity + programmable payments.”

MAGNE.AI has not yet completed all validations from engineering signals to large-scale delivery but has already provided enough public materials for the market to continue tracking. Financing, team, and event updates can be viewed onMAGNE.AI’s RootData project page; phone, certification, and production progress can be seen onMAGNE.AI’s official website; the technical status of Agent Pay and AI BOX can be found onW3.MAGNE.AI.

References

[1] RootData:MAGNE.AI project page and“2025 Web3 Industry Annual Report”. MAGNE.AI entered the report's AI track financing Top 30 with publicly disclosed $10 million funding at that time; RootData did not provide a publicly unified Tier rating based on this.

[2] Chainwire:MAGNE.AI completed $2.64 million in additional strategic funding. Funding amounts, investors, total financing, and fund usage are consistent with the company's press releases.

[3] MAGNE.AI:Phone Gen1 specification page. Used for verifying 6.78 inch screen,10 TOPS INT8 NPU, three-tier security architecture, dual space, and edge-side AI positioning.

[4] MAGNE.AI:Project Progress Page. Used for verifying Pre-EVT, EVT P1, PVT P2, design freeze and manufacturing goals, etc.

[5] MAGNE.AI:FCC document query page. FCC ID is 2BVCPGC603606, and can be further verified through regulatory databases.

[6] MAGNE.AI:Phone Gen1 3D engineering structure viewer. The page publicly displays 31 visible components and layered disassembly information, but does not equate to mass production acceptance proof.

[7] W3.MAGNE.AI:MAGNE AI BOX technology and Release Gate page. Parameters include supplier statements, to-be-tested items, and capacity derivation limits; formal submissions should retain these limits.

[8] x402 official website. Used to explain the background of HTTP 402 based Agent pay; dynamic transaction data is not written into the text.

[9] Cloudflare Agents:x402 payment documentation. Used to illustrate that x402 has entered the availability of mainstream development tools.

[10] W3.MAGNE.AI:Agent Pay status page. The current page distinguishes between local contract Demo, testnet evidence, developing HTTP 402 processes and production payments that are yet to be opened.

[11] MAGNE.AI:Security architecture page. EAL level corresponds to components or assessment scope and should not be broadly stated as the entire configuration obtaining the same level of certification.

[12] MAGNE.AI:Project Progress Page andSeason 1 page. The progress page discloses 76,650 independent on-chain participation addresses; this metric does not equate to the final number of device users or delivered quantities.

[13] MAGNE.AI:Season 2 Campaign Hub. Used for verification of 1600 active devices, 17 USDT, MS2, and rules such as a phone draw being triggered every 100 participations.

[14] W3.MAGNE.AI:Capital market and TGE preparation milestone. The official status lists exchange due diligence, Token disclosure, auditing, exchange coordination, and liquidity preparation as ongoing matters; the TGE preparation checklist and launch window remain conditional planned matters.

免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。