I could not understand the reason of this project. What is decentralize in it, Hackers or HKN token. What is the need of decentralized in this field? And How will HKN token and decentralization is helpful because of this project. Please elaborate.
If you need Hindi translation and moderation. I can help.
The big idea behind Hacken is that it turns each owner of Hackens into a community member. Because Hacken is a specialized software utility token, being primarily focused on cybersecurity professionals and projects, it will also bring these people together by providing incentives for doing business with one another and for investment in cybersecurity startups. These people will need to communicate and interact with each other in order to make use of their Hackens. The more vibrant the community is, the more value it delivers to each member.
Hacken (HKN) is an ERC20 token, which is the only payment tool allowed in the Hacken Ecosystem. Buying Hackens today, will allow one to receive high quality cybersecurity services in the future, at an attractive price.
Yes, Hindi language is welcome.
Please send us the overview of your previous translation experience. Use this email address for that -
kissngerbounty@gmail.comSo, May I say that Hacken is a token to buy-sell cybersecurity services. But how Hacken Ecosystem help security professional and consumer linked with each other? What type of services or products can be distributed through blockchain technology and not by traditional markets.
Yes, you are right!Simply to say -Hacken is a token to buy-sell cybersecurity services.
Here is how Hacken Ecosystem help security professional and consumer linked with each other and about use of blockchain:
We are building platform, that is providing Cebersecurity services, and when clients of our platform sign the bug bounty program agreement, our team creates a relevant blockchain block containing data about the product, the terms of service agreement and a timestamp.
The next block of the chain, which is specific to this client, will contain information on vulnerabilities, discovered during our security research.
Also we will build Cybersecurity Analytics Center, with such areas of research: Blockchain security, vulnerabilities and countermeasures.
All services are charged ONLY in Hackens.
Ok, now the picture is somewhat clearer. Clients will use the Hacken platform and submit their product information and use Hacken Token for payment. I assume that only data related to product is shared on blockchain not the product release and source files itself. Now, if a white hacker find bugs or vulnerabilities where he/she will share this information, on the blockchain or to some centralized servers? Who will authenticate that found bugs etc are relevant and hacker has to be paid for this? And what if other hacker found more bugs in the same product? Will he/she paid again for this?
Thank you for your question - her is answer for it:
Your question consists of a number of separate questions of their own. We answer them in the order in which they are mentioned in your post:
I assume that only data related to product is shared on blockchain not the product release and source files itself
This assumption is correct. We only use blockchain to issue HackenProof Vulnerabilities and Countermeasures Certificate and to prove authenticity of its contents ( number of vulnerabilities was fixed, client reaction) and timestamps. We store no customer sensitive information in the blockchain.
Now, if a white hacker finds bugs or vulnerabilities, where he/she will share this information, on the blockchain or to some centralized servers?
The researcher will share this information to our web portal HackenProof platform via bug bounty participant panel.
Who will authenticate that found bugs etc are relevant and hacker has to be paid for this?
The technical team of the client will investigate the vulnerabilities and determine whether they are relevant. The terms and rules of the bug bounty program will be stipulated by the document called policy.
Policy will contain all the information covering the depth and scope of the work to be performed by the researchers. It will explain to researchers what the customer needs.
We will also use policy as a proof of the customers intentions in an unlikely event of conflict between the client and the researcher regarding the relevance of the vulnerability that was discovered. If the client disagrees with our understanding of the policy, the incident will be submitted to the Public Board of Trustees of Hacken Ecosystem for further mediation.
And what if other hacker found more bugs in the same product? Will he/she paid again for this?
We are not sure we understand this question. The bug bounty program can have as many participants as the clients decides. They will be all submitting bug reports, which will be sorted chronologically and grouped by the issues covered.
The purpose of the bug bounty program is to discover as many bugs as possible within the scope determined by the client. Each participant of the bug bounty program gets paid proportionally to the number of bugs discovered, reported and accepted by the client.
