eeonevision / anychaindb Goto Github PK

The data of advertisers in database is not encrypted and visible to all.
Several advertisers sends open data about uniques identifier of their users (client id) and this data can be used by other unfair affiliates.
Use of encryption method from advertiser's side is not acceptable because leads to mess in data.

The proposal is apply BLAKE2B encryption to sensitive data in conversions/transitions.
Whitepaper: https://blake2.net/blake2.pdf

Currently access to database is not authenticated and may use some unfair users to destroy it

Proposal is apply standard Mongo auth with user/pass as public/private keys of account.
The authentication will set up in process of deploying the node.

The unsafe method option in config.toml file should be set to false

The Leadschain now exposes four ports:

• 27017 - MongoDB Instance
• 46656 - validators communication port
• 46657 - RPC interface
• 8889 - Leadschain REST API

For security reasons needs to be closed from external access ports: 27017, 46657.

Hi I am interested in your project, but don't know how to contact you, do you have some email or telegram handle?

The result is:

{
    "code": 400,
    "msg": "json: Unmarshal(non-pointer []*state.Conversion)",
    "data": null
}

When get transition/conversion ID need set status code from 400 to 404:

{
    "code": 400,
    "msg": "Conversion not found",
    "data": null
}