Ripple(XRP)


  • admins


    Ripple is the global leader on distributed financial technology. The team developed and supports adoption of the Ripple protocol, a technology that enables the free and instant exchange of value. The San Francisco-based startup is funded by Google Ventures, IDG Capital Partners, the venture arms of CME Group and global data storage company Seagate Technology, Jerry Yang’s AME Cloud Ventures, ChinaRock Capital Management, China Growth Capital, Wicklow Capital, Andreessen Horowitz, Core Innovation Capital, FF Angel, Lightspeed Venture Partners, Bitcoin Opportunity Corp., Pantera Capital, and Vast Ventures.

    Website:

    https://ripple.com

    Blockchain

    https://www.ripplecharts.com/#/graph/

    Forum

    https://forum.ripple.com/

    Wallets

    Web Client : https://ripple.com/client/

    Downloadable Client : http://download.ripple.com/

    Github : https://github.com/ripple/ripple-client

    Help : https://ripple.com/insights/ripple-labs-releases-d

    News:

    http://cointelegraph.com/tags/ripple

    Gateways

    http://www.ripplebusiness.org/

    https://therocktrading.com/

    https://dividendrippler.com/

    https://payroutes.com/#/login

    https://justcoin.com/

    https://wisepass.com/

    http://www.rebopay.com/

    https://www.weexchange.co/

    Exchanges:

    BTC:

    Bitcoin Indonesia - Justcoin - Bittrex - Kraken - BTC38 - Cryptsy - RippleGateways - Poloniex

    USD:

    The Rock Trading - RippleGateways

    Cryptsy

    CNY:

    Jubi - BTC38 - RippleGateways

    JPY:

    RippleGateways

    USDT:

    Poloniex

    EUR:

    RippleGateways - LiteBit.eu - The Rock Trading

    Social:

    https://twitter.com/Ripple

    https://www.facebook.com/RippleXrp/

    https://www.facebook.com/RippleLabs/

    More:

    http://www.xrpchat.com/links/



  • CME Group Executive Miguel Vias Joins Ripple



    Ripple is proud to announce another
    addition to our team: Miguel Vias, head of XRP markets. In his new role,
    Vias will utilize his considerable expertise building liquidity for new
    financial products by working with market makers, traders, investors
    and exchanges to strengthen the XRP markets and set the stage for
    large-scale institutional adoption.Global financial institutions are
    increasingly looking for solutions to consolidate the liquidity tied up
    with the nostro accounts required to fund their overseas payments.
    Digital assets allow for banks to fund their payments in real-time, and
    in the process, cut down their dependency on nostro accounts. A strong
    XRP reinforces these economics.Vias joins us from CME Group, where
    he was global head of precious metals and metal options at the largest
    precious metals desk in the world. Prior to the CME, Miguel honed his
    craft at the commodities desks of Morgan Stanley, Bank of America, and
    Mitsui. He brings nearly two decades of trading experience to our team. We talked with Vias about what brought him to Ripple, and what he’s most excited to do in his new position.


    What made you decide to get into fintech, or come to Ripple
    specifically? This is a little bit of a career change for you, so can we
    talk about what interests you about this position?


    My interest in fintech goes back to
    early 2012. While I was working in London, I’d begun to hear about
    bitcoin. A borderless currency without a central counterparty was
    theoretically appealing, but I had my doubts, especially given the
    complex systems bitcoin on its own was attempting to replace. Still, the blockchain and distributed
    financial technology could clearly solve some interesting problems. Two
    years after joining CME, I came across Ripple and XRP, and immediately
    knew I’d found something. Ripple and XRP removed most of the initial
    reservations I had around bitcoin, namely that there was an actual group
    of people focused solely on integrating into the financial system,
    instead of displacing it. Since I bought my first XRP two years
    ago, I’ve kept a close eye on everything Ripple- and XRP-related and
    have been impressed with the progress the company has made. From
    building the team, to the product, to the market infrastructure, it’s
    obviously the best blockchain-focused fintech startup in the world. So
    when I had the opportunity to become part of the team, there was no way I
    was going to pass it up.


    How does your experience in commodities translate to working with XRP?


    XRP is uniquely qualified as a
    liquidity solution, to help banks and corporates currently holding
    balances in nostro accounts all over the world to facilitate payments
    without trapping their cash. As a digital asset, it can reduce the
    amount of capital in float. As a bridge currency, it can enable
    liquidity concentration around fewer currency pairs, making cross-border
    payments more efficient.Looking at it through the lens of my
    experience, XRP’s commodity and foreign exchange characteristics
    (specifically its limited supply) makes it very similar to precious
    metals. The considerations around inventory and delivery that make
    trading a digital asset like XRP unique are also at the core of the
    commodities markets. As a result, my understanding of precious metals,
    especially when it comes to market structure, will be ever more helpful
    as we increase the access to, and liquidity of, XRP. Additionally, my experience in OTC
    markets and at an exchange will aid in charting a path toward wholesale
    XRP adoption. Similar to other digital assets, XRP exists in an
    interesting hybrid of OTC and exchange-traded markets. If we want to
    transform XRP into an institutionally viable currency, it’s crucial to
    understand how both those markets function individually, how they
    complement each other, and how we can leverage a deep understanding of
    both to further develop XRP.


    What about your new role is most exciting to you? What do you think the future of digital currency will look like?


    As I mentioned, I think the natural
    ethos of digital currencies actually limits their utility and thus
    general adoption. In order for any currency, digital or not, to achieve
    critical institutional adoption requires a team of people to manage its
    progress. As a thought experiment it might be comforting to think that
    open source adoption is possible, but the reality is much more
    complicated. That’s a lengthy prelude to what I
    find most exciting about the role, which is being primarily responsible
    for ensuring XRP achieves institutional adoption. The idea that I will
    be part of the team which will help grow the first institutionally
    useful digital currency is amazing. As for the future of digital
    currencies or distributed ledgers generally, I think we will continue to
    see usage increase in more institutional areas. The role XRP plays in reducing the
    capital needed to fund cross-border payment businesses is equally
    applicable to any cross-system or cross-asset transaction. Beyond the
    foundational use case of payments, digital assets will lower collateral
    requirements across the whole of the capital markets, for example, with
    securities settlement, derivatives markets, and repo lending. A digital asset may well be included
    in baskets of world reserve currencies in the years to come. It will
    take some time, and a ton of effort, but I have no doubt in the very
    near future we will live in a world where much of our existence will
    revolve around digital currencies and distributed ledger technologies.


    With regards to XRP, what can we look forward to in the future?


    We’re planning to launch a quarterly
    XRP update that will focus on the state of the market, XRP deal
    structures and sales targets. Most importantly, our intent is to make
    XRP more broadly accessible by listing it on additional exchanges. So,
    stay tuned! I can’t wait to get started.


    By,









  • rippled version 0.40.0 Released


    Ripple has released rippled version 0.40.0, which introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL). Ripple recommends that all server operators upgrade to version 0.40.0 by Tuesday, 2017-01-17, for service continuity.

    Highlights of this release include:

    • Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users to cryptographically escrow XRP on RCL with an expiration date. Ripple expects Suspended Payments to be enabled via an Amendment named “SusPay” on Tuesday, 2017-01-17. See below for details.

    Action Required

    If you operate a rippled server, then you should upgrade to version 0.40.0 by Tuesday, 2017-01-17, for service continuity.

    Impact of Not Upgrading

    If you operate a rippled server but don’t upgrade to version 0.40.0 by Tuesday, 2017-01-17, when SusPay is expected to be activated via Amendment, then your server will become amendment blocked, meaning that your server:

    • Cannot determine the validity of a ledger
    • Cannot submit or process transactions
    • Does not participate in the consensus process
    • Does not vote on future amendments
    • Could rely on potentially invalid data

    If the SusPay amendment is vetoed or does not pass via majority vote, then your server will not become amendment blocked.

    For instructions on updating rippled on supported platforms, see Updating rippled on supported platforms.

    The md5sum for the rpm is: 27d0d142f29bcde7d240d91d44b5d7dc

    The md5sum for the source rpm is: b3b5ab6897f3c08b492f383ef7763c21

    For other platforms, please compile version 0.40.0 from source.

    The first log entry should be the change setting the version:

          commit 7fc780dd70faef819eace27a12de35dd1363c069
          Author: Nik Bougalis <[email protected]>
          Date:   Tue Dec 20 09:20:17 2016 -0800
    
          Set version to 0.40.0
    

    Network Update

    The Ripple operations team plans to deploy version 0.40.0 to a subset
    of rippled servers under its operational control configured with the
    new websocket implementation, starting at 2:00 PM PDT on Tuesday,
    2016-12-20. The network will continue operating during deployment and no
    outage is expected.

    Learn, ask questions, and discuss

    Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.

    Other resources:

    Full Release Notes

    The rippled 0.40.0 release includes Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users cryptographically escrow XRP on RCL with an expiration date. Ripple expects Suspended Payments to be enabled via an Amendment named “SusPay” on Tuesday, 2017-01-17.

    You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.

    New and Updated Features

    Previously, Ripple announced the introduction of Payment Channels during the release of rippled version 0.33.0, which permit scalable, off-ledger checkpoints of high volume, low value payments flowing in a single direction. This was the first step in a multi-phase effort to make RCL more scalable and to support Interledger Protocol (ILP). Ripple expects Payment Channels to be enabled via an Amendment called PayChan on a future date to be determined.

    In the second phase towards making RCL more scalable and compatible with ILP, Ripple is introducing Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users to cryptographically escrow XRP on RCL with an expiration date. Ripple expects Suspended Payments to be enabled via an Amendment named “SusPay” on Tuesday, 2017-01-17.

    A Suspended Payment can be created, which deducts the funds from the sending account. It can then be either fulfilled or canceled. It can only be fulfilled if the fulfillment transaction makes it into a ledger with a CloseTime lower than the expiry date of the transaction. It can be canceled with a transaction that makes it into a ledger with a CloseTime greater than the expiry date of the transaction.

    In the third phase towards making RCL more scalable and compatible with ILP, Ripple plans to introduce additional library support for crypto-conditions, which are distributable event descriptions written in a standard format that describe how to recognize a fulfillment message without saying exactly what the fulfillment is. Fulfillments are cryptographically verifiable messages that prove an event occurred. If you transmit a fulfillment, then everyone who has the condition can agree that the condition has been met. Fulfillment requires the submission of a signature that matches the condition (message hash and public key). This format supports multiple algorithms, including different hash functions and cryptographic signing schemes. Crypto-conditions can be nested in multiple levels, with each level possibly having multiple signatures.

    Lastly, we do not have an update on the previously announced changes to the hash tree structure that rippled uses to represent a ledger, called SHAMapV2. This will require brief scheduled allowable downtime while the changes to the hash tree structure are propagated by the network. We will keep the community updated as we progress towards this date (TBA).

    Bug Fixes

    • Correct an issue in payment flow code that did not remove an unfunded offer (#1860)
    • Sign validator manifests with both ephemeral and master keys (#1865)
    • Correctly parse multi-buffer JSON messages (#1862)


  • Bitstamp Now Trading XRP

    Bitstamp, one of the world’s leading digital asset exchanges, today announced it will launch trading of XRP, the digital asset native to the Ripple Consensus Ledger. Specifically, XRP/EUR and XRP/USD trading pairs will be available for trading on Bitstamp’s exchange beginning January 17, 2017. They will be available to all customers and regions currently supported by Bitstamp, and payment processors can utilize this XRP liquidity to facilitate cross-border payments to and from Europe.

    Ripple is also pleased to announce that Bitstamp, the first and only digital asset exchange to be fully licensed to work in all 28 EU member states, is the first partner exchange for Ripple’s XRP incentive program. Designed to increase liquidity and tighten spreads, the incentive program will offer rebates and compensation to qualifying liquidity providers in XRP pairs at partner exchanges

    “The relationship with Bitstamp and launch of XRP volume incentives underscores our commitment to making XRP the institutional standard bearer for value transfer globally,” notes Miguel Vias, Head of XRP Markets at Ripple. “XRP is uniquely capable of introducing more liquidity to exchanges to support global payment volume, especially in exotic corridors. Ripple’s adoption with banks puts XRP in pole position to become a global settlement asset, which translates to more liquidity for Bitstamp, and more value for institutional and individual investors.”

    “After evaluating a number of digital currencies for inclusion on our exchange, it soon became clear that customer demand for XRP was particularly strong,” notes Nejc Kodrič, CEO at Bitstamp. “Fortunately, Ripple and XRP also happen to be a good fit for the requirements of our EU licence and so we are delighted to be able to respond to our customers’ needs in this way.”

    Working with a greater number of exchanges to list XRP is an important step to serve the growing demand for global payments in major and exotic currency corridors. XRP was created specifically for institutional settlement in seconds. As evidenced byR3’s recent trial with XRP for interbank cross-border payments, the use of Ripple and XRP can enable both cost-cutting and revenue opportunities for participating institutions.

    For digital asset exchanges interested in listing XRP or joining the XRP incentive program, please contact us.



  • rippled version  0.40.1 Released

    The rippled team has released version 0.40.1, which increases SQLite database limits in all rippled full-history servers. Ripple recommends upgrading to 0.40.1 only if server operators are running rippled servers with full-history of the ledger. There are no new or updated features in the 0.40.1 release.

    Action Recommended

    If you operate a rippled server and have full-history of the ledger, then you should upgrade to 0.40.1 immediately.

    Impact of Not Upgrading

    If you operate a rippled server and have full-history of the ledger, but don’t upgrade to version 0.40.1, then your server may crash when restarted.

    For instructions on updating rippled on supported platforms, see Updating compile version 0.40.1 from source.

    The first log entry should be the change setting the version:

    $ git log -1 upstream/master
    commit e91aacc9a3d2f332a93981270c3812e26189226e
    Author: Nik Bougalis <[email protected]>
    Date:   Thu Jan 5 09:38:28 2017 -0800
    Set version to 0.40.1
    

    Bug Fixes

    Increase SQLite database limits to prevent full-history servers from crashing when restarting. (#1961)

    Network Update

    The Ripple operations team has deployed version 0.40.1 to all full-history rippled servers under its operational control.

    Learn, ask questions, and discuss

    Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.

    Other resources:




  • Load Testing Data API

    By
    Rome Reginelli

    The Ripple Data team will be running load balancing tests on Ripple Data API starting Wednesday, 2017-01-18, at 2pm PST, which will last approximately 15 minutes. The Ripple Data API is an open and free resource that provides access to information about changes in the Ripple Consensus Ledger, including transaction history and processed analytical data.

    Action Recommended

    If you operate software or services that rely on the Ripple Data API, then we recommend that you alert end users with the relevant information provided in this post.

    Impact of Tests

    If you operate software or services that rely on the Ripple Data API, then you may experience a brief outage and / or inconsistent data, including transaction history and processed analytical data, for a period of approximately 15 mins.

    For more information regarding the Ripple Data API, please see Ripple Data API Documentation.

    Learn, ask questions, and discuss

    Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.

    Other resources:

    • The Ripple Forum
    • The Ripple Dev Blog
    • Ripple Technical Services: [email protected]
    • XRP Chat

Log in to reply
 

Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.