Open complaint

Apart from voting on a certain subject (i.e. a proposal or complaint), a validator can also open a complaint for a certain account ID or hash based entity. The two functionalities that allow a validator to do this are: open_account_complaint(documentation_ipfs, complaint_for, complaint_type) and open_hash_complaint(documentation_ipfs, complaint_for, complaint_type).

Note:

The only key difference between these two functionalities is the value type for the complaint_for parameter, as on functionality accepts only AccountId values for this parameter while the other one accepts only hash values (i.e. H256 values). This is due to the fact that we store user based types via the users AccountId value, while on the other hand we store projects and carbon credit batches under their corresponding hash values.

If a validator wishes to open a complaint for a account ID based entity, he/she should provide some adequate documentation for their claim in the form of a IPFS link to said documentation. Apart from this, the validator should also provide the account ID of the entity for which the complaint is being opened and the type of complaint that is in question (e.g. project owner complaint, project complaint, etc.). When providing the documentation for the complaint the validator needs to use some form of documentation (IPFS link) that previously hasn't been used. Failing to do so will result in the functionality failing.

It is also worth mentioning that there is a corresponding fee associated with this functionality call. Here you can find more about the pallet fees.

Carbon credit batch status:

All of the possible complaints except the batch complaint work in a similar fashion in that their passing would result in the increase of the penalty level for the entity to whom the complaint was meant for. The carbon credit batch on the other had functions so that the carbon credit batch becomes "frozen" once a complaint has been submitted for it. If the complaint passes the batch will be "redacted" and if not it will once again gain the "active" status