paxmoneta_logo_Blog2

As interest in Ripple increases around the world, the ecosystem is steadily expanding into new and untapped markets. Recently, Minsung Park, a former lawyer and technology whiz brought Ripple to South Korea with the newest Ripple gateway, Pax Moneta.

Like many innovators building on the Ripple protocol, Mingsung’s history and breadth of experience is rich and unique, having helped to draft laws and write software that spurred the mass adoption of public key infrastructure within his home country.

“My parents wanted me to be a lawyer, so I became a lawyer,” said Minsung, who has helped translate various Ripple documents into Korean, such as the Ripple Primer (Korean). “But my basic instinct was toward science. It was my basic instinct that introduced me to the Internet. In my body and my soul, I am focused on this sort of scientific thinking.”

Minsung sees the potential of Ripple to help better connect his country and its citizens to the broader economic machine, reducing friction between neighboring markets, like China and Japan, as well as beyond, such as in the U.S. and Europe.

Tell us about yourself!

I was born in 1968 so I am 46. Sometimes I forget my age. I majored in law, with a focus on criminal law and information law. At the time, I remember the Internet was just introduced to Korea while I was in graduate school.

The concept quickly piqued my interest so I started digging. “What is the Internet?” I wanted to know. I discovered Mozilla. At the time, I was able to use a phone to connect to the Internet. One of the first things I did was create an Internet group at my university as part of the computer science and law departments, which ran a web server.

I completed my law major, but, personally, because of the Internet, I was interested in programming. From there, I ended up working at a government agency, the Korean Information Society Development Institute or KISDI. One of my primary responsibilities was to help formulate a law regarding the Korean Signature Act (1999) based on a public key system or PKI.

This was how I first came across the idea of a cryptocurrency, around 1996 or 1997, but I didn’t yet fully comprehend the meaning of currency or cryptocurrency. As time went on, I continued my research on the idea of the cryptographic key and kept on learning programming, including languages like C and C++. I ended up creating software for law firms working with government agencies, such as the Korea National Police Agency and the Korea Intelligence Services as well as other organizations using special cryptography with Western countries. Over time, many companies would integrate PKI, both for commercial and government websites in Korea.

I also ran a trading and development company with a focus in futures and options so I had an opportunity to live in the UK for around three years. Through that experience, I saw that the banking systems of Western countries were very developed and there was a good chance we could introduce these systems to Korea.

Three years ago, I returned to Korea, where I continued my study of cryptography, programming, and electronic trading. That’s when I read an article about Bitcoin, which brought back the idea of a cryptocurrency that I came across during my time with KISDI. I ran to the closest bookstore to learn more. During that search, I found Ripple, another way to transfer value digitally.

That’s when I started working on and developing a Ripple gateway, Pax Moneta, which is the first Ripple gateway in South Korea. Pax Moneta means “peace of money,” a clever play on words, originating from the term “Pax Romana” or “Pax America”

That’s quite a journey! What ended up attracting you to Ripple?

The reason why I created a Ripple company is simply because the technology is just great. It makes sense. In a way, Bitcoin is about replacing currency like the U.S. Dollar. On the other hand, Ripple is complementary and can help exchange any currency, KRW, CNY, GBP, or USD. That means Ripple can work with governments instead of against them. Personally, I will still use Bitcoin, but Ripple can be used as a method to help exchange value quickly between many countries.

So I have a lot of belief in Ripple, which I feel is supported by my background. I majored in law, but my basic instinct was always based on natural sciences. That’s why I love Ripple and I’m lucky because I think I can understand both areas.

What sort of challenges did you face?

I tried to build a rippled server. It was very difficult, but ultimately, I succeeded. Then I had to figure out how to use rippled, ripple-lib, and gatewayd.

One issue is that Node.js and Angular.js were very new to Koreans. Most developers in Korea are using Java. I couldn’t find a book in Korean for Angular.js so this was a challenge, but I was able to find English resources on the Internet. It was often difficult to sleep. If I’m interested in something, I cannot see anything, but this single passion.

After a bit of studying, I was able to better understand gatewayd and ripple-lib. A few months ago, my gateway was nearly ready so I contacted the International Ripple Business Association or IRBA.

Congratulations, that’s a huge accomplishment! Is the Ripple technology being embraced locally?

There have been some difficulties, primarily because most Koreans don’t know the existence of Ripple. We now have a gateway, but many Koreans don’t understand what a gateway is. So one thing we have to do is create a more intuitive Ripple client on top of gatewayd for Koreans to use.

Tell us about your team!

At the moment, we have four people, to cover programming, design, and marketing, but we are actively recruiting. We’re still small. We’re a startup.

Since one of the main challenges for Pax Moneta is Ripple mindshare in Korea, do you have an explicit marketing strategy?

As you know, Korea is located between China and Japan. Traditionally, KRW and USD has been essential to the Korean economy. I want to help Korea become a bridge between the USA and China. So in the long view, Pax Moneta should focus on these two countries.

There are many Koreans who own factories in China and there are also many Chinese people who want to come to Korea so there is high demand for exchange between KRW and CNY.

What’s the regulatory climate surrounding these technologies like in Korea?

There was a recent government petition on virtual currencies. In general, the view seems to be that virtual currencies are convenient, like Ripple, which is fast and operates within the law, but the price is not stable. So at the moment, the Bank of Korea does not have any explicit plan to support it.

As you may know, in Korea, the government plays a significant role in supporting companies so the issues of regulation are very important. But I believe it will be similar to adoption of the Internet. Today, the Internet is used by the Korean government. In the future, I think Ripple will be used, too. When my son and my grand children become parents, they will use virtual currencies.

The Korean government does block certain things, but in general, they want to support innovation, like with AG pay and Kakao pay. We’re entering a new era and I think there will be many chances in front of us if we are prepared for the future.

Any final thoughts?

Yes, just this: “If all roads lead to Rome, then all values lead to Ripple.”

 

Follow Ripple on Twitter

Ripple

The Stellar Development Foundation (SDF) which maintains Stellar, a network built on a modified version of the Ripple code base, recently published a post claiming flaws in the Ripple consensus algorithm. We take any reports about possible security issues very seriously and after reviewing the information conclude that there is no threat to the continued operation of the Ripple network. We’d like to share our thoughts.

Quoting the post in question:

Issue 1: Sacrificing safety over liveness and fault tolerance—potential for double spends

The Fischer Lynch Paterson impossibility result (FLP) states that a deterministic asynchronous consensus system can have at most two of the following three properties: safety (results are valid and identical at all nodes), guaranteed termination or liveness (nodes that don’t fail always produce a result), and fault tolerance (the system can survive the failure of one node at any point). This is a proven result.

This is correct.

 

Any distributed consensus system on the Internet must sacrifice one of these features.

This is potentially misleading. The FLP result shows that no system can provide those guarantees and reach consensus in bounded time. Real-world implementations of consensus like Paxos and Ripple however use probability to achieve safety, liveness and fault tolerance within a given time limit with very high likelihood.

If consensus is not achieved in this timeframe, the algorithm will retry and once again achieve consensus with very high likelihood and so on. In statistical terms, consensus will eventually be reached with probability 1, satisfying liveness under a probabilistic model. In practice, progress is usually made every round and two or more rounds are very rarely needed.

This means that distributed consensus systems like the Ripple network and Google’s Spanner database exist and can provide extremely high availability if configured correctly.

 

The existing Ripple/Stellar consensus algorithm is implemented in a way that favors fault tolerance and termination over safety.

This is incorrect. We have not reviewed Stellar’s modified version of Ripple consensus, but as far as the Ripple consensus algorithm is concerned, the protocol provides safety and fault tolerance assuming the validators are configured correctly. For a detailed proof, please see our consensus white paper.

 

This means it prioritizes ledger closes and availability over everyone actually agreeing on what the ledger is—thus opening up several potential risk scenarios.

This is incorrect. If a quorum cannot be reached, validators will retry until connectivity has been restored.

 

Issue 2: Provable correctness

Prof. David Mazières, head of Stanford’s Secure Computing Group, reviewed the Ripple/Stellar consensus system and reached the conclusion that the existing algorithm was unlikely to be safe under all circumstances.

We look forward to reading Prof. Mazières’ findings once they are published.

 

Based these findings, we decided to create a new consensus system with provable correctness.

As mentioned before, a proof of Ripple’s correctness is available in the form of the Ripple consensus white paper.

As Ripple Labs’ chief cryptographer and the original developer of Ripple consensus David Schwartz pointed out yesterday, there cannot be two conflicting majority sets without overlap. For bootstrapping with a small set of trusted validators, it is appropriate to use a crash-recovery fault model, meaning a simple majority such as three out of five is sufficient. In other words, it is impossible for the Ripple network to experience an unintentional ledger fork as Stellar’s did because our nodes require votes from a majority of validators. In the future, we will generally recommend a supermajority greater than two thirds to account for Byzantine faults (validators that act arbitrarily or maliciously), but otherwise the same concepts apply.

In either case, anyone wishing to join a specific set of mutually consenting validators in the Ripple topology can do so by configuring their local Ripple node appropriately. We recognize the immense task of building the world’s first global consensus graph. It is a hard problem, but not an impossible one. Like the transition from Arpanet to the distributed routing topology of the modern internet, it will require time, education and a great deal of caution. But thanks to our amazing partners and colleagues, we are ready to tackle this challenge.

The Ripple network and its distributed ledger have used the Ripple consensus protocol to operate reliably for two years and currently manage $ 1.4 million in daily volume. We continue to invest in scaling Ripple to support the world’s cross-border transactions with bank partners in the U.S. and Europe actively integrating today.

Ripple

Day 1 – Monday 24th Nov – ÐΞV: Mission and Processes

The first day of ÐΞVcon-0 kicked off early at 7am with the Eth Dev Ltd UK communications team arriving at the venue (Ethereum Dev UG’s workspace in Kreuzberg, Berlin) to set up the 4K high quality recording equipment and arrange the space for the event. 

Before set-up

After a quick coffee and croissant/pain au chocolat, everyone was ready for the first presentation – “Welcome! Our mission: ÐApps” which was delivered by Gavin Wood. Gavin made it very clear within this presentation the need for decentralised applications in today’s society with two very powerful opening quotes, “Progress has led to the concentration of power” and “Our mission therefore is decentralisation”. Following the presentation on ÐApps, Gavin invited everyone present to introduce themselves and explain their roles in Eth Dev. It was humbling to see how Ethereum has attracted such a magnificent team of incredibly talented people from such a wide variety of backgrounds. 

Gavin 1

Next up, Stephan Tual gave a talk highlighting the important role of the UK based communications team in building a strong and populous Ethereum community. He also touched on the streamlining of internal communications procedures to maximise Eth Dev’s efficiency. With 81 Ethereum meetup/hackathons taking place from Tehran to New York and with over 6000 members worldwide, the Ethereum community has grown exponentially over the past 11 months. Still, there is always more to be done. With the inclusion of 4 new members to the team, new educational tools on the horizon and increased interaction with the community, Stephan hopes Ethereum can become a worldwide phenomenon as we move forward to the release of the genesis block. 

IMG_6668

Straight after Stephan’s talk, Sven Ehlert gave an insightful presentation on how Scrum and Agile will be utilised to again maximise the efficiency of Ethereum’s software development.  This will be achieved by focusing on the key elements of the “product” that are needed for completion, and by applying incremental development goals with short deadlines for each of the individual developer teams (Mist, C++, Solidity etc). This will hopefully increase the overall output whilst breaking down what is a truly enormous project into manageable pieces. 

Sven

Finally to cap off the first day, Alex Van de Sande gave an update on Mist, the Ethereum Go client’s ÐApp Navigator. As many of you will have seen in Alex’s recent Mist presentation, the ÐApp Navigator will be an incredibly useful and powerful tool for people looking to interact with Ethereum and will really help make it accessible and easy to use by everyone from the outset – which is of course important for swift adoption.  

Alex

Day 2 – Tuesday 25th Nov – Languages, Ðapps & Architecture

After Monday’s introduction and team updates, day 2 would focus strongly on the direction of Ethereum’s languages, ÐApp creation and architecture updates. Gavin Wood and Christian Reitwießner started off with a talk on the vision of the Solidity language and the roadmap to its completion as it comes closer to a language that supports all features provided by the Ethereum Virtual Machine. You can try solidity in your browser now.

This was followed by a brief chat from Gavin this time focusing on the importance of secure documentation in ÐApp Development. The concept is to intertwine documentation and code in Solidity so that the documentation can be used by the client to alert the user of any significant actions that may take place as a consequence of running the code in certain smart contracts. 

Gav blog-44

Marek Kotewicz then gave an update on the Javascript API in a workshop setting allowing a lot of to-and-fro with the audience. He explained how it works, how to use it with smart contracts and what tools will be available to enable its use and uptake in the future.

After lunch, Piotr Zieliński presented on Golem, a project that aims to use Ethereum to coordinate a P2P distributed computation network for research use. Participants of the network share their computing power and in return receive a token of worth, incentivising their continued participation. Users can also access the resources to implement their own tasks and distribute them across the network.

Golem

Following Piotr, Sven Elert took the stage again to speak further on optimising Ethereum’s workflow using continuous integration. CI is a concept intended to improve the quality of whichever project it is being used with. Though Ethereum already uses CI, we wish to further refine the process as we move forward. To this end, Sven introduced several new and different implementations to make the developers lives easier as the project moves forward.  

To finish off day 2, Lefteris Karapetsas gave an interesting presentation about using Emacs for C++ Ethereum development. He highlighted several plugins to use in order to improve workflow as well as the plugin he’s working on for syntax highlighting on Solidity for Emacs. It is very cool to see personal projects increasing Eth Dev’s efficiency!

Day 3 – Wednesday 26th Nov – Client Comparisons and What is Ethereum?

Wednesday’s presentation and panel content offered a great opportunity to get the whole team on the same page from a client perspective. With Martin Becze arriving from San Francisco, we had representatives for each client ready for a panel talk later on in the day. The aim of panel was to increase the development team’s understanding of the different clients and highlight the minor differences between each client and how they implement the Ethereum Virtual Machine. 

The morning commenced with Vinay Gupta leading a workshop which had everyone present trying to come up with a definitive answer to “What is Ethereum?”. It turns out it’s not as easy as we thought! Each person had a chance to stand up and offer their own personal 30 second definition on what Ethereum is. The answers were diverse, and it was interesting to see how people changed their angle of approach depending on which audience the explanation was aimed at. 

Blog Collage-55

Following Vinay’s workshop, Martin Becze brought everyone up to speed with node-ethereum – a Node.js project he has been working on with Joseph Chow in Palo Alto. The talk started by outlining the ethereumjs-lib and node-etheruem’s architecture, then focused on areas where the client differs in structure from the other C++, Go and Python client implementations. Jeff Wilcke also gave a brief update on Ethereum Go client on the whiteboard before the panel discussion.

Martin

The presentation space was then rearranged for the panel with Gavin Wood (Alethzero), Jeff Wilcke (Ethereum Go), Heiko Hees (Pythereum) and Martin Becze (Node-Ethereum). Each took turns outlining how each client handles state transactions, moves account balances, runs the EVM and saves data to accounts whilst handling sucides and out-of-gas exceptions. Questions where then posed by the audience, discussions continued on late into the night as day 3 drew to a close. 

Client panel-61

Day 4 – Thursday 27th Nov – Robustness and security

Though it is exceptionally useful to have a large suite of tools available for developers and users wanting to interact with Ethereum, it means nothing if the security and robustness of the network are in anyway compromised. To this end, the Eth Dev team is working very hard to audit the software with several external partners and ensure network stability from the release of the genesis block onwards.

To this end, Sven Ehlert, Jutta Steiner and Heiko Hees kicked off the morning with a workshop on the Stress Testing Project. The goal of the project is to again use continuous integration and take it one step further. With CI, the Dev team can test to make sure that each client will behave correctly when it executes a contract. In this respect it will simulate how clients would interact with the blockchain in the real world. This will allow us to understand how the network will behave if the clients have different properties. For instance – clients with low bandwidth and less cpu power interacting with those with more resources available. The project pays special attention to how this will affect potential forks of the blockchain. Later on, the team will simulate attacks on the Ethereum blockchain and network to test its durability and resilience. 

After the workshop, Christoph Jenzsch presented on the why and how of unit testing in the Ethereum project. In his talk, Christoph described several different types of test that need to be carried out – unit tests, integration tests and system tests. He also explained the different tools available to make it easy for every developer involved in Ethereum to get working on the huge amount of testing that needs to be carried out before it’s released. 

Christoph

Next, Jutta Steiner took the stage to deliver a talk on “Achieving Security”. She explained how our approach to security is to initiate both an internal audit and a massive external audit with established software security firms, academics, blockchain research firms and companies interested in utilising Ethereum all taking part. Jutta is also working on a bounty program which will be open to the community rewarding those who test and explore the protocol and software. We’ll be releasing more information on this shortly if you wish to take part.

IMG_7007-65

After a quick lunch, Alex Leverington updated us on the vision and roadmap of the Libp2p Multi  Protocol Network Framework. The p2p networking protocol is geared towards security as it is entirely encrypted from end to end. He contrasted the Ethereum network with the internet as we know it today, emphasising the difference between using SSL certificates and p2p anonymous networks. He also commented on Ethereum’s 3 network protocols – Whisper, Swarm and Ethereum itself. All 3 protocols run on the same line, so framing/multiplexing is being used to stop them from interfering with each others bandwidth needs. A key point to take away from this is that other ÐApps can potentially build their own protocols and use the multiplexing to optimise the connection as well.

Gavin followed up with a presentation on the what and why of Whisper: the Multi DHT Messaging System with Routing Privacy. Consensus is expensive, and for things like pure communications there are more elegant solutions available than using blockchain tech, hence the need for Whisper. To understand Whisper in general, think transactions, but without the eventual archival, any necessity of being bound to what is said or automated execution & state change. He also talked about some specific use cases for Whisper, such as ÐApps that need to provide dark (plausible denial over perfect network traffic analysis) comms to two correspondents that know nothing of each other but a hash. This could be a ÐApp for a whistleblower to communicate to a known journalist exchange some small amount of verifiable material and arrange between themselves for some other protocol (Swarm, perhaps) to handle the bulk transfer.

To finish off the day, Daniel Nagy bought us up to speed on Swarm, Ethereum’s decentralised file storage and transmission protocol specifically targeted toward static web content hosting. Daniel also covered DHT (Distributed Hash Table – Kademlia). This will allow peers to connect to other peers distributed throughout the network instead of peer that are simply close to each other. By deterministically connecting to random peers, you know that each peer will have a better picture of the overall state of the network, increasing its viability.

Day 5 – Friday 28th Nov – Blockchain Theory and The Future

The fifth and final day of DEVcon 0! After a week of talking about the near future of Ethereum’s development and completion, the last day would be focused on future iterations of Ethereum and blockchain technology as a whole.

Vitalik Buterin and Vlad Zamfir started off day five with a whiteboard presentation on Ethereum 1.x. There are several problems that need to be solved as blockchain technology moves forward in the future – scalability and blockchain interoperability being at the forefront of those issues. The idea of Ethereum interacting with thousands of other blockchains is an attractive one, this in itself solves certain scalability problems in that work can distributed across many chains as opposed to bloating one central chain. 

Vitalik and Vlad

Gavin then joined Vitalik and together they talked about the Ethereum Light-Client. A light client protocol is especially important for Ethereum as it will allow it to run on low capacity environments such as mobile phones, IoT (Internet of Things) devices and browser extensions. The two explained the development process and usage of Patricia Merkle Trees to implement it. Expect the light client to be ready for the release of Ethereum 1.0.

After lunch, Juan Batiz-Benet of Filecoin/IPFS showed the audience the technology behind IPFS and Bitswap. He also presented some Ethereum/IPFS use cases such as content addressed files, IPNS naming and high performance distributed filesystem and tool integration.

Juan

Gavin once again took the stage to reveal Mix, the Ethereum IDE. Mix is being developed in conjunction with Alethzero and expected to be released in the next 12 to 18 months. It supports a  rather amazing features, including documentation, compiler and debugger integration as you type, information on code health, valid invariant, code structure and code formatting, as well as variable values and assertion truth annotations.

Finally, Vitalik wrapped up the event with a presentation showing some ideas for Ethereum 2.0 (Sharding, Hypercubes) and thanked all of those who attended. 

Overall, ÐΞVcon-0 was very enriching and worthwhile for everyone who attended. As expected, the Eth Dev team is now  very much on the same page and ready to push forward to the release of the genesis block. All of the presentations from DEVcon 0 were recorded and are currently being edited together by our resident graphic designer/video editor Ian Meikle. Starting on the 8th, a steady stream of content – “The ÐΞVcon-0 Series” will be added to the Ethereum Youtube Channel

The post ÐΞVcon-0 Recap appeared first on ethereum blog.

ethereum blog

ripple-earthport-2

Ripple Labs is thrilled to announce a partnership with Earthport, a regulated financial institution whose cross-border platform represents the largest open network for global bank payments.

The London-based firm, which has offices in New York and Dubai, will integrate the Ripple protocol alongside its existing payments network. Through this global partnership, Earthport’s customers will be able to leverage Ripple’s friction-free cross-border payments solution and benefit from lower liquidity management costs, all while maintaining the robust standards of compliance that regulators expect.

“We constantly evaluate new technologies to reduce costs and delays associated with global bank payments for our clients, but require these innovations to meet our high, exacting standards for compliance,” said Hank Uberoi, CEO of Earthport. “Ripple is a new technology and, once integrated in our payments service could bring benefits in efficiency and speed to global transfers. Earthport will apply its existing compliance framework, rule sets and secure payments network to any Earthport clients transacting using the Ripple protocol.”

Growth in international trade, e-commerce, and demographic shifts in population have driven both corporate and consumer demand for faster, cost-efficient, reliable and transparent cross-border payment solutions.

earthport-graph

Earthport is the largest open network for global bank payments, servicing businesses and financial institutions across 60 countries around the world. (Image: Earthport)

Ripple Labs is incredibly proud to have a partner at the forefront of the payments industry. Earthport was awarded the B2B Payments Innovation of the Year 2014 at the second annual FStech/Retail Systems Payments Awards. The company—which is listed on the Alternative Investment Market (AIM) on the London Stock Exchange and is authorised and regulated by the Financial Conduct Authority under the Payment Service Regulations 2009—services major institutional clients in over sixty countries.

“Traditional cross-border payments are inefficient today because both the technology and compliance frameworks underpinning them were built country by country decades ago,” said Chris Larsen, co-founder and CEO of Ripple Labs, the developer of the Ripple protocol. “The Earthport and Ripple partnership brings together the leading global payments and technology infrastructures to immediately transform and modernise the global payments industry.”

Earthport’s proven compliance platform provides an immense opportunity for international scalability given their expertise in navigating local regulations. For Ripple Labs, the partnership represents another major milestone as part of the company’s mission to develop and expand the Ripple network by plugging into the existing financial system.

Follow Ripple on Twitter

Ripple

Kaum ein Altcoin wurde mit so viel Gedöns und Begeisterung verkündet wie Ethereum. Aber was ist dran an dem System, das, so die Medien, "alles" dezentralisieren will und über das schon gemunkelt wurde, es könne den …
ethereum – Google Blogsuche

(PresseBox) (GENF, Schweiz, 15.05.2012) Die unabhängige Privatbank Bankhaus Main nutzt ab sofort die Lösung Triple’A Plus des …
temenos – Bing News

Yesterday was the first proper day of ÐΞVhub Berlin being open, following the first Ethereum internal developers’ symposium ÐΞVcon-0. I want to post a few images to let you gauge the mood here.

IMG_7451

Henning, Marek, Viktor and Felix hacking on the couch

IMG_7452

Aeron and Brian in discussion

IMG_7454

Alex and Jutta conferencing over network and security

IMG_7456

The rest of the team hacking in the lab

The post From inside Ethereum ÐΞVhub Berlin appeared first on ethereum blog.

ethereum blog

lawsky

Superintendent Ben Lawsky hasn’t shied away from maintaining an open dialogue with the community.

While the early days of the web provide an intuitive roadmap for how the emergence of digital payment protocols and the ecosystem that surrounds them will evolve over time, there’s one defining difference between the evolving state of finance today and the Internet of the 80s: Regulations.

There’s a lot more at stake when transferring value versus information. It’s why finance is the most heavily regulated industry on the planet. It’s also why the internet-of-value has taken such a long time to materialize. The bar is just that much higher.

As these emerging technologies push us further into uncharted territory, navigating these regulatory waters has become a core component of our mission here at Ripple Labs. And as creators of an open source protocol, we’re committed to being transparent about that process. To provide insight on our perspective, we’re publishing our BitLicense comments (pdf), which we recently submitted to regulators.

The Ripple Labs perspective

Our position on regulations is straightforward. An effective regulatory framework opens the door to mainstream adoption. The goal is to provide necessary protections for end users without stifling innovation by burdening developers and small businesses. Instead, smart regulations can level the playing field, legitimize a burgeoning industry, and empower entrepreneurs.

But getting regulations right is an immense task. That’s why it’s pertinent that Ripple Labs works intimately with regulators, our numerous stakeholders, and the industry-at-large in helping to collectively shape the rules that will define the way forward.

BitLicense

It’s incredibly encouraging that the U.S. government appears up to the task with Superintendent Ben Lawsky of the New York State Department of Financial Services leading the way by maintaining an open dialogue and recently, drafting the first proposal of BitLicense, a set of rules that aim to bring clarity to how government officials and businesses deal with cryptocurrencies.

As the only U.S. regulator to step up to the plate—at both state and federal levels—Superintendent Lawsky should be commended for assuming this monumental responsibility. BitLicense elevates the industry as a whole, putting us in the same club as the big banks. Most of all, throughout Lawsky’s numerous interactions with the community—including his speech at Money20/20 in Las Vegas last month—it’s clear that New York’s first Superintendent of Financial Services not only comprehensively understands and respects the awesome potential of these new technologies but also what’s at stake.

Indeed, the implications of BitLicense will have far broader implications beyond the crypto-community, as Lawsky alluded to during his Vegas keynote, noting that his framework for Bitcoin regulations will eventually serve as a model for all regulated institutions. Along those lines, this isn’t merely about the future of Bitcoin or Ripple, it’s about the future of finance as a whole—one in which the lines between new technologies and the existing system continue to blur.

Again, for his fearless and influential leadership, Lawsky deserves to be commended. Even so, he could do more—especially if he and the rest of the state’s ruling body want New York to become a hub for technological innovation. Below is a summary of our comments and suggestions that we believe could help BitLicense reach its ultimate goals while still maintaining an environment that supports and fosters innovation and small businesses.

Reduce barriers of entry. New York should support developers who need the freedom to build. Costly compliance requirements create huge barriers of entry for small businesses. To accommodate innovation, we suggest a “registration regime” versus a “licensing regime” with a threshold for smaller firms, significantly reducing potential upfront costs and waiting around that often deters new businesses. This way, entrepreneurs can begin the regulatory process in good faith and start their business right away.

Create a level playing field. A key criticism of the initial BitLicense proposal is that it didn’t create a level playing field between cryptocurrencies and everyone else. There are arguments to be made why cryptocurrencies should be held to a higher standard their unique properties, but if that’s the case, those arguments need to be explicitly mapped out to each special feature individually relative to existing rulesets. With the initial draft, it’s often unclear why increased controls are being implemented only for cryptocurrencies.

The rules regarding information security is one example, which requires third-party code verification. In this case, rather than opting for a more organic approach, Lawsky went from 0-60 with these baseline regulations. While it may be true that this new rule could very well be a “coming attraction for all banks,” emerging technologies shouldn’t have to serve as the canary in the coal mine. If a new rule is believed to be beneficial to the public’s interests, it should be applied to all relevant parties on day one rather than arbitrarily to the new kids on the block. Otherwise, BitLicense undermines a sense of fairness by appearing to favor established interests.

The overall scope is too broad. Such is the nature of emerging technologies with few past precedents, they can be difficult to properly define, but even under that context, the way BitLicense defines these new technologies is far too general and vague. If the purpose of regulations is to provide clarity, the proposal as it currently exists risks further muddying the waters by leaving far too much to subjective interpretation. The first step then is to provide a concise definition of the technology at hand. The approach we prefer is to highlight the technology’s fundamental distinctions. In the case of virtual currencies, this is the first time we’ve seen assets exist in a digital context (as opposed to liabilities).

Beyond reaching consensus on a proper definition, we believe that limiting the scope of these new regulations requires a more balanced and organic approach to how we assess risk. It’s logical to focus on the risks added by new technologies, but it’s just as important to take into consideration existing risks that innovation helps to mitigate. In that sense, BitLicense should not only temper negative characteristics, but also foster and expand positive traits. In current form, the former is at times, over the top, while the latter is lacking.

The way forward

Overall, the development of BitLicense represents a huge step in the right direction, despite being imperfect as regulators and industry participants continue to work together toward a meaningful and mutually beneficial consensus.. That governments are dedicating these resources toward legitimizing new businesses is a huge stamp of approval for technologies that only a few short years ago didn’t even exist.

At Ripple Labs, we’re deeply cognizant of our responsibility to our partners, our community, and the industry, and we take great pride in participating in this ongoing process, one we believe will have a huge impact on our ability to deliver these breakthrough technologies to people around the world.

That last part is key. Even if the U.S. will, at times, lead the way, the scope and reach of Ripple and other digital payment protocols in general transcends borders. As such, our regulatory work extends to a global scale. Last Friday, our team submitted a letter to the Australian Parliament regarding the regulation of digital currencies, which is available on their website for download. (We are submission #21.) We are also in the process of engaging with other foreign regulators.

As always—as an ongoing conversation and an evolving process—we are open to any and all feedback. We look forward to hearing from you.

Follow Ripple on Twitter

Ripple

(PresseBox) (Frankfurt am Main, 01.12.2011) Temenos, weltweit führender Core Banking-Anbieter, ist zum fünften Mal in Folge mit …
temenos – Bing News

Bei Ethereum gibt es neue Informationen zum IPO. Chefentwickler Vitalik Buterin hat die geänderten IPO-Bedingungen im Bitcointalk veröffentlicht. Überraschend war zunächst einmal die Preiserhöhung für mich. So erhält …
ethereum – Google Blogsuche