xrpscan / hermes

Project Hermes: XRP Ledger Validation message service
https://xrpscan.com
MIT License
6 stars 4 forks source link

Support ingress from multiple rippled instances to source validations #11

Open pkcs8 opened 2 years ago

pkcs8 commented 2 years ago

Requested by Rabbit - One standalone hermes instance connects to a single rippled server only. Sourcing validations from multiple rippled servers can provide better visibility of the network.

pkcs8 commented 2 years ago

@crypticrabbit It is possible to run the standalone ingress processors by passing RIPPLED_URL environment variable.

[xrpscan@xrpscan-unstable hermes]$ RIPPLED_URL='wss://xrplcluster.com' node dist/cmd/ingress
[Hermes] info [mongod] Connected: mongodb://localhost:27017/hermes_prod
[Hermes] info [xrpl] Connected: wss://xrplcluster.com
[Hermes] info [ingress] Ingressing validation messages from wss://xrplcluster.com
^C
[xrpscan@xrpscan-unstable hermes]$ RIPPLED_URL='wss://xrpl.ws' node dist/cmd/ingress
[Hermes] info [mongod] Connected: mongodb://localhost:27017/hermes_prod
[Hermes] info [xrpl] Connected: wss://xrpl.ws
[Hermes] info [ingress] Ingressing validation messages from wss://xrpl.ws

Along with the ingress startup script available at bin/ingress.sh, it should be possible to run multiple ingress processors that source validations from multiple rippled servers. Please let me know if this setup works.

jscottbranson commented 2 years ago

Thanks so much, I'll give that a try once I get my node functioning (maybe after Apex).