Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Organisation "proof of ownership" #44

Closed
onbjerg opened this issue Aug 28, 2019 · 0 comments · Fixed by #181
Closed

Organisation "proof of ownership" #44

onbjerg opened this issue Aug 28, 2019 · 0 comments · Fixed by #181
Labels
enhancement New feature or request
Milestone

Comments

@onbjerg
Copy link
Contributor

onbjerg commented Aug 28, 2019

In order to provide customisation features for organisations on Apiary, we need some way to prove that a specific account "owns" or "controls" an organisation.

This should be possible with the new Agent app.

Possible solution

Apiary would have a Registry contract somewhere that maps an organisation address to a list of "editor" addresses. In order to add an address to the list for your organisation you have to execute e.g. add(address editor) on this Registry contract.

Upon calling of this method, the contract will check if the caller is an Agent app and add the editor to the list of addresses for the kernel of the Agent app.

Apiary would periodically check for events (e.g. EditorAdded(address org, address editor)) on the Registry contract and give these addresses editing rights on Apiary to their respective organisations (see #17 for authentication).

Caveats: Right now it is only possible to use the Agent app using dao act in aragonCLI. Also, this approach requires organisations to have an Agent app.

@onbjerg onbjerg added the enhancement New feature or request label Aug 28, 2019
@onbjerg onbjerg added this to the 2.1.0 milestone Aug 28, 2019
@onbjerg onbjerg removed this from the 2.1.0 milestone Aug 28, 2019
This was referenced Aug 28, 2019
@onbjerg onbjerg added this to the 2.3.0 milestone Aug 29, 2019
@onbjerg onbjerg linked a pull request May 1, 2020 that will close this issue
3 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant