ERC-7811: Wallet Asset Discovery

ERCs
, ,
13

I think I lean towards having some sane filters defined in the spec vs leaning on a capability approach. I would think a capability-per-filter would lead to fragmented support and diminish the overall usefulness of filters in general.

The assets filter is one example that’s already defined in the spec. I could also see a ‘assetType’ filter, ‘spam’ filter, ‘chain’ filter

i.e.

{
  "account": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "assetFilter": {
    "0x1": ["0x456", "native"]
  },
  "assetTypeFilter": ["ERC20", "native"],
  "chainFilter": ["0x1"],
  "spamFilter": true
}

Maybe spam filter could be an optional one? Though I feel like most wallets have spam filtering in place these days

For example, it can also be assumed that the wallet would filter the spam tokens anyways and would not send them back to the client.

I 100% expect wallets to filter spam by default, I am just thinking of the case where a dapp may want to request unfiltered asset ownerships to avoid wallets flagging false positives. Maybe this isn’t a thing though

2 Likes