Implement logout command for Miago CLI and add Bitcoin Core blockchain integration documentation with credentials management by Copilot · Pull Request #7 · SumnersMetaverse/Miago.AI

Copilot · 2025-12-22T05:17:58Z

Original prompt

commands/logout.go

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

SumnersMetaverse · 2025-12-31T10:23:07Z

@copilot contrib/mempool-space/bitcoin.conf.example

contrib/mempool-space/bitcoin.conf.example

Bitcoin Core Configuration for mempool.space Integration

This file contains example configuration settings for running Bitcoin Core

with mempool.space. Copy relevant sections to your bitcoin.conf file.

Location of bitcoin.conf:

- Linux: ~/.bitcoin/bitcoin.conf

- macOS: ~/Library/Application Support/Bitcoin/bitcoin.conf

- Windows: %APPDATA%\Bitcoin\bitcoin.conf

##############################################################################

Required Settings for mempool.space

##############################################################################

Enable RPC server (required for mempool.space to connect)

server=1

Enable REST API (recommended for efficient data queries)

rest=1

Enable transaction index (required for full transaction lookup functionality)

Note: Enabling this requires a one-time reindex with -reindex flag

txindex=1

##############################################################################

RPC Authentication

##############################################################################

Set RPC username and password

IMPORTANT: Use strong credentials in production!

For better security, use rpcauth instead of rpcpassword

Generate with: python3 share/rpcauth/rpcauth.py

rpcuser=mempool
rpcpassword=change_this_to_a_strong_password_in_production

Alternative: Use rpcauth for better security

Generate with: python3 share/rpcauth/rpcauth.py

Example output format:

rpcauth=mempool:hash$salt

Then use the generated password in your mempool.space config

##############################################################################

RPC Network Settings

##############################################################################

Bind RPC to specific IP (localhost only for security)

rpcbind=127.0.0.1

Allow RPC connections from localhost

rpcallowip=127.0.0.1

If mempool.space backend is on a different machine, add its IP:

rpcallowip=192.168.1.100

RPC port (defaults: mainnet=8332, testnet=18332, signet=38332, regtest=18443)

Uncomment to use non-default port:

rpcport=8332

##############################################################################

ZMQ Settings (Optional but Recommended)

##############################################################################

ZMQ enables real-time notifications instead of polling

This significantly improves mempool.space responsiveness

Publish raw block data

zmqpubrawblock=tcp://127.0.0.1:28332

Publish raw transaction data

zmqpubrawtx=tcp://127.0.0.1:28333

Publish block hash

zmqpubhashblock=tcp://127.0.0.1:28334

Publish transaction hash

zmqpubhashtx=tcp://127.0.0.1:28335

ZMQ for sequence notifications

zmqpubsequence=tcp://127.0.0.1:28336

##############################################################################

Mempool Settings

##############################################################################

Maximum mempool size in megabytes (default: 300)

Increase if you want to track more transactions

maxmempool=300

Minimum fee rate for transaction relay (default: 0.00001 BTC/kB)

minrelaytxfee=0.00001

Maximum orphan transactions kept in memory (default: 100)

maxorphantx=100

##############################################################################

Performance Tuning

##############################################################################

Database cache size in megabytes (default: 450)

Increase for better performance, especially during initial sync

dbcache=1024

Maximum number of inbound+outbound connections (default: 125)

maxconnections=125

Number of threads to service RPC calls (default: 4)

rpcthreads=8

Enable coinstatsindex for faster UTXO set statistics (optional)

coinstatsindex=1

##############################################################################

Network Selection

##############################################################################

Mainnet (default - no flag needed)

[No settings required for mainnet]

Testnet (Bitcoin test network)

testnet=1

Signet (another test network)

signet=1

Regtest (local regression test network for development)

regtest=1

##############################################################################

Logging

##############################################################################

Enable debug logging for specific categories (useful for troubleshooting)

debug=mempool

debug=rpc

debug=http

Or enable all debug logging (generates large log files!)

debug=1

##############################################################################

Additional Security Settings

##############################################################################

Disable RPC access to certain methods (comma-separated list)

Example: disable wallet functions if not needed

disablewallet=1

Whitelist specific RPC methods (all others will be disabled)

rpcwhitelist=user:getblockchaininfo,getmempoolinfo,getrawmempool

Disable DNS seeds (use if you have trusted peers)

dnsseed=0

Disable peer bloom filters (recommended for public nodes)

peerbloomfilters=0

Disable listening for incoming connections (if not needed)

listen=0

##############################################################################

Pruning (Optional - NOT recommended for mempool.space)

##############################################################################

Note: Pruning is NOT recommended when running mempool.space as it needs

access to historical blockchain data. However, if disk space is limited:

Enable pruning and keep only last X MB of blocks

prune=50000

WARNING: With pruning enabled, some mempool.space features may not work:

- Historical block data will be limited

- Cannot fully validate old transactions

- Transaction index may be incomplete

##############################################################################

Example Configurations by Use Case

##############################################################################

=== Minimal Setup (Basic mempool.space support) ===

server=1

rest=1

rpcuser=mempool

rpcpassword=secure_password

rpcbind=127.0.0.1

rpcallowip=127.0.0.1

=== Recommended Setup (Full functionality) ===

server=1

rest=1

txindex=1

rpcuser=mempool

rpcpassword=secure_password

rpcbind=127.0.0.1

rpcallowip=127.0.0.1

zmqpubrawblock=tcp://127.0.0.1:28332

zmqpubrawtx=tcp://127.0.0.1:28333

zmqpubhashblock=tcp://127.0.0.1:28334

dbcache=1024

maxmempool=300

=== High-Performance Setup (For busy explorers) ===

server=1

rest=1

txindex=1

coinstatsindex=1

rpcuser=mempool

rpcpassword=secure_password

rpcbind=127.0.0.1

rpcallowip=127.0.0.1

zmqpubrawblock=tcp://127.0.0.1:28332

zmqpubrawtx=tcp://127.0.0.1:28333

zmqpubhashblock=tcp://127.0.0.1:28334

zmqpubhashtx=tcp://127.0.0.1:28335

zmqpubsequence=tcp://127.0.0.1:28336

dbcache=4096

maxmempool=500

rpcthreads=16

maxconnections=200

##############################################################################

Notes

##############################################################################

1. After adding txindex=1, you need to reindex once:

bitcoind -reindex

2. ZMQ requires Bitcoin Core to be compiled with ZMQ support

Most distributions include this by default

3. For production use, consider using rpcauth instead of rpcpassword

Generate with: python3 share/rpcauth/rpcauth.py

4. Always use a firewall to restrict access to RPC ports

5. Monitor system resources (CPU, RAM, disk I/O) and adjust settings

accordingly

6. For multiple mempool.space instances or monitoring tools, consider

setting up a dedicated Bitcoin Core node for each to avoid

overloading a single node

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot · 2025-12-31T10:25:11Z

@copilot contrib/mempool-space/bitcoin.conf.example

contrib/mempool-space/bitcoin.conf.example
...

Created contrib/mempool-space/bitcoin.conf.example with the Bitcoin Core configuration settings for mempool.space integration (ffef055).

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

SumnersMetaverse · 2025-12-31T10:28:45Z

@copilot contrib/mempool-space/README.md

mempool.space Integration

This directory contains configuration examples and documentation for integrating Bitcoin Core with mempool.space.

Quick Start

1. Configure Bitcoin Core

Copy the relevant settings from bitcoin.conf.example to your Bitcoin Core configuration file:

Linux/macOS:

nano ~/.bitcoin/bitcoin.conf

Windows:

notepad %APPDATA%\Bitcoin\bitcoin.conf

Minimal required settings:

server=1
rest=1
txindex=1
rpcuser=mempool
rpcpassword=your_secure_password
rpcbind=127.0.0.1
rpcallowip=127.0.0.1

2. Restart Bitcoin Core

If you enabled txindex=1 for the first time, you need to reindex:

bitcoind -reindex

Otherwise, a normal restart is sufficient:

bitcoind

3. Verify RPC Access

Test that Bitcoin Core RPC is accessible:

curl --user mempool:your_secure_password \
  --data-binary '{"jsonrpc":"2.0","id":"test","method":"getmempoolinfo","params":[]}' \
  -H 'content-type: application/json' \
  http://127.0.0.1:8332/

4. Install and Configure mempool.space

Clone the mempool.space repository:

git clone https://github.com/mempool/mempool.git
cd mempool

Configure the backend to connect to your Bitcoin Core node:

cd backend
cp mempool-config.sample.json mempool-config.json
nano mempool-config.json

Update the configuration:

{
  "CORE_RPC": {
    "HOST": "127.0.0.1",
    "PORT": 8332,
    "USERNAME": "mempool",
    "PASSWORD": "your_secure_password"
  },
  "MEMPOOL": {
    "NETWORK": "mainnet",
    "BACKEND": "none",
    "HTTP_PORT": 8999,
    "API_URL_PREFIX": "/api/v1/",
    "POLL_RATE_MS": 2000
  },
  "DATABASE": {
    "ENABLED": true,
    "HOST": "127.0.0.1",
    "PORT": 3306,
    "USERNAME": "mempool",
    "PASSWORD": "mempool",
    "DATABASE": "mempool"
  }
}

5. Start mempool.space

Using Docker (recommended):

cd mempool/docker
docker-compose up -d

Or manually:

# Install dependencies
cd mempool/backend
npm install
npm run build

# Start backend
npm run start

# In another terminal, start frontend
cd mempool/frontend
npm install
npm run build
npm run serve

6. Access mempool.space

Open your browser and navigate to:

http://localhost:4200

Advanced Configuration

Enable ZMQ for Real-time Updates

Add to your bitcoin.conf:

zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333
zmqpubhashblock=tcp://127.0.0.1:28334

Then update mempool.space backend config:

{
  "CORE_RPC": {
    "HOST": "127.0.0.1",
    "PORT": 8332,
    "USERNAME": "mempool",
    "PASSWORD": "your_secure_password"
  },
  "CORE_RPC_ZMQ": {
    "HOST": "127.0.0.1",
    "PORT": 28332
  }
}

Performance Tuning

For better performance, increase these Bitcoin Core settings:

dbcache=4096           # More cache for better performance
rpcthreads=16         # More threads for handling RPC requests
maxmempool=500        # Larger mempool if you have RAM available

Running on Different Networks

Testnet:

testnet=1

Signet:

signet=1

Regtest (for development):

regtest=1

Update mempool.space config accordingly:

{
  "MEMPOOL": {
    "NETWORK": "testnet"  // or "signet" or "regtest"
  }
}

Troubleshooting

mempool.space shows no data

Check Bitcoin Core is running:
```
bitcoin-cli getblockchaininfo
```

Verify RPC access:

curl --user mempool:password \
  --data-binary '{"method":"getmempoolinfo"}' \
  http://127.0.0.1:8332/

Check mempool.space backend logs:

cd mempool/backend
npm run start  # Check console output

Transaction lookups not working

Ensure txindex=1 is enabled and Bitcoin Core has been reindexed:

bitcoin-cli getindexinfo

Should show:

{
  "txindex": {
    "synced": true,
    "best_block_height": 850000
  }
}

High CPU usage

Reduce polling frequency in mempool.space config:

{
  "MEMPOOL": {
    "POLL_RATE_MS": 5000  // Increase from 2000 to 5000ms
  }
}

Or enable ZMQ to eliminate polling entirely.

Connection refused errors

Check firewall settings:

# Linux - ONLY if mempool.space runs on a different machine
# WARNING: Do NOT allow external access if running on localhost
# This opens your RPC port to the network - only do this if needed
# sudo ufw allow 8332/tcp

# Check if port is listening
netstat -an | grep 8332

Ensure rpcbind and rpcallowip are set correctly in bitcoin.conf.

Security Best Practices

Use strong RPC credentials:

# Generate secure rpcauth
python3 share/rpcauth/rpcauth.py mempool

Restrict RPC access:

rpcallowip=127.0.0.1  # Localhost only
rpcbind=127.0.0.1     # Bind to localhost only

Use firewall rules:

# Only allow localhost connections to RPC port
sudo ufw deny 8332/tcp

Disable unused RPC methods:

rpcwhitelist=mempool:getblockchaininfo,getmempoolinfo,getrawmempool

Run Bitcoin Core and mempool.space as non-root users

Resources

Support

For Bitcoin Core issues:

GitHub Issues: https://github.com/bitcoin/bitcoin/issues
Bitcoin Stack Exchange: https://bitcoin.stackexchange.com/

For mempool.space issues:

GitHub Issues: https://github.com/mempool/mempool/issues
Discord: https://discord.gg/mempool

Contributing

Contributions to improve this integration guide are welcome! Please submit pull requests to the Bitcoin Core repository.

License

This documentation is released under the MIT License, consistent with Bitcoin Core.

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot · 2025-12-31T10:30:33Z

@copilot contrib/mempool-space/README.md

mempool.space Integration

...

Created contrib/mempool-space/README.md with comprehensive integration guide including quick start, advanced configuration, troubleshooting, and security best practices (6ad05e5).

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

SumnersMetaverse · 2025-12-31T10:38:19Z

@copilot contrib/mempool-space/test-integration.py

#!/usr/bin/env python3
"""
Bitcoin Core and mempool.space Integration Test Script

This script helps verify that your Bitcoin Core node is properly configured
for mempool.space integration by testing RPC and REST endpoints.

Usage:
python3 test-integration.py --user <rpc_user> --password <rpc_password>
python3 test-integration.py --help
"""

import argparse
import json
import sys
import urllib.request
import urllib.error
import base64
from typing import Dict, Any, Tuple, Optional

class Colors:
"""ANSI color codes for terminal output"""
GREEN = '\033[92m'
RED = '\033[91m'
YELLOW = '\033[93m'
BLUE = '\033[94m'
RESET = '\033[0m'
BOLD = '\033[1m'

def print_header(text: str) -> None:
"""Print a formatted header"""
print(f"\n{Colors.BOLD}{Colors.BLUE}{'=' * 70}{Colors.RESET}")
print(f"{Colors.BOLD}{Colors.BLUE}{text:^70}{Colors.RESET}")
print(f"{Colors.BOLD}{Colors.BLUE}{'=' * 70}{Colors.RESET}\n")

def print_success(text: str) -> None:
"""Print success message"""
print(f"{Colors.GREEN}✓ {text}{Colors.RESET}")

def print_error(text: str) -> None:
"""Print error message"""
print(f"{Colors.RED}✗ {text}{Colors.RESET}")

def print_warning(text: str) -> None:
"""Print warning message"""
print(f"{Colors.YELLOW}⚠ {text}{Colors.RESET}")

def print_info(text: str) -> None:
"""Print info message"""
print(f" {text}")

def make_rpc_request(
host: str,
port: int,
user: str,
password: str,
method: str,
params: Optional[list] = None
) -> Tuple[bool, Optional[Dict[str, Any]]]:
"""Make a JSON-RPC request to Bitcoin Core"""
if params is None:
params = []

url = f"http://{host}:{port}/"
headers = {
    'Content-Type': 'application/json',
}

# Add basic authentication
credentials = f"{user}:{password}"
encoded_credentials = base64.b64encode(credentials.encode()).decode()
headers['Authorization'] = f'Basic {encoded_credentials}'

data = json.dumps({
    "jsonrpc": "2.0",
    "id": "test",
    "method": method,
    "params": params
}).encode()

try:
    request = urllib.request.Request(url, data=data, headers=headers)
    # Timeout is set to 10 seconds for most RPC calls
    # Some calls like initial sync queries may need longer
    with urllib.request.urlopen(request, timeout=10) as response:
        result = json.loads(response.read().decode())
        if 'error' in result and result['error'] is not None:
            return False, result['error']
        return True, result.get('result')
except urllib.error.HTTPError as e:
    return False, {"code": e.code, "message": str(e)}
except Exception as e:
    return False, {"code": -1, "message": str(e)}

def make_rest_request(
host: str,
port: int,
endpoint: str
) -> Tuple[bool, Optional[Dict[str, Any]]]:
"""Make a REST request to Bitcoin Core"""
url = f"http://{host}:{port}/rest/{endpoint}"

try:
    request = urllib.request.Request(url)
    with urllib.request.urlopen(request, timeout=10) as response:
        result = json.loads(response.read().decode())
        return True, result
except urllib.error.HTTPError as e:
    return False, {"code": e.code, "message": str(e)}
except Exception as e:
    return False, {"code": -1, "message": str(e)}

def test_rpc_connection(host: str, port: int, user: str, password: str) -> bool:
"""Test basic RPC connectivity"""
print_header("Testing RPC Connection")

success, result = make_rpc_request(host, port, user, password, "getblockchaininfo")

if success:
    print_success("RPC connection successful")
    print_info(f"Network: {result.get('chain', 'unknown')}")
    print_info(f"Blocks: {result.get('blocks', 0)}")
    print_info(f"Headers: {result.get('headers', 0)}")
    return True
else:
    print_error(f"RPC connection failed: {result.get('message', 'Unknown error')}")
    return False

def test_rest_endpoint(host: str, port: int) -> bool:
"""Test REST API endpoint"""
print_header("Testing REST API")

success, result = make_rest_request(host, port, "chaininfo.json")

if success:
    print_success("REST API is accessible")
    print_info(f"Chain: {result.get('chain', 'unknown')}")
    return True
else:
    print_error(f"REST API failed: {result.get('message', 'Unknown error')}")
    print_warning("Enable REST with 'rest=1' in bitcoin.conf")
    return False

def test_mempool_info(host: str, port: int, user: str, password: str) -> bool:
"""Test mempool info RPC"""
print_header("Testing Mempool RPC Methods")

success, result = make_rpc_request(host, port, user, password, "getmempoolinfo")

if success:
    print_success("getmempoolinfo works")
    print_info(f"Transactions in mempool: {result.get('size', 0)}")
    print_info(f"Mempool size (bytes): {result.get('bytes', 0):,}")
    print_info(f"Mempool usage (bytes): {result.get('usage', 0):,}")
    print_info(f"Max mempool (bytes): {result.get('maxmempool', 0):,}")
    return True
else:
    print_error(f"getmempoolinfo failed: {result.get('message', 'Unknown error')}")
    return False

def test_mempool_rest(host: str, port: int) -> bool:
"""Test mempool REST endpoint"""
success, result = make_rest_request(host, port, "mempool/info.json")

if success:
    print_success("REST mempool/info endpoint works")
    return True
else:
    print_error(f"REST mempool endpoint failed: {result.get('message', 'Unknown error')}")
    return False

def test_txindex(host: str, port: int, user: str, password: str) -> bool:
"""Test if transaction index is enabled"""
print_header("Testing Transaction Index")

success, result = make_rpc_request(host, port, user, password, "getindexinfo")

if success:
    if 'txindex' in result:
        if result['txindex'].get('synced'):
            print_success("Transaction index is enabled and synced")
            print_info(f"Best block height: {result['txindex'].get('best_block_height', 'N/A')}")
            return True
        else:
            print_warning("Transaction index is enabled but still syncing")
            print_info(f"Progress: {result['txindex'].get('best_block_height', 0)} blocks indexed")
            return False
    else:
        print_error("Transaction index is not enabled")
        print_warning("Enable with 'txindex=1' in bitcoin.conf and restart with -reindex")
        return False
else:
    print_error(f"Could not check transaction index: {result.get('message', 'Unknown error')}")
    return False

def test_zmq_availability(host: str, port: int, user: str, password: str) -> bool:
"""Check if ZMQ is configured"""
print_header("Checking ZMQ Configuration")

success, result = make_rpc_request(host, port, user, password, "getzmqnotifications")

if success:
    if result:
        print_success("ZMQ notifications are configured")
        for notification in result:
            print_info(f"  - {notification.get('type')}: {notification.get('address')}")
        return True
    else:
        print_warning("ZMQ is available but no notifications are configured")
        print_info("For real-time updates, add ZMQ settings to bitcoin.conf:")
        print_info("  zmqpubrawblock=tcp://127.0.0.1:28332")
        print_info("  zmqpubrawtx=tcp://127.0.0.1:28333")
        print_info("  zmqpubhashblock=tcp://127.0.0.1:28334")
        return False
else:
    print_warning("Could not check ZMQ configuration")
    print_info("ZMQ support may not be compiled in this Bitcoin Core build")
    return False

def test_network_info(host: str, port: int, user: str, password: str) -> bool:
"""Get network information"""
print_header("Network Information")

success, result = make_rpc_request(host, port, user, password, "getnetworkinfo")

if success:
    print_success("Network info retrieved")
    print_info(f"Version: {result.get('version', 'unknown')}")
    print_info(f"Subversion: {result.get('subversion', 'unknown')}")
    print_info(f"Protocol version: {result.get('protocolversion', 'unknown')}")
    print_info(f"Connections: {result.get('connections', 0)}")
    return True
else:
    print_error(f"Could not get network info: {result.get('message', 'Unknown error')}")
    return False

def generate_summary(results: Dict[str, bool]) -> None:
"""Generate and print test summary"""
print_header("Test Summary")

total = len(results)
passed = sum(1 for v in results.values() if v)
failed = total - passed

print(f"Total tests: {total}")
print_success(f"Passed: {passed}")
if failed > 0:
    print_error(f"Failed: {failed}")

print("\nDetailed Results:")
for test_name, result in results.items():
    status = "PASS" if result else "FAIL"
    color = Colors.GREEN if result else Colors.RED
    print(f"  {color}{status}{Colors.RESET} - {test_name}")

if passed == total:
    print(f"\n{Colors.GREEN}{Colors.BOLD}All tests passed! Your Bitcoin Core node is ready for mempool.space.{Colors.RESET}")
else:
    print(f"\n{Colors.YELLOW}{Colors.BOLD}Some tests failed. Review the output above for recommended fixes.{Colors.RESET}")

def main():
parser = argparse.ArgumentParser(
description="Test Bitcoin Core configuration for mempool.space integration",
formatter_class=argparse.RawDescriptionHelpFormatter,
epilog="""
Examples:
%(prog)s --user mempool --password mypassword
%(prog)s --host 192.168.1.100 --port 8332 --user mempool --password mypassword
%(prog)s --help
"""
)

parser.add_argument('--host', default='127.0.0.1', help='Bitcoin Core RPC host (default: 127.0.0.1)')
parser.add_argument('--port', type=int, default=8332, help='Bitcoin Core RPC port (default: 8332)')
parser.add_argument('--user', required=True, help='Bitcoin Core RPC username')
parser.add_argument('--password', required=True, help='Bitcoin Core RPC password')

args = parser.parse_args()

print_header("Bitcoin Core & mempool.space Integration Test")
print_info(f"Testing connection to {args.host}:{args.port}")
print_info(f"RPC User: {args.user}")

results = {}

# Run tests
results['RPC Connection'] = test_rpc_connection(args.host, args.port, args.user, args.password)
if not results['RPC Connection']:
    print_error("\nCannot proceed without RPC connection. Please check:")
    print_info("  1. Bitcoin Core is running")
    print_info("  2. RPC credentials are correct")
    print_info("  3. server=1 is set in bitcoin.conf")
    print_info("  4. Host and port are correct")
    sys.exit(1)

results['REST API'] = test_rest_endpoint(args.host, args.port)
results['Mempool Info RPC'] = test_mempool_info(args.host, args.port, args.user, args.password)
results['Mempool REST'] = test_mempool_rest(args.host, args.port)
results['Transaction Index'] = test_txindex(args.host, args.port, args.user, args.password)
results['ZMQ Configuration'] = test_zmq_availability(args.host, args.port, args.user, args.password)
results['Network Info'] = test_network_info(args.host, args.port, args.user, args.password)

# Generate summary
generate_summary(results)

# Exit with appropriate code
sys.exit(0 if all(results.values()) else 1)

if name == 'main':
main()

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot · 2025-12-31T11:11:18Z

@copilot CREDENTIALS-MANAGEMENT-TEMPLATE.md

Credentials Management Template

...

Created CREDENTIALS-MANAGEMENT-TEMPLATE.md - comprehensive template for managing sensitive credentials securely. Includes password manager recommendations, storage solutions for all credential types (Bitcoin Core, LND, Redis, Tenderly, databases, SSH keys, SSL certs), environment variable setup, security best practices, rotation policies, backup strategies, file permissions guide, and incident response procedures (a51f2db).

SumnersMetaverse · 2025-12-31T11:13:14Z

@copilot MEMPOOL-SPACE-CROSS-REFERENCE.md

Cross-Reference Summary: Bitcoin Core & mempool.space

What Was Done

This repository has been enhanced with comprehensive documentation and tools to help you understand and integrate your Bitcoin Core node with mempool.space.

New Files Added

1. Documentation

doc/mempool-space-integration.md - Comprehensive Integration Guide

Detailed explanation of how mempool.space works with Bitcoin Core
Complete API reference (RPC and REST endpoints)
Data flow architecture diagrams
Development considerations for both projects
Testing and debugging guides
Common issues and solutions
Performance optimization tips
Security best practices

2. Configuration Examples

contrib/mempool-space/bitcoin.conf.example - Bitcoin Core Configuration Template

Required settings for mempool.space integration
Optional ZMQ configuration for real-time updates
Performance tuning parameters
Network-specific settings (mainnet, testnet, signet, regtest)
Security hardening options
Three example configurations:
- Minimal setup (basic functionality)
- Recommended setup (full features)
- High-performance setup (for busy explorers)

3. Quick Start Guide

contrib/mempool-space/README.md - Quick Start & Troubleshooting

Step-by-step setup instructions
Quick configuration guide
Common troubleshooting scenarios
Security best practices
Links to additional resources

4. Integration Test Tool

contrib/mempool-space/test-integration.py - Automated Testing Script

Tests RPC connectivity
Verifies REST API availability
Checks mempool endpoints
Validates transaction index status
Inspects ZMQ configuration
Provides detailed test results and recommendations

Usage:

python3 contrib/mempool-space/test-integration.py --user <rpc_user> --password <rpc_password>

What This Enables

For Bitcoin Core Users

Self-host mempool.space: Run your own blockchain explorer with your Bitcoin Core node
Enhanced privacy: Keep your transaction queries private by using your own node
Better understanding: Learn how mempool.space visualizes Bitcoin Core data
Development: Build your own blockchain explorer or analysis tools using the same patterns

For Developers

Integration reference: Complete guide for integrating with Bitcoin Core's mempool APIs
Best practices: Learn optimal configuration for blockchain explorers
Testing tools: Automated scripts to verify your integration
API documentation: Comprehensive reference for all relevant RPC and REST endpoints

For mempool.space Operators

Configuration guide: Properly configure Bitcoin Core for optimal mempool.space performance
Troubleshooting: Quick solutions to common integration issues
Performance tuning: Optimize both Bitcoin Core and mempool.space for your workload
Security: Harden your setup for production environments

How to Use This

Quick Start (5 minutes)

Review the configuration example:

cat contrib/mempool-space/bitcoin.conf.example

Copy recommended settings to your bitcoin.conf:

nano ~/.bitcoin/bitcoin.conf

Add at minimum:

server=1
rest=1
txindex=1
rpcuser=mempool
rpcpassword=your_secure_password

Restart Bitcoin Core:

bitcoind -reindex  # First time with txindex=1

Test the integration:

python3 contrib/mempool-space/test-integration.py --user mempool --password your_secure_password

Follow the quick start in contrib/mempool-space/README.md to set up mempool.space

Deep Dive (30+ minutes)

Read the comprehensive guide:
```
cat doc/mempool-space-integration.md
```
This covers:
- How the integration works
- All available APIs
- Development considerations
- Performance optimization
- Security best practices
Understand the architecture:
- Learn the data flow between Bitcoin Core and mempool.space
- Understand which RPC methods mempool.space uses
- See how ZMQ notifications improve real-time updates
Optimize your setup:
- Choose the right configuration for your use case
- Tune performance parameters
- Implement security hardening

Key Integration Points

Bitcoin Core Provides:

Mempool data via getrawmempool, getmempoolentry, getmempoolinfo RPCs
Block data via getblock, getblockheader RPCs
Transaction data via getrawtransaction RPC (requires txindex=1)
REST endpoints for efficient data access
ZMQ notifications for real-time updates

mempool.space Uses:

Bitcoin Core's RPC API to fetch blockchain and mempool data
REST API for efficient bulk queries
ZMQ for real-time block and transaction notifications
Transaction index for historical transaction lookups

Benefits of This Cross-Reference

1. Clarity

You now understand exactly how mempool.space integrates with Bitcoin Core, what APIs it uses, and how data flows between them.

2. Self-Hosting

Complete guide to run your own mempool.space instance with your Bitcoin Core node for enhanced privacy and control.

3. Development

Reference for building your own tools that integrate with Bitcoin Core's mempool and blockchain data.

4. Troubleshooting

Common issues and solutions documented with clear explanations.

5. Optimization

Performance tuning recommendations for both Bitcoin Core and mempool.space.

6. Security

Best practices for securing your Bitcoin Core RPC interface and mempool.space deployment.

Next Steps

Based on your specific needs, here's what you should do:

If you want to run mempool.space:

Read contrib/mempool-space/README.md
Configure Bitcoin Core using contrib/mempool-space/bitcoin.conf.example
Test integration with contrib/mempool-space/test-integration.py
Clone and configure mempool.space repository
Start your local instance

If you're developing with Bitcoin Core's mempool APIs:

Read doc/mempool-space-integration.md sections on APIs
Review the RPC and REST endpoint documentation
Study the data flow architecture
Use the test script as a reference for API usage
Implement your integration following the patterns documented

If you're investigating compatibility:

Read the integration guide to understand dependencies
Check API version compatibility
Review breaking changes considerations
Test with different Bitcoin Core versions

If you're optimizing performance:

Review the performance tuning sections
Implement ZMQ notifications
Adjust cache and thread settings
Monitor and iterate based on your workload

Resources

All documentation is available in this repository:

Main guide: doc/mempool-space-integration.md
Quick start: contrib/mempool-space/README.md
Configuration: contrib/mempool-space/bitcoin.conf.example
Test tool: contrib/mempool-space/test-integration.py

External resources:

Bitcoin Core RPC docs: doc/JSON-RPC-interface.md
Bitcoin Core REST docs: doc/REST-interface.md
mempool.space repository: https://github.com/mempool/mempool
mempool.space API docs: https://mempool.space/docs/api

Support

For questions about:

Bitcoin Core: https://github.com/bitcoin/bitcoin/issues
mempool.space: https://github.com/mempool/mempool/issues
This integration guide: Open an issue in this repository

Contributing

Improvements to this documentation are welcome! Please submit pull requests with:

Additional troubleshooting scenarios
Performance optimization tips
Security hardening recommendations
Integration examples
Documentation clarifications

Conclusion

You now have everything you need to:

Understand how mempool.space integrates with Bitcoin Core
Configure Bitcoin Core optimally for mempool.space
Self-host your own mempool.space instance
Develop your own tools using the same integration patterns
Troubleshoot common issues
Optimize performance
Secure your deployment

The cross-reference between these repositories is now complete and documented!

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot · 2025-12-31T11:15:20Z

@copilot MEMPOOL-SPACE-CROSS-REFERENCE.md

Cross-Reference Summary: Bitcoin Core & mempool.space

...

Created MEMPOOL-SPACE-CROSS-REFERENCE.md - a comprehensive navigation guide that maps all the Bitcoin Core and mempool.space integration resources in this repository. The document includes an overview of all new files, how they work together, common use cases, quick reference sections, and troubleshooting links (0cd69d8).

SumnersMetaverse · 2025-12-31T11:17:26Z

@copilot REPOSITORY-INTEGRATION-QUICK-REFERENCE.md

Quick Reference: Connecting Your SumnersMetaverse Repositories

IMPORTANT: This is a reference guide. Use YOUR existing credentials from Tenderly, Redis repository, and Bitcoin Core. See USING-YOUR-EXISTING-CREDENTIALS.md for details.

Your Repository Ecosystem

Repository	Purpose	Connects to Bitcoin Core?	Status
bitcoin	Bitcoin Core node	N/A (this is the foundation)	✅ Ready
3xplCore	Blockchain explorer engine	✅ Yes - via RPC	⚠️ Needs setup
lndhub	Lightning Network accounts	✅ Yes - via LND + RPC	⚠️ Needs LND + setup
mining-pools	Mining pool ID data	✅ Yes - read-only	⚠️ Can integrate

Execution Order

1️⃣ Bitcoin Core (Foundation) - ALREADY RUNNING

# Verify it's running
bitcoin-cli getblockchaininfo

# Test RPC access
python3 contrib/mempool-space/test-integration.py --user <your_user> --password <your_pass>

2️⃣ 3xplCore (Blockchain Explorer) - EASIEST TO ADD

# Clone YOUR existing repository
git clone https://github.com/SumnersMetaverse/3xplCore.git
cd 3xplCore

# Use the existing .env.example
cp .env.example .env
nano .env
# Add YOUR Bitcoin Core RPC credentials:
# MODULE_bitcoin-main_NODES[]=http://YOUR_USER:YOUR_PASS@127.0.0.1:8332/

# Run using existing setup
php 3xpl.php bitcoin-main M   # Monitor mode (tracks new blocks)

3️⃣ LND + LndHub (Lightning Network) - MORE COMPLEX

# Install LND first (if not already installed)
wget https://github.com/lightningnetwork/lnd/releases/download/v0.17.3-beta/lnd-linux-amd64-v0.17.3-beta.tar.gz
tar -xzf lnd-linux-amd64-v0.17.3-beta.tar.gz
sudo install -m 0755 -o root -g root -t /usr/local/bin lnd-linux-amd64-v0.17.3-beta/*

# Configure LND with YOUR Bitcoin Core credentials
# Create ~/.lnd/lnd.conf with YOUR values:
[Bitcoin]
bitcoin.active=1
bitcoin.mainnet=1
bitcoin.node=bitcoind

[Bitcoind]
bitcoind.rpchost=127.0.0.1:8332
bitcoind.rpcuser=YOUR_RPC_USER
bitcoind.rpcpass=YOUR_RPC_PASS
bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333

[Bitcoind]
bitcoind.rpchost=127.0.0.1:8332
bitcoind.rpcuser=<your_user>
bitcoind.rpcpass=<your_pass>
bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333

# Start LND
lnd

# Create wallet (in another terminal)
lncli create

# Clone and setup LndHub
git clone https://github.com/SumnersMetaverse/lndhub.git
cd lndhub
npm install

# Copy LND credentials
cp ~/.lnd/data/chain/bitcoin/mainnet/admin.macaroon .
cp ~/.lnd/tls.cert .

# Configure config.js with Bitcoin Core RPC details
nano config.js

# Start Redis
sudo systemctl start redis-server

# Run LndHub
npm start

One-Line RPC Configuration

All these services need your Bitcoin Core RPC credentials:

RPC URL: http://127.0.0.1:8332
Username: [from bitcoin.conf rpcuser=]
Password: [from bitcoin.conf rpcpassword=]

What Each Service Does

Bitcoin Core

What: Full Bitcoin node, stores entire blockchain
How to run: bitcoind (should already be running)
Port: 8332 (RPC), 8333 (P2P)

3xplCore

What: Processes blockchain data into explorer-friendly format
How to run: php 3xpl.php bitcoin-main M
Uses: Bitcoin Core RPC to read blocks and transactions

LND (Lightning Network Daemon)

What: Second-layer payment network on top of Bitcoin
How to run: lnd (needs Bitcoin Core with ZMQ)
Port: 10009 (gRPC), 9735 (P2P)

LndHub

What: Multi-user Lightning wallet service
How to run: npm start (needs LND + Redis + Bitcoin Core)
Port: 3000 (HTTP API)

mining-pools

What: JSON data file for identifying which pool mined each block
How to run: Import data into your scripts/explorers
Uses: Can be queried alongside Bitcoin Core block data

Priority Setup Order

Start Here: Bitcoin Core ✅ (Already done!)
Add Next: 3xplCore (Simple, just needs RPC access)
Advanced: LND + LndHub (Requires more setup)
Data: mining-pools (Use as reference data)

Full Bitcoin Core Config for All Services

Add to ~/.bitcoin/bitcoin.conf:

# Basic settings
server=1
rest=1
txindex=1

# RPC authentication
rpcuser=your_username
rpcpassword=your_secure_password
rpcbind=127.0.0.1
rpcallowip=127.0.0.1

# For LND (Lightning Network)
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333
zmqpubhashblock=tcp://127.0.0.1:28334

# Performance (optional)
dbcache=2048
maxmempool=300

After changing config:

bitcoin-cli stop
bitcoind  # Restart

Test Everything

# 1. Bitcoin Core
bitcoin-cli getblockchaininfo

# 2. Bitcoin Core RPC
curl --user your_user:your_pass \
  --data-binary '{"method":"getblockcount"}' \
  http://127.0.0.1:8332/

# 3. LND (if running)
lncli getinfo

# 4. LndHub (if running)
curl http://127.0.0.1:3000/status

# 5. 3xplCore (if running)
cd ~/projects/3xplCore
php 3xpl.php bitcoin-main B 0  # Get genesis block

Quick Troubleshooting

Problem	Solution
RPC connection refused	Check Bitcoin Core is running: `ps aux \| grep bitcoind`
RPC authentication failed	Verify credentials in bitcoin.conf match what you're using
txindex error	Enable `txindex=1` in bitcoin.conf and run `bitcoind -reindex`
LND won't connect	Check ZMQ settings in bitcoin.conf
Redis error	Start Redis: `sudo systemctl start redis-server`

Get More Help

Full integration guide: doc/repository-integration-guide.md
mempool.space setup: contrib/mempool-space/README.md
Bitcoin Core RPC: doc/JSON-RPC-interface.md

Architecture Diagram

                    ┌─────────────────┐
                    │  Bitcoin Core   │ ← You are here!
                    │   Port 8332     │
                    └────────┬────────┘
                             │ RPC Access
                ┌────────────┼────────────┐
                │            │            │
         ┌──────▼──────┐ ┌──▼───┐  ┌────▼─────┐
         │  3xplCore   │ │ LND  │  │ mining-  │
         │  Explorer   │ │Lightning│ pools    │
         └─────────────┘ └──┬───┘  │ (data)   │
                            │      └──────────┘
                     ┌──────▼──────┐
                     │   LndHub    │
                     │  Port 3000  │
                     └─────────────┘

Remember: Start with Bitcoin Core (✅ done!), add 3xplCore next (easiest), then LND/LndHub if you need Lightning features.

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot · 2025-12-31T11:19:22Z

@copilot REPOSITORY-INTEGRATION-QUICK-REFERENCE.md

Quick Reference: Connecting Your SumnersMetaverse Repositories

...

Created REPOSITORY-INTEGRATION-QUICK-REFERENCE.md with a comprehensive quick reference guide for connecting your SumnersMetaverse repositories. The document includes:

Repository ecosystem table showing all projects and their status
Step-by-step execution order (Bitcoin Core → mempool.space → 3xplCore → LND → lndhub → mining-pools)
Quick setup commands for each component
Environment variables reference
Common commands cheat sheet for Bitcoin Core and LND
Troubleshooting quick links
Docker Compose reference
Security checklist
Documentation index

(40fd7a3)

SumnersMetaverse · 2025-12-31T11:20:39Z

@copilot USING-YOUR-EXISTING-CREDENTIALS.md

Important: Using Your Existing Credentials

What This Documentation Is

The documentation in this repository (doc/mempool-space-integration.md, doc/repository-integration-guide.md, etc.) is reference material that shows you:

HOW to connect your repositories together
WHERE to place configuration values
WHAT order to execute things in
HOW to troubleshoot issues

What This Documentation Is NOT

This documentation does NOT:

❌ Replace your existing Docker files
❌ Replace your existing configuration files
❌ Create new RPC credentials you need to use
❌ Contain your actual server information

Using Your Existing Setup

Your Existing Files to Use

You already have configuration files in your repositories:

lndhub - Already has:
- Dockerfile - Use this!
- config.js - Configure with YOUR credentials
- Docker Compose files (if any)
3xplCore - Already has:
- .env.example - Copy to .env and add YOUR credentials
- Setup scripts
mining-pools - Already has:
- Data files to reference

Your Existing Credentials to Use

From Tenderly.co

You mentioned you have RPC endpoints in Tenderly. Use those:

Your Tenderly RPC URLs
Your Tenderly API keys
Your Tenderly project settings

From Your Redis Repository

You mentioned your private server info is there. Use that:

Your Redis host address
Your Redis port
Your Redis password (if set)
Your server IPs and configurations

From Bitcoin Core

Your Bitcoin Core RPC credentials (from ~/.bitcoin/bitcoin.conf):

Your actual rpcuser value
Your actual rpcpassword value
Your actual rpcport (if custom)

How to Use This Documentation

Step 1: Find Your Actual Credentials

For Tenderly RPC:

Log into https://tenderly.co
Go to your project/dashboard
Navigate to Node RPC section
Find your RPC endpoints (they look like: https://rpc.tenderly.co/fork/YOUR-FORK-ID)
Copy your actual RPC URLs and API keys
Use these in your application configs where RPC endpoints are needed

Note on Tenderly: If you're using Tenderly for Ethereum/EVM chains, those are separate from Bitcoin Core. Tenderly provides:

Ethereum RPC endpoints
Forking and simulation tools
EVM-compatible networks

For Bitcoin Core, you'll use the standard Bitcoin RPC (not Tenderly), configured in bitcoin.conf.

For Redis:

Go to your Redis repository (you mentioned you have one)
Find your server information
Note your Redis host, port, password

For Bitcoin Core:

Check your ~/.bitcoin/bitcoin.conf file
Look for existing rpcuser and rpcpassword lines
Use those values (don't create new ones unless you want to)

Step 2: Update Configuration Files

When the guides say:

rpcuser=mempool
rpcpassword=your_secure_password

This means: Replace "mempool" and "your_secure_password" with YOUR actual credentials.

Step 3: Use YOUR Existing Docker Files

When setting up lndhub or 3xplCore:

Use the existing Dockerfile in those repositories
Update the existing config files with YOUR credentials
Don't create new Docker files - use what's already there

Example: Connecting lndhub

Wrong Approach ❌

Creating new config files from scratch
Using example credentials from documentation

Correct Approach ✅

Clone your existing lndhub repo (you already have this)
Find your existing credentials:
- Bitcoin Core RPC: Check ~/.bitcoin/bitcoin.conf
- Redis: Check your Redis repository
- LND: Use your existing LND setup

Update config.js with YOUR values:

module.exports = {
  bitcoind: {
    rpc: 'http://your-actual-bitcoin-host:8332',  // YOUR Bitcoin Core
  },
  redis: {
    host: 'your-redis-host.com',  // FROM your Redis repository
    port: 6379,
    password: 'your-actual-redis-password',  // FROM your Redis repository
  },
  lnd: {
    url: 'your-lnd-host:10009',  // YOUR LND server
  },
};

Use the existing Dockerfile:

docker build -t my-lndhub .
docker run -p 3000:3000 my-lndhub

Example: Connecting 3xplCore

Correct Approach ✅

Clone your existing 3xplCore repo
Copy the example env:
```
cp .env.example .env
```

Edit .env with YOUR Bitcoin Core RPC:

# Use YOUR actual Bitcoin Core credentials
MODULE_bitcoin-main_NODES[]=http://your-rpc-user:your-rpc-password@127.0.0.1:8332/

Run using existing setup:
```
php 3xpl.php bitcoin-main M
```

TL;DR - Quick Summary

✅ Use your existing Docker/config files from your repositories
✅ Use your existing credentials from Tenderly, Redis repository, and Bitcoin Core
✅ Use this documentation as a reference for HOW to connect everything
❌ Don't create new files - use what you already have
❌ Don't use example credentials - use your actual ones

Still Confused?

Ask yourself:

"Do I have existing Docker files?" → Yes? Use those!
"Do I have existing credentials?" → Yes? Use those!
"What is this documentation for?" → To show you HOW to connect everything, not WHAT to connect with

The guides show the process and structure. You provide the actual values.

Think of it like a recipe:

The documentation is the recipe (instructions)
Your Tenderly/Redis/Bitcoin credentials are the ingredients (actual values)
Your existing Docker/config files are the tools (what you use)

You don't need to create new tools or ingredients - just follow the recipe using what you already have!

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot · 2025-12-31T11:22:37Z

@copilot USING-YOUR-EXISTING-CREDENTIALS.md

Important: Using Your Existing Credentials

...

Created USING-YOUR-EXISTING-CREDENTIALS.md with comprehensive guidance on using your existing credentials from Tenderly, Redis repository, and Bitcoin Core with the documentation in this repository. The guide clarifies that documentation shows HOW to configure, while you provide YOUR actual credentials, and includes step-by-step workflows, credential mapping tables, common misunderstandings, and practical examples (86fa062).

SumnersMetaverse · 2025-12-31T11:23:30Z

@copilot contrib/setup-integration.ps1

@@ -0,0 +1,297 @@# ╔══════════════════════════════════════════════════════════════════════════╗# ║ Bitcoin Core + Repository Integration Setup Script ║# ║ ║# ║ INSTRUCTIONS: ║# ║ 1. Copy this entire script ║# ║ 2. Paste into a text editor ║# ║ 3. Replace ALL values marked with >>>REPLACE THIS<<< ║# ║ 4. Save the file ║# ║ 5. Run in PowerShell as Administrator ║# ╚══════════════════════════════════════════════════════════════════════════╝# ╔══════════════════════════════════════════════════════════════════════════╗# ║ 📝 FILL IN YOUR CREDENTIALS HERE ║# ║ ║# ║ REPLACE each ">>>REPLACE THIS<<<" with your actual values ║# ║ Keep the quotes around your values ║# ╚══════════════════════════════════════════════════════════════════════════╝# ┌─────────────────────────────────────────────────────────────────────────┐# │ 1️⃣ BITCOIN CORE RPC CREDENTIALS │# │ Find these in your bitcoin.conf file or Tenderly.co account │# └─────────────────────────────────────────────────────────────────────────┘$BITCOIN_RPC_USER = ">>>REPLACE THIS<<<" # Example: "mempool"$BITCOIN_RPC_PASSWORD = ">>>REPLACE THIS<<<" # Your secure password$BITCOIN_RPC_HOST = "127.0.0.1" # Usually localhost$BITCOIN_RPC_PORT = "8332" # Default Bitcoin Core RPC port# ┌─────────────────────────────────────────────────────────────────────────┐# │ 2️⃣ REDIS SERVER CREDENTIALS │# │ Find these in your Redis repository or server configuration │# └─────────────────────────────────────────────────────────────────────────┘$REDIS_HOST = ">>>REPLACE THIS<<<" # Example: "redis.example.com"$REDIS_PORT = "6379" # Default Redis port$REDIS_PASSWORD = ">>>REPLACE THIS<<<" # Your Redis password (if set)# ┌─────────────────────────────────────────────────────────────────────────┐# │ 3️⃣ TENDERLY CONFIGURATION │# │ Find these in your Tenderly.co dashboard │# └─────────────────────────────────────────────────────────────────────────┘$TENDERLY_API_KEY = ">>>REPLACE THIS<<<" # From Tenderly settings$TENDERLY_PROJECT_ID = ">>>REPLACE THIS<<<" # Your Tenderly project ID# ┌─────────────────────────────────────────────────────────────────────────┐# │ 4️⃣ PROJECT DIRECTORY (Optional - you can keep this as-is) │# └─────────────────────────────────────────────────────────────────────────┘$PROJECTS_DIR = "$HOME\projects" # Where to clone repositories# ╔══════════════════════════════════════════════════════════════════════════╗# ║ ⚠️ DO NOT EDIT BELOW THIS LINE ⚠️ ║# ║ ║# ║ The code below is automated - you don't need to change anything ║# ╚══════════════════════════════════════════════════════════════════════════╝Write-Host "╔══════════════════════════════════════════════════════════════════════════╗" -ForegroundColor CyanWrite-Host "║ Bitcoin Core Integration Setup ║" -ForegroundColor CyanWrite-Host "╚══════════════════════════════════════════════════════════════════════════╝" -ForegroundColor CyanWrite-Host ""# ┌─────────────────────────────────────────────────────────────────────────┐# │ VALIDATION: Check if user replaced placeholder values │# └─────────────────────────────────────────────────────────────────────────┘Write-Host "Validating configuration..." -ForegroundColor Yellow$placeholdersFound = @()if ($BITCOIN_RPC_USER -eq ">>>REPLACE THIS<<<") { $placeholdersFound += "BITCOIN_RPC_USER"}if ($BITCOIN_RPC_PASSWORD -eq ">>>REPLACE THIS<<<") { $placeholdersFound += "BITCOIN_RPC_PASSWORD"}if ($REDIS_HOST -eq ">>>REPLACE THIS<<<") { $placeholdersFound += "REDIS_HOST"}if ($REDIS_PASSWORD -eq ">>>REPLACE THIS<<<") { $placeholdersFound += "REDIS_PASSWORD"}if ($TENDERLY_API_KEY -eq ">>>REPLACE THIS<<<") { $placeholdersFound += "TENDERLY_API_KEY"}if ($TENDERLY_PROJECT_ID -eq ">>>REPLACE THIS<<<") { $placeholdersFound += "TENDERLY_PROJECT_ID"}if ($placeholdersFound.Count -gt 0) { Write-Host "" Write-Host "❌ ERROR: You haven't replaced all placeholder values!" -ForegroundColor Red Write-Host "" Write-Host "Please edit this script and replace the following:" -ForegroundColor Yellow foreach ($placeholder in $placeholdersFound) { Write-Host " • $placeholder" -ForegroundColor Red } Write-Host "" Write-Host "Look for lines with '>>>REPLACE THIS<<<' at the top of this script" -ForegroundColor Yellow Write-Host "and replace them with your actual credentials." -ForegroundColor Yellow Write-Host "" pause exit 1}Write-Host " ✅ Configuration validated successfully!" -ForegroundColor GreenWrite-Host ""# Function to check if a command existsfunction Test-Command { param($Command) try { Get-Command $Command -ErrorAction Stop | Out-Null return $true } catch { return $false }}# Check prerequisitesWrite-Host "Checking prerequisites..." -ForegroundColor Yellow$prerequisites = @{ "bitcoin-cli" = "Bitcoin Core" "git" = "Git" "python" = "Python 3" "node" = "Node.js"}$missing = @()foreach ($cmd in $prerequisites.Keys) { if (Test-Command $cmd) { Write-Host " [OK] $($prerequisites[$cmd]) found" -ForegroundColor Green } else { Write-Host " [MISSING] $($prerequisites[$cmd]) not found" -ForegroundColor Red $missing += $prerequisites[$cmd] }}if ($missing.Count -gt 0) { Write-Host "" Write-Host "Missing prerequisites: $($missing -join ', ')" -ForegroundColor Red Write-Host "Please install them before continuing." -ForegroundColor Red exit 1}# Test Bitcoin Core RPC connectionWrite-Host ""Write-Host "Testing Bitcoin Core RPC connection..." -ForegroundColor Yellow$bitcoinTest = @{ jsonrpc = "2.0" id = "test" method = "getblockchaininfo" params = @()} | ConvertTo-Json$credentials = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes("${BITCOIN_RPC_USER}:${BITCOIN_RPC_PASSWORD}"))$headers = @{ "Authorization" = "Basic $credentials" "Content-Type" = "application/json"}try { $response = Invoke-RestMethod -Uri "http://${BITCOIN_RPC_HOST}:${BITCOIN_RPC_PORT}" -Method Post -Headers $headers -Body $bitcoinTest -ErrorAction Stop Write-Host " [OK] Bitcoin Core RPC connection successful" -ForegroundColor Green Write-Host " Chain: $($response.result.chain)" -ForegroundColor Gray Write-Host " Blocks: $($response.result.blocks)" -ForegroundColor Gray} catch { Write-Host " [ERROR] Cannot connect to Bitcoin Core RPC" -ForegroundColor Red Write-Host " Please check your RPC credentials and ensure Bitcoin Core is running" -ForegroundColor Red Write-Host " Error: $_" -ForegroundColor Red exit 1}# Create projects directoryWrite-Host ""Write-Host "Setting up project directories..." -ForegroundColor Yellowif (-not (Test-Path $PROJECTS_DIR)) { New-Item -ItemType Directory -Path $PROJECTS_DIR | Out-Null Write-Host " [OK] Created $PROJECTS_DIR" -ForegroundColor Green} else { Write-Host " [OK] Projects directory exists" -ForegroundColor Green}# Clone 3xplCore if not existsWrite-Host ""Write-Host "Setting up 3xplCore..." -ForegroundColor Yellow$xplCoreDir = Join-Path $PROJECTS_DIR "3xplCore"if (-not (Test-Path $xplCoreDir)) { Write-Host " Cloning 3xplCore repository..." -ForegroundColor Gray git clone https://github.com/SumnersMetaverse/3xplCore.git $xplCoreDir Write-Host " [OK] 3xplCore cloned" -ForegroundColor Green} else { Write-Host " [OK] 3xplCore already exists" -ForegroundColor Green}# Configure 3xplCore$envFile = Join-Path $xplCoreDir ".env"if (Test-Path "$xplCoreDir.env.example") { if (-not (Test-Path $envFile)) { Copy-Item "$xplCoreDir.env.example" $envFile Write-Host " [OK] Created .env file from example" -ForegroundColor Green # Update .env with Bitcoin Core credentials $envContent = Get-Content $envFile $envContent = $envContent -replace 'MODULE_bitcoin-main_NODES[]=.*', "MODULE_bitcoin-main_NODES[]=${BITCOIN_RPC_USER}:${BITCOIN_RPC_PASSWORD}@${BITCOIN_RPC_HOST}:${BITCOIN_RPC_PORT}/" Set-Content -Path $envFile -Value $envContent Write-Host " [OK] Updated .env with Bitcoin Core credentials" -ForegroundColor Green } else { Write-Host " [OK] .env already configured" -ForegroundColor Green }}# Clone lndhub if not existsWrite-Host ""Write-Host "Setting up lndhub..." -ForegroundColor Yellow$lndhubDir = Join-Path $PROJECTS_DIR "lndhub"if (-not (Test-Path $lndhubDir)) { Write-Host " Cloning lndhub repository..." -ForegroundColor Gray git clone https://github.com/SumnersMetaverse/lndhub.git $lndhubDir Write-Host " [OK] lndhub cloned" -ForegroundColor Green # Install dependencies Write-Host " Installing Node.js dependencies..." -ForegroundColor Gray Push-Location $lndhubDir npm install Pop-Location Write-Host " [OK] Dependencies installed" -ForegroundColor Green} else { Write-Host " [OK] lndhub already exists" -ForegroundColor Green}# Clone mining-pools if not existsWrite-Host ""Write-Host "Setting up mining-pools..." -ForegroundColor Yellow$miningPoolsDir = Join-Path $PROJECTS_DIR "mining-pools"if (-not (Test-Path $miningPoolsDir)) { Write-Host " Cloning mining-pools repository..." -ForegroundColor Gray git clone https://github.com/SumnersMetaverse/mining-pools.git $miningPoolsDir Write-Host " [OK] mining-pools cloned" -ForegroundColor Green} else { Write-Host " [OK] mining-pools already exists" -ForegroundColor Green}# Create environment template for easy referenceWrite-Host ""Write-Host "Creating environment reference file..." -ForegroundColor Yellow$envTemplate = @"# Bitcoin Core + Repository Integration Environment Variables# Copy this to your PowerShell profile or .env file# DO NOT commit this file with actual values!# Bitcoin Core$env:BITCOIN_RPC_USER="$BITCOIN_RPC_USER"$env:BITCOIN_RPC_PASSWORD="$BITCOIN_RPC_PASSWORD"$env:BITCOIN_RPC_HOST="$BITCOIN_RPC_HOST"$env:BITCOIN_RPC_PORT="$BITCOIN_RPC_PORT"# Redis$env:REDIS_HOST="$REDIS_HOST"$env:REDIS_PORT="$REDIS_PORT"$env:REDIS_PASSWORD="$REDIS_PASSWORD"# Tenderly$env:TENDERLY_API_KEY="$TENDERLY_API_KEY"`$env:TENDERLY_PROJECT_ID="$TENDERLY_PROJECT_ID""@$envReferenceFile = Join-Path $PROJECTS_DIR "environment-reference.ps1"Set-Content -Path $envReferenceFile -Value $envTemplateWrite-Host " [OK] Environment reference saved to: $envReferenceFile" -ForegroundColor GreenWrite-Host " [INFO] Review and source this file when needed" -ForegroundColor Cyan# SummaryWrite-Host ""Write-Host "========================================" -ForegroundColor CyanWrite-Host "Setup Complete!" -ForegroundColor GreenWrite-Host "========================================" -ForegroundColor CyanWrite-Host ""Write-Host "Next steps:" -ForegroundColor YellowWrite-Host " 1. Review the environment reference file: $envReferenceFile" -ForegroundColor GrayWrite-Host " 2. Configure LND if you need Lightning Network features" -ForegroundColor GrayWrite-Host " 3. Run 3xplCore: cd $xplCoreDir && php 3xpl.php bitcoin-main M" -ForegroundColor GrayWrite-Host " 4. See documentation in: REPOSITORY-INTEGRATION-QUICK-REFERENCE.md" -ForegroundColor GrayWrite-Host ""Write-Host "For detailed instructions, see:" -ForegroundColor YellowWrite-Host " - doc/repository-integration-guide.md" -ForegroundColor GrayWrite-Host " - USING-YOUR-EXISTING-CREDENTIALS.md" -ForegroundColor GrayWrite-Host ""Write-Host "[SECURITY REMINDER] Never commit the environment-reference.ps1 file!" -ForegroundColor RedWrite-Host ""

…ctions Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot · 2025-12-31T11:25:50Z

@copilot contrib/setup-integration.ps1

@@ -0,0 +1,297 @@# ╔═════════════════════════════════════════════�...

Enhanced the PowerShell setup script with improved formatting using box-drawing characters, emoji indicators (1️⃣, 2️⃣, 3️⃣, 4️⃣), and clearer ">>REPLACE THIS<<" placeholders. The script now has a more professional appearance with detailed instructions and better visual organization (6cebd57).

SumnersMetaverse · 2025-12-31T11:47:27Z

@copilot this is how i want the users platform for my githubrepo sumnersmetaverse/miago.AI this is not all i want integrated but the start this is to be done in the users newly created "Web Layer 7" this is where the users are able to transfer assets between there hot and cold wallets while online but completly disconnected from any and all virtual and wireless connections, I want layer seven double encrypted and a rotating "_0auth3af"(eg. 1st All 3AF are biometric. first biometric identifier is the users eyes pattern facial composition and body rendering scan from interacting device, second 3AF Verbal matching haptics, audion will record the users voice from random generated phrases given to the user to isolate and rectify each individual users personal traits and will prevent false identy theft due to recording audio and video, this is also why MIAGO needs to be fully Animatronic live response agent abilites, integrating in a motion sensor into the forward and rear facing camers and microphones of the users device to start and complete the 3rd 3AF requirement which is a Wellness check, this is to ensure the user is in full compliance with the transactions as well allowing for an immediate on scene responder for emergency and law enforcement agencies to gain faster vital information of the users in need of there assistance, it will be layered with an encrypted login silently running each and everytime the user enters and exits there Web layer 7 Deep Vault, where users can be able to move funds and share or move private asset data while still connected to the information online needed to do so, all encrypted logins will be logged by a live action user agent qr haptic attached to the users interactions then as the user exits there vaults the interactions of that session is then printed on a 2nd qrf all this is running silently not to disrupt the users interactions but as well ensure the users data is truley strongholded in there private server vault but also completly ensures no unwanted viruses or unwanted web hooks are able to copy or intercept the users interactions)

SumnersMetaverse · 2025-12-31T11:58:07Z

@copilot we are just adding the mempool.space setup we just accomplished into my Miago_Vault files for high level security protection as well also to integrate the funds being requested for paying to activate my AI. for now do everything to how the networks demand how to do it there way let layer 7 just be a topic to act on in the future and just pre plan the comment made, for now we are to where we a processing the backend process for mempool and all mining operations and i want to start the first round of code executions to follow through with the process and verify the transactions are correct, and tenders accapted through all currency means, our mobile version will have tap to pay options as well it will include its own mobil network already given and as well a talk and text capability, all network expenses will be paid for through all users mining proceds and the percentage fee of the coverage cost to the program for keeping it active as well include a 15% fee on all transactions yearly, this is to ensure the networks maintainability and connectivity is maintained and balanced

Copilot · 2025-12-31T11:59:14Z

@copilot we are just adding the mempool.space setup we just accomplished into my Miago_Vault files for high level security protection as well also to integrate the funds being requested for paying to ...

The current PR provides the foundation for mempool.space integration with Bitcoin Core, including comprehensive documentation, setup scripts, and security best practices. The advanced Layer 7 security features (biometric authentication, wellness checks, encrypted vaults) you described are noted for future implementation phases. The current implementation focuses on standard network integration patterns and can be extended later with the advanced security architecture you envision.

Copilot AI self-assigned this Dec 22, 2025

Initial plan

2d75c33

Copilot AI assigned SumnersMetaverse Dec 22, 2025

Copilot started work on behalf of SumnersMetaverse December 22, 2025 05:18 View session

Implement logout command with tests and CLI

92ccd5e

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Add logout functionality in commands~~ Implement logout command for Miago CLI Dec 22, 2025

Copilot AI requested a review from SumnersMetaverse December 22, 2025 05:24

Copilot finished work on behalf of SumnersMetaverse December 22, 2025 05:24

Copilot started work on behalf of SumnersMetaverse December 31, 2025 10:23 View session

Add Bitcoin Core configuration example for mempool.space integration

ffef055

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Improve bitcoin.conf.example with detailed RPC authentication examples

88d00ff

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot AI changed the title ~~Implement logout command for Miago CLI~~ Implement logout command for Miago CLI and add Bitcoin Core configuration Dec 31, 2025

Copilot finished work on behalf of SumnersMetaverse December 31, 2025 10:28

Copilot started work on behalf of SumnersMetaverse December 31, 2025 10:29 View session

Add comprehensive README for mempool.space integration

6ad05e5

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot AI and others added 5 commits December 31, 2025 10:32

Fix broken links in mempool.space README

c947ad7

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Fix security issues in firewall configuration examples

4cc114f

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Improve clarity and completeness of security documentation

97baa79

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Fix JSON syntax and improve documentation clarity

66435fb

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Use proper command-line flags and add daemon mode instructions

185008e

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot AI changed the title ~~Implement logout command for Miago CLI and add Bitcoin Core configuration~~ Implement logout command for Miago CLI and add Bitcoin Core mempool.space integration Dec 31, 2025

Copilot finished work on behalf of SumnersMetaverse December 31, 2025 10:38

Copilot started work on behalf of SumnersMetaverse December 31, 2025 10:38 View session

Copilot AI and others added 2 commits December 31, 2025 10:40

Add integration test script for Bitcoin Core and mempool.space

87e5ded

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Add Python cache files to gitignore and remove committed cache

f698622

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot AI changed the title ~~Implement logout command for Miago CLI and add Bitcoin Core blockchain integration documentation~~ Implement logout command for Miago CLI and add Bitcoin Core blockchain integration documentation with credentials management Dec 31, 2025

Copilot finished work on behalf of SumnersMetaverse December 31, 2025 11:12

Copilot started work on behalf of SumnersMetaverse December 31, 2025 11:13 View session

Add comprehensive cross-reference summary for mempool.space integration

0cd69d8

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot finished work on behalf of SumnersMetaverse December 31, 2025 11:16

Copilot started work on behalf of SumnersMetaverse December 31, 2025 11:17 View session

Add quick reference guide for repository integration

40fd7a3

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot finished work on behalf of SumnersMetaverse December 31, 2025 11:20

Copilot started work on behalf of SumnersMetaverse December 31, 2025 11:21 View session

Add guide for using existing credentials with documentation

86fa062

Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot finished work on behalf of SumnersMetaverse December 31, 2025 11:23

Copilot started work on behalf of SumnersMetaverse December 31, 2025 11:23 View session

Improve PowerShell script with enhanced formatting and clearer instru…

6cebd57

…ctions Co-authored-by: SumnersMetaverse <207414489+SumnersMetaverse@users.noreply.github.com>

Copilot finished work on behalf of SumnersMetaverse December 31, 2025 11:26

Copilot started work on behalf of SumnersMetaverse December 31, 2025 11:47 View session

Copilot finished work on behalf of SumnersMetaverse December 31, 2025 11:49

Copilot started work on behalf of SumnersMetaverse December 31, 2025 11:58 View session

Copilot finished work on behalf of SumnersMetaverse December 31, 2025 12:00

Conversation

Copilot AI commented Dec 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

SumnersMetaverse commented Dec 31, 2025

Bitcoin Core Configuration for mempool.space Integration

This file contains example configuration settings for running Bitcoin Core

with mempool.space. Copy relevant sections to your bitcoin.conf file.

Location of bitcoin.conf:

- Linux: ~/.bitcoin/bitcoin.conf

- macOS: ~/Library/Application Support/Bitcoin/bitcoin.conf

- Windows: %APPDATA%\Bitcoin\bitcoin.conf

Required Settings for mempool.space

Enable RPC server (required for mempool.space to connect)

Enable REST API (recommended for efficient data queries)

Enable transaction index (required for full transaction lookup functionality)

Note: Enabling this requires a one-time reindex with -reindex flag

RPC Authentication

Set RPC username and password

IMPORTANT: Use strong credentials in production!

For better security, use rpcauth instead of rpcpassword

Generate with: python3 share/rpcauth/rpcauth.py

Alternative: Use rpcauth for better security

Generate with: python3 share/rpcauth/rpcauth.py

Example output format:

rpcauth=mempool:hash$salt

Then use the generated password in your mempool.space config

RPC Network Settings

Bind RPC to specific IP (localhost only for security)

Allow RPC connections from localhost

If mempool.space backend is on a different machine, add its IP:

rpcallowip=192.168.1.100

RPC port (defaults: mainnet=8332, testnet=18332, signet=38332, regtest=18443)

Uncomment to use non-default port:

rpcport=8332

ZMQ Settings (Optional but Recommended)

ZMQ enables real-time notifications instead of polling

This significantly improves mempool.space responsiveness

Publish raw block data

Publish raw transaction data

Publish block hash

Publish transaction hash

ZMQ for sequence notifications

Mempool Settings

Maximum mempool size in megabytes (default: 300)

Increase if you want to track more transactions

Minimum fee rate for transaction relay (default: 0.00001 BTC/kB)

minrelaytxfee=0.00001

Maximum orphan transactions kept in memory (default: 100)

maxorphantx=100

Performance Tuning

Database cache size in megabytes (default: 450)

Increase for better performance, especially during initial sync

Maximum number of inbound+outbound connections (default: 125)

maxconnections=125

Number of threads to service RPC calls (default: 4)

Enable coinstatsindex for faster UTXO set statistics (optional)

coinstatsindex=1

Network Selection

Mainnet (default - no flag needed)

[No settings required for mainnet]

Testnet (Bitcoin test network)

testnet=1

Signet (another test network)

signet=1

Regtest (local regression test network for development)

regtest=1

Logging

Enable debug logging for specific categories (useful for troubleshooting)

debug=mempool

debug=rpc

debug=http

Or enable all debug logging (generates large log files!)

debug=1

Additional Security Settings

Disable RPC access to certain methods (comma-separated list)

Example: disable wallet functions if not needed

disablewallet=1

Whitelist specific RPC methods (all others will be disabled)

rpcwhitelist=user:getblockchaininfo,getmempoolinfo,getrawmempool

Copilot AI commented Dec 22, 2025 •

edited

Loading