Set up Bitcoin node and Lightning infrastructure with Docker
Create Docker Compose configuration, Bitcoin and LND configuration files, and bootstrap/init scripts for setting up a Bitcoin full node, LND, and LNbits on a Digital Ocean droplet. Replit-Commit-Author: Agent Replit-Commit-Session-Id: 418bf6f8-212b-4bb0-a7a5-8231a061da4e Replit-Commit-Checkpoint-Type: full_checkpoint Replit-Commit-Event-Id: 0b0f1422-94e9-40dc-9b10-29c5f33a1bac Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/9f85e954-647c-46a5-90a7-396e495a805a/418bf6f8-212b-4bb0-a7a5-8231a061da4e/sPDHkg8 Replit-Helium-Checkpoint-Created: true
This commit is contained in:
30
infrastructure/configs/bitcoin.conf
Normal file
30
infrastructure/configs/bitcoin.conf
Normal file
@@ -0,0 +1,30 @@
|
||||
# Bitcoin Core — mainnet
|
||||
# Placed at /data/bitcoin/bitcoin.conf on the droplet
|
||||
|
||||
# Network
|
||||
server=1
|
||||
listen=1
|
||||
bind=0.0.0.0
|
||||
|
||||
# RPC (internal Docker network only — never exposed publicly)
|
||||
rpcbind=0.0.0.0
|
||||
rpcallowip=172.0.0.0/8
|
||||
rpcuser=satoshi
|
||||
# rpcpassword is set by setup.sh — do not hardcode here
|
||||
|
||||
# ZMQ — LND uses these to get notified of new blocks/txs
|
||||
zmqpubrawblock=tcp://0.0.0.0:28332
|
||||
zmqpubrawrx=tcp://0.0.0.0:28333
|
||||
|
||||
# Performance
|
||||
dbcache=512
|
||||
maxmempool=300
|
||||
maxconnections=40
|
||||
|
||||
# Prune options — choose one:
|
||||
# Full node (recommended, ~600GB): comment out both prune lines
|
||||
# Pruned (~10GB, lower cost but loses historical tx data):
|
||||
# prune=10240
|
||||
|
||||
# Logging
|
||||
debug=0
|
||||
Reference in New Issue
Block a user