-
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
Removal of notaries from the Filecoin plus program #934
Comments
Thank you for raising Issue #934. As part of the Filecoin project, we highly value community feedback. |
In #913 we have explained that we are both first-round signers for these two LDN applications, and we do not know whether these SP nodes are the same organization , taking a step back, whether it is the same agency, has not reached an agreement, why remove us? |
I feel sad to see the news. “Based on multiple flags from the community in the T&T WG slack, calls as well as open disputes in the tracker, the following notaries are being recommended for removal from the main multisig” First of all, when I do due diligence, there will be subjective assessment in addition to objective observation (according to the previous notary's investigation report), so not every signature has a comment. Secondly, in the process of customer data encapsulation, I will also urge customers to pay attention to unreasonable "warnings" and require them to respect the rules. |
If there is anything unreasonable, please point out the specific deficiencies and let us improve. |
Since the implementation of the v4 notary work, I have actively participated in community governance meetings. For LDN signatures, I will investigate data samples in advance, test execution reports, and check data retrieval. Everything is executed in strict accordance with the rules of filplus. I do not belong to the most active group working in the community, but I also belong to the above-average level. I never participate in meaningless quarrels in the community, and I treat clients in all regions equally. |
Dear Filecoin Community Members & RG, We are passionate about our work and have always strived to execute our duties in a fair and impartial manner. Hence, the news that we are being recommended for removal from the main multisig "based on multiple community flags and open disputes" has left us troubled and perplexed. We would like to seize this opportunity to clarify our stance. For any possible misunderstandings or false reports, we are completely open to investigation and explanation. We fully respect the decision-making process of our community and the feedback of its members, but we'd like to underline that in order to respond and improve upon specific issues, it's essential for us to understand the allegations in detail. If possible, we request comprehensive information about the charges leveled against us. This will help us identify where the problem lies, how to resolve it, and how to continue serving our community in a better manner. We respect the viewpoints of every community member, and we believe that we all share a common goal - we all aspire for the Filecoin community to continue developing and achieve greater success. We regret any potential misunderstandings, but we also have faith that our community can overcome this issue through dialogue and understanding. We sincerely look forward to responses and guidance so that we can collectively work towards the progress of the Filecoin community. Thank you for your understanding and support. Sincerely, |
Dear Community Member: |
Hello @raghavrmadya , as a member of the community, I would like to share some personal thoughts with you. I will try my best to express them in a neutral language, and I apologize if any discomfort arises. My intention is to foster a positive community environment to support the development of fil+: Firstly, regarding the Notary Nodes (NNs) mentioned in the proposal, what is their current status? Are they allowed to sign as usual, or are they under investigation, which prohibits them from signing? Secondly, concerning the NNs mentioned in the proposal, what are the reasons for their removal? The accusations lack evidence and are generalized without specific details. This not only makes it difficult for other community members to judge but also makes it challenging for the nominated NNs to respond to the accusations. Thirdly, regarding the proposal's origin, as you, the leader of fil+, initiated this proposal, we all respect you. However, this kind of proposal can cause panic among the Notary Nodes in the community. If a proposal originates from accusations made by community members, it is advisable for them to submit proposals themselves in such situations. Fourthly, I suggest optimizing the proposal process and criteria. Lately, there have been many proposals in the community, some of which lack clear reasons and have resulted in a lot of negative feedback. This has also caused a significant waste of community members' energy as they have to constantly pay attention to proposal contents, even if they follow the rules, as they may face baseless accusations. Finally, I would like to add a few more suggestions regarding proposals:
I hope to receive feedback from other community members as well. Thank you. |
While going through ND Labs’ application, I have a high level of suspicion that ND Labs is colluding with sxx-future and 1ane-1 to abuse DC. Some applications are here - filecoin-project/filecoin-plus-large-datasets#1720 DaYouGroup, Aaron01230, ipollo00 are colluding and are actively abusing DC Example application- filecoin-project/filecoin-plus-large-datasets#1989 I have little to no confidence that the business listed in the above application is a real business about agriculture and fisheries |
More to come |
@Bitengine-reeta This is why your name is here - filecoin-project/filecoin-plus-large-datasets#1466 Additionally, can you explain such selective engagement as a notary with certain clients? |
MetaWave info continues to ignore due diligence by other notaries and has a pattern of singing. I do not think such behavior is conducive to the program and should stop, immediately. Example - filecoin-project/filecoin-plus-large-datasets#1558 |
additionally, you cannot just ignore active due diligence by a notary and just sign. That's just sub optimal due diligence, as seen here - filecoin-project/filecoin-plus-large-datasets#1918 |
For everyone's knowledge, BobbyChoii and Takichain have been added to the above list |
Zc fil, BobbyChoii, Casey-PG, and Takichain's due diligence approach of signing here is highly questionable - filecoin-project/filecoin-plus-large-datasets#1938 I have a high degree of suspicion that the aforementioned notaries are colluding to abuse DC |
I will continue to post more examples from my manual review of LDNs for the past three months that have led me to this stage. I'm also open to community feedback and it is my job to find patterns of potential abuse and make the community aware. If you disagree, please show evidence of DMs with the client or others forms of evidence of DD for applications that you have signed. In many applications, I found the aforementioned notaries blindly trusting some other notaries listed above. This, in my opinion, not encouraging quality usage of DC. Lastly, @NDLABS-Leo , I'm not the leader of fil+, I'm here just to ensure quality usage of DC, and that sometimes requires what we are doing now. |
|
Thank you for your response. In addition, regarding your response, I would like to provide the following explanations:
Once again, I express my respect to you. |
We are profoundly thankful to RG for providing a comprehensive explanation on this matter. We have responded in detail to each point of concern you've raised in a specific document. Furthermore, following our thorough examination, we can affirm that there is no collusion in any form with 1ane-1. https://docs.google.com/document/d/1My_QbNyGKIUfHO0sSqxBLKTpDqD1K5m5bBqymOVL-_E/edit?usp=sharing |
@newwebgroup Are you asserting the validity of your own examination and determining its accuracy? Shouldn't that be decided by the community? |
For #1989, this was the first round of signatures when i was review. In the absence of past records, I verified that there was no problem with the client’s company background, and then I asked questions about the data content. If the client did not explain clearly, I gave the opportunity to continue asking. The description and content given by the client were allowed and accepted. So, I signed the client.
|
I was shocked to see this proposal again. In the past, there was no very clear regulation for notarial review, so most notaries relied on the content in this link and their own review mechanism to review an LDN. The same goes for us. Since I served as a notary, we have been continuously learning and actively participating in notarial governance meetings. Although our team's English is not very good, But we purchased a real-time translation hardware device worth $800 to support us in understanding every notary governance meeting and keeping up with Filecoin. We have dedicated personnel who spend a few hours every day reviewing and reviewing LDNs. On #898 , we have also announced our team's review mechanism. We are not sure if community members and RG have carefully reviewed it, or if we have any mistakes, you can remind us in a timely manner. Our team is very eager to help Filecoin further succeed. |
Dear Mr. RG, why do you always like to handle problems through a guilty verdict? Every industry has a process of making judgments, so can you immediately convict and sentence them? Example:
|
#1989 We signed in the third round, and thus we referred to the early comments for auditing the situation of the LDN. You can view through the link provided by c12xf (filecoin-project/filecoin-plus-large-datasets#1989 (comment)), their data samples are in line with the description of the LDN, indeed content in the agriculture sector. Here you can view the screenshot or link (https://pan.baidu.com/s/1tPGfZSxZ6V2yg39UEJGxqg?pwd=dfxk). After confirmation, we used the CID checker for a detailed review of CID sharing, data distribution, and retrieval rate. Upon discovering the existence of CID duplication, we have inquired with the customer. According to the customer's feedback, we understand that the 12.5 TiB of duplicate data was not produced intentionally. The customer has explicitly stated that Dahua has given up this portion of data, and there will no longer be the situation of CID sharing. Moreover, this LDN's storage is distributed across more than 5 different regions with 16 nodes, fully demonstrating the customer's respect for the FIL+ specification. We believe that this presence is of great value to the Filecoin network, which is also the reason we chose to sign. If there is any issue that we might have overlooked during the signing process, please inform us. We will provide an explanation for related issues, and appropriately optimize our workflow in future notary work. |
Don't explain too much, you have already been convicted. Removable Removable!!!^^ ^^ |
Thank you for your response and for outlining the reasons for the proposed removal, letting us understand the grounds for our inclusion in the removal list. We have already addressed issue #1918, and I would like to reiterate our response here In relation to our offline discussions with the client that wasn't disclosed on Github, we commit to enhancing transparency in such matters moving forward.
It's infuriating that with the limited number of active clients and active notaries, the probability of 'in pair' occurrences is extremely high after multiple rounds of signings. This should not be a legitimate reason to justify our removal.
I think our level of activity is quite satisfactory. Once more, we direct your attention to our discussion in #933. We have an earnest desire for the FILPlus project to continue advancing and flourishing. Our suggestions are intended to reduce community friction and promote greater fairness within FILPlus. We respectfully express that Topblocks should not be considered for removal from Notaries Pool. |
It is true that the first round of inspection was a little looser. |
At least start a vote with all notaries please. |
@herrehesse I don't know what I have to explain to you. Is this another round of convictions? It's just so funny, you're giving me evidence that doesn't make sense, that you're messing with 666 |
I am messing with the devil @fsector-1 ? |
@herrehesse Mr |
Your words here, not mine mr.
|
We need to end FIL+. @DaYouGroup |
Some notaries are applying for LDN Big Data quotas for their own SPs The Filecoin community should update its review criteria for notaries issuing LDN Big Data quotas to prevent some notaries from abusing their rights as notaries. |
Thank you RG for expressing his opinion truthfully. The community has generated a lot of controversy lately none of which we want to see. Trust itself is full of controversies, what you trust may not be what I trust. trust in the web3 world is built on mechanisms, not KYC/KYB. If there is a need to vote to resolve disputes, we want everyone to have an equal opportunity to participate. |
The research found that some notaries and data holders have been trading offline for profit and selling LDN quotas, which is a serious violation of the filecoin project's development obstacles |
You mean selling datacap like Bitmain is currently doing? @SwitfSystem |
I was on the call "T&T dispute resolution call", and during the discussion of this issue, only 2 notaries were given chance to speak for like 1 min each, and this issue was decided a go ahead? There are 18 people on the removal list and it seems 2 mins are too short to decide their fate. I am wonder if all of them got the notification of this meeting taking place at all given the short notice. |
@kernelogic everyone got a chance, no one responded simply. Secondly it’s their job to be active & responsive, most of them are privately contacted by governance without any response. They get another chance in V5 soon. |
@kernelogic, please refer to the recording here - https://protocol.zoom.us/rec/share/b3E1tci4dcuprXXT2QnEXbwNychvObfYs43hKDeWkUNpim08BqMJUqRMUgVE7AY.1nZV-WJ6BECtul8E |
everyone was given a chance to speak. I did not limit anyone but no one spoke up. If the issue is language, they are welcome to post comments in their preferred language but simple silence does not help anyone get to facts |
Given that there were 90+ people on the call today, I would find it hard to believe they were not on the call, especially given that #934 was explicitly listed and updates were sent in the fil-plus and t&t wg channels. Still, I haven't closed this issue but apart from destor2023 and Aaron01230 (geoffrey), no one contirbuted |
I fiind it most reasonable that notaries that have provided reasonable counter facts, not just words, such as @Bitengine-reeta @DaYouGroup @NDLABS-Leo @1ane-1 and @ipollo00 engage. Additionally, @igoovo displayed honestly that they did let things loose. As the person who opened the issue, I would like to propose that we keep this issue open for another week, and if we don't get concrete evidence of conducting robust due diligence, they must be removed |
Forgive me if I'm mistaken, it sounded like from the meeting, the decision was to only allow the two who spoke up, destor2023 and Aaron01230 to keep the status, for others, such as @Bitengine-reeta @DaYouGroup @NDLABS-Leo @1ane-1 @ipollo00 @igoovo @newwebgroup who provided counter facts, but didn't get a chance to speak up during meeting, still on track to be removed. Anyways, since this issue is still open for another week, let's see what else can be done in the mean time. If zoom presentation is required to be considered eligible, more time should be allocated to adequately allow 18 people to present. That's all what I am trying to say. Thanks. |
@raghavrmadya I sent the Evidence to the T&T Call chating room on Friday.https://docs.google.com/document/d/1RC3CQLjJNrmst2zodMYyc0fYsni2gRuyxaNC2kpB678/edit |
Hi, @raghavrmadya Secondly, during the last TT meeting, ND was also present, but due to the large number of attendees and limited speaking time, not all accused individuals had the opportunity to speak. Additionally, ND was unsure if we needed to unmute ourselves to provide an explanation, so we did not speak. Thirdly, since the content of this proposal is about removing notary. so, do we only have to provide the proof of the related LDN's signature by ND? Lastly, what should be our next steps? Will there be a separate meeting for explanations, or should we continue to submit evidence on GitHub? Once again, I express my respect to you. |
Let me reiterate the due diligence we conducted during the LDN 1989 review, as this was the third round, So, we conducted the following due diligence work: 1.Data verification: We carefully examined the application information, referred to the early comments and cross-referenced it with the relevant data. No inconsistencies were found with the application information. Regarding the accusation of non-agricultural data in the LDN, the provided link led to a video of a dairy farm, which, in our view, qualifies as agricultural data. If this does not meet the requirements for agricultural data, we are unsure of what would. 2.CID robot inspection: We used a CID robot to check if the packaging process adhered to Fil+'s specifications. During the inspection, we discovered instances of CID sharing. However, upon communicating with the client, we learned that it was an inadvertent error, and the client pledged it would not happen again. Furthermore, we can confirm the client has fulfilled their commitment through the latest CID report. 3.Node distribution check: We verified if the node distribution complied with Fil+'s specifications. Although the specifications are advisory rather than strict requirements, we consistently encourage clients to adhere to them as closely as possible. In this audit, LDN is distributed across five different regions, including Singapore, Shenzhen, Los Angeles, Clifton, England, and Hong Kong, totaling 16 nodes. Each storage allocation is below 20%, fully aligning with Fil+'s guidelines. Based on the results of these investigations, we concluded that the LDN complies with Fil+'s specifications and proceeded with the signing. As for the situations of other notaries, we are not aware of them and are not familiar with their circumstances. Thus, there is no evidence of collusion or abuse. We had already explained the above details in Github comments two weeks ago but received no response. We would appreciate your confirmation on whether Github comments are effective or if you prefer opening a separate ISSUE for further clarification or conducting a voice meeting. Please inform us through Github. |
In this LDN, we just asked a few simple questions and checked some relevant data. However, due to various reasons, we did not sign at that time. We hope you can carefully check it. When we mentioned this issue in the last meeting, we were unable to speak in a timely manner due to language issues, but Our review mechanism has been announced on #898, and it can be seen that #898 has been closed. If there are any further questions, we hope you can point them.Thks! |
Prior to this, NWG has submitted an explanation document on Github.And also participated in the last T&T meeting. So what should we do next? |
Hi @raghavrmadya
For those other notaries who do not provide evidence going to be removed next week?
Please give feedback on whether you agree or not under everyone's evidence. Everyone seems to be very confused now. |
Dear RG,As a V3 and V4 notary,contirbutor to filecoin,we strictly abide by the fil+ guidelines, perform corresponding due diligence, and actively participate in filecoin activities as members of the Oribit community. We have not colluded with anyone in this. It seems to me shameful to do so. Given the last time you showed the picture of our collusion with NDlabs and NWG we put together the documentation to clarify. We also participated in the conference call last Friday, and we were ready to speak. We thought we needed to be called to speak, so we waited, but we missed the opportunity to speak. Therefore, I wanted to post the content of the explanation and the link to the Google document on zoom before the end of the meeting. I wonder if you have seen it here? If you feel that we still need more evidence to clarify, I sincerely want to arrange a zoom meeting with you to resolve this matter. Thank you so much. |
This discussion has made it clear that an evidence-based approach is NOT helpful in keeping notaries in check. IMO, the room for interpretation given to notaries is being heavily abused and we need strict guidelines by the community on due diligence and what a notary must do before signing. As such, this specific discussion has reached a dead end. In the coming days, I will open separate issues outlining the instances of abuse against specific notaries listed in this thread |
Based on multiple flags from the community in the T&T WG slack, calls as well as open disputes in the tracker, the following notaries are being recommended for removal from the main multisig
DaYouGroup
1ane-1
woshidama323
zcfil
newwebgroup
ipollo00
Normalnoise
Aaron01230
igoovo
Bitrise0111
AthSmith
Casey-PG
destor2023
Bitengine-reeta
UnionLabs2020
MetaWaveInfo
TakiChain
BobbyChoii
The text was updated successfully, but these errors were encountered: