[ANN] MMCPool.com - GPU,CPU(yam) - The Awesomest Pool!

[dima1236]

Looks good, any irc channel yet ?

[alachua]

Just jumped on this pool let's see how it runs.

[pinwc4]

Hopefully with all that hash we will see a block soon.  Should average about a block an hour based on the coin calculator.  Is that correct?

Anyone tried the Mac version yet, when I get home I will try it and add a few more clients to the pool. 

[Chronos24]

I will be trying this out later tonight.
Thank you for the pool .

[foolsh]

Just replying to leave a note that libtool is also required for Ubuntu

Nice job on the pool!

[dima1236]

So lets sum some things

1. Big thank you for the pool
2. Network Hashrate ATM = 2^32 * 0.00000949 / 6 = 6793 HPM
3. Pool Hashrate ATM = 1684.64 HPM and growing
4. Pool / Network = ~25%
5. We still ain't finding any blocks
6. Anything wrong ??

[alachua]

we just found one

[isaacgoldbourne]

I think the source to the pool needs to be released. It won't do the coin any favors if this gets to 51% (by the looks of things it will by tomorrow)

[dima1236]

Even if we have 51% on the pool no fork will be initiated if we have strong connection to the main node.

I think the source to the pool needs to be released. It won't do the coin any favors if this gets to 51% (by the looks of things it will by tomorrow)

[isaacgoldbourne]

Even if we have 51% on the pool no fork will be initiated if we have strong connection to the main node.

I think the source to the pool needs to be released. It won't do the coin any favors if this gets to 51% (by the looks of things it will by tomorrow)

I know it won't fork, but it undermines the security of the coin for any one entity to have 51% of the hashing power as they could perform a 51% attack.

I'm not saying they will, but because they have the capability it devalues the coin.

[arcke]

I keep getting this, mining for an hour
 
PROOF OF WORK RESULT: Rejected

On another machine I start the miner

./minerd --url http://work.mmcpool.com/ --user <address> --threads 1

and it says "KIlled" after being. What can be wrong?

[dima1236]

Ypool had 120% network rate on PTS in the early days, and nothing went WRONG

Even if we have 51% on the pool no fork will be initiated if we have strong connection to the main node.

I think the source to the pool needs to be released. It won't do the coin any favors if this gets to 51% (by the looks of things it will by tomorrow)

I know it won't fork, but it undermines the security of the coin for any one entity to have 51% of the hashing power as they could perform a 51% attack.

I'm not saying they will, but because they have the capability it devalues the coin.

[isaacgoldbourne]

I keep getting this, mining for an hour
 
PROOF OF WORK RESULT: Rejected

On another machine I start the miner

./minerd --url http://work.mmcpool.com/ --user <address> --threads 1

and it says "KIlled" after being. What can be wrong?

If its two different machines we can rule out it being them (well, its unlikely).

Whats your network setup?

[dima1236]

new hash rate : 2006.09HPM , keep it going guys , we should be finding 2-3 blocks / hr at least now 

[arcke]

I keep getting this, mining for an hour
 
PROOF OF WORK RESULT: Rejected

On another machine I start the miner

./minerd --url http://work.mmcpool.com/ --user <address> --threads 1

and it says "KIlled" after being. What can be wrong?

If its two different machines we can rule out it being them (well, its unlikely).

Whats your network setup?

The first is behind a firewall at my home only getting rejects.
The second is a cloud vps server (512MB,  1 virtual core)