Kraken - Gateway/Issuer Address?

[Guest]

Does anyone know why Kraken does appear in the https://charts.ripple.com data for payments, but does NOT seem to have a 'gateway address'?

I am using the Tools API to examine the network data: https://data.ripple.com/v2/gateways

Any thoughts on this would be useful.

Maybe Kraken is using someone's else address acquired through an acquisition?

--

I am using JSON formatter:

http://pro.jsonlint.com/

Edited December 31, 2016 by Guest
omitted information

[Professor Hantzen]

Kraken isn't a gateway (unfortunately...).  They don't issue IOU's on the Ripple network, they just allow you to buy & sell XRP on their own proprietary exchange.  I don't believe they are listed under "Payments", but under "All Exchanges"?  This figure is an estimate of XRP trading taking place outside of the Ripple network (with a breakdown per exchange).

[Malloy]

https://bithomp.com/explorer/rLHzPsX6oXkzU2qL12kHCH8G8cnZv1rBJh

[Malloy]

Poloniex if you need it too https://bithomp.com/explorer/rDCgaaSBAWYfsxUYhCk1n26Na7x8PQGmkq

Interesting to compare both holdings... Polo's got 535M XRP and Kraken 323M.

[Guest]

Hi Prof/Malloy,

Both comments are helpful. Prof Hantzen, given the address that Malloy provides 'rLHzPsX6oXkzU2qL12kHCH8G8cnZv1rBJh'... what is the address? The Bithomp machine resolves this to Kraken stuff, but I have not found here the address is located within the Ripple network.

--

I had not been aware of Bithomp... very interesting beginning. What do you think it will become? Is it just experimental?

I am just beginning to think about how I might query the Ripple network data. I/we are working on an iOS/Android app coupled with an Agent in MS Azure, that retrieves information from the major global exchanges. It is modeled loosely after the Bloomberg app. The purpose is experimental from a price data and 'news' perspective. The focus now is on:

- price / volume data (near real-time)

- news (RSS, Twitter, Google Search, Bing Search for specific websites which do not support RSS

- strategic information such as, legislation, regulations, events, and exchange specific information

- video

 

We are mostly interested in establishing an agent(s) based cloud service that can analyze crypto-currency network transactions. Today, the agents gather price-data from about fifty (5) exchanges globally in between 5-10 seconds depending on details... and news information. Once, we have it running properly (2017 Q2), we are thinking of adding peer-to-peer functionality. ILP-Kit may be useful, in this regard.

With regard to the platform... we have Azure nodes in Toronto, Amsterdam and Singapore. The SuperNode is in Toronto. Additional, nodes can be rolled out easily from updates to the SuperNode. We rather prefer the Ripple Network for peer-to-peer transactions as they will resolve quickly.

 

Thanks to each of you!

[Professor Hantzen]

12 hours ago, Max Entropy said:

Both comments are helpful. Prof Hantzen, given the address that Malloy provides 'rLHzPsX6oXkzU2qL12kHCH8G8cnZv1rBJh'... what is the address?

No Problem.  That address is the one kraken uses to receive and send XRP into their exchange.  You'll note it holds no IOU's - just XRP. If you have an account on Kraken you use for trading, and you want to sell XRP on Kraken, you send your XRP to that address, along with a Destination Tag (specified in your Ripple transaction) that identifies that XRP amount with your kraken account.  For sending from Kraken you need only specify a Ripple address which you control.

This is distinct from Bitstamp's issuer address for example (rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B), which operates as a full gateway - that address holds many IOU's and you are able to trade those on the Ripple network.  Unfortunately, as useful as bithomp is, it doesn't always tell you when it's not telling you something... in this case I think the amount of IOU's for bitstamp maxes out bithomp somehow (or at least it did on my machine), you can try going to charts.ripple.com and click on "Accounts Explorer" and put the bitstamp address in to see the IOU's issued there if bithomp doesn't work for you.

Edited December 31, 2016 by Professor Hantzen
typo

[Warbler]

@Professor Hantzen Right, we don't show balances if account has more than 200 connections.. otherwise it's can take to long for large gateways...

Agree about showing the message. Any suggestions for that message?

https://bithomp.com/explorer/bitstamp

shows now:

"Rest of balances are hidden (too many of them to show)."

If you have any other suggestions, we are always happy to improve our service

Happy New Year.

[Professor Hantzen]

1 hour ago, Warbler said:

@Professor Hantzen Right, we don't show balances if account has more than 200 connections.. otherwise it's can take to long for large gateways...

Agree about showing the message. Any suggestions for that message?

https://bithomp.com/explorer/bitstamp

shows now:

"Rest of balances are hidden (too many of them to show)."

If you have any other suggestions, we are always happy to improve our service

Happy New Year.

That's great!  Thank you - I will definitely let you know any other suggestions.  I love bithomp - I regularly use it for research and exploring accounts.  I especially like how it's possible to traverse accounts back to their origins, and the other way too - seeing activations.  It's a great way to look at the dataset!

In the case of an issuer with many connection - would it be possible to show the first 200 balances, and then the "too many" message?  Also adding the amount of balances not shown would be useful, if that's easy to do and doesn't require traversing paginated results (or you're back to the same problem I guess...).  I know from experience that paginated results can be a bit of a pain,  the Ripple data API can be a bit buggy.

[Warbler]

16 hours ago, Professor Hantzen said:

That's great!  Thank you - I will definitely let you know any other suggestions.  I love bithomp - I regularly use it for research and exploring accounts.  I especially like how it's possible to traverse accounts back to their origins, and the other way too - seeing activations.  It's a great way to look at the dataset!

In the case of an issuer with many connection - would it be possible to show the first 200 balances, and then the "too many" message?  Also adding the amount of balances not shown would be useful, if that's easy to do and doesn't require traversing paginated results (or you're back to the same problem I guess...).  I know from experience that paginated results can be a bit of a pain,  the Ripple data API can be a bit buggy.

Happy to know, you like our tool.

We don't show first 200 balances, because all summary balances would be calculated wrong in that case (not all of the balances included)

As a solution we can make a special view for gateways (without summery balance calculation by currency) for first 200/400 balances...

We can't show amount of hidden balances, unless we download all balances first.. so it's easier to show all balances, rather than to show amount of non shown balances.

Thinking to make a button "show all balances" (in case when account has more than 200 balances)

Though that request may time out. For large issuers, there can be several tens of thousands of results...

(so, even that solution still can end up as: "Rest of balances are hidden (too many of them to show)." )

I guess, we can find a better way for that, but we just don't prioritize it now...

Added a bit extra info in the "Information" part:

https://bithomp.com/explorer/gatehub

Receiving XRP: not allowed (shows only if accounts doesn't accept XRP)

Destination tag: required (shows only if account requires a destination tag for incoming transfers)