Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

Account UX #82

Open
lrettig opened this issue May 12, 2020 · 6 comments
Open

Account UX #82

lrettig opened this issue May 12, 2020 · 6 comments
Assignees

Comments

@lrettig
Copy link
Member

lrettig commented May 12, 2020

NEAR protocol has two nice features baked into accounts that I think we should consider:

  • "Link Drop" - the ability to send coins or tokens to someone who doesn't even have an account yet
  • OAUTH emulation - the ability to authorize apps (i.e., dapps) to use parts of an account on an ongoing basis, without needing additional signing

@YaronWittenstein I think it would be a good idea to understand how this was done to make sure we're not making decisions now that would make adding things like this more difficult down the road. Happy to help look into it.

@avive
Copy link
Contributor

avive commented May 25, 2020

@lrettig - please send some links so we can look deeper.

@lrettig
Copy link
Member Author

lrettig commented May 25, 2020

@avive okay - will take a closer look this week!

@lrettig lrettig self-assigned this May 25, 2020
@avive
Copy link
Contributor

avive commented Jun 18, 2020

Reminder - please send some info on these features so we can have a look and consider. btw - we do have a nice daily spending limit feature in smart wallet. I think that OAUTH only make sense when you have dapps on the platform so I'm not sure it is relevant for 0.3.5 where there's only our smart wallet contract. Link drop feature may be interesting depending on the use cases - we need to understand this better.

@lrettig
Copy link
Member Author

lrettig commented Jun 26, 2020

NEAR calls this "account keys." Lots more info here: https://docs.near.org/docs/concepts/account#access-keys. This is exactly the sort of thing that might be impossible to add later if we don't consider the design now.

@avive
Copy link
Contributor

avive commented Feb 12, 2021

@lrettig - didn't you move this to smip or pm repo?

@lrettig
Copy link
Member Author

lrettig commented Feb 14, 2021

This isn't a separate research task yet. It's sort of encapsulated by account abstraction. I think we can close this in favor of that, bearing in mind these use cases.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants