Bitcoin ‘difficulty ribbon’ chart hasn’t been this bullish since March
This post was originally published on this siteThis post was originally published on this siteBitcoin (BTC) simply needs history to repeat itself to see significant price rises, according to two indicators now flipping bullish. On Sep. 28, on-chain monitoring resource Glassnode noted that Bitcoin’s difficulty ribbon compression had broken out of its green “buy” zone for the first time since the March […]
Why Verge Needs DigiShield NOW! And Why DigiByte Is SAFE!
Hello everyone, I’m back! Someone asked a question recently on what exactly happened to XVG – Verge and if this could be a problem for DGB – DigiByte - Here: DigiByte vs Verge It was a great question and there have been people stating that this cannot be a problem for us because of DigiShield etc… with not much explanation after that. I was curious and did a bit more investigating to figure out what happened and why exactly it is that we are safe. So take a read.
Some Information on Verge
Verge was founded in 2014 with code based on DogeCoin, it was initially named DogeCoinDark, it later was renamed Verge XVG in 2016. Verge has 5 mining algorithms as does DigiByte. Those being:
However, unlike DigiByte those algorithms do not run side by side. On Verge one block can only be mined by a single algorithm at any time. This means that each algorithm takes turns mining the chain.
Prior to the latest fork there was not a single line of code that forced any algo rotation. They all run in parallel but of course in the end only one block can be accepted at given height which is obvious. After the fork algo rotation is forced so only 6 blocks with the same algo out of any 10 blocks can be accepted. - srgn_
Mining Verge and The Exploit
What happened then was not a 51% attack per say, but the attacker did end up mining 99% of all new blocks so in fact he did have power of over 51% of the chain. The way that Verge is mined allowed for a timestamp exploit. Every block that is mined is dependent on the previous blocks for determining the algorithm to be used (this is part of the exploit). Also, their mining difficulty is adjusted every block (which last 30 seconds also part of the exploit). Algorithms are not picked but in fact as stated previously compete with one another. As for difficulty:
Difficulty is calculated by a version of DGW which is based on timestamps of last 12 blocks mined by the same algo. - srgn_
This kind of bug is very serious and at the foundation of Verge’s codebase. In fact, in order to fix it a fork is needed, either hard fork or soft fork! What happened was that the hacker managed to change the time stamps on his blocks. He introduced a pair of false blocks. One which showed that the scrypt mining algorithm had been previously used, about 26 mins before, and then a second block which was mined with scrypt. The chain is set up so that it goes through the 5 different algorithms. So, the first false block shows the chain that the scrypt algorithm had been used in the recent past. This tricks it into thinking that the next algorithm to be used is scrypt. In this way, he was essentially able to mine 99% of all blocks.
Pairs of blocks are used to lower the difficulty but they need to be mined in certain order so they can pass the check of median timestamp of last 11 blocks which is performed in CBlock::AcceptBlock(). There is no tricking anything into thinking that the next algo should be x because there is no algo picking. They all just run and mine blocks constantly. There is only lowering the difficulty, passing the checks so the chain is valid and accepting this chain over chains mined by other algos. - segn_
Here is a snippet of code for what the time stamps on the blocks would look like:
SetBestChain: new best=00000000049c2d3329a3 height=2009406 trust=2009407 date=04/04/18 13:50:09 ProcessBlock: ACCEPTED (scrypt) SetBestChain: new best=000000000a307b54dfcf height=2009407 trust=2009408 date=04/04/18 12:16:51 ProcessBlock: ACCEPTED (scrypt) SetBestChain: new best=00000000196f03f5727e height=2009408 trust=2009409 date=04/04/18 13:50:10 ProcessBlock: ACCEPTED (scrypt) SetBestChain: new best=0000000010b42973b6ec height=2009409 trust=2009410 date=04/04/18 12:16:52 ProcessBlock: ACCEPTED (scrypt) SetBestChain: new best=000000000e0655294c73 height=2009410 trust=2009411 date=04/04/18 12:16:53 ProcessBlock: ACCEPTED (scrypt)
Here’s the first falsified block that was introduced into the XVG chain – Verge-Blockchain.info As you can see there is the first fake block with a time stamp of 13:50:09 for example and the next is set to 12:15:51, the following two blocks are also a fraudulent pair and note that the next block is set to 12:16:52. So essentially, he was able to mine whole blocks - 1 second per block!
This exploit was brought to public attention by ocminer on the bitcointalk forums. It seems the person was a mining pool administrator and noticed the problem after miners on the pool started to complain about a potential bug. What happened next was that Verge developers pushed out a “fix” but in fact did not really fix the issue. What they did was simply diminish the time frame in which the blocks can be mined. The attack still was exploitable and the attacker even went on to try it again! “The background is that the "fix" promoted by the devs simply won't fix the problem. It will just make the timeframe smaller in which the blocks can be mined / spoofed and the attack will still work, just be a bit slower.” - ocminer Ocminer then cited DigiShield as a real fix to the issue! Stating that the fix should also stipulate that a single algo can only be used X amount of times and not be dependent on when the algo was last used. He even said that DigiByte and Myriad had the same problems and we fixed them! He cited this github repo for DigiByte:
It seems that the reason that this exploit was so lucrative was because the difficulty adjustment parameters were not enough to reduce the rewards the attacker recieved. Had the rewards per block adjusted at reasonable rate like we do in DGB then at least the rewards would have dropped significantly per block. The attacker was able to make off with around 60 million Verge which equals about 3.6 million dollars per today’s prices. The exploit used by the attacker depended on the fact that time stamps could be falsified firstly and secondly that the difficulty retargeting parameters were inadequate. Let’s cover how DigiShield works more in detail. One of the DigiByte devs gave us this post about 4 years ago now, and the topic deserves revisiting and updates! I had a hard time finding good new resources and information on the details of DigiShield so I hope you’ll appreciate this review! This is everything I found for now that I could understand hopefully I get more information later and I’ll update this post. Let’s go over some stuff on difficulty first then I’ll try giving you a way to visualise the way these systems work. First you have to understand that mining difficulty changes over time; it has to! Look at Bitcoin’s difficulty for example – Bitcoin difficulty over the past five months. As I covered in another post (An Introduction to DigiByte Difficulty in Bitcoin is readjusted every 2016 blocks which each last about 10 mins each. This can play out over a span of 2 weeks, and that’s why you see Bitcoin’s difficulty graph as a step graph. In general, the hash power in the network increases over time as more people want to mine Bitcoin and thus the difficulty must also increase so that rewards are proportional. The problem with non-dynamic difficulty adjustment is that it allows for pools of miners and or single entities to come into smaller coins and mine them continuously, they essentially get “free” or easily mined coins as the difficulty has not had time to adjust. This is not really a problem for Bitcoin or other large coins as they always have a lot of miners running on their chains but for smaller coins and a few years ago in crypto basically any coin other than Bitcoin was vulnerable. Once the miners had gotten their “free coins” they could then dump the chain and go mine something else – because the difficulty had adjusted. Often chains were left frozen or with very high fees and slow processing times as there was not enough hash power to mine the transactions. This was a big problem in the beginning with DigiByte and almost even killed DogeCoin. This is where our brilliant developers came in and created DigiShield (first known as MultiShield). These three articles are where most of my information came from for DigiShield I had to reread a the first one a few times to understand so please correct me if I make any mistakes! They are in order from most recent to oldest and also in order of relevance.
DigiShield is a system whereby the difficulty for mining DigiByte is adjusted dynamically. Every single block each at 15 seconds has difficulty adjusted for the available hashing power. This means that difficulty in DigiByte is as close as we can get to real time! There are other methods for adjusting difficulty, the first being the Bitcoin/Litecoin method (a moving average calculated every X number of blocks) then the Kimoto Gravity Well is another. The reason that DigiShield is so great is because the parameters are just right for the difficulty to be able to rise and fall in proportion to the amount of hash power available. Note that Verge used a difficulty adjustment protocol more similar to that of DigiByte than Bitcoin. Difficulty was adjusted every block at 30 seconds. So why was Verge vulnerable to this attack? As I stated before Verge had a bug that allowed for firstly the manipulation of time stamps, and secondly did not adjust difficulty ideally. You have to try to imagine that difficulty adjustment chases hashing power. This is because the hashing power on a chain can be seen as the “input” and the difficulty adjustment as the corresponding output. The adjustment or output created is thus dependent on the amount of hashing power input. DigiShield was designed so that increases in mining difficulty are slightly harder to result than decreases in mining difficulty. This asymmetrical approach allows for mining to be more stable on DigiByte than other coins who use a symmetrical approach. It is a very delicate balancing act which requires the right approach or else the system breaks! Either the chain may freeze if hash power increases and then dumps or mining rewards are too high because the difficulty is not set high enough! If you’ve ever taken any physics courses maybe one way you can understand DigiShield is if I were to define it as a dynamic asymmetrical oscillation dampener. What does this mean? Let’s cover it in simple terms, it’s difficult to understand and for me it was easier to visualise. Imagine something like this, click on it it’s a video: Caravan Weight Distribution – made easy. This is not a perfect analogy to what DigiShield does but I’ll explain my idea. The input (hashing power) and the output (difficulty adjustment) both result in oscillations of the mining reward. These two variables are what controls mining rewards! So that caravan shaking violently back and forth imagine those are mining rewards, the weights are the parameters used for difficulty adjustment and the man’s hand pushing on the system is the hashing power. Mining rewards move back and forth (up and down) depending on the weight distribution (difficulty adjustment parameters) and the strength of the push (the amount of hashing power input to the system). Here is a quote from the dev’s article. “The secret to DigiShield is an asymmetrical approach to difficulty re-targeting. With DigiShield, the difficulty is allowed to decrease in larger movements than it is allowed to increase from block to block. This keeps a blockchain from getting "stuck" i.e., not finding the next block for several hours following a major drop in the net hash of coin. It is all a balancing act. You need to allow the difficulty to increase enough between blocks to catch up to a sudden spike in net hash, but not enough to accidentally send the difficulty sky high when two miners get lucky and find blocks back to back.” AND to top it all off the solution to Verge’s time stamp manipulation bug is RIGHT HERE in DigiShield again! This was patched and in Digishield v3 problems #7 Here’s a direct quote: “Most DigiShield v3 implementations do not get data from the most recent blocks, but begin the averaging at the MTP, which is typically 6 blocks in the past. This is ostensibly done to prevent timestamp manipulation of the difficulty.” Moreover, DigiShield does not allow for one algorithm to mine more than 5 blocks in a row. If the next block comes in on the same algorithm then it would be blocked and would be handed off to the next algorithm. DigiShield is a beautiful delicate yet robust system designed to prevent abuse and allow stability in mining! Many coins have adopted out technology!
Verge Needs DigiShield NOW!
The attacker has been identified as IDCToken on the bitcointalk forums. He posted recently that there are two more exploits still available in Verge which would allow for similar attacks! He said this: “Can confirm it is still exploitable, will not abuse it futher myself but fix this problem immediately I'll give Verge some hours to solve this otherwise I'll make this public and another unpatchable problem.” - IDCToken DigiShield could have stopped the time stamp manipulation exploit, and stopped the attacker from getting unjust rewards! Maybe a look at Verge’s difficulty chart might give a good idea of what 1 single person was able to do to a coin worth about 1 billion dollars.
Edit - Made a few mistakes in understanding how Verge is mined I've updated the post and left the mistakes visible. Nothing else is changed and my point still stands Verge could stand to gain something from adopting DigiShield! Hi, I hope you’ve enjoyed my article! I tried to learn as much as I could on DigiShield because I thought it was an interesting question and to help put together our DGB paper! hopefully I made no mistakes and if I did please let me know. -Dereck de Mézquita I'm a student typing this stuff on my free time, help me pay for school? Thank you! D64fAFQvJMhrBUNYpqUKQjqKrMLu76j24g https://digiexplorer.info/address/D64fAFQvJMhrBUNYpqUKQjqKrMLu76j24g
Bitcoin mining difficulty up another 24% in just the last 30 days!
A year ago the hashpower needed to mine Bitcoin was insane, the network was considered unbreakable. But its continued to double every few months. This is an indicator that the $ cost for many miners has continued to increase, yet investment into mining continues to thrive. Mining is basically an entire sub economy of the tech sector creating massive amounts of wealth and jobs. Here's a link showing charts for the increase in hash power...it shocked me in January and I didnt think it would just keep going up so much during this bear market. https://www.coinwarz.com/difficulty-charts/bitcoin-difficulty-chart With so many questions about miner cost influencing supply and thus price, I'd like to hear your thoughts. If hashpower doubles again, the price support will likely gone up? Seeing as the 2014 crash had essentially no miner investment on this scale, its logical to assume that this is a game changer that continues to evolve. Even the people getting free hydro will start to be squeezed out with these difficulty levels. It reminds me of the way the diamond miners can control supply to influence price. Thoughts?
BTC is Quickly Losing Investor Appeal - Here's One Factor Why
BTC mining difficulty is accelerating in it's increase. BTC miners control the fate of BTC & hold a massive proportion of BTC (unlike ETH). BTC has no transition to proof of stake planned. As mining difficulty increases rapidly certain mining pools will shut down. Any semblance of democratized control will be lost. Mining will quickly become near completely centralized to Chinese/Asian mining farms. All protocol decisions will be decided by them. Chinese mining farms evidently don't care about the tech or the ecosystem. They care about profiting off of easy price manipulation, long & short. The is awful for the BTC ecosystem, it's prospects, and it's fate. It may well ruin investor perception & the price of BTC. https://www.coinwarz.com/difficulty-charts/bitcoin-difficulty-chart
Broader market participants are only just beginning to realize this. And only recently have powerful BTC alternatives have emerged.
[uncensored-r/Bitcoin] Simple proof this is a coordinated attack against Bitcoin
The following post by yooooooolo is being replicated because the post has been silently removed and some comments within it have been silently removed. The original post can be found(in censored form) at this link: np.reddit.com/ Bitcoin/comments/7cctoc The original post's content was as follows:
Hello there, I am in my last year of the program and like all of you I need to write an Extended Essay about a topic of my choosing. After various nights of stress and a few "aha" moments I picked out CompSci ( I like computers so this should be easy, right .... WRONG! ) In the field of CompSci I chose the topic of Cryptography (FML) more specifically the Proof-of-Work concept and its use of computational power. It sounds very impressive and dandy but I am stuck, very stuck... I picked out a subject that is out of my grasp, but is all too late and I only have a few weeks left until I am required to hand in my EE. Here comes my questions: 1) I am not doing any CompSci at school, I only picked the topic because I like it and I have been around computers since a I was a little lad, I know how they work internally and a few programming languages including C++ and Java. 2) Will the people that read my EE, grade me on the contents while keeping in mind I did all the research and learned "CompSci" by myself, or will they grade it like any other alumni who is doing his/her EE on CompSci while studying in school? 3) In order to elaborate a comprehensive conclusion I need to create a small peace of software that will help me monitor the different temps in my system under very specific circumstances. Will the reader also grade me on my effort to build such a software? Or am I just loosing my time trying to make one? For me writing a 4k word essay on Crypto is very easy the hard part and the only time consuming out of all this is the creating the necessary program. If the answer to question 3 is no, for my EE do I have to have any formulas/programs or can I use information that is publicly available to elaborate my conclusion (EX. The Bitcoin difficulty charts and estimation based on your computer setup). Thank you in advance.
The Bitcoin difficulty chart provides the current Bitcoin difficulty (BTC diff) target as well as a historical data graph visualizing Bitcoin mining difficulty chart values with BTC difficulty adjustments (both increases and decreases) defaulted to today with timeline options of 1 day, 1 week, 1 month, 3 months, 6 months, 1 year, 3 years, and all time Bitcoin simply needs history to repeat itself to see significant price rises, according to two indicators now flipping bullish.On Sep. 28, on-chain monitoring resource Glassnode noted that Bitcoin’s difficulty ribbon compression had broken out of its green “buy” zone for the first time since the March coronavirus crash.. Glassnode hints at “significant” BTC price increases The difficulty is a measure of how difficult it is to mine a Bitcoin block, or in more technical terms, to find a hash below a given target. A high difficulty means that it will take more computing power to mine the same number of blocks, making the network more secure against attacks. Bitcoin difficulty ribbon compression historical chart showing buy zone breakouts. Source: Glassnode. $145,000 by 2022? Another chart doing the rounds on cryptocurrency Twitter this week is the spot volume currency index from BitWise. Difficulty is re-calculated every 2016 blocks to ensure blocks are found every 10 minutes on average. As more computers attempt to mine Bitcoin Core (BTC) and increase the Hash Rate, the difficulty will increase. If the Hash Rate decreases, difficulty will decrease.
Mining Bitcoin or Ethereum is a hard task for your computer. But why? And what does the difficulty have to do with the security of blockchains? Learn all abo... and.. there it is my own dc DON'T CLICK THIS!!! https://www.youtube.com/channel/UC2L9_OTurArowTkPi0GTrOQ?sub_confirmation=1 FOLLOW US ROBLOX https://ww... In today's video I tried out these new obby games that recently appeared on Roblox called Difficulty Chart obbies. These obbies are all similar because they ... In this video I completed All Stages Wrap Around Difficulty Chart, a new difficulty chart similar to the Wallhop Difficulty Chart but for Wraparounds. 🔴SUBSC... The Difficluty Chart Obby - https://www.roblox.com/games/4682718683/The-Difficulty-Chart-Obby-WIP?refPageId=b99cbd43-dc33-4b59-82e1-f0fa2589bc9a This is a vi...