Overview
- Complete provider setup for InterwovenKit with all required dependencies.
- Two variants: basic setup (no Privy/AutoSign) and AutoSign setup (requires Privy).
- Use the basic setup unless you need AutoSign or embedded wallet features.
Basic setup
For apps that don’t need AutoSign or embedded wallets.This setup uses
initiaPrivyWalletConnector as a wagmi connector option, but
does not require PrivyProvider at runtime.AutoSign setup (requires Privy)
For apps that need AutoSign or embedded wallet features. Privy is required for AutoSign to work:Notes
- Call
injectStyles()once at app startup to avoid duplicate style tags. - Privy is required for AutoSign. AutoSign will not work without
PrivyProviderandprivyContext. - Replace
YOUR_PRIVY_APP_IDwith your own Privy app ID. This is distinct from the importedPRIVY_APP_ID(which is Initia’s shared Privy app ID). - The
privyContextprop must be passed from within a component that has access to Privy hooks (usePrivy,useLoginWithSiwe,useCreateWallet,useWallets). 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 (
- Config vs runtime: Both setups use
initiaPrivyWalletConnectorin wagmi config (config-time), but only the AutoSign setup requiresPrivyProviderat runtime. The connector itself does not require Privy runtime unless you need AutoSign or embedded wallet features.