Schlagwortarchiv für: What

taxi2

An open marketplace has expanded both supply and demand for taxi services. Photo: Daniel Horacio Agostini

One unique feature of Ripple is the open nature of the network, which has numerous benefits for banks, market makers, regulators and ultimately consumers.

Given that the idea of an open value network is somewhat of a new paradigm, it’s worth going over just exactly what might mean for the payment ecosystem’s various stakeholders.

The benefit of an open network for banks

Managing information is pivotal for banks. As part of their daily operations, banks need to manage an endless flow of payment data, which also includes customer information. Not only do customers expect and demand this information to be kept private, regulators require it. Moreover, it’s important for banks to maintain confidentiality since transaction information—such as the volume or the currency—is considered competitive intelligence.

Throughout our numerous conversations with banks and financial institutions, a common question was whether or not an open network could facilitate both privacy and confidentiality. At first glance, “open” may seem concerning because banks naturally expect payment networks to be private.

In reality, Ripple satisfies both privacy and confidentiality. While transaction information on the ledger is public, payment information is not. It’s difficult for anyone to associate transaction information with any specific bank.

Finally, there are benefits to transparency, especially for cross-border (out-of-network) payments, which have traditionally been relatively opaque. End-to-end traceability will not only reduce risk and delays, it should also reduce the cost of compliance allowing banks to lower costs of fee-disclosures and regulatory reporting.

The benefit of an open network for market makers

The market for settling payments is huge. The heart of the issue is that it isn’t necessarily accessible. This undermines both efficiency and competition. Meanwhile, market makers already specialize in managing capital and the associated risks. As we’ve discussed previously, what Ripple does is essentially allow market makers to access what is essentially a marketplace for float, where market makers can compete to provide liquidity, which lowers costs for banks and businesses.

One way to understand the impact of expanding accessibility is to look at how Uber affected the marketplace for taxis. In San Francisco, the taxi market was about $ 140 million per year, according to Uber CEO Travis Kalanick. But Uber is already making three times that with revenues of $ 500 million per year. This means that competition doesn’t necessarily cannibalize existing revenue, it can help the entire pie grow much larger. In the case of Uber, by expanding the supply of drivers and offering a far better experience, many more customers decided to use taxi services rather than other modes of transportation, expanding the marketplace and eventually spurring on both innovation and competition.

The benefit of an open network for regulators

The role of regulators is to protect the welfare of any payment systems, primarily because payments can be used to finance activity that is deemed detrimental to society—such as crime and terrorism. As a result, being able to track payments is fundamental to regulators doing their job.

With the way things are today, it’s extremely difficult to monitor transaction activity given disparate systems, networks, and platforms plus the continued prevalence of physical cash. As a result, transaction monitoring is a highly manual and operationally intensive process, which means that regulators incur high costs simply to do their job or in some cases, they aren’t able to do their job as effectively as they would like.

For regulators, the open nature of Ripple provides further transparency and payment traceability, thereby reducing their costs while allowing them to do their jobs more effectively. If regulators and banks are able to automate compliance processes with Ripple, it reduces costs for everyone in the ecosystem.

In the end, however, the real winners are consumers, who benefit from a safer, more open, and competitive ecosystem that provides a platform for innovation, better access, and lower costs.

Follow Ripple on Twitter

Ripple

We’re proud to announce the first release of our new Gateway Guide, a comprehensive manual to operating a gateway in the Ripple network. Whether you’re trying to understand how a gateway makes revenue, or how to use the authorized accounts feature, or even just what a warm wallet is, the gateway guide has you covered.

The guide comes with step-by-step, diagrammed explanations of typical gateway operations, a hefty list of precautions to make your gateway safer, and concrete examples of all the API calls you need to perform in order to get your gateway accounts set up and secure.

We’re proud of all the work we’ve done to make the business of running a gateway easier, but there’s still more work to do. If you have any questions, comments, or ideas, please send feedback to – or post it on our forums. We’d love to hear from you!

Ripple

OK so a minor update about what we are (and are not) doing here at Ethereum DEV.

We are, first and foremost, developing a robust quasi-Turing-complete blockchain. This is known as Ethereum. Aside from having quasi-Turing-completeness, it delivers on a number of other important considerations, stemming from the fact we are developing entirely new blockchain technology including:

  • speedy, through a 12 second blocktime;
  • light-client-friendly through the use of Merkle roots in headers for compact inclusion/state proofs and DHT integration to allow light clients to host & share small parts of the full chain;
  • ÐApp-friendly, even for light-clients, through the use of multi-level Bloom filters and transaction receipt Markle tries to allow for lightweight log-indexing and proofs;
  • finite-blockchain-friendly – we designed the core protocol to facilitate upgrading to this technology, further reducing light-client footprint and helping guarantee mid-term scalability;
  • ASIC-unfriendly – through the (as yet unconfirmed) choice of PoW algo and the threat we’ll be upgrading to PoS in the Not-Too-Distant future.

It is robust because:

  • it is unambiguously formally defined, allowing a highly tractable analysis, saturation tests and formal auditing of implementations;
  • it has an extensive, and ultimately complete, set of tests for providing an exceptionally high degree of likelihood a particular implementation is conformant;
  • modern software development practices are observed including a CI system, internal unit tests, strict peer-reviewing, a strict no-warnings policy and automated code analysers;
  • its mesh/p2p backend (aka libp2p) is built on well-tested secure foundations (technology stemming from the Kademlia project);
  • official implementations undergo a full industry-standard security audit;
  • a large-scale stress test network will be instituted for profiling and testing against likely adverse conditions and attacks prior to final release.

Secondly (and at an accordingly lower priority), we are developing materials and tools to make use of this unprecedented technology possible. This includes:

  • developing a single custom-designed CO (contract-orientated) language;
  • developing a secure natural language contract specification format and infrastructure;
  • formal documentation for help coding contracts;
  • tutorials for help coding contracts;
  • sponsoring web-based projects in order to get people into development;
  • developing a block chain integrated development environment.

Thirdly, to facilitate adoption of this technology, gain testers and spur further development we are developing, collaborating over and sponsoring a number of force-multiplying technologies that leverage pre-existing technology including:

  • a graphical client “browser” (leveraging drop-in browser components from the Chromium project and Qt 5 technology);
  • a set of basic contracts and ÐApps, including for registration, reputation, web-of-trust and accounting (leveraging the pre-existing compilers and development tech);
  • a hybrid multi-DHT/messaging system, codenamed Whisper (leveraging the pre-existing p2p back end & protocols);
  • a simple reverse-hash lookup DHT, codenamed Swarm (also leveraging the pre-existing p2p back end & protocols), for which there is an ongoing internal implementation, but which could end up merging or being a collaboration with the IPFS project.

We are no longer actively targeting multiple languages (LLL and Mutan are mothballed, Serpent is continued as a side project). We are not developing any server technology. And, until there is a working, robust, secure and effective block chain alongside basic development tools, other parts of this overall project have substantially lower priority.

Following on from the release of the Ethereum block chain, expect the other components to get increasingly higher amounts of time dedicated to them.

The post Ethereum ÐΞV: What are we doing? appeared first on ethereum blog.

ethereum blog

Presented by Stephan Tual, CCO. Companion Document: https://medium.com/@ethereumproject/4790bf5f7743 Ethereum is a platform that makes it possible for any de… Categories : Kryptowährungen. Bookmark the …
ethereum – Google Blogsuche

Codius was developed by Ripple Labs, which also created its own digital currency called Ripple. Codius aims to be interoperable between a variety of cryptocurrency, such as Ripple and bitcoin, although it is managed by the private company. “Codius can interact with other ledgers and web services. It can work on bitcoin and it can work on any other system,” says Stefan Thomas, Ripple’s CTO…

Ripple