Overview
- Complete provider setup for InterwovenKit with all required dependencies.
- Two variants: basic setup and AutoSign setup.
- Use the basic setup unless you need automatic signing for approved message types.
Basic Setup
For apps that don’t need AutoSign.This setup uses
initiaPrivyWalletConnector as a wagmi connector option for
Initia’s bundled social-login entry in the wallet list.AutoSign Setup
For apps that need AutoSign. Configure AutoSign directly onInterwovenKitProvider.
Notes
- Call
injectStyles()once at app startup to avoid duplicate style tags. - AutoSign derives its signing wallet from the connected wallet’s signature
flow. Configure it with
enableAutoSignonInterwovenKitProvider. enableAutoSignconfiguration:- Boolean (
true): Enables AutoSign with default message types based on chain type:minievm:/minievm.evm.v1.MsgCallminiwasm:/cosmwasm.wasm.v1.MsgExecuteContractdefault:/initia.move.v1.MsgExecute
- Record (
Record<string, string[]>): Per-chain allowlist of specific message type URLs. Use this to control exactly which message types can be auto-signed (e.g.,MsgSend,MsgDelegate,MsgExecute).
- Boolean (
- Use
autoSignFeePolicywhen you need to restrict fee denoms or tune gas-multiplier behavior for AutoSign.