arrow-left arrow-right brightness-2 chevron-left chevron-right circle-half-full facebook-box facebook loader magnify menu-down rss-box star twitter-box twitter white-balance-sunny window-close
Profiles on Apiary
2 min read

Profiles on Apiary

Today we are introducing Profiles as a feature on Apiary which enables DAOs that are indexed to claim their profile and assign editor rights to individuals.
Profiles on Apiary

Apiary aims to help people explore and understand the Aragon ecosystem.

We started by indexing all of the Aragon organizations and apps on mainnet and exposed them via an open GraphQL API as daolist. We also have built a simple DAO explorer interface as Apiary. These tools make it easier to keep track of KPIs related to DAO adoption, and organizations have started to treat the Apiary scores as a bit of a DAO Leaderboard.

But KPIs and analytics really only tell part of the story, what are all these organizations? What are they working on? How can I get involved or contribute?

Today we are introducing Profiles as a feature on Apiary which enables DAOs that are indexed to claim their profile and assign editor rights to individuals. We think that this will allow Apiary users to better understand the Aragon ecosystem and for Aragon organizations to more effectively promote what they are working on and help them attract new contributors.

Claiming an Organization Profile

One of the interesting challenges with introducing the profile feature was finding a way for us to validate that a user should be able to edit a listing on behalf of an organization. What we ended up doing is having a user request permission from the organization that the profile is associated with directly, then only if the organization approves the user is added as an editor.

When you try and claim a profile for the first time or if you are not an editor and you request edit rights you will be prompted to sign a transaction and likely require you to create a vote in the organization before you can proceed:

Once the permission has been added (e.g. after the vote has passed) then the account that requested access will have permission to edit the profile. The organization can revoke edit access for any editors that have been granted access using the Permissions app in the Aragon client.

The solution we came up with is actually really interesting and could potentially be used in the future to enable DAOs to more securely manage different web2 assets like GitHub, Twitter, Medium, or Discord accounts by delegating authority while maintaining the ability to revoke or re-assign privileges.

Profile Metadata

We wanted profiles to enable organizations to provide the basic information about their organization so that someone interested could learn more. Organizations can provide a basic description of their organization, set the display name and logo, and provide links to resources like the organizations webpage or primary Telegram channel.

This is what 1Hive LLC’s profile looks like:

Feedback and Support

If you have any trouble using Profiles or just want to give 1Hive some feedback or suggestions on Apiary in general, please either hop on our community chat or submit an issue on Github.