Topic: [ANN][YAC] YACoin ongoing development - page 158. (Read 380091 times)

You won't find any block if you have your wallet encrypted and locked. Either unlock it for a long time period (walletpassphrase 99999999) or remove encryption.

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..

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.



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://bitcointalksearch.org/topic/m.2207446

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

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. Dependencies were a b*tch though. I think I got upnp linked in but couldn't get qrencode working due to pthread linking errors that I can't figure out (yet). If nothing else it gets rid of the checkpoint message. It also uses a different icon for the exe (public domain by bitdwarf), but it only really shows in explorer and I didn't bother replacing any other graphics. It is using these dependencies:

BOOST_LIB_SUFFIX=-mgw46-mt-s-1_50
BOOST_INCLUDE_PATH=d:\\boost-1.50.0-mgw
BOOST_LIB_PATH=d:\\boost-1.50.0-mgw\\stage\\lib
BDB_INCLUDE_PATH=d:\\db-4.8.30.NC-mgw\\build_unix
BDB_LIB_PATH=d:\\db-4.8.30.NC-mgw\\build_unix
OPENSSL_INCLUDE_PATH=d:\\openssl-1.0.1e-mgw\\include
OPENSSL_LIB_PATH=d:\\openssl-1.0.1e-mgw
MINIUPNPC_INCLUDE_PATH=d:\\miniupnpc-1.8-mgw
MINIUPNPC_LIB_PATH=d:\\miniupnpc-1.8-mgw\\miniupnpc

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. Also, you really should encrypt your main wallets to protect yourself this sort of thing. 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.

http://tig.org/crypto/yacoin-qt.zip

I also recompiled the minerd_scrypt_jane_avx that god3 posted for x64, with the single change to not print the LONGPOLL messages when running in quite (-q) mode. Again, I don't know how to prove it isn't malware.

http://tig.org/crypto/minerd_avx.zip

would the following errors be the weirdness you saw when trying to get it to compile under mingw?

I'm giving this a shot - hopefully the guide to building bitcoin-qt with mingw applies here.  I hate to say it, but I was spoiled by the ease of adding dependencies and packages under ubuntu... this seems antiquated

OK, all of floodyberry's changes have been merged to  https://github.com/joebauers/yacoin.git   I compiled in Debian and everything still works great.

*** Someone with windows will need to see if they can get everything compiled from my changes. ***

Note: That https://github.com/yacoin/yacoin is what everyone will want to use for Production builds - https://github.com/joebauers/yacoin.git is just to test the changes from floodyberry.

Keep me updated on what happens there.  If you're working on it, I'll work on other things.  I had blocked out some time during the weekend to look at the updated commits to scrypt-jane and see about cranking out a full Windows installer package.  If you check on the scrypt-jane update and whether it fixes Windows builds, I'll concentrate on the other things that need to get wrapped up.

PM me when you've compiled, I'll get a VM spun up for testing

colors are too soft though

I love it! It looks kinda industrial, like something related to real, solid goods.

Only one way to find out! I will add the changes to my repo and you (or someone with Windows) can test from there - if everything looks good I will send a pull request to WM to request that it's added.

great idea, i like this!   

It's really cool to see a live altcoin build brick by brick. :-)

The challenge is to find a way to calculate the income functions of hardware ... it is very important for someone who decides to invest in mining .. but the change in N makes it very difficult ..

Made some here: http://imgur.com/hq9J1OT,UWl7yoB,BDVfAPk (3 sizes)

Example:



Alt colour :

http://imgur.com/rcpKRbT http://imgur.com/998DjGF http://imgur.com/qidJeRX

I was doing some digging, and saw that there were commits to scrypt-jane a couple weeks ago labelled as "fixes so it will compile and run under mingw" - if you pulled that, could we get updated Windows binaries and get them posted?

https://github.com/floodyberry/scrypt-jane

That's probably the closest option at this point.  In that scenario, scrypt-salsa would accurately refer to the algorithm used by Litecoin, and scrypt-chacha would accurately refer to the algorithm used by YAC.  It's not perfect, as it describes the choice of mixing algorithm but not the choice of hash.  But until someone does something strange like create an altcoin that uses chacha20/8 combined with SHA256 instead of Keccak512, I think "scrypt-chacha" is probably concise enough for now.

So, unless anyone has a different idea, let's indeed call it scrypt-chacha and correct people that call it scrypt-jane (since that's not correct regardless what we decide it should be called!).