dex.useCancel

Cancels an order from the Stablecoin DEX orderbook.

Usage

example.ts

import {  } from 'wagmi/tempo'

const  = ..()

// Call `mutate` in response to user action (e.g. button click, form submission)
.({
  : 123n,
})

.('Cancelled order ID:', .?.)
Cancelled order ID: 123n

config.ts

import { createConfig, http } from 'wagmi'
import { tempoTestnet } from 'wagmi/chains'
import { KeyManager, webAuthn } from 'wagmi/tempo'

export const config = createConfig({
  connectors: [
    webAuthn({
      keyManager: KeyManager.localStorage(),
    }),
  ],
  chains: [tempoTestnet],
  multiInjectedProviderDiscovery: false,
  transports: {
    [tempoTestnet.id]: http(),
  },
})

Asynchronous Usage

The example above uses a *Sync variant of the action, that will wait for the transaction to be included before returning.

If you are optimizing for performance, you should use the non-sync dex.cancel action and wait for inclusion manually:

import { Hooks } from 'wagmi/tempo'
import { Actions } from 'viem/tempo'
import { useWaitForTransactionReceipt } from 'wagmi'

const cancel = Hooks.dex.useCancel()
const { data: receipt } = useWaitForTransactionReceipt({ hash: cancel.data })

// Call `mutate` in response to user action (e.g. button click, form submission)
cancel.mutate({
  orderId: 123n,
})

if (receipt) {
  const { args: { orderId } } 
    = Actions.dex.cancel.extractEvent(receipt.logs)

Return Type

See TanStack Query mutation docs for more info hook return types.

data

See Wagmi Action dex.cancel Return Type

mutate/mutateAsync

See Wagmi Action dex.cancel Parameters

Parameters

config

Config | undefined

Config to use instead of retrieving from the nearest WagmiProvider.

mutation

See the TanStack Query mutation docs for more info hook parameters.

Action

• dex.cancel