<<  >> (p.23)
    Author Topic: [ANN][YAC] YACoin ongoing development  (Read 380580 times)

    • dcl595
    Sr. Member
    ****
    Offline Offline

    Activity: 381
    Merit: 250


    View Profile
    June 01, 2013, 06:43:56 AM
    Last edit: June 01, 2013, 03:47:02 PM by dcl595
     #441
    Quote from: seleme on May 31, 2013, 10:42:07 PM
    colors are too soft though

    Heres a psd file so anyone can modify the colours, this one also has slightly stronger colours to start with :

    https://mega.co.nz/#!VhYm3bbT!HluFg2Gner_jFDWU4lDII2RHKg1XtvWx5CAqrb0LkCk

    Example : http://imgur.com/scPsMZi & http://imgur.com/n5oCmJO

  • WindMaster (OP)
    Sr. Member
    ****
    Offline Offline

    Activity: 347
    Merit: 250


    View Profile
    June 01, 2013, 07:03:33 AM
     #442
    Quote from: ongle on June 01, 2013, 05:21:58 AM
    If it helps anybody, last weekend I was finally able to build the client on x64 windows (using windmaster and floodyberry's github projects). I'm not sure why people say scrypt won't compile on windows, I don't recall having issues with that part.

    If you were working from floodberry's github repository, that's a newer version of the scrypt-jane library that reportedly has been corrected to compile cleanly.  Previous version did not, due to the SSE instructions.


    Quote from: ongle on June 01, 2013, 05:21:58 AM
    If nothing else it gets rid of the checkpoint message.
    ...
    I didn't post it right away because nobody knows me and I didn't want to be accused of adding malware. Maybe someone trusted in the community could check it out. If you have any doubts, don't download it please.

    Hanzac already released a 64-bit Windows build based on my GitHub repository about 2 weeks ago after I fixed the checkpoint warning.  Multiple people have checked it out and haven't observed it to do anything suspicious or unusual:
    https://bt.irlbtc.com/view/206577.msg2207446#msg2207446

  • Boing7898
    Sr. Member
    ****
    Offline Offline

    Activity: 686
    Merit: 259



    View Profile
    June 01, 2013, 08:37:53 AM
     #443
    Quote from: ongle on June 01, 2013, 05:21:58 AM
    If you are doing solo mining and have to leave it unencrypted, I suggest making two wallets and transfer coins to the encrypted wallet from time to time. As always, backup your data before running any random downloads from teh interwebs.

    Sorry if this is offtopic but can't I solo-mine with my wallet encrypted?
    My wallet is encrypted and I'm solo-mining with the minerd and I'm not getting any errors.. Huh

  • sairon
    Sr. Member
    ****
    Offline Offline

    Activity: 406
    Merit: 250


    One does not simply mine Bitcoins


    View Profile
    June 01, 2013, 10:31:56 AM
     #444
    Quote from: Boing7898 on June 01, 2013, 08:37:53 AM
    Quote from: ongle on June 01, 2013, 05:21:58 AM
    If you are doing solo mining and have to leave it unencrypted, I suggest making two wallets and transfer coins to the encrypted wallet from time to time. As always, backup your data before running any random downloads from teh interwebs.

    Sorry if this is offtopic but can't I solo-mine with my wallet encrypted?
    My wallet is encrypted and I'm solo-mining with the minerd and I'm not getting any errors.. Huh

    You won't find any block if you have your wallet encrypted and locked. Either unlock it for a long time period (walletpassphrase <pass> 99999999) or remove encryption.
    GPG key ID: 5E4F108A || BTC: 1hoardyponb9AMWhyA28DZb5n5g2bRY8v

  • ongle
    Newbie
    *
    Offline Offline

    Activity: 22
    Merit: 0


    View Profile
    June 01, 2013, 12:55:16 PM
     #445
    Quote from: Thirtybird on June 01, 2013, 05:53:21 AM
    Thank you for posting that it is possible - I've been pondering away most of the night without a terrible amount of success.  Any chance you could link me your Makefile.mingw?  I know there are some problems in there (as the included one wasn't even including scrypt-jane.o in the objects and didn't have the algorithms chosen in the compiler flags like the unix makefile has).

    The only dependancy differences I'm noting is that you used boost 1.50 and I've used boost 1.53 - I'm still getting the error I mentioned above, but now that it's actually trying to include scrypt-jane, I've got a whole host of other errors for that which don't make a lot of sense...

    Sure. This only gets you so far, have to do the qt pro build afterwards. I think I wasted a lot of time trying to build from within MSYS but ultimately ran this from CMD.

    Code:
    mingw32-make -f makefile.mingw

    Code:
    # Copyright (c) 2009-2010 Satoshi Nakamoto
    # Distributed under the MIT/X11 software license, see the accompanying
    # file COPYING or http://www.opensource.org/licenses/mit-license.php.

    USE_UPNP:=0
    USE_IPV6:=1

    INCLUDEPATHS= \
     -I"d:\boost-1.50.0-mgw" \
     -I"d:\db-4.8.30.NC-mgw\build_unix" \
     -I"d:\openssl-1.0.1e-mgw\include"
     
    LIBPATHS= \
     -L"d:\boost-1.50.0-mgw\stage\lib" \
     -L"d:\db-4.8.30.NC-mgw\build_unix" \
     -L"d:\openssl-1.0.1e-mgw"

    LIBS= \
     -l boost_system-mgw46-mt-s-1_50 \
     -l boost_filesystem-mgw46-mt-s-1_50 \
     -l boost_program_options-mgw46-mt-s-1_50 \
     -l boost_thread-mgw46-mt-s-1_50 \
     -l boost_chrono-mgw46-mt-s-1_50 \
     -l db_cxx \
     -l ssl \
     -l crypto

    DEFS=-DWIN32 -D_WINDOWS -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE
    DEBUGFLAGS=-g
    CFLAGS=-mthreads -O2 -msse2 -w -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter $(DEBUGFLAGS) $(DEFS) $(INCLUDEPATHS)
    LDFLAGS=-Wl,--dynamicbase -Wl,--nxcompat

    # scrypt-jane specific parameters
    DEFS+=-DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME

    xCXXFLAGS_SCRYPT_JANE=-O3 -msse2 -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter \
        $(DEBUGFLAGS) $(DEFS) $(HARDENING) $(CXXFLAGS)

    TESTDEFS = -DTEST_DATA_DIR=$(abspath test/data)

    ifndef USE_UPNP
    override USE_UPNP = -
    endif
    ifneq (${USE_UPNP}, -)
     INCLUDEPATHS += -I"d:\miniupnpc-1.8-mgw"
     LIBPATHS += -L"d:\miniupnpc-1.8-mgw\miniupnpc"
     LIBS += -l miniupnpc -l iphlpapi
     DEFS += -DSTATICLIB -DUSE_UPNP=$(USE_UPNP)
    endif

    ifneq (${USE_IPV6}, -)
    DEFS += -DUSE_IPV6=$(USE_IPV6)
    endif

    LIBS += -l kernel32 -l user32 -l gdi32 -l comdlg32 -l winspool -l winmm -l shell32 -l comctl32 -l ole32 -l oleaut32 -l uuid -l rpcrt4 -l advapi32 -l ws2_32 -l mswsock -l shlwapi

    # TODO: make the mingw builds smarter about dependencies, like the linux/osx builds are
    HEADERS = $(wildcard *.h)

    OBJS= \
        obj/alert.o \
        obj/version.o \
        obj/checkpoints.o \
        obj/netbase.o \
        obj/addrman.o \
        obj/crypter.o \
        obj/key.o \
        obj/db.o \
        obj/init.o \
        obj/irc.o \
        obj/keystore.o \
        obj/main.o \
        obj/net.o \
        obj/protocol.o \
        obj/bitcoinrpc.o \
        obj/rpcdump.o \
        obj/rpcnet.o \
        obj/rpcmining.o \
        obj/rpcwallet.o \
        obj/rpcblockchain.o \
        obj/rpcrawtransaction.o \
        obj/script.o \
        obj/sync.o \
        obj/util.o \
        obj/wallet.o \
        obj/walletdb.o \
        obj/noui.o \
        obj/kernel.o \
        obj/pbkdf2.o \
        obj/scrypt_mine.o \
        obj/scrypt-x86.o \
        obj/scrypt-x86_64.o \
    obj/scrypt-jane.o

    all: yacoind.exe

    test check: test_yacoin.exe FORCE
    test_yacoin.exe

    obj/%.o: %.cpp $(HEADERS)
    g++ -c $(CFLAGS) -o $@ $<

    obj/scrypt-x86.o: scrypt-x86.S
    $(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<

    obj/scrypt-x86_64.o: scrypt-x86_64.S
    $(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<

    obj/scrypt-jane.o: scrypt-jane/scrypt-jane.c
    gcc -c $(xCXXFLAGS_SCRYPT_JANE) -MMD -o $@ $<

    yacoind.exe: $(OBJS:obj/%=obj/%)
    g++ $(CFLAGS) $(LDFLAGS) -o $@ $(LIBPATHS) $^ $(LIBS)

    TESTOBJS := $(patsubst test/%.cpp,obj-test/%.o,$(wildcard test/*.cpp))

    obj-test/%.o: test/%.cpp $(HEADERS)
    g++ -c $(TESTDEFS) $(CFLAGS) -o $@ $<

    test_bitcoin.exe: $(TESTOBJS) $(filter-out obj/init.o,$(OBJS:obj/%=obj/%))
    g++ $(CFLAGS) $(LDFLAGS) -o $@ $(LIBPATHS) $^ -lboost_unit_test_framework $(LIBS)

    clean:
    -delQ yacoind test_yacoin
    -delQ obj\*
    -delQ obj-test\*

    FORCE:

  • ongle
    Newbie
    *
    Offline Offline

    Activity: 22
    Merit: 0


    View Profile
    June 01, 2013, 12:59:02 PM
     #446
    Quote from: WindMaster on June 01, 2013, 07:03:33 AM
    Hanzac already released a 64-bit Windows build based on my GitHub repository about 2 weeks ago after I fixed the checkpoint warning.  Multiple people have checked it out and haven't observed it to do anything suspicious or unusual:
    https://bt.irlbtc.com/view/206577.msg2207446#msg2207446

    Yea, I even sent him a question or two. I was already working on it when I saw that. I was also trying to enable all the options on Windows, qrencode was the only one I couldn't get going. *shrug*

  • Boing7898
    Sr. Member
    ****
    Offline Offline

    Activity: 686
    Merit: 259



    View Profile
    June 01, 2013, 01:09:58 PM
     #447
    Quote from: sairon on June 01, 2013, 10:31:56 AM
    Quote from: Boing7898 on June 01, 2013, 08:37:53 AM
    Quote from: ongle on June 01, 2013, 05:21:58 AM
    If you are doing solo mining and have to leave it unencrypted, I suggest making two wallets and transfer coins to the encrypted wallet from time to time. As always, backup your data before running any random downloads from teh interwebs.

    Sorry if this is offtopic but can't I solo-mine with my wallet encrypted?
    My wallet is encrypted and I'm solo-mining with the minerd and I'm not getting any errors.. Huh

    You won't find any block if you have your wallet encrypted and locked. Either unlock it for a long time period (walletpassphrase <pass> 99999999) or remove encryption.
    Oh fuck..I forgot my wallet password and wasted hours of mining on nothing..
    Bye 140 YACs ;_;

  • cryptrol
    Hero Member
    *****
    Offline Offline

    Activity: 637
    Merit: 500


    View Profile
    June 01, 2013, 02:21:21 PM
     #448
    Rise Nfactor RISE !

        "blocks" : 77242,
        "currentblocksize" : 1527,
        "currentblocktx" : 1,
        "difficulty" : 1.39981203,
        "errors" : "",
        "generate" : false,
        "genproclimit" : -1,
        "hashespersec" : 0,
        "networkhashps" : 56745133, <- 56Mh the network hash is rising
        "pooledtx" : 1,
        "testnet" : false,
        "Nfactor" : 9,
        "N" : 1024,
        "powreward" : 23.64000000

  • cryptrol
    Hero Member
    *****
    Offline Offline

    Activity: 637
    Merit: 500


    View Profile
    June 01, 2013, 02:34:27 PM
    Last edit: June 01, 2013, 03:18:20 PM by cryptrol
     #449
    I you are trying to build yacoind on windows you will find out a lot of errors because of the windows makefile (makefile.mingw) is untouched from novacoin, so the new scrypt version is not getting compiled (blame pocopoco).

    I used this makefile ( added some comments for the changed lines) :
    Code:
    # Copyright (c) 2009-2010 Satoshi Nakamoto
    # Distributed under the MIT/X11 software license, see the accompanying
    # file COPYING or http://www.opensource.org/licenses/mit-license.php.

    # No UPNP for this make file
    USE_UPNP:=
    USE_IPV6:=1

    # Change the gcc version and boost version with the ones you have
    # I used gcc 4.7 and boost 1.53
    INCLUDEPATHS= \
     -I"/home/user/boost_1_53_0" \
     -I"/home/user/db-4.8.30.NC/build_unix" \
     -I"/home/user/openssl-1.0.1e/include"

    LIBPATHS= \
     -L"/home/user/boost_1_53_0/stage/lib" \
     -L"/home/user/db-4.8.30.NC/build_unix" \
     -L"/home/user/openssl-1.0.1e"

    LIBS= \
     -l boost_system-mgw47-mt-s-1_53 \
     -l boost_filesystem-mgw47-mt-s-1_53 \
     -l boost_program_options-mgw47-mt-s-1_53 \
     -l boost_thread-mgw47-mt-s-1_53 \
     -l boost_chrono-mgw47-mt-s-1_53 \
     -l db_cxx \
     -l ssl \
     -l crypto

    DEFS=-DWIN32 -D_WINDOWS -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE
    DEBUGFLAGS=-g
    CFLAGS=-static -mthreads -O2 -msse2 -w -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter $(DEBUGFLAGS) $(DEFS) $(INCLUDEPATHS)

    LDFLAGS=-Wl,--dynamicbase -Wl,--nxcompat

    # This are the scrypt-jane specific parameters needed to compile you can use -msse2 if you don't have sse3
    DEFS_JANE=-DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -O3 -msse3

    TESTDEFS = -DTEST_DATA_DIR=$(abspath test/data)

    ifndef USE_UPNP
    override USE_UPNP = -
    endif
    ifneq (${USE_UPNP}, -)
     INCLUDEPATHS += -I"C:\miniupnpc-1.6-mgw"
     LIBPATHS += -L"C:\miniupnpc-1.6-mgw"
     LIBS += -l miniupnpc -l iphlpapi
     DEFS += -DSTATICLIB -DUSE_UPNP=$(USE_UPNP)
    endif

    ifneq (${USE_IPV6}, -)
    DEFS += -DUSE_IPV6=$(USE_IPV6)
    endif

    LIBS += -l kernel32 -l user32 -l gdi32 -l comdlg32 -l winspool -l winmm -l shell32 -l comctl32 -l ole32 -l oleaut32 -l uuid -l rpcrt4 -l advapi32 -l ws2_32 -l mswsock -l shlwapi

    # TODO: make the mingw builds smarter about dependencies, like the linux/osx builds are
    HEADERS = $(wildcard *.h)

    # Notice I added the scrypt-jane obj at the end
    OBJS= \
        obj/alert.o \
        obj/version.o \
        obj/checkpoints.o \
        obj/netbase.o \
        obj/addrman.o \
        obj/crypter.o \
        obj/key.o \
        obj/db.o \
        obj/init.o \
        obj/irc.o \
        obj/keystore.o \
        obj/main.o \
        obj/net.o \
        obj/protocol.o \
        obj/bitcoinrpc.o \
        obj/rpcdump.o \
        obj/rpcnet.o \
        obj/rpcmining.o \
        obj/rpcwallet.o \
        obj/rpcblockchain.o \
        obj/rpcrawtransaction.o \
        obj/script.o \
        obj/sync.o \
        obj/util.o \
        obj/wallet.o \
        obj/walletdb.o \
        obj/noui.o \
        obj/kernel.o \
        obj/pbkdf2.o \
        obj/scrypt_mine.o \
        obj/scrypt-x86.o \
        obj/scrypt-x86_64.o \
    obj/scrypt-jane.o

    all: yacoind.exe

    test check: test_yacoin.exe FORCE
    test_yacoin.exe

    obj/%.o: %.cpp $(HEADERS)
    g++ -c $(CFLAGS) -o $@ $<

    obj/scrypt-x86.o: scrypt-x86.S
    $(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<

    obj/scrypt-x86_64.o: scrypt-x86_64.S
    $(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<

    # This is needed to compile scrypt-jane with the DEFS_JANE we set before
    obj/scrypt-jane.o: scrypt-jane/scrypt-jane.c
    gcc -c $(xCXXFLAGS_SCRYPT_JANE) $(DEFS_JANE) -MMD -o $@ $<

    yacoind.exe: $(OBJS:obj/%=obj/%)
    g++ $(CFLAGS) $(LDFLAGS) -o $@ $(LIBPATHS) $^ $(LIBS)

    TESTOBJS := $(patsubst test/%.cpp,obj-test/%.o,$(wildcard test/*.cpp))

    obj-test/%.o: test/%.cpp $(HEADERS)
    g++ -c $(TESTDEFS) $(CFLAGS) -o $@ $<

    test_bitcoin.exe: $(TESTOBJS) $(filter-out obj/init.o,$(OBJS:obj/%=obj/%))
    g++ $(CFLAGS) $(LDFLAGS) -o $@ $(LIBPATHS) $^ -lboost_unit_test_framework $(LIBS)

    clean:
    rm yacoind.exe -f
    rm obj/*.*
    rm obj-test/*.*

    FORCE:


    EDIT 1: Fixed the clean section, you can't use del under mingw.

  • sairon
    Sr. Member
    ****
    Offline Offline

    Activity: 406
    Merit: 250


    One does not simply mine Bitcoins


    View Profile
    June 01, 2013, 02:56:01 PM
     #450
    Quote from: cryptrol on June 01, 2013, 02:21:21 PM
    Rise Nfactor RISE !

    Here comes 3x longer confirmation time Cheesy
    GPG key ID: 5E4F108A || BTC: 1hoardyponb9AMWhyA28DZb5n5g2bRY8v

  • Joe_Bauers
    Hero Member
    *****
    Offline Offline

    Activity: 802
    Merit: 1003


    GCVMMWH


    View Profile
    June 01, 2013, 05:38:41 PM
     #451
    Quote from: cryptrol on June 01, 2013, 02:34:27 PM
    I you are trying to build yacoind on windows you will find out a lot of errors because of the windows makefile (makefile.mingw) is untouched from novacoin, so the new scrypt version is not getting compiled (blame pocopoco).

    I used this makefile ( added some comments for the changed lines) :
    Code:
    # Copyright (c) 2009-2010 Satoshi Nakamoto
    # Distributed under the MIT/X11 software license, see the accompanying
    # file COPYING or http://www.opensource.org/licenses/mit-license.php.

    # No UPNP for this make file
    USE_UPNP:=
    USE_IPV6:=1

    # Change the gcc version and boost version with the ones you have
    # I used gcc 4.7 and boost 1.53
    INCLUDEPATHS= \
     -I"/home/user/boost_1_53_0" \
     -I"/home/user/db-4.8.30.NC/build_unix" \
     -I"/home/user/openssl-1.0.1e/include"

    LIBPATHS= \
     -L"/home/user/boost_1_53_0/stage/lib" \
     -L"/home/user/db-4.8.30.NC/build_unix" \
     -L"/home/user/openssl-1.0.1e"

    LIBS= \
     -l boost_system-mgw47-mt-s-1_53 \
     -l boost_filesystem-mgw47-mt-s-1_53 \
     -l boost_program_options-mgw47-mt-s-1_53 \
     -l boost_thread-mgw47-mt-s-1_53 \
     -l boost_chrono-mgw47-mt-s-1_53 \
     -l db_cxx \
     -l ssl \
     -l crypto

    DEFS=-DWIN32 -D_WINDOWS -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE
    DEBUGFLAGS=-g
    CFLAGS=-static -mthreads -O2 -msse2 -w -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter $(DEBUGFLAGS) $(DEFS) $(INCLUDEPATHS)

    LDFLAGS=-Wl,--dynamicbase -Wl,--nxcompat

    # This are the scrypt-jane specific parameters needed to compile you can use -msse2 if you don't have sse3
    DEFS_JANE=-DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -O3 -msse3

    TESTDEFS = -DTEST_DATA_DIR=$(abspath test/data)

    ifndef USE_UPNP
    override USE_UPNP = -
    endif
    ifneq (${USE_UPNP}, -)
     INCLUDEPATHS += -I"C:\miniupnpc-1.6-mgw"
     LIBPATHS += -L"C:\miniupnpc-1.6-mgw"
     LIBS += -l miniupnpc -l iphlpapi
     DEFS += -DSTATICLIB -DUSE_UPNP=$(USE_UPNP)
    endif

    ifneq (${USE_IPV6}, -)
    DEFS += -DUSE_IPV6=$(USE_IPV6)
    endif

    LIBS += -l kernel32 -l user32 -l gdi32 -l comdlg32 -l winspool -l winmm -l shell32 -l comctl32 -l ole32 -l oleaut32 -l uuid -l rpcrt4 -l advapi32 -l ws2_32 -l mswsock -l shlwapi

    # TODO: make the mingw builds smarter about dependencies, like the linux/osx builds are
    HEADERS = $(wildcard *.h)

    # Notice I added the scrypt-jane obj at the end
    OBJS= \
        obj/alert.o \
        obj/version.o \
        obj/checkpoints.o \
        obj/netbase.o \
        obj/addrman.o \
        obj/crypter.o \
        obj/key.o \
        obj/db.o \
        obj/init.o \
        obj/irc.o \
        obj/keystore.o \
        obj/main.o \
        obj/net.o \
        obj/protocol.o \
        obj/bitcoinrpc.o \
        obj/rpcdump.o \
        obj/rpcnet.o \
        obj/rpcmining.o \
        obj/rpcwallet.o \
        obj/rpcblockchain.o \
        obj/rpcrawtransaction.o \
        obj/script.o \
        obj/sync.o \
        obj/util.o \
        obj/wallet.o \
        obj/walletdb.o \
        obj/noui.o \
        obj/kernel.o \
        obj/pbkdf2.o \
        obj/scrypt_mine.o \
        obj/scrypt-x86.o \
        obj/scrypt-x86_64.o \
    obj/scrypt-jane.o

    all: yacoind.exe

    test check: test_yacoin.exe FORCE
    test_yacoin.exe

    obj/%.o: %.cpp $(HEADERS)
    g++ -c $(CFLAGS) -o $@ $<

    obj/scrypt-x86.o: scrypt-x86.S
    $(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<

    obj/scrypt-x86_64.o: scrypt-x86_64.S
    $(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<

    # This is needed to compile scrypt-jane with the DEFS_JANE we set before
    obj/scrypt-jane.o: scrypt-jane/scrypt-jane.c
    gcc -c $(xCXXFLAGS_SCRYPT_JANE) $(DEFS_JANE) -MMD -o $@ $<

    yacoind.exe: $(OBJS:obj/%=obj/%)
    g++ $(CFLAGS) $(LDFLAGS) -o $@ $(LIBPATHS) $^ $(LIBS)

    TESTOBJS := $(patsubst test/%.cpp,obj-test/%.o,$(wildcard test/*.cpp))

    obj-test/%.o: test/%.cpp $(HEADERS)
    g++ -c $(TESTDEFS) $(CFLAGS) -o $@ $<

    test_bitcoin.exe: $(TESTOBJS) $(filter-out obj/init.o,$(OBJS:obj/%=obj/%))
    g++ $(CFLAGS) $(LDFLAGS) -o $@ $(LIBPATHS) $^ -lboost_unit_test_framework $(LIBS)

    clean:
    rm yacoind.exe -f
    rm obj/*.*
    rm obj-test/*.*

    FORCE:


    EDIT 1: Fixed the clean section, you can't use del under mingw.



    Very cool.  Thirtybird, were you able to get it to work with these settings?

  • cryptrol
    Hero Member
    *****
    Offline Offline

    Activity: 637
    Merit: 500


    View Profile
    June 01, 2013, 06:47:23 PM
     #452
    And don't forget to use the scrypt-jane from https://github.com/floodyberry/scrypt-jane , the one that comes with yacoin does not compile on mingw.

  • forsetifox
    Sr. Member
    ****
    Offline Offline

    Activity: 266
    Merit: 250



    View Profile
    June 01, 2013, 07:11:40 PM
     #453
    Quote from: cryptrol on June 01, 2013, 02:21:21 PM
    Rise Nfactor RISE !

        "blocks" : 77242,
        "currentblocksize" : 1527,
        "currentblocktx" : 1,
        "difficulty" : 1.39981203,
        "errors" : "",
        "generate" : false,
        "genproclimit" : -1,
        "hashespersec" : 0,
        "networkhashps" : 56745133, <- 56Mh the network hash is rising
        "pooledtx" : 1,
        "testnet" : false,
        "Nfactor" : 9,
        "N" : 1024,
        "powreward" : 23.64000000


    My Yacoin client still says Nfactor is 8 but according to my hashes it did go up. What's up with that?

  • Thirtybird
    Hero Member
    *****
    Offline Offline

    Activity: 693
    Merit: 500



    View Profile
    June 01, 2013, 10:48:50 PM
     #454
    Quote from: Joe_Bauers on June 01, 2013, 05:38:41 PM
    Quote from: cryptrol on June 01, 2013, 02:34:27 PM
    I you are trying to build yacoind on windows you will find out a lot of errors because of the windows makefile (makefile.mingw) is untouched from novacoin, so the new scrypt version is not getting compiled (blame pocopoco).

    I used this makefile ( added some comments for the changed lines) :
    Code:
    # Copyright (c) 2009-2010 Satoshi Nakamoto
    # Distributed under the MIT/X11 software license, see the accompanying
    # file COPYING or http://www.opensource.org/licenses/mit-license.php.

    # No UPNP for this make file
    USE_UPNP:=
    USE_IPV6:=1

    # Change the gcc version and boost version with the ones you have
    # I used gcc 4.7 and boost 1.53
    INCLUDEPATHS= \
     -I"/home/user/boost_1_53_0" \
     -I"/home/user/db-4.8.30.NC/build_unix" \
     -I"/home/user/openssl-1.0.1e/include"

    LIBPATHS= \
     -L"/home/user/boost_1_53_0/stage/lib" \
     -L"/home/user/db-4.8.30.NC/build_unix" \
     -L"/home/user/openssl-1.0.1e"

    LIBS= \
     -l boost_system-mgw47-mt-s-1_53 \
     -l boost_filesystem-mgw47-mt-s-1_53 \
     -l boost_program_options-mgw47-mt-s-1_53 \
     -l boost_thread-mgw47-mt-s-1_53 \
     -l boost_chrono-mgw47-mt-s-1_53 \
     -l db_cxx \
     -l ssl \
     -l crypto

    DEFS=-DWIN32 -D_WINDOWS -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE
    DEBUGFLAGS=-g
    CFLAGS=-static -mthreads -O2 -msse2 -w -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter $(DEBUGFLAGS) $(DEFS) $(INCLUDEPATHS)

    LDFLAGS=-Wl,--dynamicbase -Wl,--nxcompat

    # This are the scrypt-jane specific parameters needed to compile you can use -msse2 if you don't have sse3
    DEFS_JANE=-DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -O3 -msse3

    TESTDEFS = -DTEST_DATA_DIR=$(abspath test/data)

    ifndef USE_UPNP
    override USE_UPNP = -
    endif
    ifneq (${USE_UPNP}, -)
     INCLUDEPATHS += -I"C:\miniupnpc-1.6-mgw"
     LIBPATHS += -L"C:\miniupnpc-1.6-mgw"
     LIBS += -l miniupnpc -l iphlpapi
     DEFS += -DSTATICLIB -DUSE_UPNP=$(USE_UPNP)
    endif

    ifneq (${USE_IPV6}, -)
    DEFS += -DUSE_IPV6=$(USE_IPV6)
    endif

    LIBS += -l kernel32 -l user32 -l gdi32 -l comdlg32 -l winspool -l winmm -l shell32 -l comctl32 -l ole32 -l oleaut32 -l uuid -l rpcrt4 -l advapi32 -l ws2_32 -l mswsock -l shlwapi

    # TODO: make the mingw builds smarter about dependencies, like the linux/osx builds are
    HEADERS = $(wildcard *.h)

    # Notice I added the scrypt-jane obj at the end
    OBJS= \
        obj/alert.o \
        obj/version.o \
        obj/checkpoints.o \
        obj/netbase.o \
        obj/addrman.o \
        obj/crypter.o \
        obj/key.o \
        obj/db.o \
        obj/init.o \
        obj/irc.o \
        obj/keystore.o \
        obj/main.o \
        obj/net.o \
        obj/protocol.o \
        obj/bitcoinrpc.o \
        obj/rpcdump.o \
        obj/rpcnet.o \
        obj/rpcmining.o \
        obj/rpcwallet.o \
        obj/rpcblockchain.o \
        obj/rpcrawtransaction.o \
        obj/script.o \
        obj/sync.o \
        obj/util.o \
        obj/wallet.o \
        obj/walletdb.o \
        obj/noui.o \
        obj/kernel.o \
        obj/pbkdf2.o \
        obj/scrypt_mine.o \
        obj/scrypt-x86.o \
        obj/scrypt-x86_64.o \
    obj/scrypt-jane.o

    all: yacoind.exe

    test check: test_yacoin.exe FORCE
    test_yacoin.exe

    obj/%.o: %.cpp $(HEADERS)
    g++ -c $(CFLAGS) -o $@ $<

    obj/scrypt-x86.o: scrypt-x86.S
    $(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<

    obj/scrypt-x86_64.o: scrypt-x86_64.S
    $(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<

    # This is needed to compile scrypt-jane with the DEFS_JANE we set before
    obj/scrypt-jane.o: scrypt-jane/scrypt-jane.c
    gcc -c $(xCXXFLAGS_SCRYPT_JANE) $(DEFS_JANE) -MMD -o $@ $<

    yacoind.exe: $(OBJS:obj/%=obj/%)
    g++ $(CFLAGS) $(LDFLAGS) -o $@ $(LIBPATHS) $^ $(LIBS)

    TESTOBJS := $(patsubst test/%.cpp,obj-test/%.o,$(wildcard test/*.cpp))

    obj-test/%.o: test/%.cpp $(HEADERS)
    g++ -c $(TESTDEFS) $(CFLAGS) -o $@ $<

    test_bitcoin.exe: $(TESTOBJS) $(filter-out obj/init.o,$(OBJS:obj/%=obj/%))
    g++ $(CFLAGS) $(LDFLAGS) -o $@ $(LIBPATHS) $^ -lboost_unit_test_framework $(LIBS)

    clean:
    rm yacoind.exe -f
    rm obj/*.*
    rm obj-test/*.*

    FORCE:


    EDIT 1: Fixed the clean section, you can't use del under mingw.



    Very cool.  Thirtybird, were you able to get it to work with these settings?

    Nope.  I wonder if all the people who are having success are compiling on Windows 7 x64 - I've been working on x86.  I even went so far as to pull WindMaster's code, then pull the new scrypt-jane from floodyberry and then put in cryptrol's exact makefile.mingw (changing library paths as needed), and I still got the exact same errors I was getting.  My makefile.mingw was nearly identical to the ones posted here, so when I get a chance, I'll spin up an x64 VM and run through the same process and see if the results are any different - there may be something wrong in the x86 library that is working in the x64 library.
    YACMiner: https://github.com/Thirtybird/YACMiner  N-Factor information : https://docs.google.com/spreadsheet/ccc?key=0Aj3vcsuY-JFNdC1ITWJrSG9VeWp6QXppbVgxcm0tbGc&usp=drive_web#gid=0
    BTC: 183eSsaxG9y6m2ZhrDhHueoKnZWmbm6jfC  YAC: Y4FKiwKKYGQzcqn3M3u6mJoded6ri1UWHa

  • WindMaster (OP)
    Sr. Member
    ****
    Offline Offline

    Activity: 347
    Merit: 250


    View Profile
    June 02, 2013, 02:23:44 AM
     #455
    Quote from: forsetifox on June 01, 2013, 07:11:40 PM
    My Yacoin client still says Nfactor is 8 but according to my hashes it did go up. What's up with that?

    Try pulling and rebuilding the latest source from my github repository.  There was a space of about a day or so after I first added Nfactor and N to the getmininginfo data that it was reporting only what Nfactor was when yacoind was last started.  I fixed that and pushed the fix to github a day or two later, but you may have snagged a copy while the bug was still there.  Alternatively, restart yacoind and it'll show the right info until the next N change near the end of June.

  • Thirtybird
    Hero Member
    *****
    Offline Offline

    Activity: 693
    Merit: 500



    View Profile
    June 02, 2013, 02:33:22 AM
    Last edit: June 02, 2013, 04:50:31 AM by Thirtybird
     #456
    Quote from: Thirtybird on June 01, 2013, 10:48:50 PM

    Nope.  I wonder if all the people who are having success are compiling on Windows 7 x64 - I've been working on x86.  I even went so far as to pull WindMaster's code, then pull the new scrypt-jane from floodyberry and then put in cryptrol's exact makefile.mingw (changing library paths as needed), and I still got the exact same errors I was getting.  My makefile.mingw was nearly identical to the ones posted here, so when I get a chance, I'll spin up an x64 VM and run through the same process and see if the results are any different - there may be something wrong in the x86 library that is working in the x64 library.


    UPDATE: apparently I just needed a good night sleep - yacoind.exe is done on x86 and x64.  Joe_Bauers - your github copy was not complete...  some files were different, and the big thing even I was missing was that the files in scrypt-jane (not just scrypt-jane/code) needed to be replaced.  Once that was done, my next make suceeded (both in DOS using mingw32-make and under msys using make).  I think it would be correct at this time to add floodyberry's latest update to the yacoin src and replace the makefile.mingw with cryptrol's.  

    Once I get through the qt portion, I'll document my build steps so we can include them

    EDIT: one thought I had would be to add "-static" to the LDFLAGS in makefile.mingw
    YACMiner: https://github.com/Thirtybird/YACMiner  N-Factor information : https://docs.google.com/spreadsheet/ccc?key=0Aj3vcsuY-JFNdC1ITWJrSG9VeWp6QXppbVgxcm0tbGc&usp=drive_web#gid=0
    BTC: 183eSsaxG9y6m2ZhrDhHueoKnZWmbm6jfC  YAC: Y4FKiwKKYGQzcqn3M3u6mJoded6ri1UWHa

  • forsetifox
    Sr. Member
    ****
    Offline Offline

    Activity: 266
    Merit: 250



    View Profile
    June 02, 2013, 02:35:41 AM
     #457
    Quote from: WindMaster on June 02, 2013, 02:23:44 AM
    Quote from: forsetifox on June 01, 2013, 07:11:40 PM
    My Yacoin client still says Nfactor is 8 but according to my hashes it did go up. What's up with that?

    Try pulling and rebuilding the latest source from my github repository.  There was a space of about a day or so after I first added Nfactor and N to the getmininginfo data that it was reporting only what Nfactor was when yacoind was last started.  I fixed that and pushed the fix to github a day or two later, but you may have snagged a copy while the bug was still there.  Alternatively, restart yacoind and it'll show the right info until the next N change near the end of June.


    I'm using the latest windows binaries. Can someone build another one with the bug fix in it?

  • Joe_Bauers
    Hero Member
    *****
    Offline Offline

    Activity: 802
    Merit: 1003


    GCVMMWH


    View Profile
    June 02, 2013, 04:51:17 AM
     #458
    Quote from: Thirtybird on June 02, 2013, 02:33:22 AM
    Quote from: Thirtybird on June 01, 2013, 10:48:50 PM

    Nope.  I wonder if all the people who are having success are compiling on Windows 7 x64 - I've been working on x86.  I even went so far as to pull WindMaster's code, then pull the new scrypt-jane from floodyberry and then put in cryptrol's exact makefile.mingw (changing library paths as needed), and I still got the exact same errors I was getting.  My makefile.mingw was nearly identical to the ones posted here, so when I get a chance, I'll spin up an x64 VM and run through the same process and see if the results are any different - there may be something wrong in the x86 library that is working in the x64 library.


    UPDATE: apparently I just needed a good night sleep - yacoind.exe is done on x86 and x64.  Joe_Bauers - your github copy was not complete...  some files were different, and the big thing even I was missing was that the files in scrypt-jane (not just scrypt-jane/code) needed to be replaced.  Once that was done, my next make suceeded (both in DOS using mingw32-make and under msys using make).  I think it would be correct at this time to add floodyberry's latest update to the yacoin src and replace the makefile.mingw with cryptrol's.  

    Once I get through the qt portion, I'll document my build steps so we can include them

    Great news!  Do you have  a list of the files that weren't complete? There were a few files that were never added by pocopoco, so maybe they need to be in YAC?


    These were the commits I made:
    Update scrypt-jane-romix-template.h …
    Update scrypt-jane-romix-basic.h …
    Update scrypt-jane-portable-x86.h …
    Update scrypt-jane-mix_salsa-sse2.h …
    Update scrypt-jane-mix_salsa-avx.h …
    Update scrypt-jane-mix_chacha-ssse3.h …
    Update scrypt-jane-mix_chacha-sse2.h …
    Update scrypt-jane-mix_chacha-avx.h …
    Update scrypt-jane-salsa.h …
    Update scrypt-jane-chacha.h …

    This is YAC:
    scrypt-jane-chacha.h   a month ago   initial release [pocopoco]
    scrypt-jane-hash.h   a month ago   initial release [pocopoco]
    scrypt-jane-hash_keccak.h   a month ago   initial release [pocopoco]
    scrypt-jane-hash_sha256.h   a month ago   initial release [pocopoco]
    scrypt-jane-mix_chacha-avx.h   a month ago   scrypt-jane chacha added [pocopoco]
    scrypt-jane-mix_chacha-sse2.h   a month ago   scrypt-jane chacha added [pocopoco]
    scrypt-jane-mix_chacha-ssse3.h   a month ago   scrypt-jane chacha added [pocopoco]
    scrypt-jane-mix_chacha.h   a month ago   scrypt-jane chacha added [pocopoco]
    scrypt-jane-mix_salsa-avx.h   a month ago   initial release [pocopoco]
    scrypt-jane-mix_salsa-sse2.h   a month ago   initial release [pocopoco]
    scrypt-jane-mix_salsa.h   a month ago   initial release [pocopoco]
    scrypt-jane-pbkdf2.h   a month ago   initial release [pocopoco]
    scrypt-jane-portable-x86.h   a month ago   initial release [pocopoco]
    scrypt-jane-portable.h   a month ago   initial release [pocopoco]
    scrypt-jane-romix-basic.h   a month ago   initial release [pocopoco]
    scrypt-jane-romix-template.h   a month ago   initial release [pocopoco]
    scrypt-jane-romix.h   a month ago   initial release [pocopoco]
    scrypt-jane-salsa.h   a month ago   initial release [pocopoco]
    scrypt-jane-test-vectors.h   a month ago   initial release [pocopoco]


    And this is floodyberry's repo, so there is definitely some stuff missing:
    scrypt-conf.h         9 months ago   checkin! [floodyberry]
    scrypt-jane-chacha.h      14 days ago   check if the cpu supports the impl before saying it's available [floodyberry]
    scrypt-jane-hash.h      8 months ago   add Keccak256/512 support [floodyberry]
    scrypt-jane-hash_blake256.h   6 months ago   accidentally left 'G' defined [floodyberry]
    scrypt-jane-hash_blake512.h   6 months ago   accidentally left 'G' defined [floodyberry]
    scrypt-jane-hash_keccak.h   8 months ago   give keccak one unrolled round [floodyberry]
    scrypt-jane-hash_sha256.h   9 months ago   checkin! [floodyberry]
    scrypt-jane-hash_sha512.h   9 months ago   checkin! [floodyberry]
    scrypt-jane-hash_skein512.h   9 months ago   checkin! [floodyberry]
    scrypt-jane-mix_chacha-avx.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-mix_chacha-sse2.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-mix_chacha-ssse3.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-mix_chacha.h   9 months ago   checkin! [floodyberry]
    scrypt-jane-mix_salsa-avx.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-mix_salsa-sse2.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-mix_salsa.h      9 months ago   checkin! [floodyberry]
    scrypt-jane-mix_salsa64-avx.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-mix_salsa64-sse2.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-mix_salsa64-ssse3.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-mix_salsa64.h   6 months ago   add proof of concept salsa6420/8 mixer [floodyberry]
    scrypt-jane-pbkdf2.h      9 months ago   zero out memory with derived secrets after use [floodyberry]
    scrypt-jane-portable-x86.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-portable.h      6 months ago   allow [64,128,256,512] byte block sizes and typedef the block element… [floodyberry]
    scrypt-jane-romix-basic.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-romix-template.h   14 days ago   fixes so it will compile and run under mingw [floodyberry]
    scrypt-jane-romix.h      6 months ago   add proof of concept salsa6420/8 mixer [floodyberry]
    scrypt-jane-salsa.h      14 days ago   check if the cpu supports the impl before saying it's available [floodyberry]
    scrypt-jane-salsa64.h      14 days ago   check if the cpu supports the impl before saying it's available [floodyberry]
    scrypt-jane-test-vectors.h   6 months ago   add proof of concept salsa6420/8 mixer [floodyberry]

  • Thirtybird
    Hero Member
    *****
    Offline Offline

    Activity: 693
    Merit: 500



    View Profile
    June 02, 2013, 05:52:31 PM
     #459
    Quote from: Joe_Bauers on June 02, 2013, 04:51:17 AM
    Quote from: Thirtybird on June 02, 2013, 02:33:22 AM
    Quote from: Thirtybird on June 01, 2013, 10:48:50 PM

    Nope.  I wonder if all the people who are having success are compiling on Windows 7 x64 - I've been working on x86.  I even went so far as to pull WindMaster's code, then pull the new scrypt-jane from floodyberry and then put in cryptrol's exact makefile.mingw (changing library paths as needed), and I still got the exact same errors I was getting.  My makefile.mingw was nearly identical to the ones posted here, so when I get a chance, I'll spin up an x64 VM and run through the same process and see if the results are any different - there may be something wrong in the x86 library that is working in the x64 library.


    UPDATE: apparently I just needed a good night sleep - yacoind.exe is done on x86 and x64.  Joe_Bauers - your github copy was not complete...  some files were different, and the big thing even I was missing was that the files in scrypt-jane (not just scrypt-jane/code) needed to be replaced.  Once that was done, my next make suceeded (both in DOS using mingw32-make and under msys using make).  I think it would be correct at this time to add floodyberry's latest update to the yacoin src and replace the makefile.mingw with cryptrol's.  

    Once I get through the qt portion, I'll document my build steps so we can include them

    Great news!  Do you have  a list of the files that weren't complete? There were a few files that were never added by pocopoco, so maybe they need to be in YAC?



    I do not - I was troubleshooting one compile error I was getting in scrypt-jane-romix-template.h, and it was giving me one line number, and when I compared it to floodyberry's, it was 10 lines off.  There was some other commented out lines in the file as well so I decided to just use his repository without looking at the rest of the differences.  Sorry mate.
    YACMiner: https://github.com/Thirtybird/YACMiner  N-Factor information : https://docs.google.com/spreadsheet/ccc?key=0Aj3vcsuY-JFNdC1ITWJrSG9VeWp6QXppbVgxcm0tbGc&usp=drive_web#gid=0
    BTC: 183eSsaxG9y6m2ZhrDhHueoKnZWmbm6jfC  YAC: Y4FKiwKKYGQzcqn3M3u6mJoded6ri1UWHa

  • JimmyFL
    Member
    **
    Offline Offline

    Activity: 84
    Merit: 10



    View Profile
    June 02, 2013, 06:01:08 PM
    Last edit: June 02, 2013, 06:13:34 PM by JimmyFL
     #460
    Ok guys, I really need to cash out some money "right now" (max 3-4 days)  Embarrassed

    So don't take my 11000yac sell like a panic dumping. I really would like to keep yacoins for further investment, but there is no other way for me right now  Cry

    Btw lets make yac at least 0.0005BTC (or 0.005BTC?  Wink)
    Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 [23] 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 ... 180 »
      Print  
Page 22
Viewing Page: 23

IRLBTC™ © 2025 IRLBTC.com