Author

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

full member
Activity: 146
Merit: 100
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?
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
,./,./,

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?
full member
Activity: 215
Merit: 100
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....

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.

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

sr. member
Activity: 392
Merit: 250
Introducing DigiByte v3.0.1 MultiAlgo
Mandatory Update before block 145,000

Ok everyone, here are the 3.0.1 download links! If we could get a few people to help us test it before making it the official release, that would be great. Try sending, receiving and see how it syncs. Also, try mining the other algos. Scrypt should be the only mine-able algo until block 145,000.

We ran it through some rigorous testing the last 24 hours so we should be good to go now! We will update the wallet language translation errors later, once we get everyone updated.

Please give us feedback if everything worked for you, especially with the OSX wallet.

It is very important we get everyone updated before block 145,000 as at that point sending coins from a v3.01 wallet to a v2.9.1 wallet or early could result in problems.



As always, backup your wallet.dat before upgrading! (File -> Backup Wallet -> Select location to save to)

Git Source:
https://github.com/digibyte/DigiByteProject

Windows x64
http://www.digibyte.co/sites/digibyte.co/files//crypto/digibyte-3.0.1-win64-setup.exe
https://dl.dropboxusercontent.com/u/42300902/DigiByte_Wallets_Current/digibyte-3.0.1-win64-setup.exe
https://mega.co.nz/#!JIhUBJSK!dTy7sKFnOKlPepr0KaaecSqoi63Dh_lTPX9AlTXoTSU

Windows x32
http://www.digibyte.co/sites/digibyte.co/files//crypto/digibyte-3.0.1-win32-setup.exe
https://dl.dropboxusercontent.com/u/42300902/DigiByte_Wallets_Current/digibyte-3.0.1-win32-setup.exe

Mac OSX
http://www.digibyte.co/sites/digibyte.co/files//crypto/DigiByte-Qt-v3.0.1.dmg
https://dl.dropboxusercontent.com/u/42300902/DigiByte_Wallets_Current/DigiByte-Qt-v3.0.1.dmg
https://mega.co.nz/#!xZYgTJJa!67Hv70W24QQWIW3mIvfeFcD5u7NsZwfkg_sotvA3bDA

You need to set the algo you want to mine in the digibyte.conf:

Code:
rpcallowip=*
rpcuser=yourusername
rpcpassword=yourpassword
server=1
daemon=1
txindex=1
debug=1
algo=scrypt
rpcport=14022
port=12024
addnode=216.250.125.121
addnode=74.208.230.160
addnode=74.112.204.202
addnode=46.4.32.220
addnode=198.27.109.88
addnode=54.204.36.33
addnode=198.41.184.140
addnode=144.76.94.182
addnode=95.85.50.188
addnode=162.159.240.70

Once multi-algo mining kicks in you need one of these settings in your .conf to solo mine whichever algo you choose:
Code:
algo=scrypt
algo=sha256d
algo=groestl
algo=qubit
algo=skein
\



image is not good....

en = een

bitcoin = digibyte

bitcoin = digibyte

I don't know what's = kern

munten = digibytes || bitcoinadress = digibyteadres
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
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....

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.
full member
Activity: 215
Merit: 100
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....
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
is it right that the multi algo already started about 2.9 days?
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.



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?

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.
sr. member
Activity: 392
Merit: 250
is it right that the multi algo already started about 2.9 days?
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.



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?
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
is it right that the multi algo already started about 2.9 days?
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.
sr. member
Activity: 392
Merit: 250
is it right that the multi algo already started about 2.9 days?
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account

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?


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?
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.
legendary
Activity: 1904
Merit: 1003

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?


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?
sr. member
Activity: 392
Merit: 250

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,


Sorry, but WTF you are doing? There will be such instamine.
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?


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


It's only a suggestion
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account

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,


Sorry, but WTF you are doing? There will be such instamine.
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?
newbie
Activity: 35
Merit: 0
I have to agree, diff should be higher.
legendary
Activity: 1904
Merit: 1003

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,


Sorry, but WTF you are doing? There will be such instamine.
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
Introducing DigiByte v3.0.1 MultiAlgo
Mandatory Update before block 145,000


Awesome. What is starting difficulty at these algos?

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.

you are the best dev of the world!

is there a mac os x wallet available?
We are working on it as we speak.

I would like to try some SHA256 hash first, what pools are ready for this?

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.
RJF
hero member
Activity: 616
Merit: 500
Online since '89...
I would like to try some SHA256 hash first, what pools are ready for this?
sr. member
Activity: 392
Merit: 250
you are the best dev of the world!

is there a mac os x wallet available?
Jump to: