PersonaIam / persona-mainnet

Persona mainnet
0 stars 4 forks source link

Persona Improvement Proposal - Enrollment #6

Open stenea opened 5 years ago

stenea commented 5 years ago

User enrollment

ABSTRACT This proposal scope to decide alongside the Persona community regarding the enrollment process of users in Persona Trust Protocol and how they should be accommodated.

MOTIVATION When we started Persona more than a year ago, we’ve identified a couple of questions about how users will enroll in Persona. How would the cost of new users joining Persona be supported? Who is going to support the costs of the enrollment? We’ve decided to focus on the development of the platform and ask the community what is the right way when we reach that point.

When we are talking about enrollment we are referring to two different costs:

  1. The first is a “business cost”, similar to what is being paid when a delegate is registering as delegate.
  2. The second represents a “technical cost”, the fee to pay for information written and recorded on the blockchain.

At the same time we’ve realized that asking people who might not have anything in common with cryptocurrencies to make an account on some exchange, is not an ideal process. This means the users go through a KYC process and buy bitcoin in order to acquire Persona just to have their identity claimed in a service that provides the tools to be in control over your data. Since Persona is targeting mass adoption, whether they’re aware of cryptocurrencies or not, we are striving to keep the process as transparent and accessible as possible.

To answer these vital questions we came up with three options regarding enrollment. We are now turning to you, the Persona community, to help us make the best decision for future implementation.

SPECIFICATIONS To register on Persona and create a Persona ID a user should complete a form with the following fields: ● Username - unique ● E-mail - unique - email format should be validated After submitting the registration form, the user will receive an email with a link that will redirect the user to set its password. ● Password requirements: minimum password length of 8 or more characters. Include lowercase and uppercase alphabetic characters, numbers and symbols. Once the account is set, the minimum amount of Persona tokens (PRSN) needed to add the attributes in order to be able to use Persona identity is transferred in the user's account (PERSONA address) and the user's profile is enabled. These tokens are financed from the Enrollment Address and are set up to support the creation of new users, as everything on the blockchain requires a technical fee.

What is an Enrollment address?

The Enrollment Address is a system address set to only finance identity registrations.

This is how the Enrollment Address works: When a user creates his account, his Persona address will be automatically credited with the tokens needed to claim his minimum set of attributes. The cost for claiming the attributes is going to be recycled and sent again to the enrollment address while the fees for the transaction on the blockchain will be distributed to the delegate that forged the block. This is the same process when a user registers as a delegate. As we make new attributes available to be claimed in Persona, the cost of claiming these new attributes is going to be supported by the individual. The tokens available in the Enrollment Address can only be sent to itself. Practically the business fees are being recycled while the transaction fees are being distributed to the delegate that forged that specific block. The Enrollment Address will be funded only for the period the reward is 8 Persona tokens. As we will enter in the halving period, the Enrollment Address will stop receiving funds and keep recycling the remaining funds. In time the funds will be all consumed due to the 0.10 technical fee.

What are the options to fund this Enrollment address?

  1. The first option is to divide the rewards in half during the second year of 8 Persona tokens rewards and automatically send them to the Enrollment address. During this year, the Enrollment address will collect approximate 15.5 mil Persona tokens.

What this means in numbers:

Business fee (the cost of adding the attribute) would be 0.1 Persona. This means that for a whole set of initial attributes a user needs 1.1 Persona (where 0.10 goes to the delegate that forged that block).

Technical fee (the cost of having the data written on the blockchain) would be 0.1 Persona.

CONS: Initially the number of available tokens will be low, and it might not be enough to support all the requests.

PRO: This option blocks a certain amount of Persona tokens. It was the initial reason why the rewards were created like they are. If we would have initially generated a dedicated number of tokens for the enrollment, it would have certainly affected the inflation. Can be initially supplemented with 500.000 PRSN from Startup Fund.

  1. The second option is for the delegates to voluntarily donate as many Persona tokens as they like to the Enrollment address.

What this means in numbers: Business fee (the cost of adding an attribute would be 0.1 Persona) Technical fee (the cost of having the data written on the blockchain) would be 0.001 Persona

CONS: This second option can still cause friction for the delegates, as some will donate tokens, some will not donate, and the amount of donation can always vary. It’s almost impossible to put this option in numbers and to predict any outcome because there is no way to estimate the number of tokens collected.

PRO: There is no blockchain enforced rule and everyone can contribute with as much as they want/can.

  1. The third option is to divert some funds from the startup reserved funds to be donated to the enrollment address.

PRO: There are enough tokens to sustain millions of people that claim their identity.

CON: The technical fee received by the delegates is lower, 0.001 Persona.

Please comment on git about this first Persona improvement proposal.

kablammmo commented 5 years ago

I like option three best, and I think if implemented with a clear message that there is a limit to the amount of "free" identities that can be claimed would create a big draw.

At the same time it would be great to draw attention of communities and services to the fact the there is a huge pool of verified identities out there.

It feels like persona is solving a massive headache for people that are working on projects that might not even exists yet, but they need to know about it.

stenea commented 5 years ago

The tokens locked in enrollement address can be used only for identity claiming. They can no be sent to another address. So even if someone is trying to trick the system, by creating more than one identity, it doesn't have access to the tokens.

Silects commented 5 years ago

I'm voting for option number 1

-Curbs some heavy delegate inflation that's been ongoing sooner -Fair to all parties -Reserves startup fund for further development and project capital should it be needed in the future -Makes technical fees worthwhile, and tied to the success of the project/technology -Adds further (indirect) involvement to the delegate role -Offers the largest enrollment fund to work with (startup fund only has 12mil according to http://persona.world-domination.org/ - Can't imagine voluntary donations to exceed 5mil in any situation)