On June 24, 2026, AI community user “X Freeze” disclosed on social media that Musk has confirmed that SpaceX's new generation AI satellite constellation project is named “Starmind,” positioned as the next phase of space infrastructure after Starlink, which will directly deploy AI computing power into orbit. According to the community news, SpaceX has reportedly submitted a plan for up to 1 million AI data center satellites in orbit, with each satellite not only responsible for communication functions but also acting as solar-powered flying computing nodes. The first batch of “AI1” satellites is expected to be deployed and undergo early computing power tests around 2027. If this scale and pace are ultimately confirmed by official documents, it could mean a new “in-orbit computing layer” in the global digital infrastructure landscape, rewriting the underlying computing power and data processing pathways for financial and cryptocurrency businesses. However, currently, all key details about Starmind—from constellation architecture to licensing pathways—are disclosed by the community rather than regulatory filings or formal announcements from SpaceX, leaving significant uncertainty surrounding the project information. The core questions also arise: once AI data centers migrate to Earth’s orbit, how should they be regulated by various countries, how should they fit into existing spectrum and orbital rules, data compliance and export control frameworks, and whether the existing boundaries of financial and cryptocurrency regulation will be forced to redraw when the cryptocurrency industry outsources trading matching, risk control models, or on-chain infrastructure computing power to such “in-orbit clouds.”
Regulatory Threshold from Starlink to Starmind
Starlink has provided SpaceX with a relatively clear “satellite internet compliance template”: in the U.S., it must go through FCC’s spectrum and constellation approvals, writing every segment of frequency and layer of orbit into the license; on an international level, it must obtain spectrum and orbital resource registration and coordination through the ITU to avoid systemic interference with other constellations; when actually serving users, various regulatory agencies require local communication licenses or partnerships with local operators, accompanied by national security and data compliance checks. This entire pathway means that Starlink is still classified as “communication infrastructure,” with its regulatory focus concentrated on spectrum usage, interference control, national security access, and user data processing.
If Starmind evolves as currently disclosed, it will no longer be a single communication constellation but aims to be an “in-orbit AI data center network,” merging communication with large-scale computing: each satellite serves as both a link node and a solar-powered flying computing node. The first batch of AI1 satellites is expected to start deployment and computing power testing around 2027, with a related planning cap of up to 1 million satellites. This means there are at least two additional layers of regulatory dimensions compared to Starlink: one is at the data and cloud service dimension, where in-orbit computing is essentially a spatial extension of cross-border data processing and cloud services, which will inevitably fall under the purview of GDPR, U.S. data and cloud service regulations, and various countries’ data export rules; the second is related to sensitive computing power and export controls: the U.S. already has a mature framework for advanced AI chips, computing power exports, and sanctions against specific countries or entities, and as long as Starmind provides computing power or data processing capabilities to regulated regions or entities, it may be included in this system. At the same time, the scale leap of up to 1 million satellites will greatly amplify concerns about orbital resource management and interference risks, making ongoing regulatory obligations of the FCC, ITU, and launching countries under the Outer Space Treaty more difficult to apply simply with Starlink-era constellation approval thinking. For SpaceX, transitioning from Starlink to Starmind is not just a linear extension of “filling out a few more forms,” but rather closer to a new starting point where regulatory thresholds in spectrum, orbital positions, data, and computing power are raised simultaneously.
Who Will Regulate Compliance of In-Orbit AI Data Centers
In terms of nature, Starmind is not a simple “denser communication constellation” but transforms each satellite into an in-orbit AI data center node capable of both downlink communication and local computing and storage. From a compliance perspective, it adds three overlapping identities: first, it needs to be treated like Starlink as a communication facility subject to spectrum and constellation approvals; second, it provides a “cloud + computing power” infrastructure for global users to offer algorithm hosting and data processing; third, it actually undertakes key roles in cross-border scenarios concerning data export and computing power output. This means it must be treated as both traditional satellite scrutiny and inevitably brought into the regulatory purview of countries concerning cloud services, cross-border data, and computing power output.
If we break it down according to existing legal frameworks, the outer layer is international space law. Documents like the Outer Space Treaty clearly impose “continuous regulation” and international responsibilities on the launching country for its domestic entities, so once Starmind enters the deployment phase, regulatory authorities in the launching country must provide a pathway for conducting substantial reviews of in-orbit AI computing behaviors. However, space law itself almost does not touch on data protection and algorithm liability, only offering a framework of “who is responsible” without addressing “which country's data laws apply.” The second layer is traditional communication regulation: Starlink has already passed spectrum and orbital coordination through the FCC in the U.S. and the ITU internationally; countries require local communication licenses or partnerships with local operators upon implementation, along with national security and data compliance checks. Starmind, if it provides connections or computing power to the ground, will similarly not escape this licensing system. The third layer pertains to data and computing power: in ground-based data center scenarios, cross-border data processing must comply with GDPR, U.S. data and cloud service regulations, and various countries' data export rules. Once in-orbit computing participates in processing data of EU or other jurisdictions' residents, it will in principle still be viewed as cross-border processing, just with the server's physical location being in orbit, rendering the legal qualification of the “data export destination” more ambiguous. In addition, the U.S. has already formed a strict system regarding the export of advanced AI chips and computing power, as well as sanctions on specific entities, and it has frequently enforced sanctions violations in the cryptocurrency field. If Starmind's computing power is used in sensitive industries or for sanctioned entities, it may likely face restrictions under “computing power service export” and sanction rules. Regulatory authorities in multiple jurisdictions have repeatedly emphasized that as long as services are provided to domestic users, even if the infrastructure is completely located abroad, it may still fall under domestic regulation; this means that even if computing power physically “escapes to orbit,” legally it is unlikely to evade ground regulatory radius.
The reality is that there is currently no independent, mature regulatory framework specifically targeting “orbital data centers” publicly established globally, and regulatory practices can mostly only be stitched together between space law, communication law, data protection, and export control, leaving many gray areas concerning subjects, applicable laws, and enforcement authority. For the cryptocurrency industry, which is already highly reliant on cloud and third-party computing power, and exploring physical infrastructure-based incentives in directions such as DePIN, Starmind-class in-orbit computing may likely be seen as yet another cross-border cloud and communication infrastructure, prioritizing the application of existing national rules rather than enjoying a “space exemption.” Ultimately, the questions of who will regulate the in-orbit AI data center and under what licensing system remain key uncertainties that directly determine whether it can become a compliant option for cryptocurrency infrastructure.
Orbital Computing and Cryptocurrency Infrastructure
From a technical pathway perspective, if in-orbit AI networks like Starmind can expose general computing power interfaces, they can potentially be used by cryptocurrency trading platforms, on-chain risk control service providers, or DePIN projects as “another layer of cloud”: the front-end matching or off-chain order book can be completed by satellite clusters, with AI models in orbit conducting real-time risk control scoring on user behavior, trading counterparts, and capital flows, with results executed on-chain through contract to enforce limits or liquidation logic; DePIN projects could incorporate satellite communication and computing nodes into incentive systems, settling on-orbit inference, storage, or routing services through on-chain contracts. The cryptocurrency industry has long been accustomed to outsourcing model inference, risk control, and data analysis to cloud or distributed computing networks, and if in-orbit computing is competitively priced and has low latency, it is essentially just moving this model from data centers to orbit.
However, once critical business processes migrate to orbit, compliance issues will become more complex than “offshore clouds.” First, there’s the difficult question of establishing the “territory” of data and infrastructure: core communication and spectrum must comply with FCC, ITU approvals, and various national communication licensing under the Starlink path, while the data processing layer must face GDPR and various national data export rules, and space activities themselves still fall under the Outer Space Treaty framework, with the launching country bearing continuous regulatory and international responsibilities. Second, if in-orbit computing directly participates in trading matching, clearing risk control, or oracle calculations, regulators may easily classify it as “critical financial infrastructure,” applying existing logic—so long as it provides services to domestic users, it can assert jurisdiction, even if the satellite is registered in another country and its physical location is in orbit. After layering the launching country’s space regulation, servicing country’s financial and data regulation, and computing power export and sanction rules, the traditional narrative of regulatory arbitrage via “nodes being offshore” will be rewritten as a network of overlapping responsibilities across multiple territories, significantly shrinking the space for cryptocurrency projects to evade local rules by leveraging “in-orbit nodes.”
How Multiple Countries' Regulations Might Respond
From the U.S. perspective, once Starmind enters substantial deployment phase, the gateway will likely remain in communication and space regulation: the spectrum and constellation approvals overseen by the FCC will first assess whether these “in-orbit AI data centers” will continue to utilize the spectrum, orbit, and interference assessment frameworks of projects like Starlink, or if it needs a separate category. At the same time, the launching country has a continuing regulatory responsibility under the Outer Space Treaty, so U.S. authorities will have reason to impose conditions related to national security, data processing, and service recipients in the approval process. Subsequently, the Department of Commerce might evaluate whether providing in-orbit computing services to specific countries or entities constitutes controlled export from the perspective of advanced computing power and technology export; within the Treasury system, sanction and financial intelligence agencies may reference existing enforcement practices in the cryptocurrency field, requiring operators and recipients to perform geographical and entity screenings on on-chain businesses to prevent providing settlement, tumbling, or identity-hiding computing and network support to sanctioned entities. For projects attempting to build DePIN-type cryptocurrency infrastructure directly on Starmind, as long as they reach U.S. users or use channels related to the U.S. dollar, U.S. financial regulators could invoke the principle of “providing services to domestic users” to demand implementation modifications or take blocking measures through KYC/AML, transaction monitoring, and compliance with sanctions.
In the EU and other major jurisdictions, regulatory touchpoints are more likely to appear at the AI and data protection levels. The EU’s already passed AI Act and GDPR together mean that once applications hosted on Starmind are defined as high-risk AI (for instance, for trading risk control, identity verification, or on-chain behavior scoring), both providers and EU recipients need to meet a suite of obligations including model transparency, risk management, and human oversight, while ensuring that on-chain and off-chain data involving EU users comply with strict data transfer rules along the “in-orbit processing—cross-border return” pathway. Generally, countries require local communication licenses and security checks as commercial satellite internet is implemented; if Starmind directly opens AI computing power or network access to local users, it will be very challenging in practice to bypass collaboration with local operators or licensed entities, and related approval processes will naturally prioritize checks regarding sanctions enforcement, KYC/AML capabilities, and whether it involves regulated technology output. All in all, for all participants attempting to outsource cryptocurrency businesses to in-orbit computing, compliance with sanctions, identity and source of funds checks, and whether computing power and model outputs touch on technology export controls will constitute the compliance red line that is delineated first and is unlikely to soften in the short term.
Compliance Preparation for Cryptocurrency Projects and Platforms
For the cryptocurrency industry, in-orbit AI computing power similar to Starmind presents potential opportunities for low latency, wide coverage, and more decentralized physical infrastructure. On the other hand, its legal boundaries are currently highly uncertain: the information regarding Starmind at this stage mainly comes from community disclosures and second-hand reports; SpaceX has not released any formal regulatory documents or prospectuses, and the first batch of AI1 satellites is merely expected to start deployment and testing around 2027, which leaves any business design based on such computing power still at the “hypothetical compliance framework” stage. In this uncertainty, when cryptocurrency projects and platforms choose underlying computing power and cloud services, they can at least leverage existing cloud compliance experience into the in-orbit scenario: continuously reviewing the actual processing and landing locations of data (including the jurisdiction where ground stations are located), clarifying the sanction risk exposure of service providers and end users, conducting due diligence on third-party computing power and operators to confirm their capability to respond to various countries' cross-border data regulations, U.S. export control requirements, and local regulatory investigations, while locking down responsibilities regarding log retention, audit access, service interruptions, and compliance with regulatory directives in the contracts. Historical experience shows that the compliance boundaries of new infrastructures (such as cloud computing, CDN, etc.) are often “mapped” by the first batch of licensing paths and enforcement cases, so it will be crucial in the upcoming years to monitor whether SpaceX and various national regulatory agencies publicly file for license applications related to in-orbit AI data centers, environmental and safety reports, and the first cases concerning related service providers. Those who can first bundle the technological narrative of in-orbit computing power with verifiable compliance pathways in this round of infrastructure evolution will gain greater regulatory predictability and cross-border business space in the coming years.
Join our community to discuss and become stronger together!
Exclusive Hyperliquid benefits for AiCoin: https://app.hyperliquid.xyz/join/AICOIN88
Exclusive Aster benefits for AiCoin: https://www.asterdex.com/zh-CN/referral/9C50e2
On-chain Telegram community: https://t.me/AiCoinWhaleData
On-chain community: https://www.aicoin.com/link/chat?cid=N6OVMor5g
AiCoin on-chain Twitter: https://x.com/aicoinwhaledata
免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。
