You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm still reading, apologies if this is in the docs, and I'm sort of new to Ethereum.
If you'll allow me to explain my understanding of ERC-20 tokens and wallets, it'll help sanity check if my mental model is wrong:
An HD wallet creates a tree of deterministic addresses and any of these could have an amount of tokens assigned. Thus, the wallet must know all the tokens and query each one for balances for each wallet address. If you restore a wallet from seed it has to then regenerate all the child addresses and check all the token balances and it'll stop checking once it finds something like 20 child addresses with no balances (or activity/history?)
Does this mean that wallets that support EAS will need to do the same and look for and gather up all attestations?
And is it expected that attestations will target a single address or for privacy's sake, must be a new HD address for each attestation?
Bonus: is it expected that attestations will contain personal data? The fact that someone attended an event is personal data, but what other kinds of data are expected?
The text was updated successfully, but these errors were encountered:
I'm still reading, apologies if this is in the docs, and I'm sort of new to Ethereum.
If you'll allow me to explain my understanding of ERC-20 tokens and wallets, it'll help sanity check if my mental model is wrong:
An HD wallet creates a tree of deterministic addresses and any of these could have an amount of tokens assigned. Thus, the wallet must know all the tokens and query each one for balances for each wallet address. If you restore a wallet from seed it has to then regenerate all the child addresses and check all the token balances and it'll stop checking once it finds something like 20 child addresses with no balances (or activity/history?)
Does this mean that wallets that support EAS will need to do the same and look for and gather up all attestations?
And is it expected that attestations will target a single address or for privacy's sake, must be a new HD address for each attestation?
Bonus: is it expected that attestations will contain personal data? The fact that someone attended an event is personal data, but what other kinds of data are expected?
The text was updated successfully, but these errors were encountered: