Bitcoin Forum
January 22, 2018, 02:54:16 PM *
News: Electrum users must upgrade to 3.0.5 if they haven't already. More info.
 
   Home   Help Search Donate Login Register  
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 ... 171 »
  Print  
Author Topic: [ANN][YAC] YACoin ongoing development  (Read 351780 times)
ColonelPooteh
Member
**
Offline Offline

Activity: 60


View Profile
May 21, 2013, 12:51:24 AM
 #221

For some reason whenever I open my yacoin-qt client it utilizes 100% of my cpu. I have an FX-8350 so there is no reason that it should be doing that. Does anyone have any idea what may be causing that spike?



nevermind, I figured it out. My YaCoin.conf was set to gen=1. I changed it to gen=0 and that fixed the problem.

The Official Lottocoin Thread
BTC: 12UPfp6JGmWB92JaSda8DMZBtxh32B8neQ
LTC: Lboc6BrwcH1AdRxK35CL8TvFCUKCni7CXv
1516632856
Hero Member
*
Offline Offline

Posts: 1516632856

View Profile Personal Message (Offline)

Ignore
1516632856
Reply with quote  #2

1516632856
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1516632856
Hero Member
*
Offline Offline

Posts: 1516632856

View Profile Personal Message (Offline)

Ignore
1516632856
Reply with quote  #2

1516632856
Report to moderator
1516632856
Hero Member
*
Offline Offline

Posts: 1516632856

View Profile Personal Message (Offline)

Ignore
1516632856
Reply with quote  #2

1516632856
Report to moderator
1516632856
Hero Member
*
Offline Offline

Posts: 1516632856

View Profile Personal Message (Offline)

Ignore
1516632856
Reply with quote  #2

1516632856
Report to moderator
dragon2nd
Member
**
Offline Offline

Activity: 94


View Profile
May 21, 2013, 01:49:24 AM
 #222

May I ask who are the devs (both official and unofficial) of YAC?
seleme
Legendary
*
Offline Offline

Activity: 1106



View Profile
May 21, 2013, 01:52:04 AM
 #223

Dev was killed in the battle  Grin, unofficial should be the WindMaster.

  ██  ██  ██ 
██  ██  ██  ██
  ██  ██  ██ 
██  ██  ██  ██
  ██  ██  ██ 









        ███████████
      █████████████████
    ███████████████████████
  ███████████████████████████        ██████
  ████████████████████████████
   ████████████████████        ████████████
      ▀█▀              ▀█▀        ██ ████████████████
    ████████████████████████████████
██████████████████
   ██                                ███████████████████
  ██  ██████████████████████████████████████████████████
     ███████████████████████████████████████████████████
      ███████████████████████████████████████████████████
      ███████████████████████████████████████████████████
       ██████████████████████████████████████████████████
       █████████████████████████████████████████████████
             ██████                          ██████
              ▀██▀                            ▀██▀
  ██  ██  ██ 
██  ██  ██  ██
  ██  ██  ██ 
██  ██  ██  ██
  ██  ██  ██ 

.

dragon2nd
Member
**
Offline Offline

Activity: 94


View Profile
May 21, 2013, 03:27:38 AM
 #224

Dev was killed in the battle  Grin, unofficial should be the WindMaster.
Nice~
microxp
Newbie
*
Offline Offline

Activity: 24


View Profile
May 21, 2013, 03:49:40 AM
 #225

So the unofficial client has became the official client?
cryptrol
Hero Member
*****
Offline Offline

Activity: 637


View Profile
May 21, 2013, 05:56:56 AM
 #226

So the unofficial client has became the official client?
There has been no word from the original developer since the release so it is "officially" dead.
However in a P2P currency model, "official" development could be taken over whenever there is enough consensus.
And with consensus I mean that people installs and supports the new "unofficial" client.
CryptoMaster
Jr. Member
*
Offline Offline

Activity: 41


View Profile
May 21, 2013, 08:18:35 AM
 #227

This last N increase has hit my CPU mining hash rate hard, around 42%. It would be interesting to see how it hit GPU mining to see if the algorithm is going in the right direction.

I'm a bit concerned that N might be getting too big even for CPUs though. My single core EC2 micro-instance was capable of mining (at a slow rate) before the N increase, but now it's pretty much unable. Wondering what the rest of N increases might cause, perhaps the pools need to start adding variable difficulty to cater for slower CPUs or the next N increase might kill a good amount of lower-end ones.

YAC: Y6XC4y9eStUYhm2hApd2txE17o99cJhK1G
feeling2011
Newbie
*
Offline Offline

Activity: 22


View Profile
May 21, 2013, 08:44:39 AM
 #228

This last N increase has hit my CPU mining hash rate hard, around 42%. It would be interesting to see how it hit GPU mining to see if the algorithm is going in the right direction.

I'm a bit concerned that N might be getting too big even for CPUs though. My single core EC2 micro-instance was capable of mining (at a slow rate) before the N increase, but now it's pretty much unable. Wondering what the rest of N increases might cause, perhaps the pools need to start adding variable difficulty to cater for slower CPUs or the next N increase might kill a good amount of lower-end ones.


It seems that mining has no profit with the current YaCoin price.
cryptrol
Hero Member
*****
Offline Offline

Activity: 637


View Profile
May 21, 2013, 08:48:20 AM
 #229

This last N increase has hit my CPU mining hash rate hard, around 42%. It would be interesting to see how it hit GPU mining to see if the algorithm is going in the right direction.

+1
sumantso
Legendary
*
Offline Offline

Activity: 1050



View Profile
May 21, 2013, 09:45:33 AM
 #230

Opened the wallet and it says 'Checkpoint too old......'. I will just ignore it for now? On windows 32 bit.

WindMaster
Sr. Member
****
Offline Offline

Activity: 347


View Profile
May 21, 2013, 11:07:36 AM
 #231

This last N increase has hit my CPU mining hash rate hard, around 42%. It would be interesting to see how it hit GPU mining to see if the algorithm is going in the right direction.

Fortunately, difficulty will drop accordingly over time.  It's too bad it doesn't rise or fall with a larger increment (faster rate) per block though.  It's just a bit of a waiting game at this point for difficulty to become more reasonable.  It's dropping quickly though, I see it's down to about 4.4 now.


I'm a bit concerned that N might be getting too big even for CPUs though. My single core EC2 micro-instance was capable of mining (at a slow rate) before the N increase, but now it's pretty much unable. Wondering what the rest of N increases might cause, perhaps the pools need to start adding variable difficulty to cater for slower CPUs or the next N increase might kill a good amount of lower-end ones.

I think at a minimum, pool operators need to stay on top of Nfactor++ events and adjust work size / difficulty to keep things working smoothly and keep the average time to solve a share below the average time between blocks.  Otherwise everyone solo mining (like me) actually beat out pools with poorly adjusted work size.  I still leave a handful of dual Xeon servers mining for testing purposes and their block solving rate still seems to be tracking inversely proportional with hash rate and difficulty.  At this point, N is still way lower than Litecoin always had.

An Amazon micro instance mining on a poorly adjusted pool would indeed be a losing battle at this point, I'd think.  That's basically just a small shared fraction of a single Xeon core!
WindMaster
Sr. Member
****
Offline Offline

Activity: 347


View Profile
May 21, 2013, 11:11:57 AM
 #232

Opened the wallet and it says 'Checkpoint too old......'. I will just ignore it for now? On windows 32 bit.

For Win32, just ignore it.  The warning is harmless, an artifact left over from the original developer who should've at least adjusted the time before the warning appears to a more reasonable timeframe than 10 days after the release (or more accurately, 10 days after the last checkpoint, which he added just after the coin was released).
eule
Hero Member
*****
Offline Offline

Activity: 672


View Profile
May 21, 2013, 11:58:57 AM
 #233

Someone with a GPU farm and a GPU miner could easily 51%-attack the coin right now, right?
Should be top priority to get a GPU miner for the masses, even if it's unoptimized. Maybe everyone of us should donate to the bounty or we should do some effort to get an open source miner.
0.02€
Sahtor
Member
**
Offline Offline

Activity: 112


View Profile WWW
May 21, 2013, 12:10:54 PM
 #234

N rising is not a problem if we get back to CPU server/laptop based mining. The problem is if GPU or AWS farms raised the difficulty too high to not readjust back to lower levels before even speculated future profitability drops and the mining freezes.

Basicly it doesnt matter which hardware works best but we can't have sudden volatility in difficulty or the currency dies.
WindMaster
Sr. Member
****
Offline Offline

Activity: 347


View Profile
May 21, 2013, 07:56:03 PM
 #235

Changes committed to my GitHub repository:

 - Fix my previously added feature that reports N and Nfactor in the getmininginfo command.  It was only reporting what N and Nfactor were when yacoind was last started, not what it is at the immediate moment.  Duh, fixed.  Smiley

 - Added getnetworkhashps command to show estimated network hash rate.  This implementation was mostly lifted from Litecoin, still need to verify that it makes sense and operates correctly for YACoin.

 - Added network hash rate and the PoW block reward of the highest block on the blockchain to the info reported by the getmininginfo command:

Quote
yacoin@blah:~/wm/yacoin/src$ ~/yacoind getmininginfo
{
    "blocks" : 67663,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 4.10475631,
    "errors" : "",
    "generate" : false,
    "genproclimit" : 8,
    "hashespersec" : 0,
    "networkhashps" : 88885983,
    "pooledtx" : 0,
    "testnet" : false,
    "Nfactor" : 7,
    "N" : 256,
    "powreward" : 19.75000000
}

Note that this is reporting what the block reward was for the last block on the blockchain, not necessarily what the block reward is going to be for the next mined block.  So use this as an estimate of approximately what the current block reward is, knowing that the actual reward of the next mined block may/will differ slightly.
cryptohunter
Legendary
*
Offline Offline

Activity: 1624



View Profile
May 21, 2013, 08:11:50 PM
 #236

Opened the wallet and it says 'Checkpoint too old......'. I will just ignore it for now? On windows 32 bit.

For Win32, just ignore it.  The warning is harmless, an artifact left over from the original developer who should've at least adjusted the time before the warning appears to a more reasonable timeframe than 10 days after the release (or more accurately, 10 days after the last checkpoint, which he added just after the coin was released).


Im getting this warning too?  checkpoint too old? on win7 64bit? will the wallet still be able to send and receive coins? thanks

              ▄████▄
           ▄██████████▄
        ▄██████▀  ▀██████▄
    ▄██████▀        ▀██████▄
  ▄██████▀              ▀██████▄
██████▀                    ▀██████
███▀          ▄████▄          ▀███
███        ▄██████████▄        ███
███      ████████████████      ███
███      ████████████████      ███
███      ████████████████      ███
███      ████████████████      ███
███        ▀██████████▀        ███
███           ▀████▀          ▄███
███                        ▄██████
  ▀      ▄              ▄██████▀
         ███▄        ▄██████▀
         ██████▄  ▄██████▀
           ▀██████████▀
              ▀████▀

     ▄███▀ ▄█▀
 ▄███▀ ▄█▀
███▀ ▄█▀
███ █▀
███ █
███ █
███ █
███ █
███ █
███ █▄
███▄ ▀█▄
 ▀███▄ ▀█▄
   ▀███▄ ▀█▄
The Future of Insurance for Unbanked and Cryptoassets
⬢ Decentralized Insurance for emerging markets ⬢
▀█▄ ▀███▄
  ▀█▄ ▀███▄
    ▀█▄ ▀███
      ▀█ ███
       █ ███
       █ ███
       █ ███
       █ ███
       █ ███
      ▄█ ███
    ▄█▀ ▄███
  ▄█▀ ▄███▀
▄█▀ ▄███
Twitter
Reddit
Telegram
Medium
WindMaster
Sr. Member
****
Offline Offline

Activity: 347


View Profile
May 21, 2013, 08:19:08 PM
 #237

Opened the wallet and it says 'Checkpoint too old......'. I will just ignore it for now? On windows 32 bit.

For Win32, just ignore it.  The warning is harmless, an artifact left over from the original developer who should've at least adjusted the time before the warning appears to a more reasonable timeframe than 10 days after the release (or more accurately, 10 days after the last checkpoint, which he added just after the coin was released).


Im getting this warning too?  checkpoint too old? on win7 64bit? will the wallet still be able to send and receive coins? thanks

The warning is harmless.  But for Win 64-bit, you have the option of using an interim Windows 64-bit binary that hanzac compiled of my version of the client (which doesn't show that warning) and provided a link to it a page back in this thread.  All the usual warnings about running third-party binaries apply of course.
cryptohunter
Legendary
*
Offline Offline

Activity: 1624



View Profile
May 21, 2013, 08:21:16 PM
 #238

Opened the wallet and it says 'Checkpoint too old......'. I will just ignore it for now? On windows 32 bit.

For Win32, just ignore it.  The warning is harmless, an artifact left over from the original developer who should've at least adjusted the time before the warning appears to a more reasonable timeframe than 10 days after the release (or more accurately, 10 days after the last checkpoint, which he added just after the coin was released).


Im getting this warning too?  checkpoint too old? on win7 64bit? will the wallet still be able to send and receive coins? thanks

The warning is harmless.  But for Win 64-bit, you have the option of using an interim Windows 64-bit binary that hanzac compiled of my version of the client (which doesn't show that warning) and provided a link to it a page back in this thread.  All the usual warnings about running third-party binaries apply of course.

Thanks for quick reply Smiley very helpful.

              ▄████▄
           ▄██████████▄
        ▄██████▀  ▀██████▄
    ▄██████▀        ▀██████▄
  ▄██████▀              ▀██████▄
██████▀                    ▀██████
███▀          ▄████▄          ▀███
███        ▄██████████▄        ███
███      ████████████████      ███
███      ████████████████      ███
███      ████████████████      ███
███      ████████████████      ███
███        ▀██████████▀        ███
███           ▀████▀          ▄███
███                        ▄██████
  ▀      ▄              ▄██████▀
         ███▄        ▄██████▀
         ██████▄  ▄██████▀
           ▀██████████▀
              ▀████▀

     ▄███▀ ▄█▀
 ▄███▀ ▄█▀
███▀ ▄█▀
███ █▀
███ █
███ █
███ █
███ █
███ █
███ █▄
███▄ ▀█▄
 ▀███▄ ▀█▄
   ▀███▄ ▀█▄
The Future of Insurance for Unbanked and Cryptoassets
⬢ Decentralized Insurance for emerging markets ⬢
▀█▄ ▀███▄
  ▀█▄ ▀███▄
    ▀█▄ ▀███
      ▀█ ███
       █ ███
       █ ███
       █ ███
       █ ███
       █ ███
      ▄█ ███
    ▄█▀ ▄███
  ▄█▀ ▄███▀
▄█▀ ▄███
Twitter
Reddit
Telegram
Medium
ginjou
Jr. Member
*
Offline Offline

Activity: 42


Hey :)


View Profile
May 21, 2013, 09:24:20 PM
 #239

As it seems like pocopoco was only a multi account and that he won't show his face again, maybe you windmaster, should post your thread and the news about this fork on the official thread and ask a moderator to get the control of the first post of the official thread, don't you think?
This way, it will become official and the monney can regain a little bit of its previous fame Smiley

Because the way it is now, the official thread seems dead and the warning on the official windows wallet looks frightening for the noobs, so it doesn't look good for the reputation of the monney :/

I'm suggesting the idea because i beleave in this monney, but my skills in programming don't allow me to help in a better way Sad

PS: sorry for the not so fluent english Sad

Bitcoin: 1E1Z2qJGW7uuJ2r7rW84fSAuXL8JmgiL7h Litecoin: LgAPfG4a9YKm7R1ddp1QHZRcYZ7iKXg4vS
Any coin is welcomed Cheesy
sairon
Sr. Member
****
Offline Offline

Activity: 406


One does not simply mine Bitcoins


View Profile
May 21, 2013, 09:39:19 PM
 #240

maybe it would be sufficient to just drop "unofficial client fork" from the topic, it might scare a lot of people Smiley

GPG key ID: 5E4F108A || BTC: 1hoardyponb9AMWhyA28DZb5n5g2bRY8v
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 ... 171 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!