rbdrbd
|
|
May 31, 2013, 07:27:01 PM |
|
YAC was on CoinChoose for a bit, but I think sal002 took it off because it skewed the graphs. Perhaps there's another way we could have it added (on a separate "CPU Coin" section...or not have a line for it on the graph, but have it in the grid, etc). I do agree that it's very important to have it on CoinChoose, but as it is a CPU coin with a low value, the result may not be that impressive anyhow.
|
|
|
|
seleme
Legendary
Offline
Activity: 2772
Merit: 1028
Duelbits.com
|
|
May 31, 2013, 07:28:55 PM |
|
Good one, that's another bit of originality for YAC. I vote for this one.
|
|
|
|
theprofileth
Full Member
Offline
Activity: 239
Merit: 100
Socialist Cryptocurrency Devote
|
|
May 31, 2013, 07:34:17 PM |
|
Good one, that's another bit of originality for YAC. I vote for this one. I second this, it is a pretty good simple plus unicode is definetly a plus.
|
|
|
|
bitdwarf
Sr. Member
Offline
Activity: 406
Merit: 250
The cryptocoin watcher
|
|
May 31, 2013, 07:48:08 PM |
|
Anyone willing to create logos that reflect the symbol, please feel free! Sometimes the perfect graphic isn't self evident till it's seen. I'll try myself too when I can.
|
𝖄𝖆𝖈: YF3feU4PNLHrjwa1zV63BcCdWVk5z6DAh5 · 𝕭𝖙𝖈: 12F78M4oaNmyGE5C25ZixarG2Nk6UBEqme Ɏ: "the altcoin for the everyman, where the sweat on one's brow can be used to cool one's overheating CPU" -- theprofileth
|
|
|
WindMaster (OP)
|
|
May 31, 2013, 08:14:56 PM |
|
Note that scrypt-jane isn't a hashing algorithm, it's a generic scrypt library that supports many different variations of scrypt, including scrypt+salsa20/8 as used by Litecoin. I've noticed quite a few people refer to the scrypt variant used by YAC as "scrypt-jane", but that's actually wrong.
So what's the name for it? We shall give it a name, scrypt-chacha? 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!).
|
|
|
|
Thirtybird
|
|
May 31, 2013, 09:10:43 PM |
|
NOTE: No binaries are posted at this point. You'll need to build from source from my GitHub repository during these early stages of development. Windows client build is still problematic, as the scrypt-jane library does not compile cleanly with mingw.
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
|
|
|
|
JahPowerBit
Sr. Member
Offline
Activity: 335
Merit: 255
Counterparty Developer
|
|
May 31, 2013, 09:26:34 PM |
|
You need a formula for the block reward, Nfactor affects only difficulty. EDIT: from the source: int64 GetProofOfWorkReward(unsigned int nBits) { CBigNum bnSubsidyLimit = MAX_MINT_PROOF_OF_WORK; CBigNum bnTarget; bnTarget.SetCompact(nBits); CBigNum bnTargetLimit = bnProofOfWorkLimit; bnTargetLimit.SetCompact(bnTargetLimit.GetCompact());
// ppcoin: subsidy is cut in half every 64x multiply of difficulty // A reasonably continuous curve is used to avoid shock to market // (nSubsidyLimit / nSubsidy) ** 6 == bnProofOfWorkLimit / bnTarget // // Human readable form: // // nSubsidy = 100 / (diff ^ 1/6) CBigNum bnLowerBound = CENT; CBigNum bnUpperBound = bnSubsidyLimit; while (bnLowerBound + CENT <= bnUpperBound) { CBigNum bnMidValue = (bnLowerBound + bnUpperBound) / 2; if (fDebug && GetBoolArg("-printcreation")) printf("GetProofOfWorkReward() : lower=%"PRI64d" upper=%"PRI64d" mid=%"PRI64d"\n", bnLowerBound.getuint64(), bnUpperBound.getuint64(), bnMidValue.getuint64()); if (bnMidValue * bnMidValue * bnMidValue * bnMidValue * bnMidValue * bnMidValue * bnTargetLimit > bnSubsidyLimit * bnSubsidyLimit * bnSubsidyLimit * bnSubsidyLimit * bnSubsidyLimit * bnSubsidyLimit * bnTarget) bnUpperBound = bnMidValue; else bnLowerBound = bnMidValue; }
int64 nSubsidy = bnUpperBound.getuint64(); nSubsidy = (nSubsidy / CENT) * CENT; if (fDebug && GetBoolArg("-printcreation")) printf("GetProofOfWorkReward() : create=%s nBits=0x%08x nSubsidy=%"PRI64d"\n", FormatMoney(nSubsidy).c_str(), nBits, nSubsidy);
return min(nSubsidy, MAX_MINT_PROOF_OF_WORK); }
hum.. i understand. Thank you, i will look at this code this week end.
|
|
|
|
|
JahPowerBit
Sr. Member
Offline
Activity: 335
Merit: 255
Counterparty Developer
|
|
May 31, 2013, 09:33:52 PM |
|
YAC was on CoinChoose for a bit, but I think sal002 took it off because it skewed the graphs. Perhaps there's another way we could have it added (on a separate "CPU Coin" section...or not have a line for it on the graph, but have it in the grid, etc). I do agree that it's very important to have it on CoinChoose, but as it is a CPU coin with a low value, the result may not be that impressive anyhow. 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 ..
|
|
|
|
JahPowerBit
Sr. Member
Offline
Activity: 335
Merit: 255
Counterparty Developer
|
|
May 31, 2013, 09:38:00 PM |
|
great idea, i like this! It's really cool to see a live altcoin build brick by brick. :-)
|
|
|
|
Joe_Bauers
|
|
May 31, 2013, 10:01:32 PM |
|
NOTE: No binaries are posted at this point. You'll need to build from source from my GitHub repository during these early stages of development. Windows client build is still problematic, as the scrypt-jane library does not compile cleanly with mingw.
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-janeOnly 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.
|
|
|
|
bitdwarf
Sr. Member
Offline
Activity: 406
Merit: 250
The cryptocoin watcher
|
|
May 31, 2013, 10:34:31 PM |
|
I love it! It looks kinda industrial, like something related to real, solid goods.
|
𝖄𝖆𝖈: YF3feU4PNLHrjwa1zV63BcCdWVk5z6DAh5 · 𝕭𝖙𝖈: 12F78M4oaNmyGE5C25ZixarG2Nk6UBEqme Ɏ: "the altcoin for the everyman, where the sweat on one's brow can be used to cool one's overheating CPU" -- theprofileth
|
|
|
seleme
Legendary
Offline
Activity: 2772
Merit: 1028
Duelbits.com
|
|
May 31, 2013, 10:42:07 PM |
|
colors are too soft though
|
|
|
|
Thirtybird
|
|
May 31, 2013, 10:48:07 PM |
|
NOTE: No binaries are posted at this point. You'll need to build from source from my GitHub repository during these early stages of development. Windows client build is still problematic, as the scrypt-jane library does not compile cleanly with mingw.
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-janeOnly 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. PM me when you've compiled, I'll get a VM spun up for testing
|
|
|
|
WindMaster (OP)
|
|
May 31, 2013, 11:14:49 PM |
|
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-janeOnly 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. 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.
|
|
|
|
Joe_Bauers
|
|
June 01, 2013, 12:01:09 AM |
|
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-janeOnly 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. 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. 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.
|
|
|
|
Thirtybird
|
|
June 01, 2013, 01:03:39 AM |
|
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-janeOnly 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. 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. 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. 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
|
|
|
|
Thirtybird
|
|
June 01, 2013, 03:20:06 AM |
|
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-janeOnly 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. 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. would the following errors be the weirdness you saw when trying to get it to compile under mingw? obj/scrypt_mine.o: In function `Z11scrypt_hashPKvjPjh': C:\yacoin\src/scrypt_mine.cpp:101: undefined reference to `scrypt' obj/scrypt_mine.o: In function `Z15scanhash_scryptP12block_headerjRjPvS0_h': C:\yacoin\src/scrypt_mine.cpp:202: undefined reference to `scrypt' collect2.exe: error: ld returned 1 exit status
|
|
|
|
ongle
Newbie
Offline
Activity: 22
Merit: 0
|
|
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. 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.zipI 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
|
|
|
|
Thirtybird
|
|
June 01, 2013, 05:53:21 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. 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.zipI 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.zipThank 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...
|
|
|
|
|