Jonathan (@Schwartz10) and I want to propose the profile app that we have been developing (which integrates with 3box) be a “native” aragon application that is part of the Aragon client (aragon/aragon)
It doesn’t exactly make sense for a DAO to “install” the profile application, as it will likely be used by all DAOs. We both just got off a call with Brett (@sohkai) and he agreed that it makes more sense as a native app, part of the client.
A few other reasons why it will be important to include in the client:
- OrbitDB (used by 3Box) needs access to indexedDB, which is not currently possible in a standalone Aragon app due to iframe sandboxing. We spoke about a few workarounds for this strategy, including “storage spaces” as being researched and discussed here. However, these solutions are all longer term, much larger architectural initiatives that need special security considerations. However, as a native app, profiles would have access to indexedDB, so they could work with 3Box without loosening or adjusting iframe sandboxing strategy.
- 3Box asks for the
window.web3.currentProvider
, and uses it to request signatures via the JSON RPCsendAsync
method. Neither the web3 provider nor thesendAsync
method are exposed to aragon apps (seemingly on purpose), so in the short term, we’re using a very unsatisfying hack in order to make this work (we’re essentially imitating the web3 object with a single sendAsync method, that only accepts requests to the JSON RPCpersonal_sign
method). Theweb3Wallet
is available to the client, so we could use 3box and the current web3 provider properly.
Here are some standard profile designs below that make our work complementary with Aragon One’s identity initiative of ENS name claiming (subdomain of the global aragonid.eth). We wanted to show that the two concepts of a 3box profile and claiming an ENS username can intermingle.
We’d love to know what @luis and @Paty think about this. Do you think profiles are fit for the client? What concerns do you have? What more information would you like?
I’m totally open for collaboration on the designs as well (need to upload it to Figma…)
Designs
(click to enlarge the images below)
Legacy human (view mode)
Legacy human (edit mode)
(Pencil/trash icons displayed on hover)
Claiming an ENS username
Editing basic information
Pseudonymous future-human (alt design)
- Work history based on actual work you have completed/contributed (github / pando / etc history)
- Laptop sticker inspired cover region (nice to have
)
[Thanks to @Schwartz10 for providing the technical aspect of this post]