elgreco is correct...

When it is showing the rebuy, it would show another one... 45+5+5, or 45+5(+5).

Otherwise, when it is just 2 numbers, the first one is for the pot, and the second one is for the house.

-- Smoov

being able to buy the button would be nice too.

-- Smoov

Nothing... you can't predict the 'end' of a block in the first place...

When you're mining, you're brute-forcing a hash which solves the block at a certain difficulty. It could take 1 second for you to find a hash that meets the criteria, it could take you months.

You're just trying as many hashes as you can until one of them is good (measured in hashes-per-second, which is how you're judging your speed)

-- Smoov

You are starting more fresh blocks... that's why the fresh longpoll messages to start new, fresh work...

Every block has to build on top of the previous one, so when a block is found elsewhere on the network, and is distributed to the network, everyone mining starts new work for a new block to place on top of it... and when yours gets sent that new block, then your miner is told of the new block's existence, and then your miner discards the rest of the work it was trying to solve the block that was just found, and begins work on the new yet-to-be-found block. This is what the longpoll message is telling you.

Fresh block, fresh work...

-- Smoov

More efficient than not notifying you of a new block, and the new work to go along with it, so you don't waste cycles working on now-invalid work...

and yes, very normal...

-- Smoov

Don't forget win bunnies too.

I don't have enough to join the bounty, but I'd be happy to alpha/beta-test the bunnies during the process.

-- Smoov

There is something to be said for completely independent alt-chains running for experimenting with, without any chance of screwing something up with the bitcoin chain.

Now, if they decide later on (like BBQcoin did) to try listing it on exchanges with all the testing pre-mine intact, we got a different story...

Otherwise, it is harmless...

Get it set up for merge-mining and I'll add it to my mining, help test out new things and stuff, but until then, it isn't worth giving up my real-coin mining.

-- Smoov

Well... a while ago, pyramining briefly switched over to my public node while they were working on some stuff.

I ended up having between 200-400GH/s at the time, and everything seemed to go just fine with my bandwidth, so p2pmining should be ok with the added bandwidth of the ASIC traffic.

If p2pmining would let you use higher diff shares, or maybe they can set up a high-hash node too. They're pretty much doing their own sub-share-chain, so maybe they will do something to accommodate the ASICs.

Not sure if they would tho. It sounded like they came into existence mainly to cater to the smaller miner who needed lower-diff shares.

-- Smoov

ps: Krak is in one of the outlying cities/towns that don't have a lot of infastructure to spread around. Rural-ish kind of area. That's where his main bandwidth bottleneck is. They get priced accordingly. Too much demand, not enough supply. So they get capped more.

For P2Pool, it only matters if you were shooting for a higher diff share to begin with. Then you get a bigger slice of the reward for your higher diff share, but since you'll be finding less of them, it is still supposed to balance out.

Just getting a high diff share alone won't do it.

So, if you were shooting for a share at 702.33721188 or above, and hit a  2267613.78728177 diff share, your share is credited with the ~702 value... but if you have overridden your mining to look for diff 2000.00000000 shares or above instead, and hit that ~2267613 diff share, then your share is credited with the 2000 value.

Keeping track of that 2267613 is just for e-penis credit

-- Smoov

then the sharechain forks, and those who are not on v8.0 and above, get forked off onto their own sharechain, just like the LTC p2pool network did yesterday (or was it the day before?)

-- Smoov

IT'S A PONZI!!!

...

sorry... force of habit...

-- Smoov

Yep... yer fine... this is an official thread for it. The one who started the thread is part of the project.

-- Smoov

We're just giving you the facts without (much) judgement.

With tech projects like these, particularly revolving around crypto, you have to expect a mix of white-/grey-/black-hat programmers.

Value-judgements you can make for yourself, don't need us to do that for ya.

-- Smoov

Yes, you're missing something...

All the program is, is the mining program... there is nothing virus-like about it.

You install it, and point it at your own daemon, or at the pool you're using, to do your mining with.

What the malware peddlers were doing, was using their trojans, to install that program on other people's computers, with their own credentials, in effect, stealing other people's electricity to mine for themselves using the victim's computers.

The mining programs themselves, are not malware. You are not allowing access to your computer through them.

The malware peddlers, were using their own malware, to install the miner programs on other people's computers, turning their computers into miners without their permission. That's all.

The alerts are just false positives by lazy people at the scanner companies who can't be bothered to honestly investigate the miner program. They just find the trojan programs, and flag everything they find inside as a virus, even if it isn't. This isn't anything new, I've had other programs I use end up as collateral damage like that too.

As long as you download your copy of the miner directly from the official source, you're fine.

-- Smoov

As long as you downloaded it through the link at the top of the thread, yer fine...

It has been included with malware so the botnet operator can use other people's computers to mine. That's why cgminer and minerd got tagged by the virus scanners.

It isn't a virus itself, it was just the payload, but the scanner companies don't really care about that.

They aren't as thorough as they used to be. >shrugs<

-- Smoov

or at least not count the ignores of banned people against you...

-- Smoov

Well... the having to re-stretch the new window back to where I want it expanded to again, re-opening the detached chat window, etc...

Just keep the same window I've been playing in, replace the other players in their seats with those from the new table... then I keep my chat and hand history, saves me time so I can stay focused on my game, etc...

Make this behavior optional of course.

It really irritates me when I've just finished getting my windows re-aligned again on the new table, just to get moved again a minute later and have to do it all over again.

Oh... and only move the windows when we click on the top header of the window... can't tell you how many times I tried to quickly drag-select the bet to type in a new amount, and ended up moving the window instead.

-- Smoov

A non-browser, non-flash, non-java, client, would be a big improvement...

The ability to set the view to always put yourself in the bottom seat...

Remembering my window placement...

Reusing the table window in tournaments when I get moved from one table to another...

SCROLL WHEEL BETTING SUPPORT!!!

...

That's enuf to start with...

-- Smoov

Of course!

That is why I'm not suggesting them to be used as a substitute/replacement for p2pmining... just as failover for when p2pmining has its downtime. (and why I mentioned that it isn't the same share list p2pmining uses)

From my own experience, if you're primarily mining a p2pool-like pool, then your failovers work better if they are also p2pool-like.

Whenever I had BTCGuild as my failover for my own p2pool mining, I kept getting issues. Using p2pmining as my failover now works just fine.

Probably due to the rapid share frequency.

-- Smoov

Yeah, give me a few days yet, I'll have something put together.
If any of you need a public p2pool node to add to your failovers and tide you over while p2pmining is down, there is a list in this thread here.

Just use username/password the same way you would with p2pmining, and use the same payout address with all of them if you use multiple ones.

That way, you just pick up where you left off since they all share the share list amongst themselves. (not the same share list p2pmining uses, as they are a custom node )

-- Smoov