Topic: [ANN] Kryptohash | Brand new PoW algo | 320bit hash | ed25519 | PID algo for dif - page 45. (Read 149454 times)

this logic is fucking stupid,I am merely a miner and investor ,but I have the right to question.

If your as good a coder as you are a critic, then get off your hands and fix it yourself.

DEV,any responde to my question??

If you wannt bet,you have a slim chance to win ,I don't want to win you  soo easily.

you got nothing  
you'll see

Thanks for your patience.  We are working on a solution.

I'll have an update in next couple of hours.

yeah,you are right,sb just do it intentionally.

Instamine can be a side effect of these forks but we'll never know if it is intentional or not.

hours has ALREADY passed,what do you say

To be honest,I've mined 20K+ KHC,but now I feel a little frustrated,why this coin updated over and over again??!! for what?? to let dev use 6 cards to mine more coins to compasite his effort?? or something else??!!!  I don't know waht it is.

what do you want to say !!! just tell us the result  plz,I need to mine correctly.

Yes, db-5.3.28.NC


To build Kryptohash Windows wallets, you need to follow the steps on this thread https://bitcointalksearch.org/topic/building-headless-bitcoin-and-bitcoin-qt-on-windows-149479 for Bitcoin 0.9.3

But, with three changes.  

1) Boost 1.57 MUST be compiled with c++11 option :

b2 --build-type=complete --with-chrono --with-filesystem --with-program_options --with-system --with-thread toolset=gcc variant=release link=static threading=multi runtime-link=static stage cxxflags="-std=c++11" target-os=windows architecture=x86 address-model=64

2) Compile db-5.3.28.NC instead of db-4.8.30.NC

cd db-5.3.28.NC/build_unix
../dist/configure --enable-mingw --enable-cxx --disable-shared --disable-replication
make

3) Run the following configure

CPPFLAGS="-Ikeccak \
-Ikeccak/SnP \
-Ikeccak/KeccakF-1600 \
-I/c/deps64/boost_1_57_0 \
-I/c/deps64/db-5.3.28.NC/build_unix \
-I/c/deps64/openssl-1.0.1j/include \
-I/c/deps64 \
-I/c/deps64/protobuf-2.5.0/src \
-I/c/deps64/libpng-1.6.14 \
-I/c/deps64/qrencode-3.4.4" \
LDFLAGS="-L/c/deps64/boost_1_57_0/stage/lib \
-L/c/deps64/db-5.3.28.NC/build_unix \
-L/c/deps64/openssl-1.0.1j \
-L/c/deps64/miniupnpc \
-L/c/deps64/protobuf-2.5.0/src/.libs \
-L/c/deps64/libpng-1.6.14/.libs \
-L/c/deps64/qrencode-3.4.4/.libs" \
./configure \
--disable-upnp-default \
--disable-tests \
--with-qt-incdir=/c/Qt64/5.3.2/include \
--with-qt-libdir=/c/Qt64/5.3.2/lib \
--with-qt-bindir=/c/Qt64/5.3.2/bin \
--with-qt-plugindir=/c/Qt64/5.3.2/plugins \
--with-boost-system=mgw49-mt-s-1_57 \
--with-boost-filesystem=mgw49-mt-s-1_57 \
--with-boost-program-options=mgw49-mt-s-1_57 \
--with-boost-thread=mgw49-mt-s-1_57 \
--with-boost-chrono=mgw49-mt-s-1_57 \
--with-protoc-bindir=/c/deps64/protobuf-2.5.0/src

think about it

yes,you will.There must be a hard fork in the next version wallet,in this case,what you have mined now will be nothing,otherwise this coin is doomed to die.

you are not on the right fork,you'll get nothing .

This is going to solved within the next 2 - 3 hours.  Stay tuned.

Everybody stop mining now,we need to wait for the Dev to fix the wallet !!

My wallet doesn't for some reason. Maybe yours has peers with the correct blockchain in list.

It seems the fork was caused by people with older wallet 0.3.8

In hindsight, I should have made 0.3.9 mandatory released and reject older 0.3.8 connections.

Lesson learned.
 

Mine was stuck at 9160 and after restarting the wallet I have no connections.

So I'd suggest everyone not to close the wallet if you are mining.