Verge (XVG) Releases Revised Blackpaper and New Codebase

[Ozark]

The team at Verge (XVG) have ushered in the New Year with two new announcements this past week. The first one being that they have released the fifth version of the project’s black-paper. The second announcement that was made by the team at XVG was that the Verge 5.0 Codebase is available on Github for Alpha testing.

New Verge Blackpaper

The term black-paper was initially used to define a series of articles on British education published from 1969 to 1977. Their name was intended to contrast the government issued white papers at the time. A white paper is an authoritative guide or report that informs the reader about a complex issue.

In the case of cryptocurrencies, most projects issue white papers that explain to users and investors of the digital asset, on the future plans of the project. The team at Verge decided to refer to their detailed report as a black-paper.

The fifth version of the blackpaper is available online and highlights the current and future plans of the XVG network. Of particular interest in the new blackpaper, is the detailed explanation of TOR integration, I2P integration, the use of the Electrum wallet, Atomic Swaps (cross-chain trading) and Rootstock integration (side chains for smart contracts).

Alpha Release of the Verge Codebase

The Alpha version of the 5th Verge Codebase is currently available on Github. This version is currently only available to developers and aims at testing vulnerabilities as well as identifying bugs before beta/public release.

The team at Verge decided to rebase the XVG code to that of Bitcoin after the network was hacked multiple times mid last year. This was aimed at making the network more secure and less vulnerable to attacks. The rebasing included the addition of features unique to XVG such as stealth addressing and Tor.

The team had also clarified that the new codebase did not have the BTC security bug that had been identified in early October last year. The team explained:

We already took our time to investigate this issue within our latest codebase and we came to the conclusion that we aren’t vulnerable to this kind of attack. As added security, we are going to include the bitcoin fix into our new codebase as well.

SOURCE