Consuming Protocols

This section is for application developers integrating an existing Tx3 protocol. The recommended workflow is codegen: pull a published protocol into your project with trix use, generate a typed client with trix codegen, and call one typed method per transaction from your application code. At runtime that client speaks the Transaction Resolver Protocol (TRP) to a backend that turns each invocation into an unsigned transaction ready to be signed and submitted.

If instead you’re authoring the protocol itself, see Authoring Protocols.

Quick Start Step-by-step walkthrough from `trix use` to a submitted transaction, tabbed across TypeScript, Rust, Go, and Python.

Codegen Add protocols with `trix use` and generate typed clients with `trix codegen` in TypeScript, Rust, Go, or Python.

SDKs Directory of the supported runtime SDKs — repositories, package registries, and install commands per language.

Dynamic Usage The untyped SDK surface — load a protocol at runtime and address transactions by name, for when codegen isn't an option.