Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Cobalt

    XRP - The Standard (Big read)

    This is slightly more updated: https://theblockchainland.com/2018/08/31/countries-with-their-own-digital-currencies/
  2. Cobalt

    XRP - The Standard (Big read)

    The primary role of XRP has always been to facilitate flow and movement of value across channels that connect both symmetrical and asymmetrical ledgers. Any sustainable rise in value of the individual unit would eventually have to come from utility rooted in its primary role, not otherwise. Speculative pressures have an impact on its price currently because the rails of adoption are still being laid.
  3. Cobalt

    XRP - The Standard (Big read)

    This link would provide a good summary (albeit superficially) of the current situation internationally: https://cointelegraph.com/news/state-issued-digital-currencies-the-countries-which-adopted-rejected-or-researched-the-concept
  4. You're most welcome! It's great that your host is running fine now. Regarding the pod uploads, there are times when they can fail intermittently if the specified/selected host is experiencing issues such as network congestion. I believe the Codius team is working on refining the fault-recovery mechanisms e.g. retries, time-out, etc. You might also wish to view the logs of the Codius CLI to find out the exact issues causing the uploads to fail.
  5. You might wish to run "systemctl restart codiusd && journalctl -f -u codiusd" to view the error messages as they are generated during the self-test. They should be able to help you identify the issues with your host setup. Do talk to @mikkelhviid as well to explore the possibility of developing something on Codius together.
  6. One of the ways would be to look at your list of peers e.g. codius.domain.com/peers and start from there. Are you using the Codius CLI to do the upload? https://github.com/codius/codius
  7. Cobalt

    XRP and TAX

    These links point to the Australian Taxation Office's stance on cryptocurrencies so the information contained within the pages should be pretty conclusive. Tax treatment of cryptocurrencies https://www.ato.gov.au/General/Gen/Tax-treatment-of-crypto-currencies-in-Australia---specifically-bitcoin/ Record keeping https://www.ato.gov.au/General/Gen/Tax-treatment-of-crypto-currencies-in-Australia---specifically-bitcoin/?anchor=Recordkeeping#Recordkeeping Additional information https://www.ato.gov.au/General/Gen/Tax-treatment-of-crypto-currencies-in-Australia---specifically-bitcoin/?anchor=Additionalinformation#Additionalinformation
  8. It looks like you are using btp2.mlab.company. They had an issue with their balance a few days ago and it should be fine now.
  9. Which ILP connector are you using? This error message stands out: "Insufficient reserve to complete requested operation." As you mentioned you have 100 XRP in your XRPL account configured for this, the error message likely refers to the ILP connector's balance being insufficient.
  10. Cobalt

    urgent!!!!!! NEED HELP.

    Yes, this is provided your HDD was not damaged by the drop.
  11. All payments made to hosts occur on the XRPL. This means that should the need arise, it would be possible to have an audit trail that leads to the creator/uploader of the smart contracts. Additionally, at present smart contracts run as hyperd pods on the host server and their images can be archived for reference/examination if need be. From a legal perspective, it won't be a major effort to incorporate disclaimers into the Codius CLI (which is currently the only means to upload a pod to the hosts) that provide a certain degree of blanket protection to host operators.
  12. The important part of verification is knowing the identity of the party running the validator. Wietse is active and prominent within the XRP community so it is likely that the verification team knows him. If you put yourself in the shoes of the verification team, how would you go about verifying the identity of a party running a validator besides the domain name WHOIS records as a base for follow-up?
  13. From: https://developers.ripple.com/install-rippled.html -------------------- Minimum System Requirements A rippled server should run comfortably on commodity hardware, to make it inexpensive to participate in the network. At present, we recommend the following mimimum requirements: Operating System: Production: CentOS or RedHat Enterprise Linux (latest release) or Ubuntu (16.04+) supported Development: Mac OS X, Windows (64-bit), or most Linux distributions CPU: 64-bit x86_64, 2+ cores Disk: Minimum 50GB SSD recommended (1000 IOPS, more is better) for the database partition RAM: Testing: 8GB+ Production: 32 GB Amazon EC2's m3.large VM size may be appropriate depending on your workload. A fast network connection is preferable. Any increase in a server's client-handling load increases resources needs. -------------------- Based on my own experience, the biggest factors would be more of storage access times (SSD vs SSHD vs HDD) and network bandwidth. Currently there are around 23,000+ validations per day and it was only after an upgrade to SSD (from HDD) that my validator was able to keep up with the validation count. The network bandwidth consumption is also rather high, measured in GBs per day.
  14. From the link that you provided: Registry Registrant ID: Not Available From Registry Registrant Name: Registration Private Registrant Organization: Domains By Proxy, LLC Registrant Street: DomainsByProxy.com Registrant Street: 14455 N. Hayden Road Registrant City: Scottsdale Registrant State/Province: Arizona Registrant Postal Code: 85260 Registrant Country: US Registrant Phone: +1.4806242599 Registrant Phone Ext: Registrant Fax: +1.4806242598 Registrant Fax Ext: Registrant Email: It seems that you had opted to keep your information private while registering the domain name (that's good practice as an individual but not appropriate for a corporate domain name). Based on this, it would not be possible to know your identity from your domain name's WHOIS records. I believe the verification team at Ripple would not be comfortable verifying a domain name that has its registrant (and other contacts) details kept private and that, in my opinion, is the key reason for your validator's domain name remaining unverified.
  15. In my case, it was verified within a day. You just have to make sure that you are not using any anonymiser in your domain name's WHOIS records.