Accessing Personas

[smacz]

Continuing the conversation from

Anonymity vs Validated Identity on the SAFE Network

The prospect of complete anonymity and communiation security on the SAFE network is one of its most important features, as discussed in another recent thread. The flip side of this needs some discussion, too, I think. Since the network is cryptographically secured, it is inherent that, even while anonymous, an address is verifiable as belonging to the signing identity. This should allow for the ablility for anyone to have a persona which can be verified as belonging to a publicly verified iden…

How are the Personas accessed by other users? How and where is a Persona stored? How can Personas be shared?

[janitor]

Not firm yet. General idea explained in this topic.

Feature Request - Persona Trees

I have been thinking about how accounts and permissions are setup in Maidsafe. It would be really nice to be able to have multiple identities, with different access rights all managed by a single account. My idea is persona trees. When you first create an account on the network, you use a username and password to create a root persona or identity. From this root, you are able to create children persona, and children from those children. Each persona gets their own private keys, access right…

[smacz]

Thanks for the linke @janitor, I hadn’t come across that one yet. Found in that topic:

@vtnerd

We are currently working on the details, but we want to make a log-in once system, even for desktop apps. So the user logs into the SAFE launcher with a password, and then selects from a list of identities (or creates a new one) when launching an app.

That list of personas would necessarily be stored on the network. To store it on the network, that would necessarily require a PUT. Is the user going to be charged for a PUT each time they create a new Persona?

[digipl]

I think so. Possibly the personas will be, similar to the DNS, another Structured Data type. Add a new persona is add an SD, charged like 1Mb not structured data.

In fact according to this RFC, and I think is a mistake, you need to pay at least one safecoin to create an account. You have more information here.

[smacz]

@digipl you are on fire today! Great links and something I will need to study a bit farther.

It the account creation attack thread I do agree with you that an account should not incur a cost to set up, just like browsing the SAFE Network should be free.

@digipl

…everyone will need to spend safecoin to use the network for things like send messages but we cannot force to do that from the beginning. This must be a natural and free process.

Disregarding the technical implementation and account creation attack of this, would it be feasible to have free account creation, but pay for any persona creation? Think of it like visiting a forum. Anyone can view the posts, but to post yourself, you must sign up for a persona on that forum and then under that persona you can post whatever you wish? (the single forum in this analogy is the entire SAFE Network)

In that scenario, personas can indeed have a similar implementation to DNS and just be another SD type.