# PeerAssets Alias/Proof-of-identity protocol specification - Status: proposed - Type: new feature - Related components: 0003-peerassets-alias-poid-transaction-specification.proto - Start Date: 13-01-2017 ## Summary Extension of PeerAssets protocol specifies using singlet PeerAsset deck to alias the Peercoin address with any UTF-8 string with added secondary functionality of using descriptive information contained in the PeerAssets token to allow proof-of-identity verification of the privkey owner. Use of aliases in the form of @alias instead of a standard Peercoin address is made possible for all PeerAssets and Peercoin transactions. A blockchain client (wallet) can save verified alias locally and translate @Bob to a Peercoin address like PDF4NNGBGRSxnRJPyNQyMHqffqbXEtRy5T on the fly. This proposal tries to come up with an elegant solution to the problem of matching the "real life" identity of a person with an address on the blockchain by verifying that specific public key is in control of person X. This protocol allows knowing your customer (KYC) and obliging to the law in some countries. 1 Usage of this protocol for identity verification also prevents sybil attack if there is a service depending on trusting some specific key set. Unlike similar protocols for blockchain proof-of-identity, this protocol allows an alias to be transferable to another address, providing both improved privacy and utility. Mobility of the alias is possible as the alias is a simple PeerAssets "card," which means it is as mobile as any other blockchain token issued via the PeerAssets protocol. Aliases can be transferred, traded, updated or even destroyed on the blockchain. Verification of the alias works just like verifying email upon registration to some online forum, where the claim of identity is backed by proving ownership of the email address. A similar process is employed here, where the party claiming the identity behind the Peercoin address backs it by posting proof on their social media account or in a private exchange via email. Two modes of verification are possible: manual and automatic.