Jump to content

Professor Hantzen

Bronze Member
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Professor Hantzen

  1. Maybe I'm reaching beyond the limits of my knowledge. As I understand it - if you start with 128-bits, then for all practical purposes, all you have at the end - in terms of your security - are those same 128-bits? In other words, as a user of the system, is there any necessity to make a discernment between the seed and the key? And if so, why introduce a new term to describe what's effectively the same thing? (I could understand why for development, but this is user-facing.)
  2. I think this is a great idea for the benefit of the future masses - at least if it's optional, mitigating the disadvantage to those used to the "s..." version. I am curious how you've implemented the check digit in your mechanism? The common schemes I know of didn't work when I did them in my head (but maybe that's because of my head...). I use the term "secret" to refer only to the base58-encoded, "s"-prefixed and checksummed version of the "seed", which I think of as just an ordinary number with no prefix or checksum. I have wondered why the well-established "private key" was not the term used to refer to what I understand is just the private part of a public/private key-pair.
  3. Great that you've done this. I don't know much (anything) about Ruby, but in general when implementing such things, watch out for how the system might fallback on some other source of randomness in the case the intended source isn't available. This could result in something less than secure and as such may be important to understand how differing systems running the same code can serve different (but still "valid") results. On from there, for the secret_seed --> secret_human_readable part, there's a roughly-parallel node.js implementation, here.
  4. Yes, that's another side of this. I mean to suggest that the metric of on-exchange XRP versus off-exchange - when taken alone - is not necessarily indicative of anything, unless paired with other figures backing up whatever claim is being made.
  5. XRP being moved to exchanges is an interesting metric to check, but it could be a predictor of selling action as much as be representative of supply purchases. It might be useful to connect this information with flow from known XRP II accounts to more feasibly determine the latter, but even then: Given the low trading volumes on the XRP Ledger presently, what you're looking at could be also seen as indicative of how much XRP the market wants to hold on exchanges versus in "cold storage". In that sense, an argument could be made that its a stronger positive signal in terms of price to see the on-exchange number *decrease*. If more want to hold XRP in cold storage on the XRP Ledger, it means more don't want to sell their XRP, so buying it becomes more difficult (ie, more expensive).
  6. This looks like mainly a charting bug/data API bug. The historical data API is known to be buggy, but this has nothing to do with the integrity of the data on the XRP Ledger itself. When I checked more directly the amount of actual ledger closes for the past 24 hours, versus a control of a 24 hours period about one month ago - they were about the same. I also checked the past 2.5 hours versus a 2.5 hour period a month ago, same again. What I am noticing is a variation in the pattern in which ledgers are closing. The network appears to close a handful of ledgers every second or so, and then hang around 8-9 seconds before closing another one, then return to roughly once per second, and so on. It looks like the average close time is overall within normal expected frequency, but perhaps the chart backend is not averaging it usefully due to this behaviour. The endpoint of the chart may be too dependent on a small number of immediately previous ledger closes or something like that. No idea if the network assumes such a pattern regularly and that's considered ordinary or not, but I've certainly seen variance before (though usually at times of high load which that doesn't appear to be the case at the moment).
  7. Given the amount of caveats and the lengths I needed to take to describe them, I somewhat agree with the negative assessments. Though I still find it interesting that the Top 100 by this metric shows 90% of all of the ex and current Ripple employees that I am aware have ever used the board. That they reliably cluster together at the very top when ordering by RPP makes me disagree that it's useless. Moving the cut-off point to a higher reputation (~700, arrived at by limiting to the first ten pages of results), the list is still populated with many ex and current Ripple employees. In that case, there are three within the top 5, two more within the top 15, and no others within the top 100. The four excluded by the shift in cut-off point all only posted for a short period of time before disappearing, so it would appear to work better at a higher setting in that regard. It's also populated more thoroughly with names even I recognise (I'm not a particularly frequent contributor), so maybe it does indeed show more useful results at a higher cut-off to remove a greater amount of noise/outliers. I may redo it. @vsyc RPP dilutes Reputation by weighting it against Posts, so at base its an improvement over Reputation alone. It penalises high-volume, low-medium-response posters in favour of low-medium-volume, high-response posters. (Also, I must note you have a negative RPP... ) Thanks for the kind words @Tinyaccount!
  8. When reading through the forum, I often unconsciously divide a members Reputation by their Posts in my head, to get a feeling for how their contributions are percieved by other members. A higher ratio of Reactions Per Posts ("RPP" ;) ) shows that more people may be willing to demonstrate they value those members contributions. I find it interesting, but also useful. I might not read a long post by a member I don't recognise if they have a terribly low ratio, for instance. Perhaps others do something like this too? Recently, when @BobWay joined, I noticed that his RPP climbed very (x)rapidly up to being much higher than what I'm used to seeing on a regular basis. It reminded me of something I've wanted to do for a while - scrape the member data from the site, and make a chart to see where all members sit by this metric. With a few caveats (one briefly on the chart itself, more in detail below), here it is: Caveats (this list may not be exhaustive...!): 1) One limiting factor with this chart is with how people digest and respond to information when all eyes are upon them. For many people, truths can be uncomfortable, difficult or even completely unwelcome - and even when they do agree or value an insight, they don't always want to "own up to it". I like to think people are pretty open-minded and flexible here, but I've still seen this pretty normal human behaviour from time to time, as anyone would reasonably expect. So, while I believe this chart give some useful indication of something, it is not prone to including those who may regularly say things other people aren't willing to show they agree with, even though they may agree, or even though those things may be true, important and valuable. There's probably nothing that can be done about that, except to note that if there's a member missing you expected to find on here - well, you may have a good point. 2) The chart does not use a complete set of members who have Reputation. If it did, it wouldn't be very useful as it would likely be filled with outliers who made one post, received a handful of votes and never returned. And their inclusion would be at the expense of significantly more established members who might be hard to see among them or even drop off the chart entirely. Partly as a fix, and partly because I didn't have time nor inclination to click "Next" 200 times, I picked range of reputation to include and culled the rest below it. The solution is perhaps equal parts reasonable and unreasonable, given that the point at where some members are included versus excluded is essentially arbitrary. Members on the boundary could theoretically be one reaction away from topping the chart in at #1, or disappearing entirely. Nevertheless, a compromise simply had to be made. If anyone has a suggestion about how to better go about it - I'm all ears. 3) As I understand it, the "Reputation" score on the forum counts any "reaction" of any kind (and hopefully I've got that right...!). In theory, someone could game their way to the top of such a chart by posting only tremendously sad and confusing things. In practice I doubt someone would be able to gain much traction with their posts - more likely they would be ignored - so I think the metric stands a pretty good chance of being at least vaguely indicative of how members posts are perceived. (Also, in my anecdotal and unscientific experience, I see the positively-connotated Like, Thanks and Laugh buttons clicked much more often, in that order. The negative Sad and Confused buttons seem to be used at the low ends of the bell curve.) What gives me some hope that this metric is valuable in spite of these caveats, is that the resultant Top 100 is populated with almost all of the current and former Ripple Employees on the forum that I am aware of, and all of them within the top third of the chart. That was pretty cool to see! Anyway, see what you think, and if this is valuable/useful maybe I can do it again in a month or so.
  9. Well, what's your reward for asking the question? My take on summarising the answers already given: 1) It's interesting, fun and/or feels good. There is no comparable, sufficiently-utilised open ledger in existence that doesn't also destroy the environment. That's cool! 2) Running a node gets you fast and reliable access to the ledger and information on it. This can also *save* you money if you regularly query the ledger, as you can locally query stored data as much as you want without cost. If you are relying on others servers, you may be paying high fees in data every month to satisfy your queries, and have to wait on that data to be transmitted each time, possibly redundantly. It can also save you money if you trade on the decentralised exchange, and need to submit those trades fast and reliably. 3) It's very cheap to do. But this minimal costs gets you the benefits of both 1) and 2). It's not necessarily cheap to run a full-history node, but this comes with significantly stronger versions of the above benefits, which is obviously worth it to some. The only reason the Internet now exists, is because thousands of people all over the world did exactly the same thing when it was in its infancy. That's how the internet was first created. By people voluntarily connecting their computers together, at their own cost, and with no real immediate benefit other than that they thought it was cool and interesting. Many see a similar process playing out now, with the "Internet of Value" in its infancy, of which they view technologies such as the XRP Ledger as a potentially integral part. There are many people now I'm sure who would have loved to have been part of the early Internet, even if they made no money out of it - just to be able to say they were there and took part in it. However, huge businesses and even entire new industries were launched on the back of such open and giving voluntary participation. Billionaires, and trillion-dollar economies were created out of nothing, and in that case the focus wasn't even financial. So, here we have a similar thing playing out again, and this time the focus is specifically around finance and money. I'm sure you can do the math on that.
  10. Fair amount of stuff archived here if you hunt around the various dates: https://web.archive.org/web/20150422094949/https://wiki.ripple.com/Main_Page
  11. Hah, so the most valuable art in the world might be the Nazca lines - huge, and ugly. I kind of agree regarding market cap, and I was not entirely non-serious to suggest doing away with this popular valuation scheme could be healthy for crypto in terms of price. I went into this in another thread. (One thing I didn't get into deeply there is the reliance on wash-trading current market cap values have.) TL;DR: I don't necessarily see a ceiling for any crypto price, but I do think if we multiply price by supply and get a value orders of magnitude greater than all the wealth in the world, it's unlikely it's going to get up there. The reason being that the major market participants (who set price), are performing and likely will always perform similar calculations themselves as a matter of course before making decisions. I think it will take a major shift in current popular perception, for that ceiling to break. I love this argument. Thanks!
  12. Haven't watched the video, but I'm not sure I can see Chris Larsen's net-worth reaching $51.9 trillion dollars (without a serious devaluing of the USD perhaps!). The richest people in the world hover around 1/500th of that. When proposing optimistic predictions for crypto prices, it can be useful to take this into consideration. If you do, you'll see that if XRP got into the $10,000 - $15,000 range its market cap would likely eclipse the total value of every form of money, property, businesses, net-worth of individuals, derivatives, all the worlds stocks - every form of all kinds of value the world over - combined. Then again, I tend to think market cap is completely screwed as a metric. So, given that - why not? Bring on the $10K XRP! But before we do that, maybe we need to figure out a more accurate way to measure crypto's value.
  13. This is fantastic. Thank you. Something to be aware of, when xRapid users calculate cost-savings, they may - as an understandable, but still disagreeable matter of course - include the "cost" of exchange rate volatility over the time period of a regular payment. Measured in days this can be a significant risk, and in retrospect it can look very bad - especially if the FX market concerned is consistently appreciating in your favour over time (say over a quarter) but you're locking in a "bad rate" at the beginning of a several day wait period for all your transactions during that quarter. In most situations, the payment provider is not going to pass on significant savings (or profit) in this regard to the user - as it may be part of their profit model. You're typically getting either a bad rate, or a really bad one. As such, despite that in principle the risk should go both ways, it could be considered to be mainly a downside risk of payments that are anything longer than instant. On the other hand, because successful xRapid transactions are effectively instant, this kind of "cost" becomes an irrelevant factor, and so can be counted in xRapid's favour that this risk is eliminated. However - and this is the important bit - the locked-in rate with xRapid is always going to be the initial rate anyway, so in most situations this aspect of "risk" is effectively identical as for a regular payment that takes days. In principle, it's possibly a similar argument to "lost" sales versus piracy - the argument that because you didn't get something you likely couldn't have got anyway, you've suffered a loss (or in this case, a gain). I've wondered if we need to watch out for this kind of claim of "savings" regarding xRapid, so it's very nice to see that this probably *wasn't* the case for Mercury FX's claim. It looks much like they are just reporting the real, actualised cost saving transparently, and it's significant. That's great to see, especially considering how undeveloped/low-liquidity these markets are at this stage.
  14. I almost can't believe they wouldn't hire you, to me you'd be one of the prime hires of the community. You're certainly one of the most knowledgable. I've learned a huge amount from your posts. Especially valuable is that you often intelligently challenge the choices Ripple makes. I can only conclude the right person isn't aware you could be interested - or that the "right person" somehow isn't aware of your regular (daily?) contributions to the community and the repo over the past 6 years.
  15. Banks are XRP "bagholders", and they're tied into restrictive resale-agreements as well. They've purchased a quarter *billion*-worth so far among them - that we know about - directly from Ripple. They must believe XRP it has value, and will appreciate, or they wouldn't buy it, and especially not under such resale restrictions. Now the question for the rest of the XRP "bagholders", do you follow investment advice from an obviously-biased, anonymous, self-described "troll" on the internet? Or do you think for yourself, and possibly consider XRP's positives that hundreds of banks & FI's have also been "thinking" about, to the tune of millions of investment dollars each?
  16. Hah! But then, I'm not sure any of us could watch Reinhart interviewing Ripple employees & clients and for two and a half million minutes...
  17. The article I believe you're referring to cherry-picked a few companies to attack on grounds such as they had a bad website, their product was in beta, or that they had (in the authors opinion) talked up their co-located office (when in my opinion, many modern digital companies co-locate). The author even complained that because the Director was also the Secretary, the company must be a scam. I believe a more appropriate word for such a company might be "small" (or another, more positive word could be "lean"...). From this handful of complaints, the author concluded - without investigating any more - that Ripple's entire complement of 200+ companies must suffer from identical complaints and so are therefore all "scams". As such, the list of verifiable "scams" include such luminaries as SBI (one of Japans largest banking conglomerates, whose CEO's Twitter regularly tweets positive remarks regarding Ripple and XRP), Santander (who have based one of their active, customer-facing products on Ripples technology) and various other top 100 banks or FI's. I guess it would include R3 too. Realising everyone can have a bad day, I looked at a couple of the authors other articles. As a result, I am unlikely to read articles from that source again, nor post links to them or even quote them. However, one useful point may have been raised - with Ripple signing so many companies, there will inevitably come a time or two that they are inadvertently scammed themselves, and sign a relationship with a company in good faith - but the company itself was presenting an elaborate artifice to Ripple to benefit from the association. Maybe this has already happened, and maybe even the author of that article could have found such a one? But presenting any such information in such a ludicrously sensationalist and possibly libellous manner is inexcusable. Any responsible individual should contact Ripple and present any evidence of a scam directly to them.
  18. That's all fine, however I would go with @Tinyaccount's suggestion to use QR for transmitting the signed txn rather than a flash drive. As soon as a flash drive that's touched one computer touches the "air-gapped" one, you should consider it compromised. Also, in my view "secure enough" doesn't exist, unfortunately. If you're ultra-paranoid or expect nation-state level intrusion, keep in mind that "air-gapped" also doesn't necessarily exist. All computers emit various electromagnetic energy and there's little you can do about it save for building a faraday cage large enough to hold the computer and yourself, and only powering it on and off whilst inside (using a battery and inverter...). There are various ways and means for a determined attacker to get information remotely from a machine that's never been connected to anything. It's best not to display the secret on the screen of an airgapped machine for this reason as reading the screen from radio-frequency emissions (yes, LCD) may be possible if an attacker can get close enough to the source and depending on the source. Blasting white noise from the location of the computer may help mitigate some attacks. I'm not sure of the merits of adding two additional transactions to each withdrawal by changing the RegularKey each time, versus using the same RegularKey, maybe someone has an opinion on that they could share? One drawback I can see of having/using many keys is that you could end up losing control of the account by administrative error. You didn't mention the most important consideration - how are you storing whatever secret needs to be stored? Is it on the airgapped machine? As such, is the air gapped machine encrypted? And if so, how and where are you storing the password/key used to decrypt it, as that's now essentially become your "secret"? Various levels of obfuscation can be good for storing secrets. Disguise your air-gapped machine as a defunct one in a pile of other decaying computers for instance, and remove its hard drive (use a model where this is easy, or boot from flash) and place that in another location - ideally inside something else, sealed, that makes it unrecognisable as a hard drive / flash drive. If you elect to write down your secret, encode it using some method you personally can easily figure out that makes it unrecognisable as one to anyone else (drop the "s" and change the letters to numbers for instance, using a key system only you know and can remember in your head), and then label it something else, or split it into two things. Eg, "Ducati (France) Serial #" & "Old Mac CAD Program Serial #" on differently aged pieces of paper, with dashes every 5 numbers on one, and put it these with all your other genuine serial numbers in a safe. Also consider having a routine around these processes that looks like you are doing something else. Be as crafty as you like, and turn "remembering the password/secret" into "remembering how to unmask the password/secret from its disguise without anyone realising that's what you're doing". Also, one major caveat, node, linux etc are prone to logging - make sure you know how to disable those you can, or where they are kept and how to definitively erase them (which is also kind of impossible unless you're happy to rewrite over your entire drive 27 times with random characters, and do the same to the backup drive you used to store the contents of the drive whilst erasing the other one...). You could consider Tor's operating system. Another level of obfuscation is to make the air-gapped machine appear to be where your secret is entirely stored, when in fact you are booting from a flash drive you insert surreptitiously and it actually contains half of the secret, with the other half on the air-gapped machine. Aside from all that, really the best thing to do is to simply not have any singular control over your accounts - as no matter what you do, it's a single point of failure. Multi-sign with various other parties, and split the holdings into many smaller parcels with different configurations of entities as co-signers. It's essentially the same thing the wealthy have been doing with traditional holdings for aeons (via trusts, with law firms as co-signers etc).
  19. Just because a holder is under "selling restrictions", doesn't necessarily mean they are bound or will abide by them. This persons methodology also doesn't account for what would happen if those "restricted" funds were hacked. If $6 billion was shaved off the market cap, and then the biggest hack of all time dumped all those "sales-restricted" XRP back into the circulating supply again would the market cap have to be changed again? What the hacker came out afterward and said "don't worry, I'm not going to sell any, I just don't want to, ever!" - would they be taken out of "circulation" again based on trust on the hackers intentions - because that's essentially the authors reasoning in the first case? Further, I don't see any such arguments being made for the various similar cases that exist for virtually all other crypto. Satoshi's BTC have never moved - why are they included? Doesn't seem like they're in "circulation". Does Vitalik intend to dump all his ETH? Probably not, should we ask him how much he intends to sell and when, before re-computing Ethers market cap? How often should we ask? Personally I think 100B minus burned is the true "in circulating" supply, but given the escrowed amounts are on-ledger, and as such, bound by the rules that define XRP itself, I'm comfortable with circulating excluding perpetually-escrowed amounts. Anything beyond that is a pretty hard "sell" to me. All that said, anything that reduces the market cap also reduces the "glass-ceiling" the market cap imposes on most peoples perception of potential value. If it was to drop by $6 billion, I think many would just see it as a buying opportunity and it would shoot back up to where it was again... most crypto investors don't appear to understand market cap, what it represents, what (little) it's useful for and why we have it. It's become a game of "win the race", and endless garbage headlines claiming "$20 billion was added/removed to/from the markets today!". No, it wasn't. You need to look at the much lower trade volumes figure to determine that, and you need to remove an unhealthily large section of those trades for a variety of reasons to get anywhere near what was actually added or removed; likely a small fraction.
  20. Ripple's public servers have been running 24/7 with high reliability since 2013. To me the warning in theory is a disclaimer that lets them shut them down if they're costing too much to maintain or if maintaining them becomes counterproductive to the network somehow (though I can't think of how...). In practice so far it's just given them an excuse if they fail to scale fast enough to meet load, as happened during the bull-run of late 2017. Even so, they *did* work actively to scale the servers to meet load at that time, in some cases appearing to work somewhat around the clock to do so. At present, and for the foreseeable future, it would appear to be in Ripple's interests to keep these operating, and operating well - a great many XRP Ledger participants seem to use them. I'd be fairly confident using them unless you are planning to inundate the network with millions of requests in which case you should consider setting up your own private instance (which isn't particularly difficult or necessarily expensive - unless you need to host full history). As far as I'm aware, the only other completely public node you could consider "trustable" is, as others have mentioned - XRPTipBot's one. Bear in mind that using any server you don't operate also opens you up to that servers security or lack-thereof, regardless of the good intentions of the operator. Ripple have a good incentive, enough cash and expertise to ensure the security of theirs to "enterprise" level - if not also its persistence.
  21. This is extremely unlikely / effectively impossible for a variety of reasons. Firstly, institutional sales by Ripple of XRP are subject to sales restrictions - that is, for an institution to do what you're describing, they'd have to violate the terms of their contract with Ripple. Secondly, it would be considered direct market manipulation and therefore illegal. Banks/FI don't do illegal. Banks do highly unethical and questionable, but only when fully regulated to do so. There is not sufficient regulation in the crypto space to afford them such a luxury at the moment, and the sense we've got is they are on tenderhooks just buying the stuff. (Of course banks and FI's manipulate markets constantly, but they do it through "legitimate" use of endlessly recursive derivatives, subsidiaries, black box trading and regulations sprawling enough to have loopholes to exploit - crypto has none of those pieces of the puzzle in place, yet.) Thirdly, if they did this, Ripple would immediately notice - because of the transparent nature of the XRP Ledger, Ripple will know exactly how much every bank does and should have in its accounts. Fourthly, it's not in anyones vested interests to increase the volatility of XRP - if banks were doing it on purpose, Ripple (and other purchasers - there are 200 of them) would be compelled to have them cease immediately - and given that to me its likely that part of the security practice involved in these sales will involve multi-signing large movements (where Ripple may indeed be a cosigner) it's possible Ripple could even physically prevent them doing so. Fifthly (hmm, haven't used that word before - does it even exist?), there are armies of community members studying the XRP Ledger and exchange activity - this kind of manipulation, coming directly from XRP II linked accounts (all of which are known) would stand out massively and be all over this forum and everywhere else.
  22. We don't have figures for dollar value XRP purchases by institutions prior to Q4 2016, however, we can probably assume its fairly negligible to the whole picture (if you multiply the below 2016 figures x4 for instance it doesn't make a lot of difference). Relying on the figures we certainly have, we can see the following has been invested by banks/FI in XRP year over year: 2016: $4.6m 2017: $67.4m 2018: $171.7m Doesn't look too bad. That's $243.7m financial institutions the world over have invested in XRP specifically. A quarter billion dollars? I don't think there is any other crypto currency that can make even remotely a claim such as that. Interesting too, to look back and see this as a percentage of (coinmarketcap's) current "market cap" for XRP: 2016: 0.04% 2017: 0.55% 2018: 1.85% Banks/FI's have been buying up more and more of what's out there, and we know they have stringent sales restrictions when they buy. Assuming no subsequent sales, and conversely, assuming no on-market buys, almost 2% of all XRP supply, or 1 out of every 50 in the wild, may be currently owned by a bank or financial institution. That's kinda cool. Looking quarterly: 2016 Q4: 4.6m 2017 Q1: 6.7m 2017 Q2: 21m 2017 Q3: 19.6m 2017 Q4: 20.1m 2018 Q1: 16.6m 2018 Q2: 16.9m 2018 Q3: 98.0m 2018 Q4: 40.2m What I find interesting about this is what I perceive as possibly 6 months latency on banks/FI's en masse reacting to the bull run of 2017 EOY. Sales were down for the first two quarters of 2018, and only picked up (significantly) in Q3. Another way to look at it is we can't necessarily draw too much useful information from what the market's doing versus institutional sales - they may not have much in common, or if they do, there may be significant and unknown delays involved, undermining usefulness. Another way to look at the last quarter is that its the second highest quarter XRP's had in terms of institutional sales, and almost twice the size of third place. To me its too early to draw a conclusion regarding the drop in Q4. It could be an ordinary fluctuation - eg, if we had 5 years worth of figures would we always see a drop in Q4? (Even something as simple as holidays?) But on the whole, I think the report was pretty low-standard. Not in terms of numbers, but in terms of style and content. I looked forward to Miguel Vias' lucid market insights into the crypto space, his play-by-play recaps of pivotal moments from the quarter, and the many charts - some of which would have taken some effort to prepare. This Q4 2018 report is much lighter, low on content, and doesn't even bear his name. It's a shame, but perhaps it indicates he's been busy doing more important things, which I guess could be a positive.
  23. You can, but to best protect your funds, you shouldn't submit your secret to a remote server (such as s1.ripple.com). I took "not for sustained or business use" to mean "we reserve the right to shut this down if it gets too expensive for us to maintain". I don't think it's likely in the near future. They kept all of their public servers running and expanded their capabilities during the late-2017 bull run when activity and usage was much higher than it is now. You can use the XRP Ledger without third party tools, in which case you either need to create your own tools, or use those supplied by Ripple. At this stage that means either running rippled, or using the Ripple API (which has a confusing name, XRP Ledger Javascript API might be better). Either of these can be used to sign your transactions locally before submitting them to the network over websocket to Ripple's public servers. If you don't want to operate a rippled node and don't want to use Ripple API, you can run rippled in a completely offline mode (stand-alone mode), and only use it to sign your transactions, which you can then submit to Ripple's public servers over websocket. You would likely start with some JSON describing your transaction, and end up with a tx_blob of hex digits that has been "signed" by your secret, but does not actually contain your secret in any usable form - all on a local, offline machine. You can then send a simpler JSON command directly to the public server containing only this signed tx_blob. If you ever find yourself about to send your secret of a network anywhere (even Ripple's servers), you should stop as you're doing it wrong.
  24. Just had a look at that external markets endpoint. The data it returns appears to be excluding various pairs and exchanges in a manner I can't determine - and unfortunately the data api in general has been a bit unreliable in my experience. You could probably get complete data using coinapi, I know they have a lot of history, and I did verify they are reporting largely accurate data down to the sub-second, versus what I historically captured myself (on at least the one exchange I checked). They have a free tier but it's limited to 100 requests per day (not clear what the size limit is on those requests), the OHCLV historical is probably what you'd need, and according to this page https://www.coinapi.io/integration they have data available on XRP going back to November 2013 across 256 exchanges (@ peak). It also looks like they can supply compiled CSV volume data on demand, using their sister site https://www.cryptotick.com. It costs, but for data in larger time-frames it seemed reasonable. Looking forward to your next update, you're providing some of the best insights into Ripple's XRP activities I've seen anywhere. Loving it! Be interesting to see how your analysis matches up with the Q4 report.
  • Create New...