Hi [@]Acidyo, How will you manage RC of the ocdbtemp accounts? It makes me remember something on Steem someone did (1 tmp account/pool of users) if I'm not wrong and an idea I had a long time before about something similar.

On the frontend, the temp account name is displayed in the username the user registered with, either his twitter account or facebook, or they can choose one but be aware that its not going to be immutable and they may have to change it later. This means that whenever that user leaves a comment, a vote or writes a post, everyone else using that website sees his username, not "ocdbtemp3".

To show the "the username the user registered" on your frontend (or others who would like to do) you can use the json_posting_metadata of the ocdbtemp account by adding a "alias" property (a string of the alias username) and when your user convert you just need to remove it from the property.

Same for post/comment you can use the json_metadata property of the operation to associate to the username the user registered (with using the same "alias" property. For the vote operation, it needs more thinking if you want to share it with other frontends, maybe with the usage of Ceramic network (mutable decentralized database).

I predict if you will add a web2 social connect system on your frontend, that 90% of people will not ask/want to convert to a real account. 90% of people outside the blockchain world like the simplicity of this type of connection even if they don't like the usage of their personal data and don't like/want to manage their own credentials/keys which seems unmanageable for them ;)