Search the Community

Hi All, We are running the XRPL validator at the University of Tokyo, Japan. Although we have been operating our XRPL validator for a few years, we were obliged to change our public key, shown below, because of occurrence of failure in our server. After the recovery of our server, we have successfully set it up our XRPL validator, and confirmed that the domain verification was properly configured. Public key: nHBZvkRq3G36n38Wd2Vifqp4sHnqxT3sJTQBs2PWFHxp5gM2TC4X When I checked if our validator is shown, for instance, in the XRPSCAN validator registry, I found it but only through the public key. Our domain name is shown below: Domain name: digieco.e.u-tokyo.ac.jp The below is the link to the XRPSCAN validator registry of ours: XRPSCAN validator registry of ours However, you can see that the domain name of our validator is not shown in that validator registry. As a reference, I also tell you the link to the result of alloy's toml checker. https://xrptools.alloy.ee/checktoml?domain=digieco.e.u-tokyo.ac.jp&display=html I have tried to fix this issue in several ways but I could not fix it. Would you please tell me the way to show our domain name in the XRPSCAN validator registry? Best regards, Tatsuru Kikuchi

The community could in a way vote on amendments without maintaining a validator themselves, this would allow the community's voice to be heard in the xrp ledger. An entity (me in this case) would be running a validator, the community could vote on amendments by sending transactions to a specific wallet that the validator maintainer owns with memos attached to them (e.g: YES/NO), the validator maintainer would run a server that would scan the wallet's ingoing transactions and scan their memos to tally up the votes. Every funded wallet on the xrp ledger can submit a vote, only once. This is a great idea in theory but the validator maintainer could manipulate the consensus vote, which creates a false narrative in the xrp ledger, the validator maintainer must be trusted by the community to not corrupt the community's decision. Also thank you @nikb for suggesting me to sign up here .

Would you please give us some advices about validator problems? Domain Verification Succeeded We have been running rippled validator at the University of Tokyo. However, it has not been working properly after May, 2020. We have tried to fix the problems, and somehow received the message, 'the domain verification was successfully completed'. However, when I saw the XRP Charts, no information has appeared yet. This is the current situation and we need some advices to fix the problems. Account Verification Failed One guess about the cause of the problems is an account verification issue. In fact, we have not yet succeeded for the account verification. In my understanding, it was not necessary for the validator to complete the account verification step at the time when our validator has been working properly. I am unaccustomed to proceed the account verification for the validator, and I would like to ask someone to give any advices in writing the correct information on the xrp-ledger.toml file. Our xrp-ledger.toml File which may include some mistakes: [METADATA] modified = 2020-12-10T00:00:00.000Z [[VALIDATORS]] public_key = "nHDpfGYGhh6eW9NVxRqbdjZvAMN1du5FVveTa7vNzzXQJ1wXdopg" attestation = "F5CC2B860A89D6DABF1C12177D24D0E6F17C04E2909E795ADBFFC51A8A9AA4E554C8F29C6DA1619AE7585667E65390F2A73D61A334453A71CA4ABE6C322D960F" network = "main" owner_country = "JP" server_country = "JP" unl = "https://vl.ripple.com" [[SERVERS]] peer = "https://digieco.e.u-tokyo.ac.jp"

I'm running XRPL validator (public key: nHBmJuwMPRh2mLrYhUdFHNKrZ3cwXEkiGAKXESM4mDvQKMF8WAp7) based on Wietse's Wind docker rippled validator repo (https://github.com/WietseWind/docker-rippled-validator). It's up and running newest rippled version 1.2.0. Now I'm trying to validate my (sub)domain (again according to the instructions of Wietse - https://medium.com/@WietseWind/verify-your-ripple-validator-show-your-domain-da19de30b19bbut) with no success. I'm little bit desperate and really don't know what I'm doing wrong. Hope someone can help me. After a few attempts I ended up with following configuration: Server 1 (S1): web hosting with simple web presentation https://www.rippled.eu Server 2 (S2): with rippled validator running CentOS with webserver running and serving subdomain https://validator.rippled.eu I edited apache ssl configuration file (ssl.conf) with these parameters: ServerName validator.rippled.eu SSLCertificateFile /.../validator.rippled.eu/cert.pem SSLCertificateKeyFile /.../validator.rippled.eu/privkey.pem SSLCertificateChainFile /.../validator.rippled.eu/chain.pem Both servers has its own Let's Encrypt certificate (S1 *.rippled.eu, S2 validator.ripppled.eu). Certificates were generated using Certbot on S2. On S1 I uploaded thru administration control panel of my webhosting service. Web browsers displays that certificates are valid. S1 has DNS A record (validator.rippled.eu and *.validator.rippled.eu pointing to public IP of S2) In verification process I'm running following command: "docker run --rm -it -v /keystore/:/keystore/ -p 80:80 xrptipbot/verify-rippledvalidator" Next listing is as folows: So I ran next command: docker exec rippledvalidator /keystore/finish_signing In final step I inserted requested data into Google Docs "XRP Ledger Validator Domain Verification" document Email: my email Domain: validator.rippled.eu Validator public key: nHBmJuwMPRh2mLrYhUdFHNKrZ3cwXEkiGAKXESM4mDvQKMF8WAp7 SSL Signature: 512B long hash Domain Signature: 128B long hash Everytime I tried, I received email with following message: Could someone point me where I'm making mistake, what's wrong with my certificate or verification process? Why is verification process missing my certificate? Am I missing something in apache configuration files (https.conf, ssl.conf) or rippled config file (rippled.cfg)? I'll be glad for every suggestion or help. Thank you.

Hello all, I am attempting to set up a Windows based Validator, with system details; AWS based server Windows Server 2019 Datacenter Xeon 2.3GHz quad core x64 based processor RAM: 16GB SSD: 80GB (plus another 50GB if required) I'm using Visual Studio Community 2019 16.3.5, with 'Desktop development with C++'. There is a pretty good guide below and I have gone all of the way through this including SSH, Git, Boost etc; https://github.com/ripple/rippled/blob/master/Builds/VisualStudio2017/README.md The CMakeSettings.json I copied from the example given at; https://github.com/ripple/rippled/blob/master/Builds/VisualStudio2017/CMakeSettings-example.json And of course I checked and updated the Visual Studio version to be 'Visual Studio 16 2019 Win64', as well as the Boost and OpenSSL locations. When I go to compile and build the project I get the below; Error CMake Error at Builds/CMake/RippledSanity.cmake:77 (message): Visual Studio 32-bit build is not supported. Use -G"Visual Studio 16 2019 Win64" C:\Program Files\Git\Cloned\rippled\Builds/CMake/RippledSanity.cmake 77 I've looked and checked everywhere, but I'm missing something. Any ideas people? The full build Output is; 1> CMake generation started for configuration: 'x64-Debug'. 1> Command line: "cmd.exe" /c ""C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe" -G "Visual Studio 16 2019" -A x64 -DCMAKE_INSTALL_PREFIX:PATH="C:\Program Files\Git\Cloned\rippled\\out\\install\\x64-Debug" -DBOOST_ROOT:STRING="C:/lib/boost" -DOPENSSL_ROOT:STRING="C:/Program Files/OpenSSL-Win64" -DCMAKE_CONFIGURATION_TYPES="Debug" "C:\Program Files\Git\Cloned\rippled" 2>&1" 1> Working directory: C:\Program Files\Git\Cloned\rippled\build\x64-Debug 1> [CMake] -- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.23.0.windows.1") 1> [CMake] -- Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.17763. 1> [CMake] -- The C compiler identification is MSVC 19.23.28106.4 1> [CMake] -- The CXX compiler identification is MSVC 19.23.28106.4 1> [CMake] -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe 1> [CMake] -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe -- works 1> [CMake] -- Detecting C compiler ABI info 1> [CMake] -- Detecting C compiler ABI info - done 1> [CMake] -- Detecting C compile features 1> [CMake] -- Detecting C compile features - done 1> [CMake] -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe 1> [CMake] -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe -- works 1> [CMake] -- Detecting CXX compiler ABI info 1> [CMake] -- Detecting CXX compiler ABI info - done 1> [CMake] -- Detecting CXX compile features 1> [CMake] -- Detecting CXX compile features - done 1> [CMake] -- Using 2 cores for ExternalProject builds. 1> [CMake] CMake Error at Builds/CMake/RippledSanity.cmake:77 (message): 1> [CMake] Visual Studio 32-bit build is not supported. Use -G"Visual Studio 16 2019 1> [CMake] Win64" 1> [CMake] Call Stack (most recent call first): 1> [CMake] CMakeLists.txt:26 (include) 1> [CMake] -- Configuring incomplete, errors occurred! 1> [CMake] See also "C:/Program Files/Git/Cloned/rippled/build/x64-Debug/CMakeFiles/CMakeOutput.log". 1> [CMake] 1> cmd.exe /c ""C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe" -G "Visual Studio 16 2019" -A x64 -DCMAKE_INSTALL_PREFIX:PATH="C:\Program Files\Git\Cloned\rippled\\out\\install\\x64-Debug" -DBOOST_ROOT:STRING="C:/lib/boost" -DOPENSSL_ROOT:STRING="C:/Program Files/OpenSSL-Win64" -DCMAKE_CONFIGURATION_TYPES="Debug" "C:\Program Files\Git\Cloned\rippled" 2>&1" returned with exit code: 1

Blog URL: https://coil.com/p/Hodor/XRP-Limitless-Scale/MfAIXnQiD XRP can scale to unlimited heights. Find out more, along with my breakdown of the latest pivotal news about the US Federal Reserve's decision to build "FedNow:" 𝐆𝐞𝐧𝐞𝐫𝐚𝐥 𝐁𝐥𝐨𝐜𝐤𝐜𝐡𝐚𝐢𝐧 𝐍𝐞𝐰𝐬: The Federal Reserve decides to 'build their own' with the latest news about a new system called FedNow. 𝐑𝐢𝐩𝐩𝐥𝐞 𝐍𝐞𝐰𝐬: MoneyGram conducts its quarterly earnings call and discusses their Ripple deal in depth; ChainTalk interviews Tomohiro Yamaguchi; and an XRP fan analyzes Ripple's UBRI initiative. 𝐗𝐑𝐏 𝐍𝐞𝐰𝐬: Coinfield and Omni create XRP Validators in support of their business; CEX, a UK-based platform, adds an XRP-GBP pairing; and DOBI, an innovative Chinese company that specializes in ATMs and 'wearables,' decides to support XRP. I hope you enjoy the read: Please feel free to share my blog with a friend or share it on any other platform - and thanks for doing so! My blog announcement links on other platforms: Twitter Reddit r/Ripple Reddit r/CryptoCurrency Reddit r/CryptoMarkets Reddit r/xrp Reddit r/RippleTalk Reddit r/alternativecoin Reddit r/CoilCommunity Bitcointalk - alt coin sub forum Bitcointalk - XRP speculation thread

I've recently updated my rippled build to v1.2.1. I cannot seem to get my validator to run on the main chain. Any ideas as to why this may be?

I am new to rippled and am trying to learn what the difference is between a stock rippled node and a validating node. As I've read, a Stock server follows the network with a local copy of the ledger whereas a Validating server participates in consensus (and does everything a stock server does, too). I am currently running an instance of rippled and have run a performance profiler on the node, first on the non-validating node and then again when the node is running as a validator. Looking through the results, it seems that even when not running as a validator, the server makes calls to functions associated with consensus (ripple::RCLConsensus::Adaptor::doAccept, ripple::RCLConsensus::Adaptor::buildLCL, etc.) If a stock server is not supposed to be participating in consensus, why would there be calls to these functions? Could anyone explain to me why this is?

I decided to setup an own Ripple validator in order to contribute to the XRP Ledger & enhance decentralization. So my newly setup Ripple Validator has been running for one week. I’d like to say many thanks Wietse Wind for his docker images and his articles that made my life easier and helped me a lot setting up my validator. If you want to setup as well follow Wietse’s instructions: https://medium.com/@WietseWind/how-to-run-a-ripple-validator-digitalocean-7e5fca1c3d77 https://medium.com/@WietseWind/verify-your-ripple-validator-show-your-domain-da19de30b19b Wietse : “After running this last command, the tool will finish with the body of the e-mail you can now send to Ripple. Ripple will check the contents of you e-mail. If everything is OK (at this point is’s hard to imagine why it wouldn’t be OK) they will reply within (probably) a few days your validator is verified. It will now show your domain in green at the Validator Registry.” Unfortunately my validator still not verified. Do you have any experience how many days do we need to have a verified validator? Thanks

I am trying to understand the difference between stock rippled servers, validators, and client-applications when it comes to signing. When looking through the documentation in dev portal, it states that Cryptographic key pairs are always tied to a specific signing algorithm. Further, one can specifically choose the key type when using the wallet_propose method to choose which cryptographic signing algorithm to use to derive the keys (secp256k1 or ed25519). However, when running a rippled server or validator, is there such an option when creating key pairs? What signing algorithm is used when sending ledgers and ledger proposals when running as a rippled server or a validator?

https://www.insightiitb.org/ripple-in-the-works

Hi All, How long does a Rippled validator check process take usually? I sent my request to Ripple in June, but it is still unverified and I didn't get any email what the issue is (if there is any) ? Regards, Pal

Curious how many people on the forum are running their own validator and the reasons why others are not. This forum is a great source of info for getting started and ongoing upkeep. The network needs trusted validators and I'm sure theres one or two here that can help!

Hello, today first time i hear about Validator its like mining ripple? if i will be Validator how much i will receive xrp ? do we have calculator for this? Thanks Alaa

I decided to contribute to the decentralization cause and started up a validator. You can find it here: https://xrpcharts.ripple.com/#/validators/ listed under validator1.ripplexrp.network Or direct link here: https://xrpcharts.ripple.com/#/validators/nHDNyfMFoQBPFurZo1CMaNiGR22uFWEGH8xSsrEY3ePAecEttS82 I'm considering starting up a few more (7 more regions available at my hosting provider), but wanted to know if that is even worth it. Is there value to multiple validators being in control of one individual? or is that contrary to decentralization?

Hey Guys, It's been an exciting few days for me as I dig into ripple! Loving the adventure so far. Anyway, I had an unused dedicated blade server in a locked cage at a secure data facility and I figured that I would have a go at setting up and configuring a validator server. It was actually relatively easy and took more time to harden the actual the server/SSH settings than it did to configure ripple and a validator. Anyway, it's been running for around 5 days now without a hiccup and is givving good results with almost no disagreement, It just goes to show how well this software all runs! Cheers!

I am trying to send a payment using ripple-lib, and I am getting this error: Here is my code: Thanks so much!

Hello folks, I was wondering how Ripple runs its applications. Do we have people in here who take care about application deployment and infrastructure administration? Some devops or SREs? I am thinking about doing a showcase of running a Ripple validator in Kubernetes. Would that make sense to you? I am curious what you are thinking. All the best, Tim.

Hi Folks, I would like to setup a validating node on AWS, just wondering what instance size you're using? For non validating, an Amazon EC2's m3.large is said to be sufficient. Cheers.

I have a cluster setup between a public facing stock server and a validating server on a private network. When starting rippled I see this on the validator: LedgerConsensus:NFO Entering consensus process, watching, synced=no 2017-Dec-30 22:45:54 LedgerConsensus:NFO Consensus mode change before=observing, after=observing 2017-Dec-30 22:45:54 NetworkOPs:DBG Initiating consensus engine 2017-Dec-30 22:45:56 Server:NFO Opened 'port_rpc_admin_local' (ip=127.0.0.1:5005, admin IPs:127.0.0.1, http) 2017-Dec-30 22:45:56 Server:NFO Opened 'port_peer' (ip=0.0.0.0:51235, peer) 2017-Dec-30 22:45:56 Server:NFO Opened 'port_ws_admin_local' (ip=127.0.0.1:6006, admin IPs:127.0.0.1, ws) 2017-Dec-30 22:45:58 LedgerConsensus:WRN View of consensus changed during open status=open, mode=observing Is there a configuration that would cause "observing mode". I have tried recreating my validator token without success. Traffic is flowing well between the servers across 51235. Thanks RJ

I remember @nikb was saying on twitter that validator tutorial is almost ready to be shared. Has it been finalized yet? @iLeeT you were interested too i believe... Any news..? Mods, pls feel free to move the topic if needed. Merry Christmas!

Which validator is faster, Ripple or Stellar? This is the only thing I've found. https://galactictalk.org/d/279-effectively-run-your-stellar-validator-node-performance-tips https://xrpcharts.ripple.com/#/validators

hi - i looked on xrpchat but couldnt see any post about setting up a mac rippled server and im having trouble setting it up on a mac. fyi - ive gone through an old mac walk-thru, but that didnt work out, so thought i would ask you lot - is mac a non-runner? thanks for the info!

Hello everyone, We downsized some servers, which provided us with extra resources to spin up a second rippled node. Thus, our validator now lives behind a non-validating node. Clustering seems to have gone well, the validator is only connected to one peer (our other node), and both nodes show that they are in a cluster. I do have some questions, though: 1. How does the trusted UNL function on a non-validating node? Do both nodes need to trust the same validators? 2. Our validator says that it is 'proposing' and I can see it on the network topology page, however, it is no longer showing up in the validator registry. I was also able to send a test transaction through the validator, and it showed up on the public ledger. Any ideas on why the validator is no longer showing up in the registry? 3. We are using the same five keys in the trusted validator (UNL) list for both nodes, the validator quorum is 5 and the non-validating node's is 3. How come the validator's quorum is higher than the non-validating node? Thank you all so much for your help & support

Can someone explain why the Ripple XRP "Validatory Registry" https://xrpcharts.ripple.com/#/validators has not been upgraded since the 17th August 2017. It is now the 4th Oct 2017.