ERC-7811 primary sources — 2026-05-07

Project status in this pass

• No standalone ERC-7811 whitepaper or litepaper surfaced.
• The clearest current source of truth was the draft ERC itself, backed by the raw ERC markdown and JAW’s implementation-facing RPC documentation.
• The sources consistently frame ERC-7811 as wallet asset-discovery infrastructure, especially for balances that dapps cannot reliably infer from onchain data alone.

Primary-source snapshots

1) Canonical ERC page

• URL: https://eips.ethereum.org/EIPS/eip-7811
• Key excerpt/signals:
  • The abstract says wallet_getAssets lets wallets tell dapps what assets the user owns, including assets that are not easily discoverable onchain.
  • The motivation says dapps can block viable actions because they only see a partial onchain balance view.
  • The specification centers on a wallet-provided asset list rather than dapp-side indexing.
• Why it mattered:
  • This is the clearest evidence that ERC-7811 belongs in the corpus as wallet visibility and balance-observation infrastructure.

2) Raw ERC markdown / filtering and return rules

• URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-7811.md
• Key excerpt/signals:
  • wallet_getAssets supports assetFilter, assetTypeFilter, and chainFilter.
  • If assetFilter is provided, the wallet MUST only return those assets.
  • If assetFilter is omitted, the wallet SHOULD return all available assets and is recommended to order them by estimated value in descending order.
• Why it mattered:
  • These details show the standard is doing more than exposing balances; it defines how the wallet curates and prioritizes the asset surface shown to dapps.

3) Raw ERC markdown / asset typing and capability integration

• URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-7811.md
• Key excerpt/signals:
  • The standard defines well-known native, erc20, and erc721 asset types but leaves the type field as an open string for future ERC-defined expansions.
  • It says wallets supporting ERC-5792 should advertise assetDiscovery through wallet_getCapabilities.
  • It also references CAIP-25 session scopes for authorization-layer integration.
• Why it mattered:
  • This is the strongest signal that ERC-7811 is intended as an extensible wallet capability surface, not just a one-off multichain token endpoint.

4) JAW wallet_getAssets docs

• URL: https://docs.jaw.id/api-reference/wallet_getAssets
• Key excerpt/signals:
  • JAW says wallet_getAssets implements EIP-7811 and returns token balances across multiple chains for an account.
  • The docs expose the same main filters: account, chain filter, asset-type filter, and per-chain asset filter.
  • Example responses include native and ERC-20 assets plus metadata like decimals, name, and symbol.
• Why it mattered:
  • This is direct evidence that ERC-7811 is already becoming implementation-facing wallet RPC plumbing.

5) JAW RPC reference

• URL: https://docs.jaw.id/api-reference
• Key excerpt/signals:
  • The provider reference lists wallet_getAssets under asset methods and wallet_getCapabilities under capability methods.
  • The docs place asset discovery alongside wallet send-calls, permissions, and signing methods in one provider surface.
  • The surrounding method list shows how asset discovery is being integrated into a broader wallet control plane.
• Why it mattered:
  • This helps place ERC-7811 inside the same expanding wallet interface stack as ERC-5792-style capabilities and permission methods.

Working conclusion

ERC-7811 is best cataloged as wallet asset-discovery infrastructure. The decisive evidence in this pass was the ERC’s explicit move to make wallets authoritative for fuller multichain asset visibility, its default wallet-side ranking and curation rules, its integration with ERC-5792 capability discovery, and JAW’s concrete provider documentation exposing the method as a real wallet RPC surface.