Local vs global data configuration

[kwannoel]

In GitLab by @ApolloUnicorn on Mar 25, 2021, 02:09

• [ ] Separate a list of user-selected addresses / assets / etc. from directories of available ones.
  • [ ] For instance, unit of account in the beginning can only be what was initially detected as the unit from the country where the user is; then the user can add or remove from the master list.
  • [ ] Native tokens from other blockchains, ERC20s, ERC721s, etc., can be added from some directory, but in the beginning the list is empty and/or only includes the CED.
• [ ] sources of trust for addresses and assets to interface with -- so some can be marked trusted, and others can be marked blacklisted, no-longer-valid, soon-to-be-deprecated, etc.

[kwannoel]

In GitLab by @ApolloUnicorn on Mar 25, 2021, 02:09

changed the description

[kwannoel]

In GitLab by @ApolloUnicorn on May 12, 2021, 04:25

assigned to @AlexKnauth, @drewc, and @fahree

[kwannoel]

In GitLab by @fahree on May 12, 2021, 04:31

"Global" configuration would be a directory of all resource types in the world.

"Local" configuration is the short list of those resource types that a given user in interested in and trusts.

e.g. if there are 36 ERC20s with name "USDT", the "real" USDT is whichever the user cares to cost such. Maybe there is another he is mildly interested in watching in that he'll locally call "USDT_bar" instead of "USDT".

[kwannoel]

In GitLab by @plotnick on Sep 9, 2021, 02:29

unassigned @drewc