It creates an issue when deriving the stealth keys, which is derived by having the user sign over a human readable message which includes the chainId.It would be confusing for users, and force them to switch to the Ethereum L1 to setup the app before they could use it on L2.Presumably we could resolve strictly on the Ethereum L1, regardless of which network the user is doing the sending/receiving from, but this introduces other challenges: Bear umbra how to#We want to deploy Umbra across multiple networks, but it's unclear how to do stealth key resolution when doing so.There are edge cases associated with tying keys to the the name directly (what happens if the user transfers or sells the name, what happens if the owner of the name is not the same as the resolution address, etc.).There are lots of code paths and corner cases associated with supporting name services (which name service to use, what resolver the user is currently using, whether they're using their own name, or an umbra.eth subdomain, etc.).The relationship between the name service and Umbra is not clear. It's confusing: users seem to think that by setting up Umbra, all transactions sent through that domain name become stealth protected.Sending is different than in normal dApps, in that it requires the sender use a domain name, when most dApps allow the user to provide a domain name OR a regular Ethereum address.Setup requires several transactions and is expensive.Through the process of development, beta testing, and early adoption, we've recognized a number of challenges with this approach: It does this using a custom resolver (for ENS) or a text record (for CNS). Current ApproachĬurrently, the Umbra app publishes these keys by associating them directly with the user's ENS or CNS name. Rather, it is a periphery concern that can be handled by some convention followed by any app(s) leveraging Umbra. The publishing of public keys- those used by senders to create stealth addresses for a given sender- is not part of the core Umbra protocol.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |