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
Current implementation from #1964 implemented only the email and connected_accounts scope, to reflect what was included in the mockup in Figma (only user-selectable scopes available at time of design). Rest of the scope value claims are missing and should be added.
This tracks:
Expand example in Figma to also include system identifier scopes grouped together without any claim values, profile scope with name and picture values as well as erc_4337 scope with wallets.
Clean up the connected_accounts scope mockup to remove verified field, picture field as neither of those data elements are shared as part of the connected_accounts claim, and add the Type as that's a data element that is shared.
All scopes that can have more than 1 claim value selected (profile, erc_4337, connected accounts) should be expandable in the table. The "CLAIM VALUE" column for such scopes will not contain concrete data but only general information about whats being shared (eg. 5 Smart Contract Wallet(s), instead of wallet IDs). The concrete data will be available in the expanded view.
Columns should be renamed:
"CLAIM NAME" column > "APP ASKED FOR"
"CLAIM VALUE" column > "WHAT’S BEING SHARED"
"SOURCE" column > "SOURCE OF DATA"
Current implementation from #1964 implemented only the
email
andconnected_accounts
scope, to reflect what was included in the mockup in Figma (only user-selectable scopes available at time of design). Rest of the scope value claims are missing and should be added.This tracks:
profile
scope withname
andpicture
values as well aserc_4337
scope with wallets.connected_accounts
scope mockup to remove verified field, picture field as neither of those data elements are shared as part of theconnected_accounts
claim, and add the Type as that's a data element that is shared.erc_4337
addresses #2256.The text was updated successfully, but these errors were encountered: