Author

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

legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
DigiByte Core v4.0.3 page download is not available
What language are you accessing?
sr. member
Activity: 469
Merit: 260
DigiByte Core v4.0.3 page download is not available
sr. member
Activity: 254
Merit: 250
Exchanges running Digibyte-Digispeed 4.0.3


-www.litepaid.com
-www.litebit.eu



Pools running Digibyte-Digispeed 4.0.3

-www.digihash.co
-http://infernopool.com/
-http://www.miners-pool.eu/  - Qubit, Groestl and Skein
-http://ispace.co.uk/
-https://www.suprnova.cc/
-https://digibyte-groestl.miningpoolhub.com/
-https://digibyte-qubit.miningpoolhub.com/
-https://digibyte-skein.miningpoolhub.com/



-This list will get quoted and updated.


TBF is also up to date:

https://dgb-groestl.theblocksfactory.com/ => Digibyte(Skein) is wrong in description. Pool side have to correct it!
https://dgb-scrypt.theblocksfactory.com/
https://dgb-sha.theblocksfactory.com/
https://dgb-skein.theblocksfactory.com/
https://dgb-qubit.theblocksfactory.com/

ALL HAVE: Daemon Version   4.0.3.0

I dont know if this one already up to date. No info for me!

http://dgb.idcray.com/index.php
hero member
Activity: 756
Merit: 500
Community Liaison,How can i help you?
legendary
Activity: 1456
Merit: 1006
Mining Pool Hub
Exchanges running Digibyte-Digispeed 4.0.3


-www.litepaid.com
-www.litebit.eu



Pools running Digibyte-Digispeed 4.0.3

-www.digihash.co
-http://infernopool.com/
-http://www.miners-pool.eu/  - Qubit, Groestl and Skein
-http://ispace.co.uk/
-https://www.suprnova.cc/


-This list will get quoted and updated.


These pools are also running 4.0.3 currently.

https://digibyte-groestl.miningpoolhub.com/
https://digibyte-qubit.miningpoolhub.com/
https://digibyte-skein.miningpoolhub.com/


Thanks.
hero member
Activity: 756
Merit: 500
Community Liaison,How can i help you?
Exchanges running Digibyte-Digispeed 4.0.3


-www.litepaid.com
-www.litebit.eu



Pools running Digibyte-Digispeed 4.0.3

-www.digihash.co
-http://infernopool.com/
-http://www.miners-pool.eu/  - Qubit, Groestl and Skein
-http://ispace.co.uk/
-https://www.suprnova.cc/
-https://digibyte-groestl.miningpoolhub.com/
-https://digibyte-qubit.miningpoolhub.com/
-https://digibyte-skein.miningpoolhub.com/
https://dgb-groestl.theblocksfactory.com/
https://dgb-scrypt.theblocksfactory.com/
https://dgb-sha.theblocksfactory.com/
https://dgb-skein.theblocksfactory.com/
https://dgb-qubit.theblocksfactory.com/



-This list will get quoted and updated.

full member
Activity: 157
Merit: 100
Pro Tip:

Those guys who are interesting in selling dgb, I would buy up dgb worth 10 btc at 36 sat.


If any are interested, it is a very good offer since dumping dgb worth 10 btc would cause a price at 30 sat.

So you make a nice profit selling to me at 36.

Only a stake of dgb worth 10 btc will be accepted.

Warning: people who are going to accept this offer, use a trusted escrow. You never know who's behind the nickname.
legendary
Activity: 1218
Merit: 1003
The community and dev team of $DGB is outstanding. The effort and strengthness is amazing. And not long time ago there was the run of speculators, who thought this is the next big thing and pumped it up to 1000 sat, not joking, 1000 sat. These silly speculators were burned and that is great. The early adopters made money on this pump but not the pumpers.

Since pumpers do not care about long term investment, they decided to take large losses and sell their bags. That is why we have the pre pump price level at the moment.

The current distribution is very healthy and there are no large whales anymore, which ho,d dgb only for more btc.

Digibyte with the new digispeed feature will attack litecoin in the sense of market cap, there is no doubt on that.

I would like the dev specialist of CLAMS to take a look on the code and help to develop it further, I would donate $100 for that.






A few more fake posts to get on the next page and my question can be ignored for a 2nd time.
most people can't even see you because they have already pressed the ignore feature of the forum. I am however, not ignoring you as much as wondering if I'd be wasting my time trying to answer you questions. What is your point?

The point is I am looking for accuracy with regards to the update because the big selling point was the propagation changes based on microsoft research because without it digispeed is nothing more then changing 30 seconds to 15 seconds and a reduction in reward per block. I am not saying this cause problems, I am only seeking the truth because if the propagation changes are still intact it is something for myr to consider using.
Well I can’t answer your question anyway, I never knew what that bit meant or if basing anything on Microsoft research sounded like a smart thing to do in the first place but I will try to find out now you bring it up.
That also means, I never considered it to be a big selling point.
I’m glad to see you looking for ways to improve MYR though, the coin is a real steal right now in terms of price, especially if it is in anyway like DigiByte and you assure me it is. Just goes to show how blind a market can be.
You really ought to spend more time doing positive things in your community though because we are not the enemy and this is not ‘Highlander’, “There can be only one!”.

I’m sure Jared will be happy to elaborate on the situation at some point but in the mean time it is quite important that we get the whole of Digibyte community onto the latest version after the hard fork, so that we can smooth out a few ripples. 4.0.3 DigiSpeed, latest release everybody!
full member
Activity: 127
Merit: 100
Pro Tip:

Those guys who are interesting in selling dgb, I would buy up dgb worth 10 btc at 36 sat.


If any are interested, it is a very good offer since dumping dgb worth 10 btc would cause a price at 30 sat.

So you make a nice profit selling to me at 36.

Only a stake of dgb worth 10 btc will be accepted.

Make it 50 and you have a deal.  Grin Grin Grin Grin
full member
Activity: 238
Merit: 100
Pro Tip:

Those guys who are interesting in selling dgb, I would buy up dgb worth 10 btc at 36 sat.


If any are interested, it is a very good offer since dumping dgb worth 10 btc would cause a price at 30 sat.

So you make a nice profit selling to me at 36.

Only a stake of dgb worth 10 btc will be accepted.
legendary
Activity: 1218
Merit: 1003
The community and dev team of $DGB is outstanding. The effort and strengthness is amazing. And not long time ago there was the run of speculators, who thought this is the next big thing and pumped it up to 1000 sat, not joking, 1000 sat. These silly speculators were burned and that is great. The early adopters made money on this pump but not the pumpers.

Since pumpers do not care about long term investment, they decided to take large losses and sell their bags. That is why we have the pre pump price level at the moment.

The current distribution is very healthy and there are no large whales anymore, which ho,d dgb only for more btc.

Digibyte with the new digispeed feature will attack litecoin in the sense of market cap, there is no doubt on that.

I would like the dev specialist of CLAMS to take a look on the code and help to develop it further, I would donate $100 for that.






A few more fake posts to get on the next page and my question can be ignored for a 2nd time.
most people can't even see you because they have already pressed the ignore feature of the forum. I am however, not ignoring you as much as wondering if I'd be wasting my time trying to answer you questions. What is your point?
legendary
Activity: 952
Merit: 1000
Also, anyone that is having syncing issues can you post the tail of your debug.log? Or send it to dev (at) digibyte.co?

Cheers

Wallet only syncs every now and then. When you leave the wallet open for a long time, it will sync fully in the end, but with bumpy syncing and can take a long time. Only when once fully synced, then all the next blocks are picked up well imediately. When it stopped syncing in between before that point, this is what i find in the debug log at the end:

2015-12-10 11:04:58 UpdateTip: new best=c867c5a0826528048a546d267e1a9c19ee4364d489e0ce0ae4c79b9763d07267  height=1462822  log2_work=71.392937  tx=2978816 algo=3  date=2015-12-10 06:30:16 progress=0.999911
2015-12-10 11:04:58 ProcessBlock: ACCEPTED
2015-12-10 11:04:58 ProcessBlock: ORPHAN BLOCK 384, prev=000000000000052df225997059d1ea8215a9eb54713c8d355082829b3ab59be5
2015-12-10 11:04:58 ProcessBlock: ORPHAN BLOCK 385, prev=a9ef3f167888bde0bcd3ba269903b8b566ce73e36f190c3bd63b325443da35e9
2015-12-10 11:04:58 ProcessBlock: ORPHAN BLOCK 386, prev=b786c8946083d1eec4ed4cb0e23b5adb86ad48c1c8b249a36ed35eb4a8f41399
2015-12-10 11:04:58 ProcessBlock: ORPHAN BLOCK 387, prev=e9cbd5a5c6df0121eedb1af90c0027026bfb5179c6c89ea19a895dc649063e8f
2015-12-10 11:04:59 ProcessBlock: ORPHAN BLOCK 388, prev=00000000000004a244f9536b3a164ae2478e06247c9760b289a39f3061de8177
2015-12-10 11:04:59 ProcessBlock: ORPHAN BLOCK 389, prev=000000000000060c0cdf7a8f551497b0a52af32bb1e894e0b688d3d00c654254
2015-12-10 11:04:59 ProcessBlock: ORPHAN BLOCK 390, prev=00000000000004e8ece0fae86b0395a54fad9bab5125a7c0e5de32890cafd471
2015-12-10 11:04:59 ProcessBlock: ORPHAN BLOCK 391, prev=34e7a3961875f044f7bb9b241a04b6607294938c0148a5998e6a4292daecef92
2015-12-10 11:04:59 ProcessBlock: ORPHAN BLOCK 392, prev=c8bf9ff5a1f4dae2b82d3a4232218e45d49e5ff9c3e309df16933b2c33522259
2015-12-10 11:04:59 ProcessBlock: ORPHAN BLOCK 393, prev=3f7ec519b01db4d208ee9314acd197f91e778588e0957c3a374a5a2db472417d
2015-12-10 11:04:59 ProcessBlock: ORPHAN BLOCK 394, prev=15feb245ed350a014dd08878aad8075e6a89a2729906beba1452e71d55c7c091
2015-12-10 11:04:59 ProcessBlock: ORPHAN BLOCK 395, prev=fa999d355fe2a76947af044724ad221063b911f086079ab4440e4a0206f5eecc
2015-12-10 11:04:59 ProcessBlock: ORPHAN BLOCK 396, prev=9e47e9e6374b20909a83d24eb810dedeb4543b5961d08622df7b94c3aaed6987
2015-12-10 11:04:59 ProcessBlock: ORPHAN BLOCK 397, prev=1db268f95619816982f0b17c06047abae34363f8c4bce42a048f2242fbfd481b
2015-12-10 11:05:00 ProcessBlock: ORPHAN BLOCK 398, prev=ced199beb7ec9c0c7c3a1fb84fd2d1cea9bb31189c42e5944479e9836c51bb1f
2015-12-10 11:05:21 ProcessBlock: ORPHAN BLOCK 399, prev=513e7c3c4f411583705573b10bce553f4a1a96ac6e0b1ef38d26794f005b64cd

Remember to run "digibyte-qt -reindex" if you are having syncing issues.

I test the reindex now. Reindexing itself is a bumpy ride too and goes very slowly, with a lot of very long pauses in syncing. Will let you know in the end what is the result Wink

Edit: It took about 1,5 hours to reindex. Later tonight or tomoorow i will open the wallet again to see if syncing is better now.
full member
Activity: 238
Merit: 100
The community and dev team of $DGB is outstanding. The effort and strengthness is amazing. And not long time ago there was the run of speculators, who thought this is the next big thing and pumped it up to 1000 sat, not joking, 1000 sat. These silly speculators were burned and that is great. The early adopters made money on this pump but not the pumpers.

Since pumpers do not care about long term investment, they decided to take large losses and sell their bags. That is why we have the pre pump price level at the moment.

The current distribution is very healthy and there are no large whales anymore, which ho,d dgb only for more btc.

Digibyte with the new digispeed feature will attack litecoin in the sense of market cap, there is no doubt on that.

I would like the dev specialist of CLAMS to take a look on the code and help to develop it further, I would donate $100 for that.




hero member
Activity: 756
Merit: 500
Community Liaison,How can i help you?
hero member
Activity: 756
Merit: 500
Community Liaison,How can i help you?
Exchanges running Digibyte-Digispeed 4.0.3


-www.litepaid.com
-www.litebit.eu
-www.bittrex.com
-www.poloniex.com


Pools running Digibyte-Digispeed 4.0.3

-www.digihash.co
-http://infernopool.com/
-http://www.miners-pool.eu/  - Qubit, Groestl and Skein
-http://ispace.co.uk/
-https://www.suprnova.cc/
-https://digibyte-groestl.miningpoolhub.com/
-https://digibyte-qubit.miningpoolhub.com/
-https://digibyte-skein.miningpoolhub.com/
-https://dgb-groestl.theblocksfactory.com/
-https://dgb-scrypt.theblocksfactory.com/
-https://dgb-sha.theblocksfactory.com/
-https://dgb-skein.theblocksfactory.com/
-https://dgb-qubit.theblocksfactory.com/
-http://www.miners-pool.eu
-https://miningpoolhub.com/

-This list will get quoted and updated.
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
Alright everyone lets make sure all mining pools and exchanges are on 4.0.3! After looking at some peoples debug logs we are still getting interference from v3 wallets. The sooner we get everyone on v4.0.3 the sooner we are back to normal.

Lets start a list of 4.0.3 updated pools and exchanges.

Remember to run "digibyte-qt -reindex" if you are having syncing issues.

★★ Introducing DigiByte 极特币 v4.0.3 DigiSpeed★★

DigiByte Core v4.0.3 Wallets & Source

 

We are still working on the OS X compile. We are sorting through some bugs. Stay tuned. Cheers.

4.0.3 Release Notes:
*Disconnects all v3 clients
*Adds checkpoint to make sure everyone is on the same chain
*Block propagation relay changes

4.0.0 Release Notes:
* Changes occur @ block 143,000
* 15 Second Blocks
* Scalability to match Visa TPS by 2021 & continued scaling through 2035 (See scalability projections here)
* Minimum TX & Relay Fee set to 1 DGB to prevent attacks
* MultiAlgo Difficulty adjustment code changed to make 51% attack much, much harder (See commit explanation)
* Transaction propagation changes based upon Microsoft research
* Reward adjusted to accommodate faster blocks, still stays the same (21 billion DGB in 21 years)
* OP_RETURN data increased to 80 bytes to allow embedding more data (like document hashes)
* Safe mode warning error fixed
* Check point added
* Private key compatibility issue fixed ( addresses from the DGB paper wallet address generator now work properly)
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
I had the same problem with another wallet, syncing issues, turned out to be the clock on my pc that was wrong.

Yes, this can be a problem as well.
member
Activity: 109
Merit: 10
DigiByte
I had the same problem with another wallet, syncing issues, turned out to be the clock on my pc that was wrong.
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
Yep, I'm still stuck on 43 weeks. Upgraded wallet to 4.0.3

Windows 64-bit client

I had a 64-bit client get stuck there but I restarted wallet and it was ok after that but there is still something not right.

If you simply mean closing the wallet and then starting it up, then I've tried that may times. :-(
Please start the wallet with the -reindex or -rescan flag.

On windows navigate to the folder where the main digibyte-qt is installed (program files). Cltr right click and you will have an option that says "open command window here." Execute the command "digibyted-qt -reindex" and the wallet should start re syncing.

Does everyone have an exact block height they are having issues with?


For Windows you need to hold SHIFT and right click the DigiByte Folder in \ProgramFiles.
And the command should be "digibyte-qt -reindex"
I'm currently resyncing now
Yes, thank you for the correction. Just caught the "digibyted" typo (old server habits die hard) Smiley

digibyte-qt -reindex

This command restarts the wallet and reindexs the entire chain to fix any reorgs or conflicts the sync process may be experiencing.
newbie
Activity: 43
Merit: 0
Yep, I'm still stuck on 43 weeks. Upgraded wallet to 4.0.3

Windows 64-bit client

I had a 64-bit client get stuck there but I restarted wallet and it was ok after that but there is still something not right.

If you simply mean closing the wallet and then starting it up, then I've tried that may times. :-(
Please start the wallet with the -reindex or -rescan flag.

On windows navigate to the folder where the main digibyte-qt is installed (program files). Cltr right click and you will have an option that says "open command window here." Execute the command "digibyted-qt -reindex" and the wallet should start re syncing.

Does everyone have an exact block height they are having issues with?

For Windows you need to hold SHIFT and right click the DigiByte Folder in \ProgramFiles.
And the command should be "digibyte-qt -reindex"
I'm currently resyncing now
Jump to: