chifra names - other notes

[tjayrush]

• Are names applied to all tools?

  • Can we name addresses wherever they appear
  • A Name? Capability?

• Names should be stored in a binary backing store

• All names (custom or not) should be stored in a single file. Having two files is overly-complicated.

• All testing on any names data should not effect the existing user modified names file (or the original names binary file)

• Some Token contracts have a name stored on chain (such as OpenSea which has Project Wyvern Exchange at 0x7be8076f4ea4a4ad08075c2508e481d6c946d12b) but then they also have a real world name (OpenSea).

• Users should be able to query by name (for example TrueBlocks-Wallet) of names that they've aliased. So chifra names --alias MyThing 0x12 and then be able to use MyThing everywhere an address is used.

• There is actually. The end user needs a way to do it themselves locally (so the end user gets what they want -- named addresses), but there needs to be a "sharing" component while still preserving privacy. Something like "I know this address is XYZ contract, and I want to share this with the world" -- chifra names --add --share

  and also "I know this addresses, but it would be really bad if it were leaked: chifra names --add --private

  . (Adding this comment to the issue as well.)

[tjayrush]

Spread out into individual issues.