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

C:/users/YourUser/AppData/Roaming/DigiByte


The DigiByte block chain is much smaller so there is less to download. But we have also set up some high speed dns seed servers. We are in the process of setting up two more so there will be 4 total.

Where is this digibyte.conf file in windows located?

I am amazed as to how fast the Digibyte block chain syncs, is there anything special about how DGB does things or is it based on the number of transactions in the blockchain?

,./,./,

Thanks for the feedback. Does the wallet sync with the net?

We are working on the icon issue. Will also get on the wallet language translation issues later. If you could supply what the translation should be in a list that would be great.

Example:
Bitcoinadres= DigiByteadres?
Bitcoinnetwerk=DigiBytenetwerk?

Ok, it's re-syncing again now. Will report back shortly.

\



image is not good....

en = een

bitcoin = digibyte

bitcoin = digibyte

I don't know what's = kern

munten = digibytes || bitcoinadress = digibyteadres

1) Backup your wallet.dat
2) Go to YourUser/AppData/Roaming/DigiByte
3) Delete the "blocks" & "chainstate" folders

The error with the 3.0.0 release will cause this issue. Once you delete those folders it will re-sync correctly.

Hmmm...  was hoping it was a one off, but I've now encountered this 3x post upgrade to 3.0.1. Windows 32bit.  Had no issues previously with upgrades, including the previous 3.0.0. Each time I choose OK, and it rebuilds and loads my wallet... but then if I close it down and launch again it repeats....

Post with download links moved to most current page here: https://bitcointalksearch.org/topic/m.8458035

If the chain was working as expected you would be absolutely correct. But since there have been big delays (stuck chain) we used the average over the last couple months to time the change. If we waited 10,000 blocks it could take a month for the change to occur.

we are now at block #141764
multi algo start at    #145000

145000-141764=3236 blocks

1 block = 1 minute

3236 minutes / 60 = 54 hours

52 / 24 = 2,1 days


I'm crazy? or day I made a mistake?

It will start in 2.9 days? Or do you mean has it already started?

It should take 1-2 weeks based up the current speed of the block chain for it to start.

is it right that the multi algo already started about 2.9 days?

This is correct, the diff will catch up very quickly. Plus the other algos need to produce blocks to allow for more of the sha blocks to be created.

You can adjust diff using profitability. But if you are sure that there will be no instamine, I don't care. If I right understand, no one can mine 300 blocks with some shitty SHA ASIC in a 5 minutes, right?

is it not a better Idea to set the difficulty to high than to low?


It's only a suggestion

There may be a few extra blocks, but no where near what there has been in the past with coin launches. The difficulty will adapt very, very quickly. Within a few minutes it will catch up. Think of it as an incentive to mine at the start of multi-algo. We have tested this on tesnet, it will be nothing like what people have seen in the past. DigiShield will jack up the difficulty very quickly, but this time it will average itself out over the previous 10 blocks. Plus a few other adjustments for better performance (no more stuck chain.)

We thought about changing the starting diff to something much higher, but then the problem is if we artificially raise the initial floor for the difficulty  it will not be able to go lower if needed. This can cause other problems. Since each algo is weighted differently, there is no reliable # to set things to.

We really have no idea what the "right" difficulty should be as there is no reliable way of figuring out what it should be. It is much better to let it find its natural equilibrium.

Once again, there will be a few minutes of bonus blocks for initial miners, but their is no reliable way to avoid this. Think of it as make up for the last few months of mining. We are way behind where we should be as far as coin production. This does not fit in well with our next step in progressing toward a micro payment currency (more of this will be released in the coming weeks.)

If anyone has any other suggestions before we make this the official update release, we have a few hours to make an adjustment. But at this point we do not see any better options?

I have to agree, diff should be higher.

Sorry, but WTF you are doing? There will be such instamine.

Starting difficulty is:

"difficulty_sha256d" : 0.00024414,
"difficulty_scrypt" : whatever scrypt diff is at switch over
"difficulty_groestl" : 0.00024414,
"difficulty_skein" : 0.00024414,
"difficulty_qubit" : 0.00024414,

Since we have a modified DigiShield the algo diffs will catch up rapidly to prevent an instamine (like what we saw at launch back in Jan.) Each algo will have its own difficulty.

We are working on it as we speak.


No pools are available yet, we just wanted a few more people to test the wallet before we pushed it out to the underlying infrastructure (pools, exchanges, block explorers). Only scrypt mining is available until the switchover at block 145,000. About 1-2 weeks depending on chain speed.