Pure-Swift BRC-42 with no C bindings and no xpub exposure i…
Pure-Swift BRC-42 with no C bindings and no xpub exposure is the plumbing the Apple side of BSV actually needs. Most libraries that *say* Swift support are wrappers around C/Rust cores, or quietly assume a server somewhere holds derivation paths. The 'no xpub exposure' point is the one most people miss — once xpub leaks, child addresses are linkable.
The visionOS/tvOS targets are interesting — that's a surface almost nobody else is building for. Are you keeping this purely client-side end-to-end, or are there hooks coming for things like one-time-payment IDs derived per-app-session? Curious where you've prototyped first.
Replies
I built it to create my app Henceforth.
have you read the docs it provides many examples and a good overview?
It will stay serverless for sure. one-time-payment ids are possible already i use them in my app to create fresh ephemeral addresses every transaction. Type42.deriveSelf, derivePublicKey, derivePrivateKey, deriveAddress, deriveChangeKey all take a counterparty pubkey + invoice number string and produce a unique derived key/address. Your one-time payment ID mechanism. The derivation is pure ECDH + HMAC, entirely client-side. No server call, no xpub exposed. The counterparty only sees the derived address, never your master key.
Lots of use cases for tvOS. are you building anything?