mineracks VSS vss.mineracks.com

A public LDK Versioned Storage Service endpoint for non-custodial Lightning wallets, run by an independent operator in Brisbane, Australia. Point a wallet at it and test it yourself.

Speaks VSS, unmodified upstream server.

Independent operator. Not affiliated with or endorsed by LDK or Spiral.

checking…

Endpoint

VSS base URL	`https://vss.mineracks.com/vss`
Health	`https://vss.mineracks.com/healthz` vss-server's own health gauge
Machine-readable	`/info`
Authentication	LDK signature auth: your wallet proves a secp256k1 key on every request and only ever sees its own storage. This is what `ldk-node`'s `build_with_vss_store` sends by default. JWT is not offered.
Protocol	VSS v0, upstream vss.proto, unmodified

Try it

From ldk-node 0.7 or later, with the storage-vss feature:

let node = builder.build_with_vss_store(
    node_entropy,
    "https://vss.mineracks.com/vss".to_string(),
    "my-wallet".to_string(),     // store_id: any value
    HashMap::new(),              // fixed headers: none needed
)?;

Or straight against the API with vss-client-ng (a random key is fine, every key is its own tenant):

let headers = Arc::new(SigsAuthProvider::new(secret_key, HashMap::new()));
let client = VssClient::new_with_headers(
    "https://vss.mineracks.com/vss".into(),
    ExponentialBackoffRetryPolicy::new(Duration::from_millis(100)),
    headers,
);
client.put_object(&PutObjectRequest { store_id: "t".into(), global_version: None,
    transaction_items: vec![KeyValue { key: "k".into(), version: 0, value: b"v".to_vec() }],
    delete_items: vec![] }).await?;

Liveness from anywhere:

curl -s https://vss.mineracks.com/healthz

Wallet labels, too

VSS is a good home for any small state a wallet must get back with its keys. BIP-329 labels are the obvious one: they say who paid you and why, so they belong with the wallet and not with whoever hosts them. Our Any Two Keys research wallet keeps its labels here: one encrypted object per vault, key and store id derived from the vault's own recovery material, newest-wins merge between computers, nothing the host can read. The scheme is written up as a small profile any wallet can implement: labels over VSS.

What runs here

Server	`lightningdevkit/vss-server` at commit `88a5703` (0.1.0-alpha.0), built from source, unmodified
Storage	PostgreSQL 16 on a dedicated virtual machine, NVMe-backed shared storage
Durability	Continuous encrypted write-ahead archiving to an on-site backup host, an encrypted off-site copy at a second provider, and nightly VM snapshots. Restores are drilled, not assumed: on 21 September 2026 the latest backup and a point-in-time restore were each rebuilt on an isolated machine and matched this database exactly, and the off-site copy passes a full checksum verification.
Transport	TLS at the Cloudflare edge. The origin has no inbound ports; it reaches the edge over an outbound-only tunnel.
Limits	4 MiB per request · 25 requests/s per client IP (burst 50) · 32 concurrent connections per client IP. Ask if a wallet needs more.
Data	We store what the client sends. LDK clients encrypt before upload, so the operator holds ciphertext and never a key.
Location	Brisbane, Australia (AS-level independent from the wallet vendors and the other public VSS hosts)
Status	Public beta since 2026-09-17. No SLA yet. Partnership terms, dedicated instances and multi-region on request.

Contact

[email protected] · mineracks.com