Build a non-custodial wallet app for the ZKas cryptocurrency
Verify and sign a shielded payment on-device before it is submitted
Register a watch-only wallet using just a viewing key
Send a payment across a fragmented wallet's many small transaction notes
| firecash/zkas-sdk | 4ssh1/mine-sweeper | achawla19/intuitcode-extension | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | TypeScript | TypeScript | TypeScript |
| Last pushed | — | 2026-01-31 | — |
| Maintenance | — | Maintained | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 4/5 | 2/5 | 4/5 |
| Audience | developer | vibe coder | developer |
Figures from each repo's GitHub metadata at analysis time.
Sending payments requires a WASM signer built from a companion repository and a wallet capability token from the hosted service.
ZKas SDK is a developer toolkit for building wallets and other apps on top of ZKas, a version of the Kaspa cryptocurrency that keeps transactions private, or shielded, by default. Rather than asking developers to build their own cryptography for this, the SDK gives them a ready made TypeScript client to talk to a hosted wallet service, handling things like checking a wallet's status, registering it for read only viewing, checking balances and transaction history, and sending a payment through a multi step process that includes verifying and signing on the user's own device before anything is submitted. The project is upfront about how much trust each setup requires. If you use the hosted TypeScript client, your seed stays on your own device while only a viewing key sits with the wallet service, meaning the service can see your wallet's activity but can never move your funds or trick your device into approving a payment you did not actually intend. There is also a fully local option, built in Rust and kept in a separate repository, that keeps everything private from the wallet service entirely, and a watch only mode that can only view a wallet's activity and never spend from it. Two specific protections are built directly into the signing device rather than left to policy. First, the device always rebuilds and checks the full payment itself before signing, confirming it matches exactly the amount and recipient that were approved. Second, it reads the network fee from the payment data itself rather than trusting a number reported by the server, and it refuses to sign anything above a maximum fee the user has approved in advance. Installing the SDK is a simple npm install, and the README includes a short code example showing how to construct a client, prepare a signer, and send a payment while tracking its progress. The project is released under the ISC license.
A TypeScript SDK for building non-custodial wallets on ZKas, a privacy-focused Kaspa fork, with on-device verification before any payment is signed.
Mainly TypeScript. The stack also includes TypeScript, Rust, WASM.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.