HAPI Protocol
Search
⌃K

How to Become an Official HAPI Reporter

HAPI is built on the tenets of quality data first. Acquiring JUST data is not difficult. Acquiring qualitative and high-confidence data is hard work. Even more so when you have an array of disjointed sources that do not communicate between one another. Adding to that the fact that Official HAPI Reporters (referred in the next paragraphs as OHR) are to be independent i.e. no one single entity is there to immediately validate theirs or any other OHRs decision.
Hence, to construct a coordinated and efficiently working decentralized cybersecurity protocol, data of which is based on multitude of different sources - a robust, thorough, and planned-out system needs to be in place for Reporters Selection.
Reporters Selection ought to constitute a set of rules, guidelines, and penalties that are set in motion for the sole reason of provisioning ONLY qualitative and high-confidence data to the on-chain HAPI database. These mandates should be commonly and indiscriminately abided by all parties without prejudice or bias to one or the other. The sole purpose of being an OHR should constitute assistance to those connected to the protocol in the awareness of any malicious activity encountered by another OHR.
Types of Reporters
  • Publisher - publishes information directly into on-chain database
  • Tracer - traces Blockchain activity and identifies funds movement across network
  • Validators - validate (certain) published information on its relation to malfeasance
  • Authority - elected via Governance, Authority figures are able to initiate a case for address redemption (exclusion of a certain address or set of addresses from the database), and arbitrate in contentious cases
Preponderance* in becoming an OHR is given to the following entities/people:
  • Certified Compliance Officers who utilize services of HAPI (be it HAPI Labs or HAPI Protocol)
  • Representatives or Incumbents of the Compliance Office of Centralized Exchanges
  • A DeFi Protocol owner, a person liable or in any other way responsible for a project's security, ownership, or governance
  • Centralized Data Intelligence Providers
  • Decentralized Data Intelligence Providers
  • Web3 Wallet Providers - Head Developer, owner or any otherwise liable individual within a company's structure
*Although the above-mentioned group are the main provisioners of data to HAPI Protocol and are given precedence over, they are still subject to the same rules and guidelines including a commensurable penalty in case of ill-intent or any other breach described in the section below. These are the basic requirements for OHR. Changes may be incurred via specific DAO enacted voting.
Individual Official HAPI Reporter and How to Become One
HAPI is the only protocol of its kind that strives to achieve as diverse data as possible. Being a "protocol" also presupposes input from different kinds of users. However, these inputs, as everything under the umbrella of HAPI Protocol, should be meticulously selected. As such we can't possibly allow ANY user to submit an address directly to the on-chain database unverified or unvalidated.
There are however ways for an ordinary user to report and submit an address to the on-chain database:
HAPI Labs
HAPI Labs, Investigative and Intelligence Gathering Department of HAPI, possesses an off-chain database that contains at the moment of writing more than 16,000 addresses. These include "empty", and/or unverified addresses. Unverified addresses from unreliable sources need first to be validated by the HAPI Labs team (or in the near future by "high tier users") and external data sources.
HAPI purposefully sequesters databases in two. Firstly, because there is no valid reason to store empty or otherwise inactive addresses. And secondly, because the HAPI on-chain database is reserved exclusively for high-confidence, malfeasant and illicit addresses.
A user contribution to the HAPI Labs database will have a far lower entry point. The user input to HAPI Labs database will also have a reward-driven model that aims to commend a user based on their contribution (both quality and quantity). Without delving deep into the user-based data input model of HAPI Protocol, the HAPI Labs database is the main intermediary in User <-> HAPI Protocol relations.
*You can read more about how to contribute to the HAPI Labs database via Scamfari here:
Becoming an OHR
Becoming an individual OHR that is outside of the group mentioned in the paragraph above, is subject to a thorough selection process that we call Reporters Selection.
As mentioned above, an OHR has the ability to submit addresses directly into a HAPI on-chain database WITHOUT validation from any party. An OHR is also whitelisted into the system and is able to report addresses directly via Reporters Interface.
Before a user or entity can become an Individual OHR there are a certain set of prerequisites that need to be fulfilled:
  • Proven successful contributions to either HAPI Labs Database or any equivalent and certified cybersecurity investigative entity
  • Certification of AML (preferably crypto-specific AML such as Chainalysis or our own Cybersecurity Course*)
  • Ability to effectively and efficiently utilize HAPI Terminal, Chainalysis Reactor, or any other Tracing, Tracking, and Intelligence Gathering Tools (the full list of viable choices will be given at the end of the manual)
  • An Individual OHR should be backed by at least one existing reporter and should not be vetoed by any existing reporters
Remuneration/rewards Schema for Individual OHRs
For the sake of incentivizing Individual OHRs to contribute data, a reward mechanism is conceived.
In the case of Individual OHRs rewards are not necessarily based on the quantity of addresses appended to the protocol. Instead, Individual OHRs are rewarded by how quickly they react to the incidents.
For example: a hypothetical DeFi Protocol "Yikes Swap" has been exploited, an Individual OHR named Chad69420 has promptly reacted to the case and began by adding the "genesis" address to the protocol. Now, besides the reward for being the first to add the address, each consecutive address from this case added by Chad69420 will also be added to the base ratio of the reward (which is the promptly added genesis address).
As such, the reward mechanism of Individual OHRs values more so the promptness of reacting to the incidents within the crypto space rather than being an active "seeker" of malicious addresses.
Rules to Abide by For All OHRs
  1. 1.
    ONLY High-confidence* data to be submitted
  2. 2.
    ONLY Real Incidents. Out of spite or otherwise unsubstantiated submissions will result in penalty
  3. 3.
    Always have proof. Proof might be requested for the sake of Address Redemption via Governance. Therefore a proof should always be kept on hand
  4. 4.
    For Individual OHRs - Do Not Submit addresses solely for the sake of rewards
  5. 5.
    Stick to substantiated proofs/claims rather than guesses. If you are unsure about whether to start a case and submit address or not - then the proof is not solid enough
Penalty for Breaching the Rules
A process of penalization may be enacted by Authority Council via Governance. In this case a vote will be initiated to determine whether an entity or person in question is subject to the Penalty.
If any OHR breached any of the above listed rules a respective penalty may be applied.
Individual OHRs penalty is rooted in stake freeze as each Individual OHR must stake HAPI before he or she is able to open cases/submit addresses. Stake Freeze is a mechanism by which an existing OHR can be flagged and his or her stake frozen i.e. inability to unstake. A penalty can be absconded if Authority Council votes for Penalty Redemption. A reoccurring rules breaching may lead to the loss of OHR title e.g. inability to earn rewards and report addresses directly to the HAPI Protocol.
Certified OHRs that breached the rules are subject to review and may, to the same respect, lose their Whitelisted status.