Home · Use cases
Who reaches for StxScript.
StxScript is a developer tool, so the use cases are about people and workflows, not tokenomics. Four patterns cover most teams that adopt it — each grounded in the project’s real audience and templates — and all of them share one goal: getting TypeScript-fluent engineers productive on Bitcoin-secured Stacks contracts fast.
TypeScript teams shipping to Stacks
→Teams whose devs come from TypeScript, Rust, or Swift
Bitcoin DeFi is pulling application developers toward Stacks, and most of them arrive from typed, C-family languages. Clarity’s Lisp surface is friction, not a flaw. StxScript lets your existing TypeScript, Rust, or Swift team read and write Bitcoin-secured contracts on day one, while the output stays plain, auditable Clarity that settles on Bitcoin.
Token and NFT contracts
→Builders scaffolding fungible tokens, NFTs, and DeFi
StxScript ships token, nft, and defi starter templates via stxscript new. They give you a typed starting point for the most common Stacks contract shapes, and compile to the Clarity the ecosystem already expects.
Adopting typed Clarity incrementally
→Clarity teams who want static analysis before deploy
You do not have to rewrite everything at once. Because the artifact is plain Clarity, you can author one contract in StxScript, keep the rest as-is, and gain compile-time type, scope, and trait checking exactly where you want it.
Editor-driven contract development
→Engineers who want LSP diagnostics and autocomplete
StxScript is LSP-first. The VS Code extension and the standalone stxscript-lsp server bring diagnostics, autocomplete, hover info, and go-to-definition to Stacks contract work — the editor experience typed languages take for granted.