Title: ERC_7682__Auxiliary_Funds_Capability
Category: ERCs

Author: lsr
Date: 2024-04-09T21:27:11.802Z

Abstract
An EIP-5792 compliant capability that allows wallets to indicate to apps that they have access to funds beyond those that can be accounted for by looking up balances onchain given the wallet’s address.
Motivation
Many applications check users’ balances before letting them complete some action. For example, if a user wants to swap some amount of tokens on a dex, the dex will commonly block the user from doing so if it sees that the user does not have that amount of tokens at their address. However, more advanced wallets have features that let users access funds from other sources. Wallets need a way to tell apps that they have access to additional funds so that users using these more advanced wallets are not blocked by balance checks.
Specification
One new EIP-5792 wallet capability is defined.
Wallet Implementation
To conform to this specification, wallets that wish to indicate that they have access to auxiliary funds MUST respond to wallet_getCapabilities calls with an auxiliaryFunds object with a supported field set to true for each chain they have access to auxiliary funds on. This specification does not put any constraints on the source of the auxiliary funds.
wallet_getCapabilities Response Specification
type AuxiliaryFundsCapability = {
  supported: boolean;
}

wallet_getCapabilities Example Response
{
  "0x2105": {
    "auxiliaryFunds": {
      "supported": true
    },
  },
  "0x14A34": {
    "auxiliaryFunds": {
      "supported": true
    }
  }
}

App Implementation
When an app sees that a connected wallet has access to auxiliary funds via the auxiliaryFunds capability in a wallet_getCapabilities response, the app SHOULD NOT block users from taking actions on the basis of asset balance checks.
Rationale
Alternatives
Advanced Balance Fetching
An alternative we considered is defining a way for apps to fetch available auxiliary balances. This could be done, for example, by providing a URL as part of the auxiliaryFunds capability that apps could use to fetch auxiliary balance information. However, we ultimately decided that a boolean was enough to indicate to apps that they should not block user actions on the basis of balance checks, and it is minimally burdensome for apps to implement.
The shape of this capability allows for a more advanced extension if apps feel more functionality is needed.
Auxiliary Funds per Asset
We could also specify auxiliary funds support per asset. We decided against this because this list could get quite large if a wallet has auxiliary funds supports for many assets, and a single boolean should be enough for apps to not block users from taking actions.
Security Considerations
Apps MUST NOT make any assumptions about the source of auxiliary funds. Apps’ smart contracts SHOULD still, as they would today, make appropriate balance checks onchain when processing a transaction.

Author: bumblefudge
Date: 2024-04-13T18:32:16.613Z

lsr:

When an app sees that a connected wallet has access to auxiliary funds via the auxiliaryFunds capability in a wallet_getCapabilities response, the app SHOULD NOT block users from taking actions on the basis of asset balance checks.


Wait, so any wallet that self-attests to having auxFunds SHOULD just be exempted from balance-checks?  I was expecting, when I got this far in the spec, to see a logic provided for checking those auxFunds against the balance check amount instead… this might be clearer with at least an illustrative advanced balance-fetch pseudocode or something?

Author: MilkyTaste
Date: 2024-11-17T19:04:57.637Z

lsr:

the app SHOULD NOT block users from taking actions on the basis of asset balance checks


Could we update this ERC to include an optional balance? The current approach implies the wallet has access to unlimited funds.
type AuxiliaryFundsCapabilityAsset = {
  address: `0x${string}`;
  balance?: `0x${string}`; // hex max available
}
type AuxiliaryFundsCapability = {
  supported: boolean;
  assets?: AuxiliaryFundsCapabilityAsset[];
}

Author: MilkyTaste
Date: 2024-11-17T19:16:17.505Z

The way this ERC is written, it is currently only usable by the front end. If the capability is sent in 5792’s wallet_sendCall request, the back end would be prompted to check / obtain / use the auxiliary funds.
I don’t think the back end should be assuming auxiliary funds are always accessed and explicit request would be better.


Ethereum Improvement Proposals


EIP-5792: Wallet Call API
Adds JSON-RPC methods for sending multiple calls from the user's wallet, and checking their status





[
  {
    "version": "1.0",
    "from": "0x...",
    "calls": [
      {
        "to": "0x...",
        "value": "0xde0b6b3a7640000", // 1e18
        "data": "0x...",
        "chainId": "0x01"
      }
    ],
    "capabilities": {
      "auxiliaryFunds": {
        "assets": {
          "address": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
          "amount": "0xde0b6b3a7640000" // 1e18
        }
      }
    }
  }
]