Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 02/22/2017 in all areas

  1. 2 points
    JoelKatz

    The "200" limit

    That's correct. If they point their client to their own server, they can set the default and the limit to whatever values they want. If the client doesn't specify a limit and lets you configure what server you point it to, you can point it to your own server and change the default to be much higher. The reason this is more complicated than retrieving anything else is that the funding status of an offer is dependent on the offers ahead of it in the book. As the server produces the response to the query, it keeps tabs of the effect of previous offers on account's funding status. To "pick up where it left off" it would need to recover that context. Or the whole design would have to change such that the client keeps track of the funding status of offers.
  2. 1 point
    rippledigital

    IOTA discussion

    Just wanted to alert people to some really interesting tech, IOTA, which many of you already know about. I'd like to keep up with what's happening over there so I thought this could be a thread we can add related articles too. I think it's a potential rival to Ripple in some ways, in other ways not so. I find the project really fascinating with great ambitions and scope, and some amazing people on the team. NOTE: I do not own any IOTA tokens, but I would like to; currently seems a bit complicated to get some as it's still in early production. Here's the best intro bits I could find: http://www.iotatoken.com More info: https://medium.com/@DavidSonstebo/iota-97592581f985#.w5vy7hut4 Here is there last "year in review" type blog: https://medium.com/iotatangle/iota-year-in-review-year-in-preview-6de510696e02#.xcj0gajio Some quotes from various sources I found particularly interesting (bold mine): I also asked around on the Slack channel about speed / confirmation time of transactions. I was told the more people use it the faster it potentially goes, and eventually a large-scale network effect means transactions settle in "seconds". So it possibly rivals Ripple/Stellar for speed too, once it's deployed properly. For me it's further interesting because they've got Gideon Samid from BitMint onboard. My "hunch" right now is (and correct me with a cane if I'm off) that IOTA is going to be another testbed for BitMint's idea of tethered (fiat) digital money, or they're working together closely to co-produce something pretty big. So presumably there's a way to issue any token on the IOTA network (tangle), like Ripple issuances, and/or, the network can be forked and changed to accommodate central banks / mints / banks who issue or govern the issuance of fiat currencies. Very interesting if so! Would love to hear you guys' thoughts... RipDig
  3. 1 point
    RafOlP

    Desktop Wallet 1.4.1

    Hi all, We just uploaded a new version of the wallet (1.4.1), you can download it here. We: - fixed a bug in the history tab - Added a simple chart to trade/advanced tab - Added labels to gateways and updated gateways and addresses - Fixed the icon in the windows version - Created windows installers Translation thread: Unfortunately there are more bugs than expected in the localization process so it will take a while to get it right. Any help from the community is welcome. The project is opensource, please collaborate https://github.com/rippex/ripple-client-desktop Cold Wallets: Regular Keys
  4. 1 point
    mDuo13

    Gatehub/PBG XAU IOU

    This is a good point. And, I think, this situation is what the Trust Line Quality feature was meant to address. Unfortunately, Trust Line Quality is hard to use. For now, the simple recommendations I have are: - Don't trade XAU.Gatehub and XAU from another (ISO-compliant) gateway using the same address - If you do trade XAU.Gatehub and XAU from another gateway using the same address, be absolutely sure that NoRipple is enabled on all your XAU trust lines.
  5. 1 point
    Haraldo

    Transferwise + Facebook

    As the man himself said "2017 will mark a sea change in XRP's use and adoption", if the dawn is really coming and if it will be brilliant this or something very similar to it can't be too far off. H
  6. 1 point
    Twarden

    RippleD WSS Issues

    If you choose to configure the latter, I suggest looking at https://www.openswan.org/
  7. 1 point
    MundoXRP

    Don't fear R3 and CBDC is here?

    Tim Swanson from R3 dropped a blog today were he explores the problems with lightning network type solutions for settlement titled "Layer 2 and Settlement". He also talks about R3's current project where they are working with two central banks to bring Central Bank Digital Currency to DLT. It's hard not to speculate that ripple is involved since they have written extensively about MAS, advised the Bank of Canada, and have participated in a large R3 trial.
  8. 1 point
    Awesome script @jn_r! The date parameter makes it really easy to track account changes over time. Thanks for posting!
  9. 1 point
    MundoXRP

    Transferwise + Facebook

    So transferwise uses earthport, and earthport uses ripple. Even if no visible connection can be seen today, it's a much smaller bridge to cross at a later date. Not to mention all the other remittance companies that earthport services today can potentially also be part of the ripple family one day: Japan Post Bank, Transferwise, Xoom, CurrencyFaire, Stripe, Azimo, Worldremit, AftabCurrency, etc... http://www.earthport.com/why-earthport/clients/
  10. 1 point
    JoelKatz

    The "200" limit

    We actually could use the new(ish) coroutine code to raise the limit. The tricky bit would be that we would need to stream the results to the client as the coroutine was running. We've built all the support for this but never used all of its pieces together in one thing before. The coroutine code is used to enable old-style path find (ripple_path_find) to use the same code as the new-style path finding. But in that case, we don't need to stream out the output. I like the idea of a "light" book_offers request. It could even summarize the order book into levels, showing in full detail only the placer's own offers.
  11. 1 point
    Professor Hantzen

    The "200" limit

    How about a flag on the book_offers request (say "limit: -1"), that requests the server to dynamically set a temporary limit as high it is able in excess of it's own maximum, based on load? So, the server would endeavour to send the whole book in one hit, but the client knows the amount of offers returned may fall short of the total, yet can rely on receiving at least the servers usual maximum. Would an optional "light" book_offers request be possible? The main reason clients request the book is to place trades against it. To do this, clients require only two numbers per offer: the quality, and the funded amount of taker_gets. In most cases the other material rippled supplies is of no use. The issuer and currency for each offer is redundant for example, as it doesn't change and is known prior to sending the request. A light request could reduce book_offers bandwidth by around 95% (~800bytes vs ~40bytes per offer).
  12. 1 point
    Malloy

    Desktop Wallet 1.4.1

    Two different market even though they have the same name. BTC.Bitstamp/XRP in the Ripple network (like you see with ripplecharts) is not the same as when you trade directly from your bitstamp account on their website online wallet... I have put many orders with USD.Bitstamp/XRP in my bitstamp online account and they never show on the ripplecharts network.
  13. 1 point
    cmbartley

    Don't fear R3 and CBDC is here?

    MIT on CBDBs: http://dci.mit.edu/ http://dci.mit.edu/assets/papers/15.998_central.pdf
  14. 1 point
    KarmaCoverage

    Don't fear R3 and CBDC is here?

    That sounds similar to a post I made here. In short I dont see any issue with the Fed running it's own RCL (or other ledger) and stacking a few ledger/networks on top of each other with varying permission sets and tweaked for specific use case needs. The international RCL ledger/network can play it's specific role, and ILP can connect the various layers of ledger/networks. What if final settlement in "real USD" occurred within a ledger like the last sentence... "This would keep the Fed's core ledger where the "real USD" is issued, insulated by 2 layers for all international & domestic payments."
  15. 1 point
    mulder

    Newbie in XRP and CRYPTOcurrency.

    or ripple XRP change the Name to FED Fedcoin but it looks like the ripple community lemmings are only daydreamer but it is a 50:50 chance like a casino ... good luck
  16. 1 point
    Morty

    Chatline of the day

  17. 1 point
    cmbartley

    Chatline of the day

    Ripple is not a disappointment, it's a shining star in this space. The price of XRP has been a disappointment. We'll see if that changes.
  18. 1 point
    Professor Hantzen

    The "200" limit

    The underlying rippled API request that is used to retrieve RCL orderbooks you see in any app or service has a parameter called "limit" which limits the amount of offers the rippled server will include in the response to the request. It's there to ensure the server being queried doesn't have to send any more data than is necessary (orderbook data on RCL is hard on bandwidth). Presumably whatever service or app you're using has set that limit to 200. This is actually quite high. In my experience at least, the public rippled servers run by Ripple for example, won't send more than 300 offers for any given book. Kraken and Polo won't help you here. They don't show offers from the Ripple network. They have their own, separate orderbooks formed of offers placed within their proprietary exchange platforms only. Confusingly, Bitstamp also does this on their platform, and yet has a separate set of orderbooks for their USD and BTC IOU's on RCL.
  19. 1 point
  20. 1 point
    For tax purposes and to get a quick overview of my accounts and to get to learn the promisses stuff in nodejs I once created the following script. It makes use of the data-api to be able to also get historical data. You can use it as follows (if you name the script 'totals'): totals [date=<dd-mm-yyyy>] [time=<hh:mm:ss>] [account=<account_list>]
  21. 1 point
    Professor Hantzen

    no liquidity exists

    When bitstamp launched XRP/USD trading, the volume and liquidity from the correspondent bitstamp IOU on RCL moved on-exchange. I'm not sure why though. Do you have a use-case for requiring liquidity on RCL, or are you using the metric as a barometer of XRP/Ripple's success?
  22. 1 point
    ripplerm

    ripple wallet

    Update v1.2.2 * show server fee on navbar. * auto-update trustlines balances and info. * support ripple-name and federation protocol like Ripple Trade.
  23. 1 point
    Twarden

    TickSize Will Be Available in 7 Days

    Ticksize amendment is a feature for Gateways to choose which significant digits to round to for TakerPays and TakerGets to be calculated on offer preference. Gateway Operators can set this value from 3 to 15 significant digits. https://ripple.com/build/transactions/#offer-preference
  24. 1 point
    miguel

    Will the SEC Approve a Bitcoin ETF?

    An ETF would be wonderful, but XRP's markets have to grow in order for something like that to be viable. We'll get there but it's unlikely to be this year.
  25. 1 point
    ripplerm

    ripple wallet

    https://ripplerm.github.io/ripple-wallet/ Latest Update: support different format of secret (seed or private-key): Base58 (ripple, or bitcoin) RFC1751 Hex an Account Generating Tool generate new account from either seed / passphrase, or account's direct private-key. index input for generating multiple accounts from single seed/secret. generating child account. (mimic bitcoin HD-wallet, BIP-0032) Refurbished trading page. show graph of Market Depth. show balances of holdings. price and volume can be auto-filled when click on balances or an offer. show QR-code for signed raw-transaction (make it easier for transfering signed-txn from cold-wallet):
×