Any user could read information from the blockchain. Therefore, for posting information in a secure way profile posting was provided in the PMES. profile is some encrypted text that has public description. Also, the profile owner could add public profile price to read access or for selling it by rights. After posting a profile to the blockchain user could retrieve it, sell it, etc.

PMES built based on the HD wallet technology. This allows the user controls his actives (coins, tokens and PMES profiles) by the seed (mnemonic, keystore file or private key). Therefore, anyone who will receive it will have access to all user's actives (coins, tokens and PMES profiles). So, private key, mnemonic and keystore file must be used only on the client side (web/mobile/desktop application) and the client application can't transfer them to the server side.

To interact with PMES server or any other, client signs the messages and passes them to this server with the public key to verify this message. Client application should have sign / verify / encrypt / decrypt functions implemented. sign function used to sign a message with the private key and then this signature could be checked by verify function. encrypt function used to encrypt seed with a password (chosen by the user) to backup seed in a secure way. decrypt function used to decrypt it respectively.

The PMES integrated with the Qtum BlockChain.

The Profile Management EcoSystem provides the following functionality:

• set in the blockchain:
  • profile (encrypted text)
  • profile description which is public
  • profile price to read access
  • profile price to buy rights of the profile
  • review of the profile
  • rating of the profile
  • offer to buy profile
• get all mentioned items from the blockchain
• change a profile owner
• sell a profile
• refill PUT wallet with tokens by wallet address
• withdraw PUT tokens

View API details here.

This repository contains the following modules:

1. ams - Account Management System - module that manages user's accounts. Has registration and authorization functionalities
2. balance - module that implements work with the blockchain wallets. For instance, adding wallets, view/increment/decrement wallet's balance
3. billing - module that contains fee estimation details
4. bip32keys - utilities used for simplifying communications with crypto-algorithms
5. coin - module that parses blockchain transactions to find PMES wallets and synchronize amount of money in blockchain with wallets in PMES
6. history - module that saves logs about actions and history of transactions
7. mail - module that saves and sends emails
8. pdms - Profile Data Management System (PDMS) - module that coordinate interactions between servers and daemons. It contains qtum_bridge module - middleware between the PMES and the blockchain
9. parser - module that parses blockchain, catches blockchain transactions and changes state of the account at the server
10. JavaScript client - provides utilities for generating public / private keys / blockchain address and sign / verify messages

An installation and running of the PMES are described here.

For using the Profile Management EcoSystem:

1. Run the PMES modules
2. Run a Python mock client
3. Create a client object and use mentioned functionalities as described in the python mock client or
4. Build an application based on the JavaScript client

The API uses the JSON RPC 2.0.

The Robin8 Profile Management EcoSystem and all modules are released under the Apache License.