Thus Spoke Zakura on Akash (Regtest)
Run the Thus Spoke Zakura v0.4.1 stack on Akash: Zakura Regtest, lightwalletd, and the wallet dashboard / HTTP API. Test coins have no value. Do not send mainnet ZEC here.
Template: awesome-akash/thus-spoke-zakura
Upstream: zcashlabs/thus-spoke-zakura tag v0.4.1
Images
| Service | Image |
|---|
Dashboard + API (app) | ghcr.io/zcashlabs/thus-spoke-zakura-app:0.4.1 |
| lightwalletd | ghcr.io/zcashlabs/thus-spoke-zakura-lightwalletd:0.4.1 |
| Zakura | zakuracore/zakura:1.6.0 (pin compiled into the 0.4.1 launcher) |
Self-bootstrap
On first start the app container runs ths-server init on its persistent volume, then ths-server serve. Serve retries until Zakura JSON-RPC and lightwalletd are up. You do not run ths on the provider; the SDL is the runtime.
How Akash publishes ports
SDL port / as are container ports. The app listens on 8080 (THS_LISTEN); lightwalletd on 9067; Zakura RPC on 18232 and P2P on 18233. Inside the deployment, services already use those (http://zakura:18232, http://lightwalletd:9067).
They are not the ports on the provider's public IP.
Default (this template): no dedicated IP.
| Service | Container listen | SDL as | How it shows up on the lease |
|---|
app (dashboard + HTTP API) | 8080 | 80 (HTTP) | Ingress hostname, often on 80/443 — open this URI in a browser |
lightwalletd | 9067 | 9067 (TCP, global) | host:<random-high-port> |
zakura RPC | 18232 | 18232 (TCP, global) | host:<random-high-port> |
zakura P2P | 18233 | 18233 (TCP, global) | host:<random-high-port> |
After the lease is ready, Leases → URIs is the source of truth. Open the app URI for the dashboard (the same UI ths opens locally). Point compact clients at the lightwalletd URI (THS_LIGHTWALLETD_TLS=false). Do not type :8080, :80, or :9067 on the provider IP unless a dedicated IP lease made those ports public.
Dedicated IPs (endpoints / kind: ip) are a paid extra and are not in this template. They can pin a public IP and sometimes the as port. Leave them off unless you need that.
Which site to use (payments)
The SDL is the same. The two Akash web UIs differ in how you pay.
Use Air when you want to pay with Keplr on-chain. Use Console when you want a conventional web payment flow.
Deploy
Web payments (Console)
Native Akash payments with Keplr (Air)
Open this template on Air
Create the deployment from the template, accept a bid, wait until app logs show ths-server serve staying up, then open the app URI for the dashboard.
