Basilica (SN39)

Overview

Basilica is a service for renting computing power, especially graphics processing units, or GPUs. GPUs can handle many calculations at once, which makes them useful for training and running artificial intelligence models. Basilica gives developers ways to find machines, connect to them, and deploy applications through a command-line tool, software development kits, and an API. Its published tools also let customers fund service credits with Bittensor’s TAO currency. (github.com)

Basilica was historically associated with Bittensor subnet 39, often written SN39. Bittensor subnets have their own alpha assets under the network’s Dynamic TAO system. The distinction between the cloud service and the subnet matters: Basilica documents GPU rentals and TAO-funded customer credits, while Bittensor’s alpha system governs staking and incentives tied to a subnet. Cathedral’s project documentation now identifies SN39 as its compute subnet. (github.com)

What the names mean

Basilica names the developer-facing compute service. TAO is Bittensor’s network currency and a documented way to add Basilica service credits. SN39 alpha refers to the Bittensor asset associated with subnet 39. These names describe different parts of the ecosystem, even though Basilica and SN39 have a shared history. (github.com)

History & Team

From subnet software to cloud tools

Basilica’s open-source repository was developed under the one-covenant organization. Its earlier code included miner and validator components for Bittensor, while its current public introduction focuses on the tools customers use to rent GPUs and deploy services. The wider Covenant site presents Basilica alongside other projects, including Templar. Basilica’s development therefore spans both subnet infrastructure and a cloud product built for application developers. (github.com)

A later project, Cathedral, describes its compute code as a fork of Basilica’s open-source work. Its documentation credits contributors to the earlier Covenant AI code, including Evan Pappas, itzlambda, and open-junius. Cathedral now describes its own work on SN39. This sequence explains why older descriptions pair the Basilica name with subnet 39, while newer SN39 materials may use another project name. (github.com)

The public materials establish Basilica’s development organization and named code contributors. They provide a stronger basis for describing the project than attaching unrelated company histories or investor lists to the SN39 asset. (github.com)

Technology & How It Works

Renting a GPU machine

Basilica’s basic workflow begins with a developer choosing available compute. The command-line tool can list machines, start a rental, show active rentals, open a secure shell connection, and shut a machine down. A developer might use that machine to prepare data, train a model, or run a program that answers AI requests. Basilica describes both secure-cloud and community-cloud GPU rentals in its repository. (github.com)

The service also supports a different workflow: deploying an application from a container image. A container packages software and its dependencies so it can run in a prepared environment. Instead of managing a rented machine through a shell, a developer can publish a service with an HTTP endpoint. Basilica’s examples include inference servers and custom containers. An inference server runs a trained model to produce outputs from new requests. (github.com)

Tools for automation

Basilica offers Python and Rust development tools as well as its command-line interface. These let a program request resources, check their status, and end them when work is complete. API tokens provide access for automated applications. Basilica’s documentation separates machine rentals, public service deployments, and account operations so developers can choose the tool that fits their task. (github.com)

Bittensor’s subnet technology works at a different layer. In the network’s general design, miners perform a subnet’s work and validators evaluate their contributions. The rules for judging that work belong to the subnet’s active mechanism. That is why understanding a compute product’s rental workflow is different from understanding how a subnet assigns rewards. (docs.learnbittensor.org)

Tokenomics & Utility

TAO, alpha, and service credits

Bittensor’s Dynamic TAO system gives each eligible subnet an alpha asset. When TAO is staked into a subnet, the network exchanges it for that subnet’s alpha through an on-chain pool. Alpha held as stake can contribute to a validator’s stake weight, while subnet emissions provide incentives for network participants according to Bittensor’s rules. The system creates a token economy around subnet participation. (docs.learnbittensor.org)

Basilica’s documented customer payment flow uses TAO in another way. Customers can send TAO to a deposit address and receive credits in their Basilica account for cloud services. Those account credits serve the rental and deployment workflow. SN39 alpha follows Bittensor’s staking system; Basilica credits follow the service’s account system. The project’s public customer guides describe the TAO funding process and how to check credit balances. (github.com)

This distinction helps explain token utility without treating every form of participation as the same transaction. A developer renting a GPU needs access to compute and a funded service account. A person acquiring subnet alpha is taking part in Bittensor’s subnet-asset system. The purpose and accounting of each activity differ. (github.com)

Ecosystem & Use Cases

Work that needs computing power

Basilica’s clearest use case is giving developers access to GPUs without first assembling their own fleet. Its documentation covers machine rentals for training, inference, and interactive work. It also covers public endpoints for applications that need to answer requests over the internet. The same tools can support a short experiment or a program that starts and manages resources automatically. (github.com)

One example is model evaluation. A validator guide for Covenant’s Crusades project describes requesting a Basilica deployment, running evaluation software on a GPU, and sending work to that deployment for testing. This shows how a compute service can support work elsewhere in the Bittensor ecosystem: another project uses the available hardware as part of its own process. (github.com)

Basilica also documents deployments for containerized applications and AI services, including OpenClaw instances. For developers, the common feature is control over compute: they can request a machine when they need direct access or deploy a service when they need a reachable application endpoint. (github.com)

Advantages & Challenges

Developer access

Basilica’s main advantage is that it brings several compute tasks into one set of tools. Developers can browse machines, rent a GPU, connect through SSH, deploy a container, and automate those actions with code. Published guides and runnable examples make the workflow easier to understand. TAO-funded credits also connect the cloud service to people already using the Bittensor network. (github.com)

The main challenges are practical. GPU rentals call for machine access, software setup, and resource management; deployed services call for a working container and application configuration. On the token side, the history of SN39 adds a naming challenge. Basilica’s service documentation describes customer cloud operations, while Cathedral’s documentation describes current work on SN39. Readers need the project name, subnet number, and intended activity to identify which system they mean. (github.com)

Where to Buy & Wallets

Accessing SN39 alpha

SN39 alpha can be acquired through Bittensor’s native subnet-staking process. A Bittensor wallet holding TAO can stake to subnet 39, exchanging TAO for the subnet’s alpha asset under Dynamic TAO. Bittensor’s command-line tools support wallet creation and subnet staking. The subnet number identifies the on-chain destination, while the associated project name should be read as part of that subnet’s history. (docs.learnbittensor.org)

Basilica cloud credits are funded through Basilica’s own account tools. The documented basilica fund command provides a TAO deposit address, and basilica balance shows the service-credit balance. A Bittensor wallet is used to send TAO; the resulting credits appear in the Basilica service account for compute use. (github.com)

Regulatory & Compliance

Digital assets and cloud services

Basilica brings together a cloud service and transactions involving digital assets. In the United States, the Internal Revenue Service treats digital assets as property for federal tax purposes. Sales and exchanges can have tax consequences, and digital assets received for work can also be taxable income. Rules for businesses that exchange or transmit virtual currency depend on what those businesses actually do. (irs.gov)

In the European Union, the Markets in Crypto-Assets framework sets authorization requirements for firms providing covered crypto-asset services. How those requirements apply depends on the activity being offered. Renting computing power, operating a customer-credit account, and providing a crypto-asset exchange service are distinct activities for this purpose. (esma.europa.eu)

Basilica’s published materials do not establish a formal halal or shariah-compliance classification for SN39 alpha. An Islamic finance assessment would consider how the asset is acquired and used, along with the subnet’s incentive design and relevant principles concerning interest, excessive uncertainty, and gambling. The documented compute service and Bittensor’s general alpha mechanism explain the activities involved, but do not supply a formal religious ruling. (github.com)

Future Outlook

Product and subnet paths

Basilica’s published tools point toward continued use as developer infrastructure. Its command-line interface, software kits, and API give builders several ways to put GPU capacity to work. The customer-facing direction is clear in the documented workflows: rentals for direct machine access, deployments for public services, and account tools for managing credits. (github.com)

SN39’s path is described through Cathedral’s separate compute documentation. Its presence on the subnet illustrates how open-source code and Bittensor subnet activity can continue along a different path from the service that produced earlier software. For readers following Basilica, future product changes belong to its cloud-service story; changes to SN39’s active mechanism belong to the subnet story. (github.com)

Summary

Basilica makes GPU computing available through rentals, deployments, and developer tools. Its history connects it to Bittensor subnet 39, while its documented cloud service uses TAO-funded account credits. SN39 alpha operates through Bittensor’s subnet-staking system, and Cathedral now documents its work on that subnet. Understanding those separate roles gives readers a clearer picture of Basilica’s place in the crypto and AI-compute ecosystem. (github.com)