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

i need you help

this error
2015-07-04 02:13:06 [Pool]   [yacoin] (Thread 1) We thought a block was found but it was rejected by the daemon, share data: {"job":"1","ip":"10.0.22.59","port":3032,"worker":"YKL5qhpF6e9ZW7HWkD7TpVZ1NAYFstpxmH","height":1125098,"blockReward":76320000,"difficulty":1,"shareDiff":"421.15416530","blockDiff":80.983556096,"blockDiffActual":0.001235711,"blockHash":"24fbc4370213e36f251dc2f1535f6eb9b1144c7b07f143be850d7b8ff35d12df"}

mens blosk is FOUND, is on the wallet but not in NOMP for payment
 
I have 4 block in the wallet

waht could be the problem?

You are right about 2 minutes. Perhaps I have got it wrong here:

Another problem would be if rogue PoW miner would combine such PoS blocks with his private chain in order to bring his chaintrust higher (trust value of PoW block following PoS block get's doubled). That would make it possible to mine under lower PoW difficulty and use a lot of small stake PoS blocks to help build up chaintrust against primary chain mined at higher PoW difficulty but containing lower number of PoS blocks.


Perhaps each PoS block in honest branch makes next PoW difficulty higher (by extending to 2 minute block time) and that makes it possible for private solo miner to eventually catch up since he is still mining on 1 minut block time?
Could that be one of main reasons why main chain can't run away easily?

For such errors just grep daemon's debug.log for "ERROR". It seems (15 posts down from the top) meaningful detailed info should be there.

ok thanks

lets see if we can find a block
to make sure i did it roght

That user was ME! And I apparently made a typo in my address. Don't make a type in your address. Now you (we) know what happens. Thanks, NineEleven.

its a fresh wallet its not locked

I am not sure, but perhaps you have your wallet locked?
I believe it needs to be unlocked in order to submit blocks from rpc.

Hello Beave162 & everyone,

To get more people/computers involved in YAC or any crypto-currency, including BTC, one needs to go after the biggest audience.  See http://www.netmarketshare.com/ and in "Market Share Reports" near the top, choose "Operating Systems", then "Desktop Share by Version".

OK, what wins with ~92% of all desktops connected to the internet?  That is what one should target!  That is why I did my videos (https://www.youtube.com/channel/UCytoaHvG3H1y9CnxZS819eQ), showing how easy it is to make a Windows version of YAC, BTC, etc.  Of course the latest version of BTC, roughly versions 9.x, 10.x, 11.x and any other *coin derived from them, now obscure the make file inside autogen machinery,  making it more difficult to tease out the minimum set of files needed to create a *coind.exe &/or *coin-qt.exe

I prefer to work with Bitcoin 0.8.6 and *coins derived from that version or older, since there was much less "confusion" about which version of gcc, which version of Qt, which version of levelDB, which version of OpenSSL (now there's a deep hole!), UPnP, QRencode,... and who knows how many more with the latest versions of Bitcoin?  Boost?, gcc?, Qt?, GMP, secp256k1, etc. etc. etc.

All with no specifications given about which version works, or doesn't, with which older or newer versions?  I tried making this argument on various bitcoin foums, but to no avail   I think there are just too many Linux geeks that are burned out looking at too many text mode screens!  I did that in the 1970s and 1980s in CPM/ZCPM and DOS (LOL).  Don't mind a good .bat file here and there to ease building a Windows gcc daemon or Qt version

Ron

one user try to use the pool
and get this

   [yacoin] (Thread 2) Unauthorized  YL5kf54wPPXKaXd5T18xCaNkyUsS1DgY7z:##### [50.150.44.120]
the other are fine

Did i made some mistake on the config?

another question


[yacoin] (Thread 1) We thought a block was found but it was rejected by the daemon, share data: {"job":"138","ip":"10.0.25.37","port":3032,"worker":"YKL5qhpF6e9ZW7HWkD7TpVZ1NAYFstpxmH","height":1124989,"blockReward":75890000,"difficulty":1,"shareDiff":"3013.13008481","blockDiff":83.74288384,"blockDiffActual":0.001277815,"blockHash":"fb5757497ed4fd380eaa473e65d9bb9c2126bed7035a39b4cade31d893635a59"}


is this normal?

Please try

http://yac.erlog.pt:81/


I think everithing is working

im NOT getting any orphans

And finaling getting my first block matured in the last 2 days

well


i think its fine
and in my solo mining i'm getting block confiermed

maybe the atack as stoped


I wold like to see some hashes on this pooj
to be sure everithing its fine

It is great to see someone step up to the plate and take action to help rather than just complain.  Thanks for your efforts.

Im going to make a quick stop on the pool just to correct a config error

I can see 2 clienets connected

Please if anithyng is not workig let me know
i'm new to this

Regards

anyone want to give a try?


http://yac.erlog.pt:81/

be gentle ok

correct - you cannot set it lower because there are differences in implementation in GPU and CPU miners...

waht are the correct values for this

 "diff": 1,
            "varDiff": {
                "minDiff": 1,
                "maxDiff": 32,
                "targetTime": 15,
                "retargetTime": 90,
                "variancePercent": 30
            }