Jump to content

Guest1

Silver Member
  • Content Count

    723
  • Joined

  • Last visited

  • Days Won

    3

Guest1 last won the day on October 29 2018

Guest1 had the most liked content!

3 Followers

About Guest1

  • Rank
    Advanced

Recent Profile Visitors

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

  1. I'm taking it from the point of view that Deposit Auth means exactly those two words in plain English. As you say, I'll try it out to see if it works. I have no doubt it will.
  2. I would like to only receive payments, orders, trust line creation from specified XRP addresses and no other XRP addresses. Is this possible? For example, there may be certain malicious XRP addresses associated with hacking and a legal entity may not want to be associated in any way. However, if a transaction is initiated form such a malicious XRP address, the transaction will be shown in the destination address and the Tx permanently printed on the XRPL.
  3. Perhaps I've misunderstood how seq numbers work. If you could kindly look at the below and see where I'm going wrong, that would be much appreciated. Here is a hypothetical situation with two central locations firing transaction requests for my XRP account to two different rippled servers: *lets assume my XRP account already has a sequence number 125 prior to the following events. Location A -> Requests the last account sequence number for my XRP account from rippled Server A -> Server A returns value 125 -> transaction X is created by Location A wi
  4. So what would be the best way to fire multiple transaction requests from say 10 transactions per second from each of say 10 different servers (100 transactions per second across 10 servers) all from the same XRP address, while somehow keeping track of the sequence number across all the transaction requests so that none of them return a "tefPAST_SEQ"? Would all the transactions first need to be channeled to a central message queuing server of sort (Redis? Kafka?) where a counter variable is used to keep track of the sequence number and increment by one for each of the rapidly incoming tran
  5. Hey @Julian_Williams, the website address has been changed quite a while ago to: http://www.xrpcalculator.com/ Enjoy!
  6. Convolutional Neural Network (CNN) at its very best. Ideally:
  7. I know that some form of a hidden ledger theory was previously known to the community and many people told me it was debunked. I have an alternative theory and it would be appreciated if you @BobWay could have a read and let me know if it makes sense or if it's not possible/feasible. ------------------------------------------------------------------------------------------------------------------------------------------------------ How Ripple can create (or possibly already have created) a hidden ledger, and subsequently turn the switch on to redirect the volume to the public ledger.
  8. - XRP + Cobalt is the only way in the foreseeable future that can settle 6,300 trades per second for five continuous hours. - Hence we are waiting for Cobalt (+ regulation) for XRP adoption at mass-scale - If payments are recorded on the digital ledgers in real-time but settlements do not happen real-time, this potentially creates a backlog of settlements and a havoc in the making. Hence R3, DTCC they need Ripple + XRP + Cobalt.
  9. I have the following javascript code to obtain wallet XRP balance. I would like to filter this balance by only 1 destination tag so that I get the wallet balance just for that specific destination tag. Does anyone know how to do this in javascript by modifying the code below? ------------------------------------ const RippleAPI = require('ripple-lib').RippleAPI; const api = new RippleAPI({ server: 'wss://s.altnet.rippletest.net:51233' }); const myAddress1 = <XRP wallet address>; api.connect().then(() => { console.log('getting acc
  10. Just a small correction: XRP "wallet" will be unobtainable by most (assuming minimum threshold of 20 XRP does not change)
  11. Just need to remember that potential of XRP drastically increases once the news hits the public that trillions will be bridged (moved) via XRP, potentially in the order of double digits to triple digits XRP price. Such a model helps to assess in your XRP selling strategy. If you know the potential is e.g. triple digits, it may be possible you wouldn't sell 100% of your stack when XRP is $3 for example as in the back of your mind you have taken into the possibility of XRP price reaching such a potential in the future.
  12. Take a simple case: Daily transaction volume = 100 trillion Circulating supply = 50 billion XRP Average number of times a single XRP is traded in a day = 5 Price of XRP is roughly 100 trillion / (50 x 5 billion) = $400 per XRP I don't care whether the subtleties of this estimate is incorrect or not. In this case all I need to know is that a reasonable range for the price of XRP would be in the order of hundreds if trillions of dollars are transacted in XRP
  13. Yes, Ripple is engaging with SWIFT, ACI, the IMF, World Bank, etc to get trillions per day transacted in XRP. Whether their model is a well-educated guess or not, we can certainly deduce that they are thinking of the price of XRP in the order of thousands when all this plays out in their favour. This is why David Schwartz said "don't miss the next Ethereum". And you are right. We should be asking ourselves "what can we take away from such a model despite it not bring a perfect representation of reality?"
  14. and I haven't received your response to this. If you think someone else's model is crap, then create your own model and bring it here. End of discussion until then.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.