after the client came up I closed it and opened it again. This time it opened quickly and some coins went to stake properly. Previously I'd had an orphan stake. This looks good.
Nice, thanks for the feedback! |
|
|
|
I downloaded the new client and ran it using the switch but yacoin still hasn't opened after 15 minutes.  Well, it should take a long time at first, read the note carefully.  Thanks Sairon! I'll try it out now...  EDIT: wow! 30 sec indeed...downloading blocks now. Thanks man! Glad it also works for you.  Tips for me and my friend who helped me write this appreciated!  |
|
|
|
Bump. A little reminder for the rich list people: your fantastic holding won't be worth much if the coin is seriously hampered by a dysfunctional wallet. We have a working prototype of a new wallet ready. Not sure if it's bug-free, though. However, works for me so far. You can get the latest windows binaries here: https://www.dropbox.com/s/pwa2lymjl6igh6q/yacoin-cc-latest.zipStill waiting for the major stakeholders to toss us some coins, though. NOTE: you NEED to move/rename (backup) everything except wallet.dat and peers.dat in the yacoin data directory and then run yacoin with -loadblock=C:\blk0001.dat (assuming you put the blk0001.dat file in C:\). This is needed because we had to change the way blocks are indexed and now the wallet starts in LESS THAN 30 SECONDS (down from more than 30 minutes). However, this initial load will take somewhere around 2 hours (still faster than downloading it through the p2p network). If you don't mind redownloading all the blocks, you can just remove the unneeded files and start yacoin normally (less hassle, but takes more time). Most of the time at startup is now spend verifying the last couple of blocks (which needs to to recompute their hashes to ensure integrity). I've lowered this number from the default 2500 to 666 (rather arbitrarily chosen, but should absolutely be set higher than 520). |
|
|
|
it is a problem with pushpool itself as it somehow keeps connections established instead of closing it (and yes - I am using block notify scripts ). After few days it is so overloaded (EDIT: sometimes there is 200000 established connections to yac port!) that there are more and more rejects - the only solution is to restart pushpool daemon. There is no such problems with stratum server so thats why this is important (no only for me but also for miners) IMHO that should be fairly easy to fix. I can take a look after wrapping up the YAC client. BTW, already achieved massive speedup on startup - need more donations! YAC price will surely spike after we release it, haha!  To the Moon! ┗(°0°)┛ Yac price is recovering nicely...usd value has increased afaik. Now I need to get a proper wallet, mine isn't updating the blockchain after a certain point We have a working prototype of a new wallet ready. Not sure if it's bug-free, though. However, works for me so far. You can get the latest windows binaries here: https://www.dropbox.com/s/pwa2lymjl6igh6q/yacoin-cc-latest.zipNOTE: you NEED to move/rename (backup) everything except wallet.dat and peers.dat in the yacoin data directory and then run yacoin with -loadblock=C:\blk0001.dat (assuming you put the blk0001.dat file in C:\). This is needed because we had to change the way blocks are indexed and now the wallet starts in LESS THAN 30 SECONDS (down from more than 30 minutes). However, this initial load will take somewhere around 2 hours (still faster than downloading it through the p2p network). If you don't mind redownloading all the blocks, you can just remove the unneeded files and start yacoin normally (less hassle, but takes more time). |
|
|
|
it is a problem with pushpool itself as it somehow keeps connections established instead of closing it (and yes - I am using block notify scripts ). After few days it is so overloaded (EDIT: sometimes there is 200000 established connections to yac port!) that there are more and more rejects - the only solution is to restart pushpool daemon. There is no such problems with stratum server so thats why this is important (no only for me but also for miners) IMHO that should be fairly easy to fix. I can take a look after wrapping up the YAC client. BTW, already achieved massive speedup on startup - need more donations! YAC price will surely spike after we release it, haha! To the Moon! ┗(°0°)┛ |
|
|
|
Hi, As promised I opened 2 new LP ports on http://yac.coinmine.pl pool to handle the load: 8088 - not recommended - heavily used 8080 - not recommended - heavily used 8881 - recommended - new 8882 - recommended - new Stratum Port: 9088 - recommended feeleep umm... are you sure you're not just running into the default "socket max conn" limit? the default in linux is set to 128, which limits the number of incoming connections per one socket (one pool port) to 128, which is absurdly low. you can check this with cat /proc/sys/net/core/somaxconn
or, if this is not the case, you must be getting some errors in the kernel log (dmesg) - if so, what are they? it's also possible you've reached max number of file handles per process (can be increased, too). |
|
|
|
I think the lack of a mining client with stratum support is a pretty big freakin deal, right? Well, not that much. Stratum protocol aims to reduce the load on pool servers with a huge number of miners by letting the miners: - create unique valid work for themselves when they run out of shares and there was not a new block on the network
- listen for changes instead of asking for them every couple of seconds, thus reducing the bandwidth used by miners/pools by disabling longpoll and making the pool push notifications to miner
The first point doesn't need correcting yet as it's not slowing down miners (because YAC mining is so slow anyway), and the second is not a big deal unless the pools run out of bandwidth due to a HUGE amount of miners. I'd say a bigger deal would be integrating CPU mining into more sophisticated clients like cgminer (AFAIK there's yacminer with only GPU support). This way you would have the option to failover from one pool to another automagically, which is needed badly right now with pools crashing every couple of minutes (no idea why they're crashing). |
|
|
|
We have a C++ dev working on the #1 issue right now (slow startup time). He has already made a huge progress. Donate now to make him type faster! |
|
|
|
I was able to compile this for x64 using the instructions I posted and it mines against yac.coinmine.pl with stratum support just fine. PMed you about syncing code as it looks like it was taken from farther back in history than the version I work with.
Thirtybird
Donations - YAC:Y4FKiwKKYGQzcqn3M3u6mJoded6ri1UWHa Sent a little change. |
|
|
|
Ok, I have compiled your version, everything works, but since I did not have any high CPU usage problems before, it doesn't help much. I have tried running both with and without -no-pos and I don't see any strange behaviour for either one. Thanks for testing anyway. |
|
|
|
Added my GPU details to the wiki now, really struggling to get any more performance out of this card while still getting 100% accepted shares. Hope this is useful.. it's a very common GPU so should help some people out.
cool, thanks! |
|
|
|
It *could* be caused by the PoS minter thread going nuts (I've got slightly over 500 transactions in one wallet, all spent and the PoS minter thread constantly eats 25% cpu). Can someone with a large amount of transactions in wallet try my latest git version? Download, compile and run it with "-no-pos" parameter.
I can try it, I did have a very small payout treshold set at the pool, left miner running on several servers for a few months and didn't care much about it and I ended up with over 1000 transactions, the current client now takes tens of minutes to start... Plus after I make a transaction from the client, it hangs for another few minutes. Where can I find your latest git version? Is it the official one at https://github.com/yacoin/yacoin ? My git devel tree is at https://github.com/saironiq/yacoin-ccIt certainly won't fix the long start-up time issue as that's a completely unrelated performance problem (working on a fix). Making a transaction is also quite computationally-intensive task (signing hundreds of inputs with ECC crypto takes time). My latest commit just completely disables the proof-of-stake minting thread when given "-no-pos" commandline argument as I noticed it consumed quite a bit of CPU time on my PC even when not doing anything with the wallet and having exactly 0.00 YAC balance (with 500 spent transactions). |
|
|
|
15,000 YACoin headed your way...
transaction id: feae5f1a863ed9d80dbe88a199804240deebfab475f44f2c5f97c2044eabad7b
Thank you very much, sairon!
Thank you, too! And thanks to St.Bit, also! |
|
|
|
Many Scrypt coins are dominated by FPGA miners. Feeling sad? No more! Yacoin is THE coin for you! FPGA mining non-existent, GPU mining becomes less and less profitable each Nfactor change. Now you can finally put that CPU of yours to a good use! Also, only a few people mine Yacoins, so there's really small competition and quite high rewards! With exchange rate of YAC skyrocketing in the past days, the profitability is over 1000% of Litecoin (depends on your hardware, though). Mind you, the most profitable vanilla Scrypt coin has only 350% profitability of LTC. Yes, the numbers are right. There's a mining profitability calculator where you can check your daily earnings in YAC, LTC and BTC if you know your hashrate for each of t hese coins/algorithms. The hashrate ratio between YAC and LTC can vary significantly due to CPU cache size and/or GPU local memory size. You can expect 1/60 to 1/70 of your LTC hashrate as a "rule of thumb" (at least for CPUs - as that's what this coin is meant for) if you don't want to benchmark your hashrates first. We also have a wiki page with mining hardware comparison at http://yacoinwiki.tk/index.php/Mining_Hardware_Comparison (yes, it's quite slim at the moment - feel free to add your own hw and hashrates). For example, with one of the CPUs listed on wiki, you can get 0.3 kh/s with YAC and around 18 kh/s with LTC (giving a ratio of 60). Plugging these numbers into the calculator yields: YAC/LTC profitability: 1149.38%
YAC Mined per day: 20.33 YAC / 0.00365962 BTC / 3.94 USD
LTC Mined per day: 0.01 LTC / 0.0003184 BTC / 0.34 USD
Cool, huh? Come joins us at http://yacointalk.com/index.php/board,4.0.html for info on how to start mining, a list of pools and assistance from a helpful community! |
|
|
|
OK thanks. Can anyone (St Bit?) confirm whether or not this occurs in yacoind? I'm having trouble replicating the issue, but I'm pretty sure it's a Qt issue. One potential solution is to load everything to a file and show just the last 50 transactions in the client.
Sorry, I can't help you. I think it's just implemented not efficiently and normal users are usually not effected since they don't have that many inputs and/or a weak PC. For most people sendig it to a new adress should fix it. My netbook had it's first issues like this at around 120 transactions and currently it's not even capable of PoS minting. It *could* be caused by the PoS minter thread going nuts (I've got slightly over 500 transactions in one wallet, all spent and the PoS minter thread constantly eats 25% cpu). Can someone with a large amount of transactions in wallet try my latest git version? Download, compile and run it with "-no-pos" parameter. I'd like to debug an issue I'm having with the latest client. Can someone point me to the instructions folks used for the development environment setup?
What issue, exactly? |
|
|
|
I like the improvement. However, you also need to include the NFactor change right? The NFactor changes are fortunately more spaced apart, but in May, all the data will be obsolete. Maybe add a column for the NFactor or just have a separate page for each NFactor? The bounty will be sent your way once I get home Monday. Thank you very much.
PS ugh the logo!
I think separate pages would be best - we can just copy the data to a new one and remove all the hashrate numbers, then let the community fill them in again. |
|
|
|
Well I think this site pretty much satisfies the bounty... what do you think St. Bitt? Only problem is it has the wrong logo... I don't think this is fullfilled yet. There needs to be a way for a miner to find it's (rough) kh/s in YAC without actually having to mine YAC first. We need to attrackt new people, not exclude them. Having said that I let Beave decide on this. I have no time. I can definitely put up a table with hashrates of popular CPUs/GPUs, though I need the data first... Another option is using that ybcminer's thingy that benchmarks hashrate for each Nfactor without having to be connected to YAC network. However, I was unable to make that work (unknown options, wtf). EDIT: wasn't there a Yacoin wiki somewhere? We can start a page with mining hardware comparison similar to https://en.bitcoin.it/wiki/Mining_hardware_comparison and everyone can edit it with their hashrates and settings! EDIT2: Here you go http://yacoinwiki.tk/index.php/Mining_Hardware_Comparison Added all my hardware. Put a link from my calc. |
|
|
|
Bumping - anyone able to do windows binaries? I can try to do it as I have a build VM for yacoind/yacoin-qt anyway. Need to finish something else first, though. Shoot me a PM if I don't report back in ~3 days, mmkay? So I tried to compile it yeasterday night, without success (anybody know how to properly build and install libcurl-dev in mingw/msys? -.-") * sairon thinks cross-compiling in linux would be a much safer bet. I managed to compile it on linux but only win32 (no idea how to do 64 bit binaries) I've got an idea how to make the libcurl-dev working, I'll try that sometime tomorrow-ish. Will let you know how it goes. |
|
|
|
|
Show Posts
