Topic: [ANN][YAC] yacoin: yet another altcoin. START is now. - page 36. (Read 346684 times)

gave up trying to get everything working on ubuntu.
Now I'm hoping someone can come up with a way to mine successfully on windows

I saw that the OP got edited with a new binary.

Testing it right now but i'm not having any luck for the last 3 hours

You wait for coins to be 30 days old, then PoS rewards will appear in the wallet. You don't need to do anything special unless the wallet is encrypted. The info in NovaCoin and PPCoin should apply for that.

I have to move some of the park due to limitation in break-circuit size.
Will the latency of using wireless or ethernet-over-powercircuit system make an inpact on the orphant rate?

Out of the house is fiber

Speaking of compatibility; have you been able to compile the QT version of the linux client? No luck with Qt5 here. I think someone should try to port the yacoin client from Qt4 to 5...

i had zero problems.... ubuntu repos are playing well with any wallet i tried compiling so far....

It is up to date ones that are the problem. Many coins assume functions have a number of arguments that is not the same as the number of arguments up to date versions of the library use, so it is precisely the fact that the machine has an up to date version installed that causes the compile problem of those older-code coins.

-MarkM-

From the little I have seen so far about TRC's "solution" it sounded like it planned to try to refer to clocks / timeservers, which is a huge can of worms that Bitcoin goes to a whole lot of trouble to work-around.

I0coin still dies regularly trying to do a DNS lookup to find an IP of a network time server, so the idea of trying to find out the time does not sound like a good idea at all.

The solutions other chains have been using seem to work well, so why go out of one's way to add another point of failure by imagining a timeserver might exist somewhere and that one might be able to find an IP number that it can be contacted at? Especially after I0Coin seems to have already demonstrated that that can be a cause of crashing of the daemon?

I only know though that the fix DVC and GRP and I don't recall which other chains used has seemed to actually work in the field, whatever alternative other chains used I am not sure has even yet been tested, as in, actually been through a major chain-hopping and shown that it is indeed resilient in recovering from hopping.

So I do hope whatever TRC did end up doing isn't opening the whole can of worms of trying to figure out what the actual clock/calendar time out in the world might be because so much work already went into making that not be something that nodes need to rely upon the accuracy of.

Basically the timestamps on blocks can be way out, but overall between the lot of them do give at least a vague general idea of approximately how much time might have passed in the real world, and depending on knowing more than what can be gleaned from those timestamps is a bit of a hairy mess, best avoided.

-MarkM-

Anyone figured out how to PoS mine with YaCoin yet?

oh i see but ubuntu repos are uptodate 

I encountered some problemes on Arch Linux regarding upnp though; the package in the repo hasn't been updated since forever and was causing trouble during the compiling process. In this case the "USE_UPNP=" Flag came in handy 

got it works.. thanks

can someone tell me howto build the cpuminer in ubuntu with the scrypt-jane option ??

It's crazy to think the reward for the first block I mined was 54.26 YAC and the last block I just mined is only 28.86 YAC. I wonder what it will be like tomorrow 

+1

ok... but that doesn't give any advantage disabling it. you might as well just keep it enabled. you never know what the future holds

any news of a gpu miner capable of mining YAC? or a windows cpu miner?

You don't have to use the password it randomly generated, it's just a suggestion if you have no other preference.  You can make the RPC password anything you want.  But otherwise, the reason you're getting this message at all is that you either don't have rpcpassword= set in your yacoin.conf file, or your yacoin.conf file is actually in the wrong place (i.e. not located at /home/you/.yacoin/yacoin.conf in your case).

I have told it to everybody yesterday!!!!  

LOL!  Though incase it was a serious question, many mining operations aren't sitting behind a DSL or cable modem (or other NAT gateway) at someone's house and have no use or desire for uPnP.