Loading...
Loading
Overview
Registration Activity
Neuron registration trends
This Interval
0
— burn · — PoW
Target / Interval
Loading
Neuron registration trends
InfiniteHash Subnet (SN89) is a decentralized Bitcoin mining and Lightning Network infrastructure platform that combines mining operations with Lightning node quality scoring. Miners contribute hashrate via Bitcoin ASIC miners pointed at a pool, earn Alpha tokens proportional to their contribution, and validators score miners based on hashrate contribution and Lightning node quality to allocate rewards in a sustainable, auction-based incentive system.
InfiniteHash operates as a decentralized Bitcoin mining pool with integrated Lightning Network infrastructure. Miners operate ASIC hardware pointing to a centralized Luxor pool endpoint, with their contributions identified via worker names containing their Bittensor hotkey. Validators run Django-based backend services (with PostgreSQL and Redis) that monitor pool mining data, track miner hotkey contributions, assess Lightning node quality, and execute the auction-based scoring mechanism.
The subnet architecture separates mining (decentralized ASIC hardware at miner locations) from validation/scoring (centralized validator backend infrastructure) with communication via pool metadata and on-chain Bittensor state.
Phase 1 (launch/market discovery): All mined Bitcoin converts to Alpha and is burned, creating continuous buying pressure as market discovers sustainable Alpha-to-hashrate conversion rates. Phase 2 (sustainable economics): Minimum hashrate threshold for base rewards eliminates incentive to overpromise hash. Alpha denominated hashprice targets exceeding BTC hashprice available in market after pool fees.
Miners run Lightning nodes to compete on quality (creating uid curve) for incremental rewards beyond base hashrate rewards. Validators assess both hashrate consistency and Lightning node operational quality.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository
Proof of Edge - Trading signals
This information was auto-extracted from the GitHub repository and may be incomplete or out of date. Always refer to the subnet's GitHub repository for the latest instructions.
Holder & total-staked metrics as of 1h ago (hourly snapshot)
Bitcoin ASIC miners required. No subnet-specific configurations needed beyond standard Bittensor baseminer setup. Miners point ASICs to Luxor pool endpoint and configure worker names with format: infinite.YOUR_HOTKEY.your_workerID
Validators run containerized services via Docker Compose. Must support Python 3.11, uv package manager, and nox task runner. Database and Redis backends required.
Procure Bitcoin ASIC hardware for mining operations
Obtain Bitcoin ASIC miners
Install standard Bittensor baseminer with no subnet-specific configurations
Install Bittensor baseminer
Set worker name using your Bittensor hotkey and chosen worker identifier
Configure worker with format: infinite.YOUR_HOTKEY.your_workerID
Configure ASIC pool endpoint to Luxor pool (or regional alternative). Use configured worker name as pool credentials.
Point ASICs to stratum+tcp://btc.global.luxor.tech:700
Install Docker with Compose plugin, Python 3.11, and required tools
apt-get install docker.io docker-compose python3.11 curl
Install uv package manager
curl -LsSf https://astral.sh/uv/install.sh | sh
Install nox task runner
pip install nox==2025.5.1
Run setup script and start Docker services (development) or ./setup-prod.sh for production
./setup-dev.sh && docker compose up -d
Wait for PostgreSQL database to be ready
cd app/src && uv run manage.py wait_for_database --timeout 10
Run Django database migrations
uv run manage.py migrate
Start development server (or use gunicorn for production)
uv run manage.py runserver
Set environment variables for database credentials, Redis connection, and Lightning network configuration
Configure .env file with database, Redis, and Lightning node parameters
Configure SSL certificates for HTTPS (production only)(optional)
Optional: ./letsencrypt_setup.sh && mkdir letsencrypt
