Skip to main content
Defined in EIP-5792
The auxiliaryFunds capability allows wallets to indicate they have access to funds beyond what can be directly verified onchain by the wallet’s address. This enables more flexible transaction execution and improved user experiences.
Magic Spend is currently disabled. Keep this page as reference for the auxiliaryFunds capability shape and integration patterns, but do not rely on this capability being available in production right now.
This capability is not yet finalized and may change in future iterations.

Parameters

This capability has no configuration parameters. It is either supported or not supported by the wallet.

Returns

object
The auxiliary funds capability configuration for the specified chain.

Example Usage

Error Handling

Wallet Implementation

Wallets supporting auxiliary funds must include the capability in their response:

App Behavior

Apps should modify their balance checking logic when auxiliary funds are supported:

Without Auxiliary Funds

With Auxiliary Funds Support

Use Cases

DeFi Applications

Enable DeFi operations even when wallet balance appears insufficient:

E-commerce Applications

Allow purchases without blocking on visible balance:

Gaming Applications

Enable in-game purchases without balance restrictions:

Error Handling

Handle auxiliary funds-related scenarios:

Best Practices

  1. Graceful Degradation: Always provide fallback balance checking for non-auxiliary wallets
  2. Clear Communication: Inform users when auxiliary funding is being used
  3. Error Handling: Handle cases where auxiliary funds may be temporarily unavailable
  4. Security: Don’t assume auxiliary funds are always available
The auxiliary funds capability improves user experience by enabling transactions that might otherwise be blocked by insufficient visible balance.
Apps should still implement proper error handling as auxiliary funds may not always be available or sufficient.
Auxiliary funds works well with other capabilities: