Proposal: Add an Official Rust SDK for Lighter (lighter-rs)

[robustfengbin]

🚀 Motivation

Lighter currently provides official SDKs in Python and Go. As the ecosystem grows, adding a Rust SDK would significantly benefit developers building high-performance trading bots, backend systems, or on-chain/off-chain infrastructure.

Rust is increasingly adopted in crypto, trading systems, MEV bots, low-latency engines, and high-integrity services. Many teams prefer Rust due to its safety, performance, and strong async ecosystem.
Having an official Rust SDK would lower integration barriers and strengthen the overall developer experience.

⸻

✅ What I have built

I have developed a fully-functional Rust SDK that already supports the main features exposed in the Lighter API:
• Repository: https://github.com/robustfengbin/lighter-sdk
• Account and nonce handling
• HTTP request signing & request builders
• WebSocket subscriptions
• Order creation, cancellation, and basic account operations
• Cross-platform dynamic library support (Linux x86_64/ARM, macOS; Windows possible)
• Example usage in examples/, along with basic tests
• Licensed under MIT OR Apache-2.0, matching Rust ecosystem conventions

The crate is production-ready and already published on crates.io.

⸻

📦 Why it matters for Lighter

An official Rust SDK would:
• Bring language-parity across major ecosystems (Go, Python, Rust)
• Enable high-performance trading applications (the Rust community is very large in this field)
• Encourage more builders to adopt the protocol
• Reduce fragmentation by providing a standard, maintained implementation
• Help teams avoid re-inventing the wheel with custom signing/request wrappers

⸻

🔧 Proposal

I would like to propose:
1. Recognizing the Rust SDK as an official SDK
2. Optionally creating a new repository under the organization, e.g.
elliottech/lighter-rs
3. I can transfer ownership of my current repository and continue as a maintainer (or co-maintainer).
4. I am also willing to add CI workflows (multi-target builds/tests), documentation, and long-term version maintenance.

If the team prefers to keep it “community-maintained”, that is also fine — I just need confirmation so I can adjust direction accordingly.

⸻

📞 What I need from maintainers
• Would you prefer the Rust SDK to be transferred under the elliottech org?
• Or remain community-maintained but listed in the official SDK section of the docs?
• If transferred, I can initiate the repository migration immediately.

Thank you for your time, and I hope this can help strengthen Lighter’s multi-language developer ecosystem!

Best regards,
A community contributor

[zounw]

Is there a java sdk?