Skip to content

New SDK: Proposal: Add Official TypeScript SDK + Windows WASM Signer for Lighter #49

@Bvvvp009

Description

@Bvvvp009

Feature Request / Contribution Proposal: Lighter-TS SDK + Windows WASM Signer

Background
The current Lighter SDKs (Python, Go) provide native signer binaries for Linux and macOS, but Windows support is missing. Also, there is no official TypeScript SDK under the ElliotTech / Lighter organization.
This gap makes it harder for Windows-based developers and those using JavaScript/TypeScript projects to adopt Lighter cleanly.

What I Built: lighter-ts
I’ve developed a full TypeScript SDK named lighter-ts. Key features:

Type safety via TypeScript: all core APIs, clients, WebSocket support, error handling, etc.
GitHub

Windows WASM signer: compile Go cryptographic library into WebAssembly, enabling signer functionality on Windows without needing Go installation.
GitHub

Same functional parity for macOS, Linux, Windows with existing SDKs.
GitHub

Examples, tests, documentation included.
GitHub

Benefits

Cross-platform support: covers Windows, which is currently missing.

Broadens SDK reach to JavaScript/TypeScript ecosystem (frontend, Node.js).

Helps reduce friction for devs who don’t want or can’t compile / install Go or use non-WebAssembly tools.

Can be official: gives clarity to users instead of multiple “unofficial” alternatives.

Proposal

I’d love to contribute this upstream. Possible ways:

Add lighter-ts as an official SDK under the elliottech / lighter-xyz organization.

If preferred, include this SDK under a shared “SDKs” folder/repo (or similar structure) so that Go, Python, TS SDKs are maintained together.

Or maintain lighter-ts separately, but under official “endorsed” status, with link from docs, etc.

Next Steps & Questions

What are your contribution policies? (CLA, code style, CI, tests)

If you agree this is useful, I’m ready to open a PR / transfer this repo as needed.

Any concerns about the security / trust model of the WASM signer? Would you want specific audits or tests?

What repo structure / naming you’d prefer (e.g. lighter-ts vs lighter-sdk-ts)?

Links

Repo: https://github.com/bvvvp009/lighter-ts

Readme / examples / tests inside the repo.

Thanks for considering this! Happy to adapt to whatever style / structure you prefer.

Best,
Karthik

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions