Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1281. (Read 3058926 times)

We definitely agree we would like to see the new mining algos kick in as soon as possible. Starting tomorrow we will begin renting some ASICS to help speed up the process. The key is for us to coordinate a steady rise in net hash. We will outline the issue in the next response.

First off, thank you very much for putting your hash toward the network and trying to help us ll get over the hump. We dont expect anyone to mine for days on end with no return. As for the problem we have mentioned it several time over the past couple months.

The problem is not with DigiShield alone as it worked fine until we combined it with the 0.9.1 protocol in April (you can see this on several charts.) DigiShield with the 0.6 Bitcoin protocol works great for several coins still and it still works for Dogecoin. We screwed up and did not do enough testing when we released the 0.9.1 wallet. We figured since no hard fork was required everything with the difficulty adjustment would stay the same.

What basically happens with the 2.9.1 protocol is when a sudden hash spike occurs blocks are sometimes discovered only milliseconds apart. Combine this with a single block average (DigiShield only goes back to the previous block) and you get an astronomically high inflated difficulty.

The next problem is when the hash rate drops and the difficulty eventually drops it drops too low and an oscillating effect occurs & the process repeats itself.

The best way to overcome this is with a steady increase in hash, not a sudden spike. Also, a consistent hash base will be a huge improvement. Starting tomorrow we will begin adding hash to the network and we will publicly post the days target hash-rate. This will help speed things up considerably. We ask if you have some hash to contribute we could definitely use it.

We dont expect people to do this for weeks on end but if we could get a rotation going that would be great.

We have been working with our investors to give us permission to disclose the details of our funding as well as some of the stuff we have planned & we are working on. This will definitely help with this problem.


We have several more pools to add to the list today. Stay tuned.


Yes, each algo needs its own .conf as well as its own instance of the daemon. This is best handled on 1 pool with the NOMP setup.

This may very well be the case.

Once again we are working with our investors to discuss a news release. We will say we currently have an exchange running we are beta testing behind the scenes.
Thank you very much for adding the pools! Will get you on the list in a few minutes. Keeping up with messages on about 10 different sites and message formats can be very time consuming. We apologize for the delay in updating the lists!


This is awesome! Thank you for taking the time to get this done! Lets keep up the support here.
We have not received word that they have updated. Yes after block 145k there will be issues sending between v3.01 and older wallets. In fact it will be impossible to do. Everyone needs to send coins from v2.9.1 or older wallets on old pools or exchanges that have not yet updated.  

If we have missed any other questions please re-post or email [email protected] We want to make sure everyone is on the same page! Thanks again everyone for supporting DigiByte! We have some awesome things around the corner!

I have finished the Digibyte section.  It will be in the book called Cryptocurrency "The Alt-ernative" (A historical reference book).  Here is the preliminary cover (a better cover is currently being worked on):



The plan is to get the book published before Christmas 2014.  

Here is the Digibyte preview section:

https://i.imgur.com/89ERDzc.png

Any donations towards this future publication are highly welcome.  I would love to see this book become a reality.  

D8FwazAemow92sytzsynouaJWPXDZ9q6zq


Main Book Bitcointalk.org Thread is:

https://bitcointalksearch.org/topic/cryptocurrency-the-alt-ernative-beginners-reference-book-483187

Any further points which the community would like to be included in the DGB section need to be messaged to me ASAP.

wow diff is up!

I agree, I think we are getting really close to the point where if we don't push to the new algo soon I feel like we will lose our momentum.  We really need a coordinated mining effort in order to push through to the change over block.

Digibyte is not doing good on Bittrex. We need to see some volume going on there, otherwise it will be removed with the way it is added.

This could be a problem ...

I pulled all my hash from the network around block 142,410 ... it then ran ok for the next 12+ hours until block 142,473 where the difficulty has now suddenly jumped to 1,000+ the highest digibyte has ever seen... could be stuck on this block for a long time.

I could probably clear it, but am getting a bit bored throwing away my own money to push the blockchain along ... especially as the Devs have not come forward and explained the cause of the problem. Happy to support them if they come up with a solution and need hashing power, but until then I have retreated to the side lines.

Also, does anyone know of a way to monitor the DGB network hashrate? All the usual sources no longer work since the introduction of the new wallet.

Good to hear. This is why i posted that.

The pools will come. The choice to include those algo's was a good decision. Qubit is great for us Nvidia miners who like to consume less power. Its probably not very clear as to which algo most people should mine with their given hardware. A grid matrix of the advantages/disadvantage using a given algo would be nice. We need pretty visuals!

They both weren't the best choices :/

no pool for SKIEN or Qubit .....

Does each algo need its own daemon with own blockchain copy up and running ?

so separate digibyted, config and datadir for each algo ?

There will be movement down when multi-algo starts. People sold coins and waiting for 2x cheaper buy back opportunity.

People too pre-occupied with pump and dumps.

good coin, why no price movement?

I have about 5.6 MH I can point at the network to help push through it. My GPU rigs are offline now due to it being summer and the profitability sucks but I am willing to turn them back on to do a coordinated effort. 

Unfortunately, all my BTC was spent buying DGB so I wont be able to rent any hashing power =\

Great, yet expensive idea! Not many of us would be able to support you with our wallets, and that's where our problem lies.
I believe that at least when it comes to this issue, it falls on the development team to push out large amounts of MH/s, especially since they had previously siad they were going to.
6 BTC atm comes out to $3000~ dollars. That's a pretty deep price, but if it would give the coin the kindling it needs to light that 145000 block fire, it might be a necessity. The Digibyte created from the mining could then be given out over time to drum interest in DGB and to once again get miners on the coin.

  block need too much time ....

  finish a transfer need about 10+ hours ..

  even can't use it .

  so , when you will add hashes to reduce the block time..

  i think it's a seriouly problem . i know many people like dgb , and i also love it .

  but for these monthes , i can't see what's new in dgb . except multialgo , but it used to much time , 2 monthes ? 3 monthes ? 4 monthes? ,

  i also want to ask the dev , is there any plan to expand the dgb , and what's about the roadmap ? anything finished ?

  if you has plans , you can show it, after multialgo , what would do next .

  and i like to see ios wallet and digipay .

  thanks .

                                        

    
  

@Digibyte

Slow block problems

I think this needs to be sorted a.s.a.p.

At current rates block 145,000 will not kick in until late October, anyone transferring funds has to wait hours for the confirmations. Any new interest in the coin quickly diminishes when it becomes apparent the mining reward is next to zero and you have to wait hours for a block even in a pool.

The multialgo v 3.0.1 has generated a lot of interest, but this is diminishing and by the time we reach block 145,000 in October a lot of these people might have already forgotten about DGB.

The slow confirmations are also making it difficult for traders and speculators with the long waits to move funds in and out of exchanges. A combination of this, the reduction in interest and the slow rate of production has lead to the low trade volumes we are seeing.

Solving the problem

For the last week I have tried throwing a few 100 MH/s at the network in a variety of ways, building up and down slowly, short bursts, longer sustained periods etc. etc. The difficulty adjustments during this period made little sense, often decreasing as my hash increased or increasing as I reduced my hash rate. Also the increase in block production was also marginal. Can you post (or PM me) the cause of this problem? Do you know what caused it?

I think the problem is intrinsic to DIGIshield, originally I thought you may have coded a failsafe that prevented drastic reductions in difficulty which was why it was stuck oscillating at the higher difficulty ... I meant to go through your code line by line this weekend but never found the time. My main concern is that if there is an issue it is not carried over to V3.0.1.

Today I directed 5,000 MH/s at the network, which reduced the block times to c. 2 mins, but tailing off the hashrate did not reduce the difficulty... however based on this I imagine something in the region of 10 GH/s (10,000MH/s) would produce a 1 minute block time and if maintained would see us to block 145,000 in about a day and a half.

I think this is achievable through a collaborative effort, happy to direct my hash and rent a load extra if other people will help maintain the hashrate for a day and a half.

Current rental rates are roughly 0.4 BTC/GH/Day (also the amount you can earn if you didn't redirect your hash) ... so 10 GH for 1.5 days = 6 BTC... however if that returns the block rate to a block a minute, given a DGB value of 40 satoshis and a block size of 7,500 DGB ... the group should earn approx. 6.5 BTC in digibyte (A bargain if you believe in Digibyte!)

I would suggest organising a coordinated approach for Fri/Sat this week with the aim of hitting block 145,000 sometime on Sunday.

Anyone interested?

Post with download links moved to most current page here: https://bitcointalksearch.org/topic/digibytedgb-core-v61651-digishield-digispeed-segwit-408268