Mitsubishi Corporation`s Funds to be moved via RippleNet

Mitsubishi Corporation, together with a few partners, are going to move real funds over RippleNet: this is another validation of Ripple’s present technology
15 May 2018   2151

The name of Mitsubishi is known to many people as a car manufacturer. The parent enterprice, nevertheless, has bigger plans for the future. In collaborance with MUFG Bank, Bank of Ayudhya, and Standard Chartered Bank, a blockchain pilot has been planned. 

This venture especially focuses on RippleNet, the technology aimed to facilitate cross-border payment flows. The main object of this test is to refine cash processing. All parties included trade with real-time and multi-currency payments on a daily basis. Cross-border transactions while stay slow, expensive, and subject to a fair amount of administration. With RippleNet, these payment flows can be bettered upon significantly. 

The goal of the pilot is to demonstrate the commercial viability of delivering high-speed cross-border payments between independent banks. As global trade continues to increase, the problems associated with cross-border payments are being experienced by smaller businesses as well. These companies don’t have the treasury resources or experience in navigating the pitfalls of today’s payment rails.
Ripple officials

Ripple’s technology is being tested for not the first time. RippleNet is a developing enterprice which basically collected support in the Asian region. Additional tests on this scale will define whether or not RippleNet is indeed a lively addition to the financial sector. The above-mentioned trial will be kept by Mitsubishi Corporation. Its subsidiaries’ accounts in Thailand and Singapore will see a real-world money transfer using RippleNet. It is also the first time a Japanese firm finishes a cross-border payment transaction over Ripple’s technology. If successful, this test can state a big precedent for other domestic firms to explore.

Depending on how the test goes, the parties intend to commercialize this payment resolve. Bringing RippleNet to the real world is an ongoing struggle, albeit things are proceeding as planned. With all of these firms showing a genuine interest in the project, Ripple has to provide the goods. Partnership with Mitsubishi Corporation at this stage paints an interesting outlook.

Potentional Vulnerabilities Found in ETH 2.0

Least Authority have found potentional security issues in the network P2P interaction and block proposal system
26 March 2020   212

Technology security firm Least Authority, at the request of the Ethereum Foundation, conducted an audit of the Ethereum 2.0 specifications and identified several potential vulnerabilities at once.

Least Authority said that developers need to solve problems with vulnerabilities in the network layer of peer-to-peer (P2P) interaction, as well as in the block proposal system. At the same time, the auditor noted that the specifications are "very well thought out and competent."

However, at the moment there is no large ecosystem based on PoS and using sharding in the world, so it is impossible to accurately assess the prospects for system stability.
Also, information security experts emphasized that the specifications did not pay enough attention to the description of the P2P network level and the system of records about Ethereum nodes. Vulnerability risks are also observed in the block proposal system and the messaging system between nodes.

Experts said that in the blockchains running on PoS, the choice of a new block is simple and no one can predict who will get the new block. In PoS systems, it is the block proposal system that decides whose block will fall into the blockchain, and this leads to the risk of data leakage. To solve the problem, auditors suggested using the mechanism of "Single Secret Leader Election" (SSLE).

As for the peer-to-peer exchange system, there is a danger of spam. There is no centralized node in the system that would evaluate the actions of other nodes, so a “malicious" node can spam the entire network with various messages without any special punishment. The solution to this problem may be to use special protocols for exchanging messages between nodes.