question, does the new wallet cointains DifficultyShield?
and if, at which block will this happen?
and if, at which block will this happen?
Yes. 16300.
Topic: [LTCD] LitecoinDark.com ★ Scrypt ★ Difficulty Shield ★ Multipool ★ Fast - page 306. (Read 368578 times)
September 16, 2014, 02:11:47 AM
Yes. 16300.
September 16, 2014, 02:09:54 AM
question, does the new wallet cointains DifficultyShield?
and if, at which block will this happen?
and if, at which block will this happen?
September 16, 2014, 01:44:44 AM
Ok. Win32 build complete. A quick rundown of what happened for anyone interested:
Straight gitian build broke. Hard. Tried to fix the base-vm image (trusty, amd64) and soon realized the issue was hardware, not software. Something happened to my build server at the worst possible time. Set up a temporary build server on a VM and started compiling by hand only to realize there were link issues due to host incompatibility. Recompiled all dependencies by hand, recompiled windows qt wallet and windows daemon by hand.
Long story short, I had some unforseen issues due to a broken server that I will have to wait until wednesday to deal with. Here's the release:
https://github.com/TrollByFire/litecoindark-staging/releases/tag/v1.1.0-pre1
Windows users: Grab the .zip
Linux users: Grab the .tar.gz and compile as usual.
Please note that DifficultyShield makes use of C++11 features and requires a minimum GCC version 4.8.0 in order to compile, and 4.9.0 or later is recommended.
Also note that I cannot upload this to the main website myself and/or tweet about it: This will have to be done by Robbert once he is awake/online. Timezones.
Straight gitian build broke. Hard. Tried to fix the base-vm image (trusty, amd64) and soon realized the issue was hardware, not software. Something happened to my build server at the worst possible time. Set up a temporary build server on a VM and started compiling by hand only to realize there were link issues due to host incompatibility. Recompiled all dependencies by hand, recompiled windows qt wallet and windows daemon by hand.
Long story short, I had some unforseen issues due to a broken server that I will have to wait until wednesday to deal with. Here's the release:
https://github.com/TrollByFire/litecoindark-staging/releases/tag/v1.1.0-pre1
Windows users: Grab the .zip
Linux users: Grab the .tar.gz and compile as usual.
Please note that DifficultyShield makes use of C++11 features and requires a minimum GCC version 4.8.0 in order to compile, and 4.9.0 or later is recommended.
Also note that I cannot upload this to the main website myself and/or tweet about it: This will have to be done by Robbert once he is awake/online. Timezones.
September 16, 2014, 01:35:31 AM
What are you talking about guys? Where is new wallet version? On litecoindark.com website there is same 1.0.1 version. Then where is 1.1.0 if I need to download? Give me a direct download link.
Take it easy, didnt you see what Troll said ?
September 16, 2014, 01:35:13 AM
What are you talking about guys? Where is new wallet version? On litecoindark.com website there is same 1.0.1 version. Then where is 1.1.0 if I need to download? Give me a direct download link.
not out yet but as soon as its the dev is done with it . He will post a link here probably at the op opening page of the forum.
September 16, 2014, 01:32:55 AM
What are you talking about guys? Where is new wallet version? On litecoindark.com website there is same 1.0.1 version. Then where is 1.1.0 if I need to download? Give me a direct download link.
September 16, 2014, 01:18:52 AM
I'm still having trouble getting any connections or blocks on the command line version I compiled on Debian 7.6. It seems that people connect for a second at a time then disconnect, and no blocks ever get downloaded. I have added all the peers listed in the few posts in this thread. Does anyone have suggestions?
Clone from the staging repository and checkout master or checkout the ltcd-1.0.1 branch (or litecoindark-1.0.1 tag) on your local clone. Master branch is never guaranteed to be stable. Releases are built from their own branch and tag. Sounds like you're getting connections that you are dropping due to protocol version numbers not matching. We didn't need to update the protocol version in 1.0.1 (nor has it changed in 1.1.0) and these changes were reverted and a newer code base will fix your problem
Code:
Building LevelDB ...
make[1]: Entering directory `/home/litecoindark/litecoindark-staging/src/leveldb'
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -DBOOST_NO_CXX11_SCOPED_ENUMS -I/home/litecoindark/litecoindark-staging/src -I/home/litecoindark/litecoindark-staging/src/obj -DUSE_UPNP=1 -DUSE_IPV6=1 -I/home/litecoindark/litecoindark-staging/src/leveldb/include -I/home/litecoindark/litecoindark-staging/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -std=c++1y -c db/builder.cc -o db/builder.o
g++: error: unrecognized command line option ‘-std=c++1y’
make[1]: *** [db/builder.o] Error 1
make[1]: Leaving directory `/home/litecoindark/litecoindark-staging/src/leveldb'
make: *** [leveldb/libleveldb.a] Error 2
Try this:
Code:
chmod a+x ./leveldb/build_detect_platform
September 16, 2014, 01:16:27 AM
any update today / this week?
September 16, 2014, 12:55:07 AM
any news on whats happening 
September 15, 2014, 11:55:04 PM
Cloning from the staging repo is now 1.1.0-pre1. You need GCC 4.8.0 or better (recommend 4.9.0) to compile it. -std=c++1y isn't supported by the default GCC in debian 7.
September 15, 2014, 11:43:40 PM
I'm still having trouble getting any connections or blocks on the command line version I compiled on Debian 7.6. It seems that people connect for a second at a time then disconnect, and no blocks ever get downloaded. I have added all the peers listed in the few posts in this thread. Does anyone have suggestions?
Clone from the staging repository and checkout master or checkout the ltcd-1.0.1 branch (or litecoindark-1.0.1 tag) on your local clone. Master branch is never guaranteed to be stable. Releases are built from their own branch and tag. Sounds like you're getting connections that you are dropping due to protocol version numbers not matching. We didn't need to update the protocol version in 1.0.1 (nor has it changed in 1.1.0) and these changes were reverted and a newer code base will fix your problem
Code:
Building LevelDB ...
make[1]: Entering directory `/home/litecoindark/litecoindark-staging/src/leveldb'
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -DBOOST_NO_CXX11_SCOPED_ENUMS -I/home/litecoindark/litecoindark-staging/src -I/home/litecoindark/litecoindark-staging/src/obj -DUSE_UPNP=1 -DUSE_IPV6=1 -I/home/litecoindark/litecoindark-staging/src/leveldb/include -I/home/litecoindark/litecoindark-staging/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -std=c++1y -c db/builder.cc -o db/builder.o
g++: error: unrecognized command line option ‘-std=c++1y’
make[1]: *** [db/builder.o] Error 1
make[1]: Leaving directory `/home/litecoindark/litecoindark-staging/src/leveldb'
make: *** [leveldb/libleveldb.a] Error 2
make[1]: Entering directory `/home/litecoindark/litecoindark-staging/src/leveldb'
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -DBOOST_NO_CXX11_SCOPED_ENUMS -I/home/litecoindark/litecoindark-staging/src -I/home/litecoindark/litecoindark-staging/src/obj -DUSE_UPNP=1 -DUSE_IPV6=1 -I/home/litecoindark/litecoindark-staging/src/leveldb/include -I/home/litecoindark/litecoindark-staging/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -std=c++1y -c db/builder.cc -o db/builder.o
g++: error: unrecognized command line option ‘-std=c++1y’
make[1]: *** [db/builder.o] Error 1
make[1]: Leaving directory `/home/litecoindark/litecoindark-staging/src/leveldb'
make: *** [leveldb/libleveldb.a] Error 2
September 15, 2014, 11:28:10 PM
Running a bit behind. Build server is giving some issues. Please bear with me.
no problem just mining these slow blocks lol but we have to get though them.
September 15, 2014, 11:27:55 PM
Please update source link in OP!
best-pool wallet will be updated soon.... (certainly before block 16300)
best-pool wallet will be updated soon.... (certainly before block 16300)
September 15, 2014, 10:45:44 PM
Running a bit behind. Build server is giving some issues. Please bear with me.
September 15, 2014, 09:55:55 PM
i only know about ,qt and exe 
if you have a exsiting wallet make a back up of the wallet.dat. before updating
already back up,..but after i download this file and extract,..what can i do next?
basically you launch it then close it down make sure its not running and copy the wallet.dat back and start and it should sync up.
Might take a few minutes to start syncing post-update. I'm also updating dns seed nodes. this will go away on its own and start working, just be patient.
ok,.i prefer to wait you update in website,.
because i confused how to set up files like this..like i said only know with qt or exe....
just download qt and exe,run...finish
September 15, 2014, 09:53:04 PM
very very nice, software development activities have been detected
3% premine has not been released
doing quick git pull and build, this is exactly what has been happening with SYNC, congrats so far, very nice
KNC miners are just around the corner you have till 4 QT but distribution is holding, you have a big one on your hands dont screw it up
git pull
Already up-to-date. (from LTCD master)
will try it tomorrow , no rush, thanks and talk soon
3% premine has not been released
doing quick git pull and build, this is exactly what has been happening with SYNC, congrats so far, very nice
KNC miners are just around the corner you have till 4 QT but distribution is holding, you have a big one on your hands dont screw it up
git pull
Already up-to-date. (from LTCD master)
will try it tomorrow , no rush, thanks and talk soon
Use staging repo. Rob's repo (official) is updated behind mine as we're on separate continents and timezones are hard.
September 15, 2014, 09:51:41 PM
i only know about ,qt and exe
if you have a exsiting wallet make a back up of the wallet.dat. before updating
already back up,..but after i download this file and extract,..what can i do next?
basically you launch it then close it down make sure its not running and copy the wallet.dat back and start and it should sync up.
Might take a few minutes to start syncing post-update. I'm also updating dns seed nodes. this will go away on its own and start working, just be patient.
so can I use my same conf. file as well or will there be one included that is updated.
same config. I have to stop posting now until finished. to many things going on at once. Will do a round of tech support Q&A posts afterwards.
September 15, 2014, 09:50:17 PM
I have never updated once, never added any nodes to my conf file and i still get 8 active connections and it syncs after 10 sec of opening my wallet. Why is this?
September 15, 2014, 09:48:50 PM
i only know about ,qt and exe
if you have a exsiting wallet make a back up of the wallet.dat. before updating
already back up,..but after i download this file and extract,..what can i do next?
basically you launch it then close it down make sure its not running and copy the wallet.dat back and start and it should sync up.
Might take a few minutes to start syncing post-update. I'm also updating dns seed nodes. this will go away on its own and start working, just be patient.
so can I use my same conf. file as well or will there be one included that is updated.
September 15, 2014, 09:44:16 PM
i only know about ,qt and exe
if you have a exsiting wallet make a back up of the wallet.dat. before updating
already back up,..but after i download this file and extract,..what can i do next?
basically you launch it then close it down make sure its not running and copy the wallet.dat back and start and it should sync up.
Might take a few minutes to start syncing post-update. I'm also updating dns seed nodes. this will go away on its own and start working, just be patient.
Jump to: