That's the idea.
The reality however is that will never happen unless both Apple and Google are fully signed up to Web3 and incorporate the clients as part of the OS.
And I don't see a single reason why they would do that when it would compromise their billion dollar payment revenue streams.
But this idea that it would be a persistently connected service running in the background on your phone. That's a completely different story.
Is there some benefit to users from OS integration eventually? ie "Pay With Ethereum" in the same way Apple Pay / Google Pay / NFC works, does that benefit from running a light client?
Sure, maybe the incentives aren't there because Apple wants Apple Pay money but whoever does implement it will make their device more useful.
No thank you, though your body and your choice.
Simpler to just change the metamask RPC provider to something I trust or even my home node. Is more difficult to change full-bodied web3 apps which rely on specific data graphs.
- download a hash-sized state root every block
- download the set of validator signatures over that hash and verify each signature against the hash. if using aggregation-friendly curve, download the aggregate signature and verify it against the root.
- for each state fragment, download the merkle uncles and compute the root hash and verify that it is the same as that signed off by the validator set.
so yes, easily within resource limits for having them running all the time with near zero impact. Find My has comparable impact.