Skip to main content
This interface is planned and not available yet. It is published here so integrators can see where the SDK is going; names and shapes may change before release. The pool client that exists today is documented from Keys, notes and scanning onwards and listed in the Pool client reference.
The intent client lets a dApp create intents, request quotes, stream offers in real time, execute the selected offer and track an intent’s status from start to finish, across chains. It also carries optional confidentiality settings and post-fulfillment actions.

Packages and entry points

  • @fluton/sdk (core)
  • @fluton/sdk/react (hooks and providers)
  • @fluton/sdk/viem (optional adapter helpers)
  • @fluton/sdk/ethers (optional adapter helpers)

Create a client

The signer is optional for server-side quoting and intent creation, and required for execute().

Quote, execute and track

Custom intents

The bridge helpers sit on a lower-level intent engine, which you can drive directly:

Modules

fluton.supported

Discover what is supported: networks, tokens and adapters.
  • getSupportedChains(): Promise<SupportedChains>
  • getSupportedTokens(chain): Promise<Token[]>
  • getCapabilities(): Promise<Capabilities> (confidential support per chain and token)

fluton.bridge

Simple bridge workflows.
  • quote(params): Promise<BridgeQuote>
  • execute(quote, opts?): Promise<ExecutionResult>
  • track(intentId | txHash, cb?): Unsubscribe

fluton.intent

The low-level intent engine.
  • create(params): Promise<IntentDraft>
  • sign(draft, signer?): Promise<SignedIntent> (private key or browser wallet signing)
  • submit(signed): Promise<{ intentId: string }> (registers the intent with the backend)
  • get(intentId): Promise<Intent>
  • status(intentId): Promise<IntentStatus>
  • execute(intentId | SignedIntent, opts?): Promise<ExecutionResult>

fluton.offers

Offer discovery and selection.
  • list(intentId): Promise<Offer[]>
  • subscribe(intentId, onOffer, onError?): Unsubscribe (WebSocket or SSE, both supported)
  • selectBest(intentId, strategy?): Promise<Offer>

fluton.utils

Utility methods.
  • parseUnits(amount, decimals)
  • formatUnits(bigint, decimals)
  • toChainKey(chainId) / toChainId(key)

Types

Chains and tokens

Intent params

Offer

React bindings

@fluton/sdk/react wraps the client in a provider and a set of hooks.
Hooks (v1):
  • useSupportedChains()
  • useSupportedTokens(chain)
  • useBridgeQuote(params, { enabled })
  • useExecuteBridge(): returns execute(quote) plus the transaction state
  • useIntentStatus(intentId) (polling or stream)
  • useOffers(intentId) (stream)
Hook return shapes follow the TanStack Query style:
Until this client ships, the pool client is the SDK: private deposits, withdrawals and transfers in Fluton Pool on Arbitrum One.