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

that is a nice tip, will certainly do this from now on=)

On the other hand, changing N=32 to N=64 in modified cgminer GPU kernels on May 14 won't be particularly challenging to anyone that already made the changes the first time, and then they'll be good again until May 17 when N=128.  About 5 minutes or less of work, from my own poke at it?  Agree, Taco?

Take a look at GRouPcoin and DeVCoin and whichever other coins use the same difficulty adjustment and timetravel exploit fix that they do. So far it seems to have been working.

It is one of the couple or more of fixes that people came up with back when namecoin demonstrated that the problem existed.

-MarkM-

I'd point out that Amazon's AWS / EC2 resources are available to (almost) anyone.  You can even provision up to 100 spot instances (bids for Amazon's unused processing power, basically) in each of their data centers, and there are 8 data centers to choose from, so it's readily possible for anyone to provision up to 800 servers at a moment's notice if they have a decent amount of Linux skill.  Small exception here though, yesterday I found that I maxed out all of Amazon's available servers in the Sao Paulo, Brazil data center before reaching 100, so I was only about to provision 760 servers.  It all comes down to risk vs potential rewards, as these resources do cost real $.  Thus is the joy of gambling..

I got in 8 hours after the coin was released due to the OP's missed release deadline (dammit, OP!).  Yet I still considered it a fair fight even 8 hours in, and I amassed quite a large quantity of YAC (well into the 5 figures).  You can bet I mourn the amount of YAC I could've mined if I were in the right place at the right time to unleash that amount of processing power right at release though..

Nonetheless, massive amounts of computing power are readily available, and available to just about anyone that knows where to look for it.  And Amazon certainly hasn't been hiding in a hole, they're a pretty visible and popular source of rented computing power.

Just hold for the next N++ event, difficulty will drop and reward will raise. You'll get to "pre-mine" it again.

Every time you set up a GPU rig, also set up, with "nice", a minerd using its spare cycles on some under the radar coin or even throw one core at each of several, and forget about them.

Some day one pops into the limelight again, like BBQ recently did, and checking your wallet you find holy cow those things add up to more money than all the coins all the GPUs raked in combined.

-MarkM-

Yeah, I agree with that but then we come again to "not releasing it for altruistic purposes". They're doing it to bank and will do all the time. Cryptocurrency is all about money now, no matter what coin it is, it's like a gold rush - greed, greed everywhere.

I've learned to live with it though and not to be too bothered with it. We're all here for money and we all can't make it at same level. Who's smarter, more creative, have more resources will always make more - it's virtual copy of real world and I don't intend to break my head about it.

Ive been busy on the scrypt mining front with my GPUs. its a fun gamble where to place the power. recently had a good payday after early mining feathercoin while difficulty was under 10 and hype hadnt started=)
So far ive used around 5200USD in equipment cost. and it has all paid for itself in the two months ive been mining diffent coins=).
So everything from now is gravy=), hope this currency will add some value and not be a power waste.

People being ready is not the problem. Deliberately not setting the dififculty high enough to start at the target time between blocks, or even longer between blocks if all those ready miners fail to actually mine the coin, is the problem.

It is well known how huge an amount of hashing power jumps on new chains, so new chains should by now have known how much higher starting difficulty for a coin needs to be in order for the first blocks to be created at the target speed or slower.

-MarkM-

It is pre-coded into the code that a huge number of blocks will be made so fast that the orphan rate will tend to be the main limit on how fast it can be, because any faster it'd be slower due to the orphans.

The starting difficulty setting is the indicator, they know damn well that setting it insanely low will cause a few minutes to an hour or few of insanely fast raking in of blocks, before the target difficulty that the initial difficulty should have been set to achieve from the outset can be reached.

Litecoin seems to have started this scam, by deliberately setting litecoin's start difficulty insanely low.

-MarkM-

I hope nobody expected that people are releasing coins for altruistic purposes, of course they're ready to mine  

YAC OP did it on the most unique way so far though so hats of boss, as well as those who did it with amazon and stuff  

Absolutely no bad blood here, I can't see a difference between that and gpu farms for others as well as asics ones that are raping bitcoins. Who knows, knows (or has enough money) - who doesn't - buys as I do  

Unfortunately, technology and amount of cheap computing power won't help mining of any coin to be a fair game for all. Those times are finished.

The devs let you in on the pre-mine by posting to the niche forum you lurk in waiting for pre-mines to participate in.

So all you pre-miners who sit here pre-mining a new coin every day love to pretend you are not pre-mining but to the whole rest of the world it is blatantly obvious that you are.

It is made glaringly obvious by the deliberately insanely low starting difficulty, for example, and in some coins is made even more obvious by the bonus payouts awarded in the blocks they expect the low difficulty to be able to get mined fast by pre-miners during the first few minutes of pre-mining.

-MarkM-

i'd call it being-at-the-right-place-at-the-right-time-mining

ok im now the built-in miner gets about 280-300khash/s on a 3,4Ghz 2500K, but sometimes dips intro 140-220.

compiling the cpu miners with the same CFLAGS gets a constant 230khash/s

Agree.  Rather than pre-mining, perhaps ready-mining?

libdb++-dev

Additionally, running excessive numbers of threads per CPU core runs the risk of less data fitting in the on-die L1/L2 caches, depending on the size of the caches and the working set (data that the code is manipulating).  The result will be a falloff in overall hash rate as the number of threads per CPU core becomes excessive.

how is it a pre mine if everyone is mining? sure, the blocks are found faster than the target time, but that's on any coin. even bitcoins are found a bit faster than the real target. thus the difficulty increases to try and balance the speeds. the rise of difficulty has also to be set in such a way that it doesn't rise too fast. as that would make the time more that the target time. a pre mine is when the dev mines coins before he releases the coin to the masses. In this case, it hasn't been so.

I don't think there has ever been a time when there was not at least one, and usually quite a few, coins you could rake in nicely with CPUs.

BBQcoin for example you had something like a year, maybe more, to rake in oodles of coins with your CPUs before the GPU people came back to it, it went on exchanges, and the CPU miners are now taking their exceedingly handsome pay for those long long long months of CPU mining it.

Meanwhile several other chains are still being lucratively mined by CPUs, some of the CPU miners hoping the GPUs come back soon drive the difficulty too high for CPUs and lobby to have the coin put on exchanges and soe others of the CPU miners hoping that will not happen for a few more months so they can build larger hoards of coins before it happens.

So if you have been letting your CPUs sit idle, that is not for lack of chains to mine, just maybe lack of foresight or, like all the people who missed out on Bitcoin's CPU-mining era, some idea that cryptocoins are not worth collecting.

-MarkM-

I keep getting this when I enter the command line above


Is there a way around it. I want to get this working... but i'm new to linux