Skip to content

Conversation

@dangell7
Copy link

@dangell7 dangell7 commented Aug 5, 2025

Justification for removal of data443.com

  • Absent from community
  • Absent from voting on amendments
  • Absent from voting on fees (still on 10 XRP without justification of why)

In my opinion data443.com has not been a good community validator. While they have been reliable as far as uptime, they are almost completely absent from voting and this imo is more important than spinning up a server on aws. I also believe anyone who is still on the old fees without providing justification to why is actionable intelligence for review and removal. It tells me they are lazy and cannot be bothered to make one simple adjustment.

@mvadari
Copy link

mvadari commented Aug 11, 2025

Note: tequ's validator is not located in Japan, so I would say the last point doesn't count

@jonaagenilsen
Copy link

Where IS tequ's validator located? Will it add to the diversity of the UNL?

@mvadari
Copy link

mvadari commented Aug 12, 2025

Where IS tequ's validator located? Will it add to the diversity of the UNL?

cc @tequdev

@mankins
Copy link
Member

mankins commented Aug 14, 2025

@dangell7 can you remove tequ's addition from this PR? Ideally we'd do these as independent items. I see that #4 has already taken care of that part.

@dangell7
Copy link
Author

dangell7 commented Aug 14, 2025

Ok it is my understand that a voting group should never be an even number. So as long as the Foundation is keeping track of that.

@mvadari
Copy link

mvadari commented Aug 14, 2025

PR title/description should be updated accordingly too

@dangell7 dangell7 changed the title Remove: data443.com Add: tequ.dev Remove: data443.com Aug 14, 2025
@pkcs8
Copy link

pkcs8 commented Aug 19, 2025

I endorse this change.

@rickyowens
Copy link

Has not been validating for 24hrs now, no communication, history of not voting, I support this.

@danielwwf
Copy link

I second this change

@mankins mankins self-requested a review August 25, 2025 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants