Adding the squidrouter.com Validator - @Squid Operator to the XRPLF dUNL #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Overall performance seems strong. I appreciate explicit mention that keys are kept in cold storage. This is a clear entity, though I am personally not familiar with them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Validator details
Validator public key: nHUHeq3QdVyLTUENPHAAJ1d5M1SbvY49rajs31mJS8CEfrvTfjn3
Operator / project: Squid
Support contact: [email protected]
Evaluation details
1) Hosting and Infrastructure
Hosting: Bare metal server on OVH
Independent hosting (no clustering with other dUNL validators): Confirmed (independently hosted; not clustered with other dUNL validators to avoid centralization risks)
2) Geographic and network distribution
Region / location: Germany (eu-west-lim)
3) Community Track Record
Squid maintains production infrastructure for the XRPL ecosystem:
4) Operational and Security Practices
Key management: Not using an HSM currently; keys are stored in cold storage for backup
Monitoring / alerting: Custom monitoring system with Telegram/Slack alerts to engineers
Incident response: No prior incidents handled; on any alert we act immediately. If special actions are required, we can be contacted via [email protected]
5) Uptime and Performance
https://livenet.xrpl.org/validators/nHUHeq3QdVyLTUENPHAAJ1d5M1SbvY49rajs31mJS8CEfrvTfjn3