Don't Trust.
Verify.
This page documents the cryptographic, infrastructure, and security architecture of the Montblanc Capital mining platform. Every claim is verifiable. Every system is explained.
The Montblanc Ledger
A cryptographically signed, append-only record of every mining reward ever distributed. Think of it as a mini-blockchain for our business — except you can download and audit the entire thing from GitHub.
What's recorded
Daily pool earnings
Total BTC mined by the pool each day, pulled directly from the ViaBTC API.
Per-user distribution
Each client’s share calculated from their hashrate allocation. Every satoshi accounted for.
Cumulative balances
Running total per wallet ID. Cross-reference any day’s balance against the chain of previous entries.
Day hash + previous hash
SHA-256 hash of the day’s data, linked to the previous day’s hash. Tamper one entry and every subsequent hash breaks.
Ed25519 signature
Every daily entry is signed with our private key. Verify with our public key — no trust required.
What's NOT in the ledger
No real names
Clients are identified by pseudonymous wallet IDs only. Like Bitcoin addresses — public but anonymous.
No email addresses
Zero PII in the ledger. Even with full access, you can’t identify a single person.
No editable fields
Append-only by design. We cannot modify past entries without breaking the cryptographic chain.
No hidden entries
The full ledger is public on GitHub. What you see is what exists. There is no “private” version.
{
"date": "2026-02-21",
"pool_total_btc": "0.00085939",
"distributions": [
{
"wallet_id": "mb_7f3a2b...c4d8",
"hashrate_share": 0.3791,
"earned_btc": "0.00032581",
"cumulative_btc": "0.02847193"
},
{
"wallet_id": "mb_9e1c4d...a2f7",
"hashrate_share": 0.1264,
"earned_btc": "0.00010862",
"cumulative_btc": "0.00943827"
}
// ... all client distributions
],
"day_hash": "a1b2c3d4e5f67890abcdef01234567890abcdef01234567890abcdef01234567",
"previous_hash": "f8e7d6c5b4a3210987654321fedcba0987654321fedcba0987654321fedcba09",
"signature": "Hx7kQ9mP2vR4wY8nL5jF3tB6dA0sKc1Uw4Xe9Zi2Nq7Rp...",
"public_key": "MCk2Tv9Qr1Xp4Wm7Yn3Zj8Bs5LdGf6HiEa0OuCv..."
}How the Hash Chain Works
day_hash:
8f4a2b...c3d1
previous_hash:
e7b9c1...a4f2
signature: ✓ valid
day_hash:
3c7e9a...b5d8
previous_hash:
8f4a2b...c3d1 ←
signature: ✓ valid
day_hash:
a1b2c3...7890
previous_hash:
3c7e9a...b5d8 ←
signature: ✓ valid
Each day's previous_hash must match the preceding day's day_hash exactly. Modify a single byte in any historical entry and every subsequent hash becomes invalid. The chain is self-auditing — break one link and the forgery is immediately visible.
Ed25519 Digital Signatures
Every ledger entry is cryptographically signed using Ed25519 — the same algorithm securing SSH, Signal, and Solana. Here's exactly how it works and why it matters.
The Signing Process
Collect daily data
Pool earnings, per-user distributions, cumulative balances, and the previous day’s hash are assembled into a JSON structure.
Compute SHA-256 hash
The entire day’s data is hashed using SHA-256, producing a unique 256-bit fingerprint. Any change to the data — even a single bit — produces a completely different hash.
Sign with Ed25519 private key
The hash is signed using our Ed25519 private key, producing a 64-byte digital signature that mathematically proves we authored this exact data.
Publish to Git repository
The signed entry is committed to the public GitHub repository. Git itself adds another layer of integrity via its own SHA-1 commit hashes.
The Verification Process
Download the ledger
git clone https://github.com/richloewenherz/montblanc-ledger
Extract public key from any entry
The public key is embedded in every ledger file.
Recompute the day hash from the raw data
Hash the distributions yourself. Compare against the published day_hash.
Verify the Ed25519 signature
Using the public key, verify the signature matches the hash. If it does — the data is authentic and unmodified.
a1b2c3d4e5f67890abcdef01234567890abcdef0123456789...
Hx7kQ9mP2vR4wY8nL5jF3tB6dA0sKc1Uw4Xe9Zi2Nq7Rp...
MCk2Tv9Qr1Xp4Wm7Yn3Zj8Bs5LdGf6Hi...
Why Ed25519?
• Fast: 70,000+ verifications/sec on standard hardware
• Small: 64-byte signatures, 32-byte public keys
• Secure: 128-bit security level, resistant to timing attacks
• Proven: Used by SSH, Signal, Solana, FIDO2, and TLS 1.3
• Deterministic: Same input always produces same signature (no random nonce vulnerabilities)
Every other mining platform
A number in a database. Editable by any admin with SQL access. Deletable without trace. No cryptographic proof it was ever different. You see what they choose to show you. If the database burns, your history burns with it.
Montblanc Capital
A signed entry in a public, append-only ledger. Hosted on GitHub with full git history. Tamper one byte and the cryptographic chain breaks. Verify with our public key — no trust required, no permission needed.
Mining Infrastructure
Physical hardware in physical facilities. Not a resold cloud contract. Here's what runs behind every TH/s we allocate.
Concrete. Steel. Silicon.
Industrial-grade mining infrastructure across multiple geographic regions.
Hardware Specifications
Operational Details
Security Model
Security isn't a feature — it's the foundation. Here's how we protect your account, your data, and your earnings.
Authentication
- •Bcrypt password hashing (cost factor 12)
- •Auto-rehash on login for future-proofing
- •JWT tokens with ES256 or HS256 signing
- •Secure HttpOnly session cookies
- •Registration rate limiting (5/hour per IP)
Data Protection
- •TLS 1.3 encryption for all data in transit
- •GPG AES-256 encrypted database backups
- •30-day backup retention on private repo
- •Soft-delete only — no hard data destruction
- •CORS strict origin policy in production
Privacy
- •Pseudonymous wallet IDs in public ledger
- •Zero PII in any public-facing data
- •No advertising cookies or tracking pixels
- •No third-party analytics sharing
- •GDPR-aligned data subject rights
Cryptography
- •Ed25519 for ledger signatures
- •SHA-256 for hash chain integrity
- •crypto.randomBytes(32) for token generation
- •SHA-256 hashed token storage (not plaintext)
- •Deterministic signing — no nonce vulnerabilities
Infrastructure
- •Dedicated VPS (not shared hosting)
- •Docker containerized services
- •Automated health monitoring (5-min intervals)
- •State-based alerting (no alert spam)
- •Daily automated DB backups to GitHub
Audit Trail
- •Public Git repository for all ledger data
- •Git commit history = immutable audit log
- •Every modification tracked and timestamped
- •374 automated test suite (backend)
- •Continuous integration on all code changes
System Architecture
A complete overview of the technology stack, from pool integration to client dashboard delivery.
┌──────────────┐ ┌──────────────┐ ┌──────────────────┐
│ ViaBTC │────▶│ Earnings │────▶│ Ledger Service │
│ Mining Pool │ │ Fetch Cron │ │ (Sign + Hash) │
└──────────────┘ │ (Daily 03:00│ └────────┬─────────┘
│ Berlin) │ │
└──────────────┘ │
▼
┌──────────────┐ ┌──────────────┐ ┌──────────────────┐
│ Bitcoin │ │ PostgreSQL │◀────│ Git Repository │
│ Node │ │ Database │ │ (Public Ledger) │
│ (Full Node) │ └──────┬───────┘ └──────────────────┘
└──────────────┘ │
│
┌─────────▼──────────┐
│ Express Backend │
│ (REST API) │
│ Port 5000 │
└─────────┬──────────┘
│
┌─────────▼──────────┐
│ Next.js App │
│ (Dashboard) │
│ Vercel CDN │
└────────────────────┘
Backend Stack
Frontend Stack
Daily Earnings Flow
03:00 CET
Fetch earnings from ViaBTC API
03:01
Calculate per-user distributions
03:02
Sign & commit to ledger
03:03
Update PostgreSQL balances
04:00 CET
Send daily report emails
Corporate Structure
Holding
Montblanc Capital Ltd.
Dublin, Ireland
Operations
RUHL IT Services FZCO
Dubai Silicon Oasis, UAE
Satisfied? Start Mining.
You've seen the architecture. Verified the approach. Now put it to work.