Jump to content

jlr

Member
  • Content Count

    81
  • Joined

  • Last visited

2 Followers

About jlr

  • Rank
    Regular

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Nice catch, you are right, the SWIFT column should be blue, since it contains (If I am right) 500 squares and 1 blue square == 10b$ takes 500*10b$ == 5t$. The same true in case of nostro/vostro.
  2. They must be targeting the big whales who want to save money and time while transferring funds across the world.
  3. Yes, it is a really good news. More good news from ripple site about XRP https://ripple.com/insights/ripplenet-surpasses-200-customers-worldwide/ More xRapid partners JNFX, SendFriend, Transpaygo, FTCS and Euro Exim Bank. From the artice : “In 2018, nearly 100 financial institutions joined RippleNet, and we’re now signing two—sometimes three—new customers per week. We also saw a 350 percent increase last year in customers sending live payments, and we’re beginning to see more customers flip the switch and leverage XRP for on-demand liquidity,” said Brad Garlinghouse, CEO of Ripple.
  4. Indeed, rL4fPHi2FWGwRGRQSH7gBcxkuo2b9NTjKK is an interesting account
  5. In short term you are right. WS made a tons of money from Lehman Brothets as well. When the time will come BTC will be thrown away. BTC cannot be used as a payment system in large scale. Totally useless, energy wasting token. It was only a good PoC and helped people to realize the importance of BC technology. No more no less. XRP the standard.
  6. Why do you need Secret Key through insecure connection? (That account has been generated just for example.)
  7. Special thanks @nikb who pointed out what the problem is with my validator settings. Ripple couldn't retrieve my SSL certificate because it was not able to connect to https://validator.agota11.com/ So it was a configuration failure because my certificate only could be accessed on 51235 validator's p2p port. Now it is working fine. Thanks again. https://xrpcharts.ripple.com/#/validators/nHUNmdXFFPWGqNoMg4XQ5W4rANtk98oHjCGkkqDWmhw7ZgpXAgP6 @Mediguy, @FreedomGundam could you please check the config of your own validators? You might have the same/similar problem with domain validation process.
  8. Hi @nikb, Thanks for looking into this. I have just sent a PM for you (nikb@ripple.com), resubmitted info about my domain info. I also happy that you are improving verification process.
  9. root@jlr:~# docker exec rippledvalidator /opt/ripple/bin/rippled server_info -q | grep pubkey_validator "pubkey_validator" : "nHUNmdXFFPWGqNoMg4XQ5W4rANtk98oHjCGkkqDWmhw7ZgpXAgP6", root@jlr:~# root@jlr:~# root@jlr:~# root@jlr:~# echo nHUNmdXFFPWGqNoMg4XQ5W4rANtk98oHjCGkkqDWmhw7ZgpXAgP6|openssl dgst -sha256 -hex -sign /keystore/validator.agota11.com-privkey.pem (stdin)= 5421b0e1d1645115ad7f66b37cca6ebae93683803ffb458d88d2825ed04ceb93b24f476addc5d657be74234efcb3bf86348e7a3212d5524769ff718e81b265f48ed67c85615f81b1b01c9c0f4864b66410317bbaa438bdca660afe64d1d5f90b24853df48e487d48f8403873bafe4f9a80bb6114db78b8ac8ee4891c51dd18d00f4f84a1875118cacbd18347696c6827f3cfec7691ccb02967649361272507ae9ac03140375fdf1591afb260699c7453be59082bbd8f3fe677d442ad32b5d68c3f44ddf8b360df4d88e7d2234db2ead5a9badbd581b18e7c847608035ba8660b91a63b6f42507acc1a6b8cecb21143a21b18d962dcf348c9e21bd90a32b5cf02 root@jlr:~# root@jlr:~# root@jlr:~# root@jlr:~# docker exec rippledvalidator /opt/ripple/bin/validator-keys --keyfile /keystore/validator-keys.json sign validator.agota11.com D7128828EA47E2BF21853307E8D6603B96E6941DE4106FE303002C9A0A4AF0B2034357F0A86AB8FBC46CA20A9D3D8609872ECEF7D1A4869C24989B763C889E09 Hi @Sukrim, Thanks for looking into this. Above you can find the information (except my email address) what I sent to Ripple and you can see how I retrieved information. https://developers.ripple.com/run-rippled-as-a-validator.html#domain-verification Thanks in advance.
  10. I am not planning to give up running validator. But it would be great if domain verification process was more transparent. No wonder why many people spreading FUD info about XRP ledger. And let me repeat myself this is only the objective domain validation step by step process. It is not about who trust me.
  11. @Mediguy I have the same experience... Do we need bigger publicity to gain any progress? Or what should we do? I am disappointed a little bit. Are there others who are in the same boat on this forum?
  12. Thanks @Sukrim https://developers.ripple.com/run-rippled-as-a-validator.html#domain-verification """ Network participants are unlikely to trust validators without knowing who is operating them. To address this concern, validator operators can associate their validator with a web domain that they control. """ I'd only like to have verified domain no more no less and the verification process seems for me pretty objective. (I am going through on four well-defined steps and I'll become verified shortly.) AFAIK this process independent who is in Ripple recommended list. Currently becoming member in Ripple's recommended validators list is not my goal. Later yes, but now I'd be satisfied with having own verified domain.
  13. @Mediguy No progress here. I wrote email 15 days ago to XRPLedger support I got a reply message that my request was forwarded to @nikb. It looks like I am in infinity loop. I don't think it would be Nik's responsibility to deal with my domain verification, but would be good to know what I should do more to have verified domain. My good quality validator (https://xrpcharts.ripple.com/#/validators/nHUNmdXFFPWGqNoMg4XQ5W4rANtk98oHjCGkkqDWmhw7ZgpXAgP6) has been working for two months with proper setup and I don't know where domain validation process got stuck. I strongly believe XRP Ledger technology and projects which run on XRP Ledger that's why I would like to run validator in order to help community. The irony of fate I had a bet with group of XRPLedger skeptics that anyone can run verified validator in the XRP network...
  14. I also started a thread exactly one month ago. Still waiting for domain validation. It seems everything is OK on my side. (I have recently updated my validator to 1.1.0 as well ) Certificate is also seems to be OK: https://www.sslshopper.com/ssl-checker.html#hostname=validator.agota11.com:51235 At this point I have no idea what to do... Now I am going to write an email to support@ripple.com I might get more info what's up with my verification process.
×
×
  • Create New...