wip: EIP-7811 improvements

ERCS/erc-7811.md

@@ -262,9 +262,29 @@
 }
 ```
 
+## Dapp Migration
+
+Dapps often rely on various backend services such as RPC or asset balance aggregators in order to display balances to the user or to restrict the actions the user can take in order to preserve user experience. It is recommended that apps take advantage of `wallet_getAssets` where possible to check what assets the user has to spend.
+
+In order to further simplify dapp migration, it is recommended that libraries providing provider-compatible (TODO link ERC) implementations polyfill `wallet_getAssets` for wallet connections that do not support it. The response SHOULD be a simple balance check for the chain only, as it is not known what abstraction capabilities the wallet has.
+
+Some dapps may not trust the `wallet_getAssets` value is correct or up-to-date with the latest balance, when compared with the current portfolio solution being used. In these cases it is recommended for dapps to merge the results of `wallet_getAssets` and their current solution by taking the maximum value of the two.
+
+## Dapp use cases
+
+When would dapps want to call this?
+
+### Checking total spendable balance for an asset
+
+E.g. DEX example with checking if enough USDC to execute the swap
+
+### Checking available assets to spend - select token UI
+
+E.g. DEX example, what assets do I have... greater than >$0.01 in value?
+
 ## Rationale
 
 <!-- TODO -->
 
 ## Security Considerations