EOS TITAN (Labs) Public Account Profiles
by @controllinghand
7/15/2018
Intro (Transparency made Real)
This new tool that EOSTitan (Labs) has created opens up all kinds of possibilities for the EOS Community.
First things first what is it?
They have created a way to create a public account profile based on an EOS account name and store it into the EOS chain.
So what? why should I care?
- We could have all of our BPs create a public account profile as a requirement. This would enable transparency so that the EOS community knows who they are
- Any votes from non verified accounts could be brought to question. Especially whale accounts.
- We could require that all exchange have to create public accounts.
- Individual users have a way to protect and control their own profile for the foreseeable future.
How does it work
- The profiles are verified to come from the real EOS account holder as they are confirmed with a 0.0001 EOS transfer to the EOSTitan account.
- The data for profiles is stored on the EOS Titan servers, and can be view with their API. Other sites can use this for their own purposes
- This transaction is kept on the blockchain and can be referenced at anytime.
A Walk through setting up a Verified Public Account Profile
- go to https://labs.eostitan.com/#/account-profiles
- click on Create/Edit Your Own Public EOS Profile
- Fill in the form
- click the set profile
- Read the fine print and send EOS
Make sure to send the EOS from the account you want your profile to be linked to and send to eostitanlabs.
Also make sure to have the memo filled out when you send the 0.0001 EOS
- After you send the EOS from your favorite wallet, wait 30 seconds and then click on the link to see it.
- You can also validate your info by checking the json and hash number
https://passwordsgenerator.net/sha256-hash-generator/
They should match. - You can also check your info from their API
https://labs.eostitan.com/api/v1/account-profiles/active-list
- Here is a screen shot of the transaction on the EOS blockchain
Edit or Update
If you want to update your profile you walk through the same steps above and you will need to send another 0.0001 EOS
Tell your friends
I don't see any verification here. Anyone could put in any data they like.
I disagree. We can see all transaction related to an EOS account. If said EOS account is registered to a BP and they update the profile with information we will know it is legit. If the BP choose to update info that is misleading we have a single point to validate and hold them accountable. A BP would be wise to make sure the Profile information is accurate. If they don't they are taking a huge risk.
Also, the only one that can make changes to the profile is the owner of the account and who holds the private key. Also, EOStitan has provided a hash so that if it doesn't match what is on the block chain then we know the profile is corrupt.
lots of checks and balances there if you ask me.
This process allows anyone to verify that the owner of the EOS account posted their profile, but does not guarantee that the profile they created is accurate. It might be described as one-way verification.
We are looking into the possibility of creating easy two-way verification for the links to social networks, as that would be more convenient. It's relatively easy to ask people in telegram whether the EOS account in their profile belongs to them though.
Excellent tool. Let's take our network back
Excellent job very interesting congratulations
Blockstack.org has defined a nice decentralized profile system. It defines a zone file to look up the profile data. It is defined in their white paper and on some articles. Look for Blockchain Naming System (BNS)
The user can choose where the data is stored, i.e. it is decentralized, better protected against single point of failure. What happens if the eostitan servers fail? The zone file is small and is store on chain.
Looks like an interesting project, but from what I understand it doesn't tie EOS accounts to profiles, so it's not quite covering the same ground. We'll hopefully move storage to IPFS before long, but for now all data can be freely downloaded by the community, and resurrected in the event of a significant server failure.
This is a useful concept, but why not a smart contract to manage and store the info? This way require_auth can be leveraged for account verification. Perhaps v2.0?
Hi, we could have implemented this using a smart contract, but explained some reasons why we didn't in our news section:
https://labs.eostitan.com/#/news