Skip to main content
An application can check that its configured TSN dependencies are reachable before preparing a payment or asking a wallet to sign. The application selects its endpoints and passes them to the SDK.
readyForNativeTransactions reports readiness of the configured dependencies for native TSN actions. It does not authorize a payment, guarantee that a Cranker will accept work, or confirm a Solana transaction. Cross-chain readiness is a separate capability and should not be used as a gate for native transfers. Refresh status when it matters to the user experience, such as before asking for a signature. Environment variables belong to the application; the SDK does not read the application’s .env file itself. For service configuration and operations, see the repository documentation.