-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of notaries being removed for inactivity #927
Comments
@raghavrmadya This is a very positive development. However, it's crucial to also address the issue of notaries who repeatedly sign abusive applications. It's concerning that many of these notaries refuse to explain themselves and instead resort to attacking those presenting evidence, demonstrating a clear dedication to their misconduct. The list is below:
The community has raised concerns about numerous instances of abuse by the aforementioned notaries who have been signing applications without proper due diligence, without asking valid questions, and consistently engaging in a recurring pattern of misconduct. Despite repeated allegations, these notaries have failed to provide satisfactory explanations or justify their actions to the community. Therefore, I strongly advise removing these notaries from the multisig at the earliest opportunity. (It is expected that the list will expand next month as our abuse detection tools improve, enabling us to identify and substantiate additional patterns that connect abuse cases and make them more apparent.) |
Can it be recovered? I sign now for Coffee Cloud. |
There was no response for a long time when I verified the client. |
Seeing no major pushbacks from the aforementioned notaries, the aforementioned notaries will be removed from the main multisig |
Thanks for reminding and all the welcome and we are really sorry for the late reply. The POWPOWER account will continue to be used. Due to internal reasons within the company, we missed a lot and caused the lack of signature before. During this period, we have been tightly following up the situation of the community in a timely manner, and we have seen the latest rules. In the future, we will have positive activity against the rules with our SLA. Please don't remove us, thanks! @raghavrmadya |
Please also do not remove us (Nonentropy Tech)! @raghavrmadya @Kevin-FF-USA |
@junyaoren Why not? You would need to give the community a clear explanation for this. |
"Due to internal reasons within the company" is no valid reason to be fully inactive. |
Thank you for your question and here is my response:
|
Hey Everyone, I really appreciate those of you that have taken the time to comment in Slack or send your input directly in this proposal. If any Notaries on this list wish to remain in the program, please open an appeal issue. The intent of the appeal is to give inactive Notaries a chance to address their applications SLA commitment. . To open an appeal, please create a new issue in this Github repository titled APPEAL.
For links related to this issue - please review Discussion - 2023 SLA Participation Community Proposal/Discussion - 911 |
I pointed out the issue of notary deactivation from round 3. |
Hi, my name is holiday, I'm in charge of Filecoin Plus project of CodoonHealth. |
Hi everyone, as mentioned in the governance call, we will be responding to all appeals in the specific issue and this issue is being closed |
Issue Description
The following notaries have been flagged the Fil+ governance team for no due diligence/singing:
Acrontech Inc.
Interstellar Storage
BigData Exchange
CodoonHealth
CoffeeCloud
Fungi Project
Ghost Byte
NonEntropy Tech.
POW POWER
Saukibit, Inc. (DBA Canza Finance)
Starboard
The following are not currently on the multisig due to unable to authenticate in Registry but were elected in v4
IPFS
Koda
Nick Merrick
emo-Capital
IPFS Japan Consortium
NFTStar
SecureExperts
This list does not represent notaries that are being flagged for abuse.
Proposed Solution(s)
Removal for inactivity from the multisig
Timeline
Community review - July 14 - July 18 2023
Removal actioned by RKH - July 19 2023
The text was updated successfully, but these errors were encountered: