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.
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.
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.
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.
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.
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.
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.
Good to hear. This is why i posted that.
We have several more pools to add to the list today. Stay tuned.
Does each algo need its own daemon with own blockchain copy up and running ?
so separate digibyted, config and datadir for each algo ?
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.
good coin, why no price movement?
There will be movement down when multi-algo starts. People sold coins and waiting for 2x cheaper buy back opportunity.
This may very well be the case.
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 .
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!
Alright, I got it working!
Here's the Casheer Digibyte Acceptance thread. Please go and voice your support! This can be a huge step forward for DGB!
To quickly familiarize you, Casheer is a multi-currency, consumer-to-merchant payment platform. At the platform's core, this simply means; you can hold any currency you choose and you can pay any merchant with any currency you choose, regardless of whether that merchant accepts the currencies you hold or not.
For example: Let's say you hold bitcoins but a merchant you'd like to make a purchase from, only accepts USD. No problem. Simply send the USD equivalent of bitcoins and the payment will be automatically converted, confirmed and USD delivered to the merchant, in seconds.
This is awesome! Thank you for taking the time to get this done! Lets keep up the support here.
@dev,
I have some DGB mined at a multipool coinmine.pw and I'm quite sure the pool is still using an old wallet
My question is simple: Is it safe to withdraw my balance directly to a new v3.01 wallet before block 145K?
OR I'll have to withdraw to an old wallet first and then reinstall new wallet?
I guess both should work but I just need someone to double-confirm
Thanks
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
dev@digibyte.co 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!
