Some key notes on the Verge white paper:
Tor directs internet traffic through a free worldwide volunteer overlay network consisting of more than seven thousand relays to conceal a user’s location and usage from anyone conducting network surveillance or traffic analysis.
I2p is highly obfuscated tunneling service using ipv6 that anonymizes all Verge data being sent over the network. Each client application has their i2p “router” build several inbound and outbound “tunnels”. In order to find other client’s inbound tunnels efficiently, they use a custom structured distributed hash table.
One of the wallets that provide native Tor and i2p support.
It supports 5 Proof-of-Work algorithm that run on its blockchain: Scrypt,X17,Lyra2rev2,myr-groestl,blake2s. All have a 30-second block target block time.
Make it possible to choose between a public or private ledger.
Use Elliptic-curve Diffie-Hellman for stealth addressing.
Allows for interoperability between Verge and all other cryptocurrencies in circulation with Atomic swap capabilities enabled.
Original attack analysis:
Let’s take a look at the blockchain.
The attacker changed the timestamp of new blocks to make the time of producing a new block increasing to 5 mins which leads to the whole chain decrease the difficulty. And we can get from the code that, the new block has to pass this check.
And since the attacker change the time stamp. The pindexPrev->GetBlockTime() has increased. So other miners that didn’t change the timestamp can’t mine a new block! In this case, the attacker can control the network and no block produced by other miners will be added to the chain.
And we can see that the attacker change time stamp to be smaller in 2007365,2007367 just to increase the difficulty so the difficulty of the chain won’t be too small.
This attack really caused a huge lose.