Jump to content

Search the Community

Showing results for tags 'validator'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • XRP
    • Please Read Before Posting
    • Press
    • General Discussion
    • Technical Discussion
    • Codius and Smart Contracts
    • Marketplace
    • Problem Solving
  • Interledger Protocol
    • Interledger Protocol Discussion
  • Other Technology
    • Alt-Coins and General Fintech
  • More
    • Fan Submissions
    • Off-Topic
    • Meta
    • Languages
  • Canadian Zerpers's Topics
  • Vegemite Ripplers's Topics
  • 2 the Moon! For Real. The Club's Topics
  • NY Zerpers - aka bitlicense island's Topics
  • Brackish Waters Club's Topics
  • Trading Places's Topics
  • Anti-Club Club's Topics
  • The Irish Brigade's Topics
  • Saloon's Request
  • XRP Trading And Price Speculation's Topics
  • The Crypto Buffett's Topics
  • Alt-Coin Trading And Price Speculation's Topics
  • Super serious Ripple club's Topics
  • Making Millions!'s Topics
  • Ripple - India's Topics
  • SWELL's Topics
  • Gospel Hour's Topics
  • Korean XRP Holders's Topics
  • Strayans lovin your work XRP!!!'s Topics
  • Technical Analysis (TA) Area's Topics
  • BTC diving deep club's Topics
  • Ripple Enamel Pin Club's Topics
  • XRP Wave Surfers's Topics
  • FUDster's retreat's Topics
  • Cooking with Snoopy's Topics
  • How it's all going to happen..'s Topics
  • Chocolate Fish's Topics
  • The Round Table's Topics
  • UK Hodlers's Topics
  • ˜”*°• Zerpmania •°*”˜'s Topics
  • XRP YouTube Videos's Topics
  • CRY ROOM's Topics
  • Night's Watch's Topics
  • CasinoCoin's Topics
  • XRP Think Tank's Topics
  • Allvor's Topics
  • NightClub's Topics
  • TeXRP's Topics
  • COIL Think Tank's Topics
  • Bob's Book Club's Topics
  • XRP FAQS's XRP Q an A’s

Calendars

  • Ripple Events
  • Vegemite Ripplers's Events
  • NY Zerpers - aka bitlicense island's Events
  • Brackish Waters Club's Events
  • Trading Places's Events
  • Anti-Club Club's Events
  • The Irish Brigade's Events
  • Saloon's Calendar
  • XRP Trading And Price Speculation's Events
  • The Crypto Buffett's Calendar
  • Alt-Coin Trading And Price Speculation's Events
  • Super serious Ripple club's Events
  • Making Millions!'s Events
  • Ripple - India's Events
  • SWELL's Events
  • Gospel Hour's Events
  • Korean XRP Holders's Events
  • Strayans lovin your work XRP!!!'s Events
  • Technical Analysis (TA) Area's Events
  • BTC diving deep club's Events
  • Ripple Enamel Pin Club's Events
  • XRP Wave Surfers's Events
  • FUDster's retreat's Events
  • Cooking with Snoopy's Events
  • Chocolate Fish's Events
  • The Round Table's Events
  • UK Hodlers's Events
  • XRP YouTube Videos's Events
  • CRY ROOM's Events
  • XRP Think Tank's Events
  • Allvor's Events
  • NightClub's Events
  • TeXRP's Events
  • COIL Think Tank's Events
  • Bob's Book Club's Calendar

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Interests


Location


Occupation


Country


Ripple Address


Biography


Location


Interests


Occupation

Found 30 results
Minimum search term is 4 characters long. Can't find what you want? Click here for the custom google search instead.

  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
  2. 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?
  3. 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.
  4. 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?
  5. 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
  6. 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?
  7. 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
  8. 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!
  9. 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
  10. 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?
  11. 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!
  12. I am trying to send a payment using ripple-lib, and I am getting this error: Here is my code: Thanks so much!
  13. 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.
  14. 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.
  15. 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
  16. 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!
  17. 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
  18. 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!
  19. 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
  20. 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.
  21. https://medium.com/@haydentiff/xrp-is-a-cryptocurrency-like-the-uss-zumwalt-is-a-boat-3b25be5226b8 I woke up to a new blog entry from our @TiffanyHayden ! Nice way to start out the morning.... Personal note: I had to look up the USS Zumwalt too, so don't feel bad! Here is her blog announcement on twitter yesterday:
  22. I've noticed a deterioration of validator agreement over the past two days as volume has surged. Agreement now tops out at around 93% when it used to routinely be around 99% for stable validators. Along with this reduced agreement I've noticed that ledger close times are also longer, sometimes up to 25sec suggesting the network may be halting periodically or at least slowing. Any ideas where this disagreement is coming from? EDIT: strange, I've just noticed that the date on the Ripple validator page is for last Thursday August the 17th... so the number above are likely inaccurate.
  23. I am wondering about the implications of opening port 51235 on a rippled validator or node (running in front of a validator). I assume doing so would carry a risk of DDoS attacks, however, it also provides other nodes with access to the ledger. In other words, it seems like there is a minor security risk and a reasonable benefit for the community. From what I understand, rippled nodes will connect to any peer to get the ledger. Is this so, or do they only connect to trusted peers? Finally, is there any reason to include my IP in the [ips] section on my ripple.txt, if port 51235 is closed? Thanks so much!
  24. This is my latest blog entry; I discuss the scalability issues with Bitcoin and Ethereum - focusing in on block size and scalability in general. Feel free to leave positive or negative feedback here, and please feel welcome to share or link to my blog as much as you like! My blog announcements on other media: Reddit Twitter Bitcointalk
×
×
  • Create New...